Extension of Time Claims: Evidence Beats Argument

Delays are inevitable. Disputes are optional. The difference is rarely theatrical advocacy — it is whether the programme evidence can show cause, effect, and entitlement without rewriting history. Delay analysis and EOT work that survives scrutiny starts from the records and the logic network, not from the conclusion someone needs.

Why arguments lose to evidence

By the time a formal extension of time (EOT) claim is drafted, both sides usually have a story. Only one side typically has a clean baseline, update trail, and delay event register that matches how the job was actually run. SCL Delay and Disruption Protocol thinking — method selection suited to the contract and the records — is useful vocabulary. It is not a substitute for a programme that was credible before the dispute.

If the baseline was fiction, every later analysis inherits the fiction. That is why programme audits before claim preparation are cheaper than forensic heroics after — and why DCMA-style integrity is a floor for analysability, not proof of entitlement (DCMA 14-point: what it catches and misses).

What "programme evidence" means in practice

A maintained baseline and update rhythm. Progress that cannot be reconciled to logic week to week will not suddenly become forensic gold in month eighteen.

Delay events captured early. Date, cause, impacted activities, mitigation tried, and who knew what when. The cheapest claim is the one you never need because early quantification plus transparent engagement turned the event into an agreed adjustment.

Method matched to the question. Impacted-as-planned, time-slice windows, and related approaches each answer different questions and demand different records. Pick the method the contract and the evidence support — then stay honest about limitations. Method shopping after the fact reads as advocacy, not analysis.

Narratives a decision-maker can follow. Boards and principals do not need a planning degree. They need: what changed, what it did to the critical path, what was mitigated, and what entitlement remains.

Live programmes beat post-mortems

The best EOT posture is project controls while the job is alive: variance with cause, a delay register that is not a surprise, and forecasts the site recognises. On Microsoft and Stack programmes we have supported, client-caused delay was absorbed without adversarial positions when the impact was quantified early and the conversation stayed factual. Waiting until practical completion to "build the claim" is how optional disputes become inevitable ones.

Owner-side and contractor-side — same standard

Whether you are preparing a claim or reviewing one, the test is identical: does the analysis follow from the programme and the contemporaneous record, or from a desired date? Owner-side review that only attacks tone without testing logic wastes time; contractor-side claims that only assert effect without a driving path waste goodwill — and usually lose.

What to have before you instruct analysis

1. Baseline and current schedule files with a clear update history
2. Delay event register (even if imperfect — start now)
3. Contract clauses that govern notice, concurrent delay, and mitigation duties
4. A decision on whether you want recovery options priced alongside entitlement

If item one is missing, fix the programme first. Analysis on a broken network produces confident nonsense.

The posture that works

Evidence beats argument. Build the record as you deliver; choose methods that fit the records you actually have; write for decisions, not for theatre. That is how delay stays a commercial adjustment instead of a relationship-ending dispute.

Nomad SPS provides delay analysis and EOT claim programme support across Australia — quantification and narratives that stand up, from planners who have lived the update cycle on hyperscale sites. If time is your number one factor, talk to us.