Can you prove what your crew did yesterday?
If the answer lives on paper, in a group chat, or in one bloke's head, then when a client disputes a service, their records are the only records, and their records win. This is about closing that gap: what proof of work actually means on a recurring run, and what it is worth.
The asymmetry that costs you money
Every recurring service business runs on trust until the first time it does not. A site gets marked as missed. An invoice gets queried. A contract comes up for renewal and someone wants twelve months of service history by Friday.
At that moment the question is not whether you did the work. You almost certainly did. The question is whether you can show it. And the uncomfortable truth about most route businesses is that the client has a system and you have a run sheet, so when the two accounts disagree, theirs is the one written down.
When the client's records are the only records, the client's records win. Not because anyone is lying, but because only one side wrote it down.
What this is worth, with a real number
One waste operator I built for had sites on the run that were being serviced every cycle and were not on any invoice. The crew did the work. The paperwork on the other side said the sites were not active. Nobody was being dishonest; two systems simply disagreed, and only one of them had evidence behind it.
Once every service carried a timestamp, a location and a photo, the gap was evidenced rather than argued: around $30,000 a month of servicing that had been going out unbilled. The system did not find money that was not there. It made visible work that was already being done for free. You can read the whole thing on the Howyabin case study.
Your number will not be that one. It might be a fraction of it, or nothing at all if your records are already tight. But most operators I audit have never actually tested the question, and the answer is usually not zero.
If you run a route, this is you
This is defined by the shape of the work, not by the trade on the ute. If your business services the same sites on a cycle, you are in this group: waste and bin services, commercial and strata cleaning, grounds and garden maintenance, pest control, pool servicing, hygiene services, facilities maintenance.
What those have in common is not the task. It is that the work is invisible after the fact unless somebody deliberately records it, and that the person driving the run is holding most of the knowledge in their head.
The three things that leak, every week
- You cannot prove it, so you cannot bill it. Services that happened and never made it onto an invoice. Extra sites added mid-contract. Make-goods done as a favour and never counted. If the run sheet and the invoice are two documents kept by two people, the gap between them is yours to absorb.
- The run only works when the right person is driving. Which sites, in what order, which gate code, which client wants what. It is in one person's head. A sick day costs a day of revenue, and a new hire takes months to be useful because there is nothing to hand them.
- The call rings out while you are on site. You are on the truck with gloves on. The caller does not leave a message, they ring the next name on the list. That is the cheapest of the three to fix, and it is usually where I start.
Proof of work and handover are the same problem wearing different hats. Write down what happens on the run, and you can both bill it and hand it over.
What I actually build
Nothing exotic, and usually on top of the software you already run rather than instead of it.
- A run record. Every site on the cycle, what was done, when, by whom, with a photo where it matters, captured on the phone in the driver's pocket. Offline-first, because half the run has no signal.
- Exception capture. Bin not out, gate locked, contamination, car parked on the strip. Recorded in two taps at the time, not remembered at the depot.
- A billing reconciliation. The one that finds the gap: what was serviced this cycle against what was invoiced. This is the piece that pays for itself.
- Something to hand a new driver. The round, in order, with the notes attached, so the run survives the person who knows it.
- A client-facing record where a facilities or strata manager wants one, so the next dispute ends in a link rather than a phone call.
Where to start
Start with the cheapest thing that stops money leaving, which is almost never the biggest build. If calls are ringing out while you are on the truck, Never Miss a Call is $165 a month and live on your existing number in about a week. If the leak is the run record itself, that is a build: from $1,500 for a smaller one, from $3,500 for a bigger one, or inside Ops Care from $1,500 a month, which is where most route operators land because the run keeps changing.
If you are not sure which of the three is costing you most, that is exactly what the Trades Tech Leak Audit is for. Thirty minutes, I map your setup, you get a one-page finding, and it is yours whether or not you ever work with me.
What operators ask me about proving the run.
What counts as proof of work?
Something dated, attributable and hard to argue with: a time on site, a photo of the finished job, who did it, and any exception they hit. The test is simple. If the client says a service did not happen, can you put something next to their claim within a minute, without ringing anyone? If the answer involves scrolling a group chat, you do not have proof, you have recollection.
Why do disputes go the client's way so often?
Because the client's records are usually the only records. A facilities manager or a council has a system; the contractor has a run sheet and a memory. When two accounts disagree and only one is written down, the written one wins. It is rarely dishonesty on either side. It is an asymmetry in record-keeping, and it is fixable.
My job app already stores photos. Is that not proof?
Partly. Most job apps will hold a photo against a job, and if yours does, use it. The gap shows up on recurring work: proving a whole round ran, spotting the site that was skipped three weeks running, producing twelve months of service history for one address when a contract comes up for renewal. Job apps are built around the job, not around the round.
Does this mean replacing the software I already run?
No, and I will say so plainly when the answer is no. The usual build sits on top of what you have: keep the job app and the accounting package, add the run record and the evidence layer around them. Ripping out working software to close a workflow gap is the expensive way round.
What does it cost?
A smaller build starts from $1,500 fixed and a bigger one from $3,500, both scoped in writing before anything starts. Most route operators end up on Ops Care from $1,500 a month instead, because a run record is not a one-off: it wants a fix or an addition most months as the contracts change.
Who owns the software?
I own the source and licence the running application to you, which is what keeps the price where it is. You get your own environment, your own data, and an admin role over it. There is a buyout option if you want the source outright, and a source-escrow commitment if Bolt On Ops ever winds up.
Not sure what fits your shop? Ask me, not a sales rep.
A 30-minute Tech Leak Audit and a one-page written finding inside 48 hours. Three prioritised fixes, no pitch, and the report is yours either way.