The Proof Gap: When Everyone Agrees the Work Happened

On most disputed items at final account, nobody is arguing about whether the work happened. The crew was there. The work is built. Everyone on both sides can see it.

The argument is about something else. Can you prove why it happened? Who directed it? What it changed? And did you do what the contract required to be entitled to raise it?

The distance between "everyone knows" and "we can show it" is the proof gap. It is where a surprising amount of margin goes.

How the gap opens

The proof gap rarely comes from a single failure. It builds up from ordinary days on a busy job.

A direction is given verbally on site and confirmed, if at all, in a meeting note. An RFI response changes a sequence, and the cost of that change is never connected back to it. A notice is due within a set number of days of an event, and the event is recorded in one place while the notice requirement sits in the conditions of contract. Each piece exists. They are just never put together while the people involved still remember how they fit.

By the time someone needs to put them together, the project has moved on. The work moved. The commercial didn't.

Why it's hard to see from the inside

Project teams are not short on judgment. An experienced project executive can usually smell where the exposure is. What they don't have is the time to trace every obligation back to its source and check whether the evidence to support it actually exists.

So the gap stays invisible until someone outside the team asks for the backup. Then it becomes very visible, very quickly.

Closing the gap starts with the contract

The instinct is to start with the evidence: gather the records and see what they show. It works better the other way round.

Start with what the contract requires. For each obligation, ask:

1. What exactly does the requirement say, and where is it written?
2. Who owes it?
3. What would prove it was met?
4. Is that proof on file, and where?

That last question is where the proof gap shows itself, one item at a time, with a clear next step for each. Some items will be fully supported. Some will need a document found. Some will have nothing behind them, and it is far better to know that before the account is agreed than after.

Don't wait for closeout

At closeout, nobody needs convincing that there's a problem. The unresolved items are in front of everyone. But by then the trail has gone cold and the people who could fill the gaps may be on another job.

The teams that see what can be reconstructed at the end usually ask the same question next: why weren't we doing this while the job was running?

Halozen works through that list with your team: every obligation cited to the clause and page, what would prove it, and whether that evidence exists. Your team decides what to pursue. A finding nobody owns goes nowhere, so each one comes with a state and an owner.