Book a DemoHow to prove cleaning was completed: evidence that ends the argument in one reply
To prove cleaning was completed, capture four things against one specific task rather than against a day: a photo of the finished work, the name of the person who did it, a completion time recorded by the system at the moment the job was closed, and the site the task belongs to. Kept together, those form an audit trail you can pull up months later and show a client without editing anything. Photos in a group chat, a signed paper sheet in the cupboard and a supervisor's word are weaker versions of the same claim, because none of them ties one piece of evidence to one obligation on one date. The working test is simple: when a client challenges last Friday's washroom clean, can you produce evidence in under a minute that a neutral third party would struggle to argue with? Software such as LogSure does this by refusing to let a task close without the required photo, then storing the photo, the person, the completion time and the site as a single record.
Written by the LogSure team. We make software that does this, and we say so further down. The first half of the page works whether you buy anything or not.
Why "we definitely did it" always loses
Monday morning. The client emails: reception bins were not emptied on Friday, and they are not paying for Friday. Your cleaner says they were emptied. Both statements carry exactly the same evidential weight, which is none, so the argument gets settled by whoever is more stubborn or by whoever is holding the money. The client is holding the money.
Put your own numbers on it. Eight contracts at £1,800 a month is £172,800 a year. Lose one you actually fulfilled because you could not evidence it and that is £21,600 gone, plus the cost of replacing it, plus every credit note you issued along the way trying to hold on to it.
The money is the smaller half. Once a site manager decides the work is unreliable, every future complaint starts from that assumption, your supervisor spends visits defending rather than building the account, and the renewal is effectively decided months before anyone discusses it. Evidence is not admin. It is what keeps the story straight.
What actually counts as proof (five tests)
Evidence that survives a challenge passes all five. Most cleaning companies capture one or two, then get a shrug from the client and cannot work out why.
- 1It points at one task, not at a day. A photo of a clean washroom proves a washroom was clean at some unknown moment. A photo attached to "Second floor washrooms, Friday round" proves that job was done. The link between the evidence and the obligation is the whole ballgame, and it is the part almost every homemade system misses.
- 2It shows the finished state of something the contract names. Photograph the area your specification talks about, from far enough back to show it. A close-up of one polished tap answers a question nobody asked. If the spec says bins emptied and liners replaced, the shot is the bin.
- 3It carries the name of the person who did it. Attribution turns evidence into testimony. It also answers the question every client asks next, which is not whether the work was done but who was on site. Without a name attached at the time, you are reconstructing a rota from memory.
- 4The time comes from the system, not from the person submitting it. A date written into a sheet on Monday for work done on Friday is a claim. A completion time captured the moment the task was closed is a record, because nobody chose it. This is the single biggest difference between proof that holds and proof that gets argued with.
- 5You can still retrieve it in four months, in under a minute. Disputes arrive late. Invoices get queried at quarter end and contract reviews look backwards. Evidence you cannot find on demand has the same value as evidence you never captured, which is why storage and search matter as much as capture.
Test five is the quiet killer. Plenty of teams capture decent evidence and still lose the argument, because producing it means asking three people to scroll their phones.
The proof ladder, weakest to strongest
Every cleaning company sits somewhere on this ladder. Which rung you are on tells you what a client can currently do to you.
- 1. Word of mouth. Your team says it happened. Worth nothing in a dispute, because the client's team says it did not.
- 2. A signed sheet in the cupboard. Proves somebody signed a sheet. It lives on the client's premises, it can be filled in for the whole week on Friday, and everyone in the building knows that.
- 3. Photos in a WhatsApp group. Right instinct, wrong container. No task link, no search by site and date, and images that have been re-compressed on the way through.
- 4. Photo, named person and system-recorded completion time, attached to the task. Now the evidence answers the question that was actually asked, and it answers it the same way in four months as it does today.
- 5. All of the above, sent to the client as a matter of routine. Proof that arrives before it is demanded stops most disputes from starting, because there is nothing left to speculate about.
The jump that protects your revenue is three to four. Rung five is the one that changes how the client describes you internally, which is where renewals are really decided.
How to do it without buying anything
You can build a defensible proof habit with a phone camera, a shared drive and some discipline. Five steps:
- Step 1: Write down what done means, site by site. Turn the specification into lines a person can photograph. Reception presentable is unprovable. Bins emptied, glass doors spot-cleaned, floor mopped is three pieces of evidence.
- Step 2: Pick the few tasks that actually get disputed. Most sites have three to five flashpoints: washrooms, reception, the client's own office, the bins. Require proof on those. Requiring a photo of everything trains staff to take fast, meaningless pictures and buries the shots that matter.
- Step 3: Standardise the shot. Same angle, wide enough to show the area, taken after the work. Consistency is what makes a run of photos readable months later, and it is what stops a client claiming you only photographed the one tidy corner.
- Step 4: Capture who and when at the moment of completion. Not at the end of the shift, and definitely not on Friday for the whole week. The entire value of a timestamp is that it was not chosen after the fact.
- Step 5: Store it so it can be found by site and date, then send it before it is asked for. One folder per site, one entry per visit, a summary to the client each month. Proof that arrives routinely changes the conversation. Proof that only appears during an argument looks like something you assembled for the argument.
This genuinely works. It also decays, and it decays in a predictable order.
What breaks first when proof is manual
- The photo gets taken; the link gets lost. Six weeks later you have the image and no way to show which visit it belongs to. Every step depends on somebody remembering, and that somebody is on their sixth site of the day.
- Filing becomes someone's evening. A supervisor with 20 staff and a daily proof habit ends up rebuilding the week in a spreadsheet on Friday night. When the week gets busy, the filing is what gets dropped, not the cleaning.
- So you settle disputes you would have won. Not because the work was missed, but because finding the evidence costs more than the credit note. Do that four times and you have taught the client that complaining pays.
How LogSure captures the same proof without the admin
LogSure is photo-verified task completion software for field service teams, used by commercial cleaning, facilities and security companies. The design goal is that proof falls out of doing the work, because any system that needs a second act of discipline after the round will not survive a busy month.
- The requirement lives on the task. If a task requires photo evidence, it cannot be marked complete without it. Nobody has to remember the rule because the app will not move on.
- Photo, person, completion time and site are stored as one record. Searchable by site, date and person months later, in seconds.
- Recurring rounds generate the same task every time. Evidence lines up date by date, so a gap shows as a gap instead of as an absence you have to notice.
- Issues get logged at the time, with a chat thread on them. The blocked cubicle, the locked office, the meeting room still in use at 7pm. Recorded on the day, which is the only time that explanation is worth anything.
- Client reports come out of the work record. Photos, times and names, rather than a summary somebody typed up from recollection on a Sunday.
- The evidence stays put. Task completion photos are retained for the life of your subscription with a guaranteed minimum of 12 months from upload, and task records and audit logs for the duration of the subscription.
One thing worth saying plainly. This is not staff surveillance, and any team that sells it internally that way gets the adoption it deserves. The record exists so that when a client claims a job was skipped, the cleaner who did it has something on their side. Good staff stop being the ones who carry the blame for missing evidence.
Pricing is usage-based on completed tasks, with unlimited users and no per-seat fees, from £99 per month. See pricing or the cleaning use case.
When you do not need any of this
If you clean one site, you are on it daily, and the person who pays you walks the floor with you, presence has already solved the proof problem. Domestic work rarely needs an audit trail either, because the customer is standing in the result.
Proof earns its keep when work is recurring, off-site and paid for by somebody who was not there to see it. If clients have never queried a visit and no contract is up for review, do not build an evidence machine for a problem you do not have.
FAQ
Is a photo on its own enough to prove a clean was done?
No. A loose photo shows that somewhere looked clean at an unknown time, taken by an unknown person, and it can be re-sent, re-used, or taken before the shift started. Proof needs four things together: the specific task, the named person, a completion time recorded by the system, and the site it belongs to.
The client says our photo could be from any week. How do we answer that?
They can keep making that argument as long as the only date attached to the evidence is the one you tell them. Remove the choice by capturing the completion time automatically when the task is closed. Do not lean on the image file's own metadata either, because photos that pass through messaging apps are re-compressed and the original capture information often does not survive the trip.
Should we require a photo on every single task?
No, and doing so usually makes proof worse. Staff shoot faster and think less, and you end up with thousands of images nobody has ever opened. Require evidence where work gets disputed, where there is a health or safety consequence, or where a client has complained before. Everything else can carry a completion record without a photo.
Does asking cleaners for photo proof mean we do not trust them?
In practice it works the other way round. When a client claims work was skipped and no record exists, the accusation lands on the cleaner and they have nothing to answer with. A proof trail means good staff get their work seen and stop absorbing blame for jobs they actually did. It also gives them a way to record the task they could not finish, and why.
How long should we keep cleaning proof?
At least as long as a client can query an invoice or raise a service issue under your contract, which for most commercial cleaning agreements is months rather than weeks. In LogSure, task completion photos are retained for the life of your subscription with a guaranteed minimum of 12 months from upload, and task records and audit logs are kept for the duration of the subscription.
Can we just use WhatsApp for cleaning proof?
You can send proof through WhatsApp. You cannot retrieve it. The photo has no link to a task, the thread cannot be searched by site and date, and the evidence you need for one Friday in March sits under three weeks of messages about vans and shift swaps. More on why proof breaks in group chat.
Do we need before-and-after photos?
For periodic work where the change is the deliverable, yes: carpet cleaning, washroom deep cleans, builders' cleans. For daily rounds it is overkill and slows the round down. A finished-state photo of each key area is the standard teams actually sustain.
Keep reading
Proof-of-work software
What a field-service proof record should contain, and how LogSure builds one.
WhatsApp alternative
Why evidence stops being evidence once it lives in a group chat.
Photo-verified task tools compared
Five tools that capture proof, and the problem each one is actually built for.
Cleaning services
How commercial cleaning teams run recurring rounds and prove them.
Next step
Bring the last dispute you lost, or the one you are arguing about right now, and book a demo. The useful version of that conversation is not a feature tour. It is working out exactly what evidence would have ended that argument on the first reply.