The Client Says ‘It Wasn’t Cleaned’: When You Lose £800 Without Proof
When a client disputes cleaning and neither side has evidence, you always lose. In the UK field service sector, this challenge is compounded by strict requirements under the Working Time Regulations 1998, UK GDPR, and the Procurement Act 2023. Companies relying on manual documentation find themselves vulnerable during client disputes, regulatory audits, or contract renewals.
The pattern that costs you money
The scenario repeats across every field service sub-sector: work is completed, but evidence is incomplete, delayed, or stored in a format that doesn’t survive scrutiny. The operative did their job. The proof didn’t. When the client challenges the invoice, the absence of robust documentation becomes a commercial liability far exceeding any individual dispute.
Under ACAS guidelines and the Employment Rights Act 1996, employers must maintain accurate records. Accuracy isn’t just capturing data, it’s capturing it verifiably, tamper-resistant, and accessible when needed. Manual processes fail all three tests.
What automated evidence changes
When proof is generated automatically – GPS-stamped attendance, server-timestamped photos, automated client reports, the entire risk profile shifts. Disputes don’t escalate because evidence exists. Clients don’t challenge invoices because they see verification themselves. Contract renewals become straightforward because compliance is demonstrable, not anecdotal.
Why Digital Evidence Wins in Court
When a client claims a cleaning didn’t happen and the service provider cannot produce evidence, the client almost always wins. UK case law (notably Globe Motors v TRW Lucas, 2016, and subsequent commercial disputes precedent) places the burden of proof firmly on whoever invoiced for a service. In practical terms: without documented evidence of work delivered, you either issue a credit note or perform a free remedial visit. £800 per disputed contract is the industry baseline cost.
For evidence to count in court or arbitration, it needs three properties: contemporaneous (created on the day of service, not reconstructed later), tamper-evident (not retroactively editable), and location-bound (with geo-coordinates of where the service was delivered). A WhatsApp “we were there, all good” doesn’t tick any of those boxes. A phone photo doesn’t either – EXIF data can be edited in seconds.
