TMIThe job is done. The crew is back at the yard. Tomorrow you'll generate the invoice. You'll pull the work order, review the notes, and build the line items from what you can reconstruct. The problem is that the invoice you're about to send is not the job that was done. It's the job your tech remembered to write down.
The materials he pulled off the truck but didn't log. The extra hour when the access panel required cutting. The scope expansion the customer approved on-site with a handshake. The follow-up he completed on the way out that wasn't on the original order. These are not exceptional cases - they're the normal conditions of fieldwork. And in a billing system built on end-of-day memory, they vanish.
The categories of leakage
Revenue leakage in the trades falls into four consistent categories, regardless of trade or company size. Understanding them specifically makes it possible to address them specifically.
The first is material leakage: parts and materials used on the job that don't make it onto the invoice. This happens most often when a tech pulls something small off the truck - a fitting, a capacitor, a few feet of wire - without logging it because the item feels too minor to be worth the administrative effort. Across a full fleet, those small items add up to a meaningful number.
The second is labor rounding: techs systematically underreporting time. Not from dishonesty, but from habit - rounding to the nearest half hour, not charging for drive time between the site and the supply house, absorbing the time it took to find the cleanout because it wasn't where the drawing said it was. These rounding errors favor the customer consistently and compound across every job.
The third is change order leakage: verbal approvals that don't make it into the system. A customer walks by, says "while you're here can you also...", the tech does it, the customer expects to pay for it, and it doesn't appear on the invoice because it was never formally documented. The customer didn't dodge the charge - the company gave it away.
The fourth is scope creep absorption: unplanned work that expands the job beyond the original estimate and gets absorbed rather than billed because the tech doesn't want to have a conversation, or doesn't know if the foreman wants to call it a change order, or just completes it and moves on.
"Billing from memory is a tax on revenue. The gap between what was done and what was invoiced is paid entirely by the contractor."
Why the fix isn't discipline, it's capture
The instinct is to address leakage with training and accountability - remind techs to log materials, require managers to sign off on scope changes, add fields to the work order. These measures help at the margin. They don't solve the underlying problem.
The underlying problem is that the billing system is designed to be completed after the work is done, from memory, in a single session. That session is the wrong place to reconstruct a day's worth of granular decisions. The right place to capture each billing item is at the moment it happens - when the part comes off the truck, when the customer gives the verbal go-ahead, when the scope expands.
A system that makes logging easier than not logging - where a tech scans a part barcode, taps a material line item, or records a ten-second voice note - produces dramatically more complete data than a system that asks them to reconstruct everything later. The difference shows up directly on the invoice.
The math worth doing
On a $3M service operation, leakage at 10% represents $300,000 in performed but unbilled work annually. That's not revenue that was lost to competition or discounted away - it's work that was done, paid for in labor and materials, and simply not invoiced. The materials cost was real. The labor cost was real. The customer got the benefit. The contractor absorbed the cost.
Recovery doesn't require recovering all of it. Moving from 10% leakage to 4% on a $3M operation is $180,000 in additional revenue at essentially zero incremental cost, because the work is already being done. The only change is that the invoice reflects it.