Why Your Backcharges Never Get Collected (And What Fixes It)

You have a legitimate backcharge. The sub damaged the finished work, or blew the schedule, or left a mess for someone else to clean up. The cost is real, it's documented in someone's memory, and it's yours to recover.

Then thirty days pass, and it isn't.

Nobody disputes that the damage happened. Nobody argues the cost was invented. The claim simply stops being collectible somewhere between the incident and the invoice — and almost no one on the job noticed the moment it happened, because nothing about that moment looked like a deadline.

The Claim Was Never the Problem

Most backcharges that go uncollected weren't weak claims. They were valid costs that nobody wrote down and served to the right party inside the window the contract actually allows.

Industry benchmarks suggest that under 20% of recoverable backcharges are actually collected on a typical job. That's not a dispute-resolution failure — most of these charges are never even formally raised. The cost gets absorbed into overhead, and the sub who caused it never sees a line item.

The reason is almost always procedural, not factual. A backcharge has a notice clock attached to it, usually specified in the subcontract: notify within X days, with specifics, or the right to recover lapses. Everyone on-site knows the damage happened. Almost nobody captures it with a timestamp on day one.

That gap between "everyone knows" and "someone recorded it formally, on time" is where nearly all of the uncollected 80% goes. It isn't lost to bad-faith subs contesting fair claims. It's lost to a process that has no owner for the fifteen minutes of documentation that would have made the claim enforceable.

Why "Everyone Knows" Isn't Evidence

A backcharge that only exists as a verbal understanding between a super and a sub is not a backcharge — it's a memory, and memories don't survive a dispute.

Documenting a cost isn't the same as protecting the right to collect it. By the time someone gets around to writing the change order, weeks have usually gone by. The photo that would have proven the damage was never taken. The notice that should have gone out within the contractual window went out late, if it went out at all — and a late notice, however obviously true the underlying claim is, is often unenforceable on its face.

This is where the compounding starts. Consider what typically happens between the incident and the (attempted) collection:

The field team notices the damage or overrun but treats it as a verbal note, not a formal record. Days pass while the item competes with everything else on the punch list for attention. The formal backcharge notice, when it finally goes out, misses the contractual window. The sub disputes it — reasonably, since there's no timestamped record establishing when the issue occurred or that notice was timely. The GC absorbs the cost rather than litigate a claim it can no longer prove.

None of those five steps requires anyone to be careless. It's the default outcome of a process that depends on a busy PM remembering to formalize something before a deadline nobody is tracking in real time.

Zoom out and the pattern repeats at the portfolio level, not just the incident level. A GC running a dozen active sites isn't failing to collect one backcharge — it's failing to collect the same category of claim, in the same way, on every site, every month. That's not a training problem for one PM. It's a structural gap in how the notice obligation gets triggered in the first place.

Under 20% of recoverable backcharges are actually collected on the typical job — most expire before a formal notice ever goes out.

The Mechanism That Actually Protects Recovery

The fix isn't a stricter policy reminding PMs to document backcharges faster. Policies compete with everything else on a PM's desk, and lose. The fix is removing the dependency on someone remembering to act inside a clock they aren't watching.

That means capturing the triggering event — the damage, the overrun, the missed condition — the moment it's reported, with a timestamp, photo, and note attached automatically, not filed later from memory. It means the notice to the responsible party goes out inside the contractual window as a matter of course, not as a task that has to survive a PM's to-do list. And it means every piece of that record — the initial capture, the notice, the sub's response, any negotiation that follows — lives in one auditable trail instead of scattered across texts, emails, and someone's recollection.

A backcharge you can't prove was ever timely isn't a backcharge. It's a write-off with extra steps.

This is the same principle behind Lexlabs' broader approach to operational exceptions: the event that matters gets logged the moment it happens, not reconstructed after the fact. For backcharges specifically, that means the notice clock starts on day one instead of day fifteen, and the evidence bundle — timestamps, photos, correspondence — is already assembled by the time anyone needs to negotiate or defend the claim.

Practically, that looks like a short list of things happening automatically instead of manually:

The field report of damage, an overrun, or a missed condition is captured with a timestamp and photo at the point it's reported — not reconstructed from memory a week later. Formal notice to the responsible sub is generated and sent inside the contract's notice window, without depending on a PM remembering the clause or the deadline. The sub's response — acknowledgment, dispute, or partial concession — is logged against the same record, so the negotiation has a paper trail from its first message. If the claim needs to escalate, the full bundle — incident, notice, correspondence — is already assembled rather than pieced together under deadline pressure.

Each of those steps is small on its own. What makes them valuable is that none of them depend on a person's memory or bandwidth on the day it matters most.

What Changes When Notice Is Automatic

Where this mechanism is in place, the recovery rate doesn't inch up. It moves into a different range entirely.

Backcharge recovery rate: under 20% collected industry baseline, versus 70-90% collected with Lexlabs. Notice timing: filed after the fact, often past the contractual window, versus timestamped automatically at the point of incident. Evidence for disputed claims: reconstructed from memory, texts, and partial photos, versus bundled automatically — photos, notice, correspondence.

The difference isn't that suppliers get tougher on disputes once notice is timely and evidence is complete — it's that there's rarely a dispute left to have. A backcharge with a timestamped photo, a notice sent inside the contractual window, and a documented trail of the exchange that followed is a very different conversation than "we're pretty sure this happened three weeks ago."

There's also a relationship benefit that's easy to miss. A sub who receives a clear, timely, well-documented notice is far more likely to acknowledge and resolve the charge without friction than one who gets a vague, late demand months after the fact. Fast, specific notice reads as fair. Slow, reconstructed notice reads as an ambush — even when the underlying claim is completely legitimate. Protecting the recovery window isn't just about the dollars; it's about keeping supplier relationships workable across the life of the project.

What This Means for the Portfolio, Not Just the Job

For an Ops Director looking at this across a book of projects rather than one site, backcharge recovery isn't a line-item curiosity — it's part of the same Cost/CPI category as cost per schedule break and invoice accuracy. Margin doesn't leak in one dramatic event. It leaks in a hundred small, valid claims that were never formalized in time, repeated across every site in the portfolio, every month.

Fixing the notice-and-evidence mechanism on one job protects that job's margin. Fixing it structurally — so the clock starts automatically everywhere, not just where a particularly diligent PM happens to be paying attention — is what turns backcharge recovery from a rounding error into a real, repeatable line of recovered margin.

See how Lexlabs works for construction cost recovery. Contact us to request a demo focused on Backcharge Recovery.