How to Write Daily Reports for Cleaning and Building Maintenance: Keeping Them Separate from Work Reports and Inspection Records, and Turning What You Notice on Site into Tomorrow's Next Step

Daily reports in cleaning and building maintenance tend to become a list of the places covered and the tasks completed that day.

For example: 'routine cleaning done floor by floor from the third floor, no particular problems'.

A record of the work matters, but on its own it does not capture where things took longer and what went well, or what you will try changing in tomorrow's work.

On top of that, cleaning and building maintenance sites already have records that contracts, the company's rules and set procedures require.

They include work reports, cleaning checklists, equipment inspection records and patrol records.

So the daily report easily looks like a task of writing the same things once more.

If it is written in a hurry while moving between sites or at the end of the work and nobody who reads it replies, writers gradually settle for a single line such as 'nothing in particular'.

In PDCA terms, the report stops at Do, the record of what happened, while Check and Act fall away.

This article looks at how to reposition the daily report from a copy of established records to a tool.

That tool is for looking back on what you noticed on site that day and turning it into the next day's work and into learning for the team.

The daily report here does not replace work reports or inspection records; it is a short reflection for passing observations from one staff member to another.

Please read it as a discussion about the system, not about blaming anyone.

A daily report for cleaning or building maintenance staff is easier to keep up when the fields are narrowed to roughly the following.

(1) Today's aim, meaning in which area or task you will try which route or way of organising the work.

(2) How it actually went, meaning what worked and what did not go as you had hoped.

(3) What you noticed on site, such as changes in areas that get dirty easily or small irregularities in equipment.

Other examples are comments from customers or people using the building, or a look back at how you organised your own work.

(4) What you want to share with the team, such as things to pass to staff at the same site or to the next person working there.

(5) What is troubling you and what you want to consult whom about. (6) Your first move tomorrow.

The key is not to repeat in the daily report what belongs in work reports or checklists.

Instead, narrow it to reflection on your own work, things to share with the team and consultations.

Consider observations such as 'with several rainy days in a row, the floor around the entrance has been getting dirtier'.

Others are 'the kitchenette sink seems to drain more slowly than last week' or 'a person using the building asked what time the toilet paper is restocked'.

Conversely, these rarely fit the items in established records and can only be picked up in the daily report.

It also helps to make it a rule not to write the names of tenants or customers in the daily report.

Describe the place and the facts instead, such as 'around the entrance' or 'the third-floor kitchenette', so that personal information stays out of it.

Too many fields stretch the writing time and end up with more blanks. Start with around five and adjust them while listening to the staff.

The norolu PDCA format has five parts: P (today's aim), D (what you actually did), C (what you noticed), A (what you will do next) and the next day's P.

Here is an example from a staff member in charge of routine cleaning in an office building (the content and figures are a fictional example for illustration).

P: 'Finish the area around the ground-floor entrance and in front of the lifts first, before the working day starts.'

D: 'Because of the rain, the entrance floor was dirtier than usual and wiping it took longer.

I only moved on to the area in front of the lifts 15 minutes before the working day started, so I ended up working in the path of people arriving at work.'

C: 'I knew that the entrance floor takes more time on rainy days, but I still went round in the same order as on dry days.

Depending on how the mat was placed, the dirt had spread further inside.'

A: 'Rain is forecast again tomorrow, so finish the area in front of the lifts first and then do the entrance.

Consult the site supervisor about how the mats are placed.'

Next day's P: 'Follow the rainy-day order and finish the work along the walkways before the working day starts.'

The trick to linking to the next day's P is to write A as one concrete thing to do next.

Rather than 'work efficiently', write 'finish the area in front of the lifts first', and the next day's report can check whether it was done.

The record of where and when you worked belongs in the work report or checklist; the daily report holds the ideas you tried in organising your own work.

One to three lines per field is enough.

The daily report can also be a place for newly joined staff and part-time staff who work short hours.

The same goes for staff who move between several buildings from day to day.

They can raise uncertainties and worries early instead of carrying them alone (a fictional example for illustration).

P: 'On the floor I have just been assigned to, go round in the set order and finish on time.'

D: 'A meeting room was in use and I could not go in, so I changed the order, and as a result I started checking the toilets later than planned.

I did not know which area I could do first instead, and I stopped partway.'

C: 'I did not yet know this site's rules on how to go round when a room is in use.

The site supervisor was at another building, so I could not ask on the spot.'

A: 'Tomorrow morning, before starting work, phone the site supervisor to confirm how to go round when a room is in use.'

Writing about uncertainties is not about reporting what you cannot do; it is about letting the team lend a hand sooner.

The site supervisor or more experienced colleagues first acknowledge in a sentence that the staff member wrote it down.

They then reply with just one useful clue. When this is done, staff feel safe writing about where they are unsure.

Keep the fields few so that people can write even on days with short hours. Avoid replies that blame people for writing about their stumbles.

Cleaning and building maintenance sites already have established records.

They include work reports, cleaning checklists, equipment inspection records and daily inspection sheets.

They also include patrol records, records of key handovers, handover notes and staff attendance records.

These are kept in their own places, based on contracts with building management companies and customers, laws, the company's rules and set procedures.

Which records must be kept, with which items and for how long, differs depending on the building, the terms of the contract and the type of work.

The daily report does not replace them.

Assume that simply writing 'equipment check, no problems' in a daily report does not make it an official inspection record. The basic split is this.

The facts of the work and the inspections go into the established records, kept in line with the set procedures.

The daily report, meanwhile, holds reflection on the team's own work, observations and next steps.

When a daily report mentions those records, do not repeat the details; a short note such as 'entered in the inspection record' or 'reported in the work report' is enough.

Drawing this line at the start reduces the burden of writing the same thing twice and keeps the daily report as a place for reflection rather than a duplicate of the records.

For which records to keep where, follow the contract, the company's rules and the judgment of the site supervisor or the person in charge at the company.

Notes such as 'something like a water stain was visible on the kitchenette ceiling' sometimes appear in the C field.

So do notes such as 'the floor was wet and a person using the building nearly slipped' or 'I almost lost my balance on a stepladder during work'.

Do not let them end in the daily report; connect them to the procedures the company has set.

You may notice something different from usual, such as a water leak, an unusual noise or smell, or a fault in equipment.

There may also have been an accident, an injury or a near miss that could have led to an injury.

When either happens, do not wait until you write the daily report and do not carry it alone.

Tell the site supervisor or the person in charge at the company straight away and respond in line with the company's procedures.

Do not touch the equipment or try to find the cause on your own judgment; for how to respond, follow the company's procedures and the judgment of the person in charge.

Perhaps something about the handling of chemicals such as detergents or of equipment concerns you.

Even if it does, do not spread your own way of doing things through the daily report.

Follow the company's procedures and the manufacturer's labelling, and check with the person in charge when unsure.

In addition, information that identifies individuals and information related to the safety of the building should be kept out of the daily report.

The first includes the names, contact details and room numbers of residents, tenants or customers.

The second includes where keys are kept, access codes, security hours, patrol routes and how to enter the building.

These should be handled in line with the established records and the company's rules.

When you receive a request or complaint from a customer or a person using the building, likewise do not settle it within the daily report; tell the person in charge using the set method.

It is important not to settle the cause or responsibility within the daily report, and not to write in a way that blames a particular person.

The daily report is the point where something is noticed; it is not the response itself.

A short line such as 'reported to the site supervisor' lets the reader confirm that it reached the formal response.

Site supervisors and area managers read staff reports every day. Trying to read every one in depth is not sustainable.

So start with A (what you will do next). Then check C (what you noticed) and the consultation field for anything you should help with.

Also check for anything to decide about the next day's staffing or the order of work.

And check for anything that should be passed on to customers or to the building management company.

Comments are easier to keep up when they acknowledge one fact and add a single question or next step.

For example: 'Thanks for noticing how the dirt builds up on rainy days.

I'll talk to the person in charge of the building about how the mats are placed tomorrow.'

At some sites, staff are spread across several buildings, work at different times and are rarely all together.

There, the daily report also becomes a place to hand observations across buildings and shifts.

Figures such as the time taken for the work and the number of places covered matter.

But consider treating the daily report as a tool for catching observations on site early.

Doing so, rather than for comparing staff by how fast they work or scoring each person's work, is the precondition for people writing honestly.

Once a week, lay out the week's reports and look back over them. Discussing them in the KPT format (Keep, Problem, Try) lets you check two things.

One is whether delays or uncertainties keep recurring in the same place or the same task.

Another is how the routes and ways of organising the work you tried worked out.

That turns one person's observation into a review of the work procedures and into improvements to how the whole team works.

With the weekly summary in norolu PDCA, you can also look back over a week of observations at once.

Even if a report is missing on some day, start by asking why rather than blaming, and review whether the fields and the writing time fit the flow of work on site.

In norolu PDCA, AI is an assistant that helps with drafting reports, asking questions to prompt reflection, and writing weekly summaries.

That line does not change in cleaning and building maintenance.

AI can tidy up a staff member's short notes or pick out areas that get dirty easily and consultations that recur across a week of reports.

But decisions such as how to change the work procedures or staffing are made by the site supervisor or the person in charge at the company.

So are decisions on how to deal with equipment irregularities or accidents, and what to tell customers or the building management company.

It is reassuring to keep the names and contact details of tenants and customers out of the daily report.

The same goes for information related to building keys and security.

As for norolu PDCA, it is designed so that daily report data is recorded in the Google Drive (spreadsheet) of the company using it.

That is, the data goes to your own organisation, following a minimal data retention approach that does not accumulate information on our side.

Keep it separate from the established records, use a short format, and keep writing reports that get a reply.

We believe that steady habit is the foundation for turning small daily observations on site into the next day's next step and into better ways of working as a team.