How much work has your site team already done that isn't on an invoice anywhere. Work the client asked for, that genuinely happened, that nobody has priced or billed yet because it's still sitting somewhere between a verbal instruction and a submitted claim.
Most commercial teams don't have a number for that. It's construction revenue leakage. Work your team already delivered, sitting outside the billing system because it never made it from a verbal instruction to a priced, submitted claim. It's one of the quieter problems in construction finance, because nobody gets an alert when revenue simply fails to appear. The work happened. The client got what they asked for. The invoice just never followed.
Where Construction Revenue Leakage starts
Every variation starts the same way. Someone gives instructions, on-site or in an email, and the work begins because stopping to wait for a formal change order would delay the job. That's normal. Construction can't run on paperwork alone.
The trouble starts after the instructions. Here's where the revenue quietly stops moving toward an invoice:
- A site engineer logs the instruction in a diary or a WhatsApp thread, but nobody converts it into a formal variation record
- The QS knows the work happened and roughly what it's worth, but hasn't priced it yet because three other urgent things came in that week
- The variation gets priced, but sits waiting for client approval, and nobody chases the approval because the work itself is already done and visible progress feels more urgent
- The project closes out, and any variation still sitting unpriced or unapproved simply doesn't make it into the final account, because closing the job took priority over chasing every change
None of this is anyone being careless. It's what happens when variations get treated as a site administration task instead of a revenue stream that needs its own discipline, tracked with the same seriousness as an invoice.
A Quick Way to see if this is Happening to you
Pull your live variation register right now and count how many entries sit in a status that isn't "invoiced" or "rejected." Now ask how long the oldest one has been sitting there.
If you can't answer that in under a minute, you likely have unbilled variations sitting on your books that nobody is actively chasing. If the oldest one has been sitting for months, some of that work may already be past the point where a client will pay it without a fight.
This is the exact mechanism the Arcadis Global Construction Disputes Report points to when it flags poor change management as one of the recurring causes of disputes worldwide. Unpriced, unapproved work doesn't just cost money quietly. It also becomes the thing clients push back on hardest once someone finally tries to bill it.
Example
Picture a mid-size contractor running a hospital refurbishment. Over four months, site logs fourteen separate instructions: extra fire-rated partitions, a relocated data room, additional structural propping after a survey found unexpected conditions. Each one gets a mention in a site diary. Two get formally priced and submitted. The other twelve sit untouched, because the commercial team is stretched across three live projects and the work itself isn't blocking progress, so it doesn't feel urgent. By the time the project nears completion and someone tries to reconstruct a final account, several of those twelve have missed the contract's notice period entirely. The work was real. The client benefited from it. Some of that revenue is now gone for good, not because the client refused to pay, but because nobody asked in time.
Why Unbilled Variations Behave Differently to Cost Overruns
Cost overruns and revenue leakage look similar on a P&L, but they come from opposite directions. A cost overrun means you spent more than planned. Unbilled variations in construction mean you did more than you're being paid for, and the money is recoverable, if someone chases it in time. Confusing the two is part of why construction revenue leakage stays hidden for so long. Finance sees a project tracking to budget on the cost side and assumes the commercial position is healthy, without checking whether every pound of work done has turned into a claim.
That distinction matters because the fix is different too. You can't buy your way out of unbilled work the way you might renegotiate a supplier rate. The only way to recover it is to have priced, approved, submitted claims, and every day that slips by without one makes the eventual conversation with the client harder.
A few things make this worse in construction specifically:
- Variations often get approved verbally on site long before there's a paper trail, so the commercial team is working from someone's memory of what was agreed
- Notice periods in most standard forms of contract are strict. Miss the window to notify a variation and you may lose the right to claim it at all, regardless of whether the work was done
- Large contractors run dozens of live variations across a project at once, and a handful sitting unpriced doesn't look urgent until they're added up
- Project teams rotate. The person who remembers the verbal instruction three months ago may not be on that project anymore by the time someone tries to reconstruct it
Why this Scales Badly as a Business Grows
A contractor running one or two projects can often catch unbilled variations through sheer familiarity with the job. Someone remembers the extra work, someone chases it before it's forgotten. That informal safety net disappears the moment a business runs multiple concurrent projects, because no one person holds the full picture anymore.
Construction revenue leakage at that scale shows up as a handful of unpriced items sitting quietly on every project across the portfolio, none of them individually alarming, all of them adding up to a meaningful chunk of revenue that was earned and never billed. This is precisely where construction revenue management needs to move from a QS's personal tracking habits to a system-level discipline that doesn't depend on any one person's memory or workload that week.
What "Pending Billable" Changes
Most systems treat a variation as either approved or not approved. That binary status is where a lot of construction revenue leakage hides, because unpriced or unapproved work simply falls out of anyone's revenue view until someone remembers to chase it.
A pending billable status changes that. The moment a variation is initiated, whether from a verbal instruction, a site diary entry, or a formal request, it enters the commercial record with a status that keeps it visible on revenue reports, even before it's priced or approved. It doesn't disappear into a separate log that only the QS checks. It shows up on the same dashboard as everything else that's owed.
This does two things. First, it stops work from falling out of the revenue conversation just because the paperwork hasn't caught up yet. Second, it puts a visible age against every unpriced item, so a variation that's been pending for six weeks stands out instead of blending into a long list nobody scrolls to the bottom of.
How Xpedeon Flags Construction Revenue Leakage
Xpedeon tracks variations from the moment they're initiated, not from the moment they're approved, closing the exact gap where construction revenue leakage usually starts. Every variation carries a pending billable status as soon as it enters the system, so unpriced or unapproved work stays visible on revenue reports instead of falling out of billing entirely. This connects directly into the same construction contract management data behind scope changes and progress claims, so a variation raised on site shows up commercially the same day, not weeks later.
Commercial and finance teams get a live view of every pending billable variation across a project or an entire portfolio, aged by how long it's been sitting since initiation. Pending billable variations don't get buried in a separate log only the QS checks. They sit on the same dashboard as everything else that's owed, which means a variation that's been open for two weeks looks very different to one open for two months, and nobody has to go looking for the old ones. The same real-time discipline runs through Xpedeon's approach to construction cost value reconciliation, where variation status feeds directly into the live commercial position instead of waiting for a month-end reconciliation to surface it.
For contractors running multiple concurrent projects, this turns construction variation tracking from a QS-level administrative task into a portfolio-level revenue control, the same shift we've written about in the context of reducing margin leakage in construction more broadly, except here the focus sits squarely on revenue recognition rather than cost.
The Takeaway
Construction revenue leakage rarely comes as a single dramatic write-off. It builds from dozens of small unpriced and unapproved variations, each one reasonable on its own, quietly falling out of anyone's active attention until a project closes and the money is gone for good.
Getting ahead of it means giving every variation a visible, aged status the day it's instructed, so nothing sits invisible long enough to become unrecoverable, rather than chasing harder once things have already gone wrong. The businesses that consistently avoid construction revenue leakage don't necessarily run fewer variations. They enter every variation into the commercial record the same day it's instructed, priced or not, approved or not, the same discipline covered in our piece on the cost of late variation orders.
Xpedeon keeps every variation visible from initiation to invoice, so construction revenue management stops depending on someone remembering to chase an old change order before it's too late to recover.