Recurring Findings and Root Cause Analysis in Cleaning

The same washroom fails in March, May and July. Each time it is cleaned, re-inspected and closed. Each time it comes back. After the third cycle, most companies hold the same conversation with the cleaner — which is sometimes the right answer, and more often just the cheapest available explanation.

Key takeaways

• One failure is an event. The same failure in the same place three times is a process finding, and it should leave the deficiency log.
• Work the causes in order: scope, access, time, equipment, then people. People is genuinely the answer less often than it feels.
• The location of a repeat tells you which cause to test. Repeats across many sites point at the standard and the training; repeats in one spot point at the building.
• A root cause you cannot verify is a guess. Every conclusion needs a test you can run in one shift.
• Some repeats are not cleaning failures at all — damaged fixtures, ventilation, drainage, pest entry — and belong on the client's list.
• Record the cause against the finding. Without it, next year's review starts from zero.

What a recurring finding actually signals

A single failed item tells you the work did not meet the standard that day. A repeat tells you the system that should have prevented it is not working. Mixing those two responses is why so many inspection programmes generate activity without improvement: rows of deficiencies that reopen in the same location are not supervision to be applied harder, they are evidence that something upstream of the cleaner is wrong.

The trigger most contractors settle on: the same item failing the same area on three consecutive rounds. Not three times ever, which catches seasonal variation, but three consecutive rounds, which removes coincidence. Some add a second trigger — any second failure of a critical item — because hygiene and safety items do not deserve a three-strike allowance.

The five-cause diagnostic

Run the causes in a fixed order, because the order stops the conversation defaulting to the person holding the mop.

Two rules make this work in practice. Stop at the first confirmed cause — if access was the problem, fixing access is the corrective action, and re-training on a task the cleaner could not physically reach teaches nothing. And write the answer down against the finding, because the pattern across six months is where the useful information lives.

Scope: the task nobody owns

Scope problems look identical to performance problems, and they are the most common cause of long-running repeats.

Watch for a finding that no one can point to a signed line for. A specification that says "washrooms cleaned daily" may not commit anyone to the underside of the hand dryer, the tops of the partition panels or the floor behind the toilet. The inspector scores against what they can see; the cleaner works against what they were told, and the finding recurs indefinitely.

The fixes are boring and effective: write the missing line into the specification at the frequency the task needs, and price it. If the client will not fund the task, remove it from the inspection criteria in writing so it stops being scored as a failure. What you cannot keep doing is scoring work nobody is paying for — that arithmetic is covered in cleaning specification writing.

Access: the hidden cause of most silent failures

Access failures rarely announce themselves. Nobody records "could not clean the east stairwell because the door was locked".

Look for these signatures:

• Findings clustered in one wing, one floor or one tenant's space
• Items failing on the same weekday, which usually means a room is booked that day
• Areas that pass when a supervisor attends and fail when they do not
• Consumables empty in an area that is otherwise clean

The fix is a written access schedule: every area, the key, code or escort it needs, who holds it, and the hours it is available. Review it after every tenancy change, because access arrangements decay faster than contracts do.

Do not improvise around access. Working unescorted in a restricted area, or using a code borrowed from a member of staff, is a safety and liability question rather than a scheduling one — critical. Report the blocked access in writing and record that the area was not serviced.

Time: the cause that hides behind effort

If the schedule contains less time than the standard requires, the result is predictable: the visible tasks get done, the low-visibility tasks lose their minutes, and the same items fail every month. The cleaner works hard and the outcome is fixed before the shift starts. Test the arithmetic rather than the person:

1. List every task in the area with its frequency.
2. Apply a realistic task time to each, including setup, chemical mixing, equipment changes and travel.
3. Add the unavoidable overhead: signing in, collecting keys, changing machine water, waste handling.
4. Compare the total with the hours actually funded for that area.

Most repeat-failure buildings fail this test in the second or third line. When they do, the conversation is with the client about scope or frequency, not with the team about pace. The tools for the arithmetic are set out in cleaning crew size and productivity planning.

Equipment and chemistry

Equipment causes produce a distinctive pattern: consistent effort, poor result. The floor is mopped and still looks dull. The glass is wiped and still films. The washroom is serviced and still smells.

Check these in order:

• Dilution. A dispenser that has drifted, or a bottle topped up by eye, produces a solution that cleans poorly or damages the surface. Controls are set out in chemical inventory and dilution control.
• Consumables matched to the surface. The wrong pad on a floor finish removes it. The wrong cloth on stainless leaves residue.
• Machine condition. Worn squeegees, clogged filters, a blocked hose and a battery that dies mid-shift all produce repeats that look like carelessness.
• Contact time. Disinfectant wiped off immediately is not disinfection. Where the finding is hygiene-related, check the dwell time against the label before you check the person.
• Water and drainage. A drain that backs up or a floor that holds water is a building issue — critical if it creates a slip or contamination risk. Report it rather than working around it.

People: tested last, not never

People causes are real, just usually downstream of one of the four above.

• A new starter who has not been shown the standard in this building, as opposed to the general method
• A visual standard nobody has demonstrated — "clean the stainless properly" means little without showing what properly looks like
• Language or literacy barriers, where a photographed standard outperforms a written one
• Turnover removing the person who knew the building

Where the cause is genuinely people, the corrective action has to be specific. "Be more careful" is not an action. Retraining, a visual standard sheet for that area, a change of tool, or pairing a new starter with someone experienced for a week are actions, and each can be verified.

When the repeat is not a cleaning problem

Some findings recur for reasons no cleaning method will fix, and raising them as cleaning deficiencies damages the credibility of the whole programme.

The professional move is to reclassify the finding: move it out of the cleaning deficiency log, raise it in writing to the client with the evidence, and keep it visible in your reporting as an open client-side item. That is not avoiding responsibility, it is stating what is in scope — and it stops your quality score being dragged down by a leaking drain.

Scope note: Pest treatment, drainage repair, ventilation work and building fabric repair are outside a cleaning contractor's scope. Confirm in writing what is included, and report rather than act on anything outside it.

Running the analysis without a meeting

Root cause analysis in cleaning does not need a workshop, just the finding record and twenty minutes.

1. Pull every finding at that location for the last six months.
2. Note the pattern: same item, same time of day, same weekday, same shift.
3. Test the five causes in order, checking evidence rather than asking for opinion.
4. Write the confirmed cause against the finding.
5. Choose one corrective action that changes the cause, with an owner and a date.
6. Re-inspect the item at the next round and record whether it held.

If the item holds, the cause was right. If it fails again, the cause was wrong or incomplete, and the next pass starts further down the list.

Closing the loop so it stays closed

A corrective action is not complete when the area is cleaned. It is complete when the change that prevents recurrence has been made and verified.

Verification is what separates a closed deficiency from a suppressed one. Photograph the corrected condition, record the date, and keep the original finding linked to it so the history is visible if it returns. The mechanics are covered in deficiency tracking cleaning, and the response to a single serious failure is set out in reacting to a failed cleaning inspection. Cause before action, verification before closure, is also the order used in workplace health and safety investigation, where CCOHS publishes guidance on incident investigation.

After six months, three things change. The repeat rate falls. Corrective actions move from "re-clean" to "change the schedule, fix the access, replace the tool". And someone can answer the client's question "why did this keep happening?" with a cause rather than a shrug. None of that needs new software — just a cause field on the finding record and a quarterly look at causes, not only scores.

Where this fits in the quality system

This sits under our the structure of a cleaning inspection, which sets out the standard these checks are measured against.

Frequently asked questions

How many times should a finding recur before it counts as a root cause problem?

Three consecutive rounds on the same item in the same area is the common trigger, because it removes coincidence and seasonal variation. Any second failure of a critical hygiene or safety item should also trigger it, since those do not warrant a three-strike allowance.

How do I know whether a repeat is a people problem or a process problem?

Test in order: scope, access, time, equipment, then people. If the task is not in the specification, the area is locked during the shift, the funded hours do not cover the standard, or the chemistry is wrong, those explain the failure without reference to effort.

What if the root cause is outside my scope?

Reclassify the finding, move it out of your deficiency log, and raise it in writing to the client or the building's maintenance function with the evidence. Keep it visible in your reporting as an open client-side item, so it is clear it was identified and referred rather than ignored.

Should I re-train the cleaner first and investigate afterwards?

No. Re-training before diagnosing wastes the training and leaves the real cause in place, so the failure returns. Diagnose first; if people turns out to be the confirmed cause, the training you then deliver targets a known gap.

Do I need special software for root cause analysis?

No. You need a finding record that carries the cause, the corrective action, the owner and the verification date, plus a periodic look at patterns across locations. Inspection software makes that easier because the history is in one place; a disciplined spreadsheet works too.

Stop managing the symptom

Cleaning the same washroom a fourth time is not a quality system; it is a subscription to the same problem. Record the cause with the finding, work the causes in order, and reclassify anything that is not actually cleaning.

NeatScore keeps the finding history in one place, with repeat locations, critical items and closure status visible, so the pattern shows up before the fourth failure does. Try it free for 14 days, or see pricing.