Construction revenue leakage: where it comes from and how to stop it.
Revenue leakage is completed work that doesn't make it onto the invoice. For specialty subcontractors, it's almost always rooted in a documentation failure — work that happened faster than the paperwork did. This guide covers the main sources and what actually fixes them.
Where revenue leakage comes from
Four patterns account for the majority of leakage on specialty subcontractor jobs — each solvable with the right documentation workflow.
Verbal-directive work that was never documented
The most common source. A GC or owner directs additional work verbally. The crew does it. No one captures it formally at the time, and by invoice day the sub has no documented basis to bill it — or the GC disputes ever having authorized it.
T&M work documented too late to bill
End-of-day or end-of-week T&M tickets miss detail that only exists at the moment of work. When GCs can't verify late documentation against their own records, they push back — and the sub absorbs the cost rather than fighting for a charge they can't prove.
Scope additions that grew too small to notice individually
Five minutes of standby here, two extra cores there, one additional pass nobody logged — individually trivial, collectively significant across a multi-month job. Small unlogged additions are the hardest leakage to find because no single item looks worth chasing.
Work captured but never invoiced
Documentation happened, but it never made it from the field log to an actual invoice line. The work exists in the record but not the billing system. This is recoverable — if someone reviews the field record against the invoice before closeout.
How Revecta's Revenue Recovery Engine works
Revecta's approach to revenue leakage is deterministic, not black-box: it checks every documented field event against a set of explicit rules — has this been priced? submitted? approved? invoiced? — and surfaces the ones that haven't completed that cycle before the invoice is sent.
The engine doesn't guess or score — it reports a specific finding with a specific reason: “this T&M event was captured but not priced,” or “this scope addition was approved but no invoice was generated.” Every finding is verifiable by the PM without trusting an algorithm.
This approach works only when field documentation is complete enough to run against. Which is why Revecta starts with field capture — the Recovery Engine is the analysis layer on top of documentation that actually happened in the field.
Frequently asked questions
What is revenue leakage in construction?
Revenue leakage in construction is any completed, billable work that fails to reach the invoice — most often because it was verbally directed and never formally documented, because documentation happened too late to support billing, or because the GC has no record of authorizing the work and disputes the charge.
How much revenue do specialty subcontractors typically leak?
There's no single reliable industry-wide figure, and we don't publish one — treat any specific percentage you see elsewhere with skepticism unless it cites a real source. What's consistent across specialty subcontractors is the risk factor: the more a trade's work is directed verbally in the field rather than through formal change orders, the more exposure it has to undocumented work never reaching an invoice. Trades with heavy verbal-scope exposure — concrete cutting, firestopping, waterproofing, demolition — tend to carry more of that risk, but the actual dollar impact depends entirely on a contractor's own documentation habits, not the trade itself.
Is revenue leakage the same as billing disputes?
Related but different. A billing dispute is active — the GC pushes back on an invoice line. Revenue leakage is often passive — the work was never invoiced at all because the sub had no documentation to support it. The passive form is harder to see and arguably more costly because there's no dispute to resolve, just missing revenue.
Can software actually fix revenue leakage, or is it a people problem?
Both. The underlying cause is a documentation gap — work happens faster than paperwork does. The right software makes documentation fast enough that crews actually do it in the field, rather than relying on reconstruction later. Revecta is designed specifically for that workflow: capture in the field, on a phone, at the point of work.