Evidencing a clean that's actually been done
A cleaning contractor doing the work correctly and a cleaning contractor who can prove the work was done correctly are, from a client's perspective, in noticeably different positions — even when the underlying quality is identical. When a complaint comes in, or a query surfaces about whether a specific area was cleaned on a specific day, "yes, it was done" is a much weaker answer than a timestamped record showing exactly that.
What "evidence" actually needs to mean
Useful evidence isn't a vague assurance that a site is generally well maintained — it's specific: this task, at this location, completed at this time, by this person, ideally with something visual attached. That's a higher bar than most contractors' historical record-keeping, which tended to rely on a supervisor's memory or a paper sheet that got filed and rarely looked at again unless something went wrong.
Photo evidence, used well
A photo attached to a completed task is one of the most direct forms of evidence available, but only if it's actually useful — a wide shot that could be any washroom on any day doesn't prove much on its own. What's actually worth photographing is a genuinely separate question from simply requiring photos, and getting it wrong produces a large volume of evidence that doesn't actually answer the question a client is likely to ask.
Why this matters most in a dispute
Most days, nobody asks for evidence — the work gets done and the contract runs quietly. The value shows up specifically when something is disputed: a complaint about a missed task, a client audit that scores a category lower than the contractor expected, or a renewal negotiation where the client is weighing whether to keep the incumbent. In each of those moments, a specific, dated record settles the question quickly. Its absence turns a fixable disagreement into a longer, more uncomfortable back-and-forth, and can colour how a client audit result gets received even where the underlying work was fine.
- Record completion at the task level, not just "site cleaned" for the day as a whole
- Attach evidence — a photo, a timestamp, a completing operative — to the specific task, not to the shift in general
- Keep the record retrievable by date and location, so a specific query can be answered in minutes rather than a search through paper sheets
- Make the recording step quick enough that staff actually do it consistently, not just when they remember or when an audit is expected
- Treat gaps in the record as seriously as gaps in the actual cleaning — an unrecorded task is, from the client's side, indistinguishable from one that didn't happen
The dispute is the only moment this matters
Evidence is an insurance policy, and like any insurance policy it is judged entirely on the one day it is claimed against. That day looks like this: a client says a washroom was not cleaned on Tuesday, wants a credit, and is annoyed. The contractor is confident it was. What settles it is not confidence — it is whether there is a timestamped record tied to that specific site, that specific date and the specific tasks, produced at the time rather than reconstructed afterwards.
Records assembled after the complaint arrives rarely persuade anybody, and they are usually the ones a contractor has. The whole value of routine evidence is that it was captured before there was any reason to.
Common mistakes
- Capturing evidence in a form only the contractor can read or interpret
- Logging shift completion rather than task completion, so the disputed task is not covered
- Batching all evidence to the end of a shift, which weakens the timestamp
- Keeping evidence for less time than the contract's dispute window
- Storing it where the account manager handling the complaint cannot get at it quickly
- Producing volume rather than specificity, and hoping quantity persuades
- Evidence needs to be specific — task, location, time, ideally an image — not a general assurance that the site is well maintained.
- The value of good records shows up most clearly during a dispute, not during an ordinary week.
- A record that's hard to retrieve quickly during a query functions little better than no record at all.
- Recording needs to be quick enough that it happens consistently, not just when an audit is expected.
- From a client's point of view, an unrecorded task and a task that wasn't done can look the same.
About this article
The CleanOptix team
Written by people who work daily with cleaning contractors on contract delivery, COSHH and the records that hold up under a inspection.
- Published
- 19 March 2026
- Last revised
- 27 September 2026
How this is researched, dated and corrected is set out in our editorial standards. If something here is wrong or out of date, email hello@cleanoptix.co.uk — corrections to a regulated detail are made as soon as we can confirm them, and the revision date above moves when they are.