Photo evidence: what's actually worth capturing on a cleaning job

Most cleaning contractors that ask staff to photograph completed work end up, after a few months, with a large library of images that don't actually answer very much. A blurry, wide shot of a washroom taken from the doorway proves a phone was pointed in roughly the right direction; it doesn't prove much about whether the specific task on the checklist was actually done to standard.

Why volume isn't the goal

The instinct, once photo capture is introduced, is often to require more of it — every task, every time, on principle. In practice this produces the opposite of what's intended: staff rushing through photos as a box-ticking step, and supervisors with too large a volume of images to meaningfully review any of them. A smaller number of genuinely useful photos beats a large archive nobody looks at, and it also fits into evidencing a clean that's actually been done far more usefully.

What actually makes a photo useful

A useful completion photo is close enough to show the specific detail that matters for that task — a clear washroom surface rather than a distant view of the whole room, a stocked consumable rather than a general shot of the dispenser unit. It's taken at a consistent angle where possible, so a supervisor or auditor reviewing it later can compare like with like across visits, and it's tied unambiguously to the task and timestamp it's meant to be evidencing.

• –Prioritise close, specific shots of the actual task over wide, general shots of the room
• –Focus photo requirements on higher-risk or higher-visibility tasks rather than requiring one for every single checklist item
• –Keep the angle reasonably consistent so photos can be compared across visits
• –Tie every photo unambiguously to a specific task and timestamp, not a general end-of-shift batch
• –Review a sample of captured photos periodically to check they're actually useful, not just being taken

Fitting into the checklist, not bolted on

Photo capture works best built into the same flow as the task checklist itself, prompted at the point a specific task is marked complete, rather than as a separate end-of-shift chore. A checklist that asks for a photo in the moment, for the right tasks only, tends to produce far more usable evidence than a blanket policy applied after the fact.

A policy that produced nothing useful

A contractor introduces mandatory photos on every checklist item across forty sites. Within two months it is generating several thousand images a week, nobody has time to look at any of them, and staff have learned to photograph whatever is nearest at the moment the app asks. When a genuine dispute arrives, the archive turns out to contain forty-one photographs of that site on that date and not one that shows the surface in question.

Reducing the requirement to two or three high-value tasks per visit produced fewer photos and far more usable ones. The counter-intuitive part is that a lighter policy generated better evidence, because staff took the remaining photos seriously and supervisors actually reviewed them.

Common mistakes

• –Requiring a photo for every task, which trains staff to produce meaningless ones
• –Never reviewing a sample, so nobody notices the photos stopped being useful
• –Accepting wide room shots for tasks that need a close view of one surface
• –Allowing an end-of-shift batch upload with no per-task timestamp
• –Letting staff re-use yesterday's photo because nothing prevents it
• –Storing photos without the site, date and task attached in a way anybody can search