Proof of Work on Site: What Actually Holds Up in the UK

A client rings on a Tuesday and tells you, flat out, that nobody turned up the Thursday before. Your crew was there. You know they were there, you spoke to the foreman on the drive home. But the only thing standing between your invoice and a full refund is a sheet somebody filled in from memory three days later, biro over a coffee ring, and memory is not evidence. It is a story, and the client has a better one.

Now swap the client for an inspector. Someone from the Fair Work Agency asks, quite reasonably, to see the hours your people actually worked, and how you know they stayed inside the weekly limit. You reach for the same folder. The dates are round numbers, every shift a tidy eight hours, not a single Friday that ran late even though half of them always do. Nobody believes a record that never has a bad day, and neither will a tribunal.

This is the quiet truth of running a field team: almost every fight you can lose comes back to one question, can you prove what the crew actually did, where, and when. The proof either builds itself while the work is happening, sealed at the moment it happens, or it does not exist on the day you need it. Reconstructed afterwards, from goodwill and guesswork, it is worth roughly nothing.

What does proof that holds up actually look like?

Start from what proof is not. It is not someone’s word, however honest, because the other side has a word too and a tribunal weighs them on the balance of probabilities. Proof that holds is objective: it does not depend on who is telling the story. It is pinned in time and in place, so there is a clock and a location welded to the fact, not a guess about “sometime that morning”. It cannot be quietly tidied up later, because a record you can rewrite is a record the other side can argue you did rewrite. And it survives distance, so that six months on, when everyone has forgotten the day, the evidence still speaks in the same clear voice it had on the morning it was made.

Put plainly, proof of work is a log that says: this person was at this address, at this time, for this job. Not a diary of where they went all afternoon, not a dot moving across a map. A fact, captured once, sealed on the spot, and readable months later by someone who was never there.

Why paper, memory and the shared spreadsheet let you down

Paper fails because it is written by hand, usually after the fact, and everyone knows it. A signing-in sheet proves that a pen touched a page, nothing more. Memory fails faster: ask anyone what time they finished on a Wednesday three weeks ago and watch them round it to the nearest polite half hour. And the shared spreadsheet, the one that feels modern, is the worst of the three dressed up as the best, because a cell has no time and no place of its own. Anyone with the link can open last month and change a nine to an eight, and it leaves no bruise. A record that can be edited by anyone, at any time, from anywhere, is not a record. It is a suggestion.

The common thread is that all three are made by hand, away from the moment, with no fixed clock and no fixed location. They ask you to trust the person filling them in, which is exactly the trust that gets tested the day something goes wrong.

Where the missing proof actually bites

It bites first in client disputes, the “you never showed up” phone call, where an objective clock-in at the right address ends the argument in one line instead of a fortnight of emails. It bites in inspections, and that ground has just shifted. The Working Time Regulations 1998 already oblige employers to keep records adequate to show the weekly and night-work limits are being met. From 6 April 2026 the Employment Rights Act 2025 goes further, adding a duty to keep adequate records of annual leave and holiday pay for six years, with the new Fair Work Agency able to demand them and serious failures treated as a criminal matter. “Adequate” is doing a lot of work in that sentence, and a folder of round numbers is not it.

It bites in payroll, where every disputed half hour is either paid twice or clawed back with bad blood, and a sealed clock-in and clock-out simply settles it. It bites in insurance and injury claims, where “was the operative on site, and when” decides whether a claim stands or falls. And it bites in tenders and contracts, where a facilities buyer increasingly wants to see how you evidence attendance before they hand you the building, and “we use paper” quietly loses you the bid. There is a legal edge to all of this too. Where an employer cannot produce records of the hours worked, tribunals have tended to lean towards the worker’s account, so the absence of proof is not neutral, it counts against you.

Proof is not surveillance, and the difference is the whole point

Here is where a lot of tools go wrong, and where the honest line sits. Recording that a job started at 8:02 at a client’s front door is proof. Following someone’s phone all day, mapping their lunch, their detour to the chemist, their drive home, is surveillance, and under UK GDPR it is also a fast route to a problem with the Information Commissioner’s Office. The test the ICO applies is proportionality: capture the fact you genuinely need for a lawful reason, tell people plainly you are doing it, and stop there. Continuous location tracking of a worker fails that test on nearly every count.

So the good version of proof is deliberately blind between the taps. It knows the crew were at the address at clock-in and gone at clock-out, and it knows nothing whatsoever about the hours in between or the miles either side. That is not a limitation to apologise for. It is the design, and it is the only version that protects the company and the worker at the same time.

Building the proof while the work happens

Which brings it back to the thesis: proof either builds itself as the work is done, or you are reconstructing it under pressure when it is already too late. The practical answer is to move the record from the memory of a tired person at the end of a shift to the moment and the place itself, sealed as it happens, and out of anyone’s reach to tidy later.

That is the whole reason GeoTapp exists. One tap to start, one tap to finish, and the app stamps the time and the location on the spot, sealed, exportable, and blind to everything in between. The software does not watch the person, it certifies the work: this crew, this address, this window, in a form a client, an inspector or a payroll run can all read the same way months later. It grew out of a real field problem, the nightly ritual of scribbling start and finish times by hand and squaring them up at month end, and it was built deliberately to record the fact and nothing more.

So the honest question to end on is the one the client already asked you: if it came down to it tomorrow, could you prove it? If the answer is a folder and a hope, you can start building proof that holds from your next shift, before the next Tuesday phone call rather than after it.