Raising and closing issues from a cleaning audit properly

An audit finding that gets written down and never followed up on is arguably worse than one that never got raised — it's now on record, visible to the client, and sitting open. The gap between a well-run cleaning operation and one that just looks well-run on the day of an audit usually comes down to whether findings actually get closed, not whether they get identified in the first place.

What a finding actually needs on the way in

A useful finding is specific enough that someone other than the person who raised it can act on it: what exactly was wrong, where, and ideally why — not "washroom below standard" but the specific issue observed, at the specific location, on the specific date. Vague findings are hard to fix precisely because it's unclear what "fixed" would actually look like.

Ownership and a realistic date

Every finding needs an owner and a date, not just a category on a report. Without both, a finding tends to sit in a general "to do" list that nobody feels personally responsible for closing, and it quietly becomes the same finding again at the next audit — which reads far worse to a client than a new issue would, because it signals nothing actually changed.

• –Write findings specifically enough that anyone could act on them, not just the person who raised it
• –Assign a named owner and a realistic date, not a general intention to address it
• –Confirm closure with evidence, not just a status change from open to closed
• –Review previously closed findings at the next audit to confirm they've actually stayed fixed
• –Track findings across the whole contract, not just per audit, so a recurring pattern is visible

Confirming closure properly

Marking a finding closed should mean more than a status flag changing colour — ideally there's a follow-up check, a photo, or confirmation at the next site visit that the issue is genuinely resolved, not just addressed in the moment it was raised. This overlaps directly with COSHH findings specifically, where a checklist that surfaces a gap needs exactly the same discipline to actually close it out rather than leaving it flagged and unresolved.

Why this matters more than the score itself

Clients running repeat audits notice patterns over time far more than they react to any single result. A contract where findings reliably get raised, fixed and closed builds a kind of trust that a strong individual score doesn't on its own — because it shows the contractor manages problems consistently, not just that problems happened not to occur this time.

Why findings die between the audit and the next one

The common failure is not that findings are ignored. It is that they are recorded in a form that cannot be actioned: a note reading "washroom standards" with no site, no owner, no date and no description of what good would look like. Three weeks later nobody can reconstruct what was meant, so it quietly lapses and reappears at the next audit as a repeat finding — which reads far worse to a client than the original.

A finding that names the site, the specific problem, one person and a date is actionable by someone who was not present when it was raised. That is the test worth applying as it is written down.

Common mistakes

• –Recording a category rather than a specific, located problem
• –Assigning to a team rather than a named individual
• –Setting a date that reflects optimism rather than the work involved
• –Closing on assertion rather than evidence
• –Never flagging repeat findings as repeats
• –Holding the list somewhere the people who need to act on it do not look