I’ve reviewed a lot of delay claims.
And I want to share something that doesn’t get said enough.
The claim that looked strongest on paper wasn’t always the one that held up.
The claim that held up was the one with the best records.
Not the best argument.
The best records.
Here’s what I mean.
I’ve seen contractors with a genuine, legitimate entitlement walk away with nothing.
Not because they were wrong.
Because they couldn’t prove it.
No contemporaneous notices.
No site diaries that matched the story they were telling.
No photographs dated to the right period.
Delay notices sent but to the wrong person under the contract.
The entitlement existed.
The evidence didn’t.
And I’ve seen the opposite.
A principal with a strong contractual position undermined completely because their own records showed they knew about the issue three months before they acted on it.
One document.
One email chain.
One meeting minute that said the wrong thing at the wrong time.
That’s how claims are won and lost.
Not in the analysis.
In the records that existed before anyone knew there was going to be a claim.
This is what most project teams don’t understand about delay and disputes:
The claim doesn’t start when the lawyer gets involved.
It starts on day one of the project.
Every RFI response.
Every instruction issued.
Every time someone said “we’ll sort it out later.”
Later is now.
And the record either supports you or it doesn’t.
Three things every project team should be doing from day one:
1. Issue notices when the contract requires it.
Not when it feels comfortable.
Not when the relationship allows it.
When the contract says to.
2. Document decisions not just outcomes.
Who was in the room. What was discussed. What was agreed.
The decision trail matters as much as the decision.
3. Keep the schedule honest.
A schedule that reflects reality – updated contemporaneously is one of the most powerful pieces of evidence in a delay claim.
A schedule adjusted after the fact is one of the most damaging.
You don’t build a strong claim under pressure.
You build it quietly, consistently, from the first day on site.
Contract first, method second.