Proof debt: work you've done but can't yet prove

Every water hygiene firm carries a balance it never sees on the books: work that is finished but not yet provable. The visit happened. The readings were taken, the tank was inspected, the engineer signed off. But the certificate isn't written, the photos are still on a phone, and the sign-off sheet is in a van door pocket. Until all of that reaches the office and gets processed, the work exists and the proof doesn't. Call it proof debt.

The mechanics are laid out well in field-service records writing. Certificates, photos and sign-offs get created at the job, then handled separately, stored in different places and processed later. Retrieval slows down. Close-out stops being consistent. Office staff spend their time chasing paperwork that should already have been filed, and, the part that actually costs money, compliance certificates go missing before an audit. The debt is invisible right up until someone asks for a specific record and it can't be produced.

The month-end marathon

Most firms clear the debt in a monthly panic. The last week of the month becomes a certificate marathon: someone in the office working through a backlog of visits, matching photos to jobs, typing up sheets, generating documents that were technically due weeks ago. It works, in the sense that the certificates go out. It also means the record is being assembled by someone who wasn't on site, from notes made by someone who was, days or weeks after the fact.

It gets worse under load. As a firm takes on more work, engineers under time pressure start submitting compliance forms late, or with information missing: a blank field here, an unsigned sheet there. Each gap is a small future job for the office, which has to chase the engineer, remember what happened, and fill it in. The debt compounds. The busier you get, the further behind the proof falls.

It helps to see where the debt physically sits, because it is never in one place. The readings are in the engineer's head or on a damp pad. The photos sit in a phone's camera roll, indistinguishable from three hundred others. A signature is on a sheet in the van door pocket. And the certificate itself exists only as a blank template until someone fills it. Nothing is lost, exactly, but nothing is filed either, and turning five scattered fragments back into one record is real work that has to happen before the job is closed. Multiply that by every visit in a month and you have the marathon.

The invoice waits on the paperwork

There is a cash cost too. A job marked complete is not the same as a job you can bill. When the documentation isn't finalised, meaning reports, photos, signatures and time logs, accounting can't raise an accurate invoice, so the invoice waits for the paperwork to catch up. Work you did on the 3rd gets billed on the 28th because that is when the certificate finally got written. The proof debt and the invoice lag are the same backlog seen from two ends.

Why it bites harder in water hygiene

In a lot of trades the paperwork supports the job. In ours it is the job. A legionella monitoring visit produces a reading and a record, and the record is the thing the client is paying for and the thing an assessor will ask to see. Miss a plumbing repair's paperwork and you have an undocumented repair that still works. Miss the monitoring record and you have, as far as anyone can later prove, an unmonitored system.

The retention rules make the debt long-lived. Monitoring records must be kept for at least five years, and HSE expects them to be "signed, verified, or authenticated by a signature or other appropriate means". A record assembled a month later from memory is harder to authenticate honestly than one signed on site at the time. And because the work is checked, by the client and by an LCA assessor, the debt comes due on a schedule, in front of someone whose job is to find the gaps. An audit is a scheduled reckoning: you know it is coming, roughly when and roughly what it will ask for, which is exactly why a firm carrying proof debt dreads it. The audit doesn't create the gaps. It finds the ones you already had. The same finished record that satisfies an assessor is also the one that settles a dispute over whether you attended at all.

Pay it off at the source

The way to kill proof debt is to stop it forming. If the record is complete the instant the engineer submits the visit, with the form filled, photos attached, signature captured and everything timestamped, there is nothing to assemble later. The office isn't building certificates from notes. It is reviewing records that already exist. Approve it, or send it back for the one missing field, and it is done. Same day, not month-end.

There is a distinction worth making explicit. A job done and a job closed are not the same event, and proof debt is the space between them. On paper the two can drift weeks apart. Capturing the record at submission collapses that gap to zero: the moment the engineer marks the visit done, it is also provable, billable and filed. Nothing sits in the space between, because there is no space.

That changes what review means. Instead of typing up someone else's work, the office is checking work that is already in final form, which is quicker and catches more. We wrote separately about how entering data once removes the retype step; proof debt is what that retype step leaves behind when it falls behind.

BlueWave was built so the record is finished when the visit is. The engineer submits, and a visit record and PDF report exist immediately, carrying who did the work, what they found and when, timestamped at capture. The office reviews it and either approves or returns it, same day. The five-year retention happens on its own, because the record was never in a pile waiting to be written up. Proof debt is one of eight leaks we built the platform around; it happens to be the one an audit finds first.

None of this strictly needs software. A disciplined firm with good filing habits can keep proof debt near zero on paper. It is just hard, because the debt builds in the exact places where discipline runs thin: the busy week, the late finish, the engineer already onto the next site. Systems earn their place by holding the line there, not by being clever.

Proof debt is invisible until an auditor, a client or a solicitor asks for one specific record. That is the worst possible moment to learn how far behind your paperwork has fallen, and it is the moment the whole thing was supposed to be ready for.