Most Extension of Time claims are judged by their final submission — the report, the delay analysis, the number of days claimed and the supporting records.
By the time that document exists, however, much of the strength of the contractual position has already been created — or lost.
An EOT claim is not a single event prepared at the end of a delay. It is a sequence of decisions that begins when the delaying event is first identified and continues through notice, contemporaneous recording, interim assessment and, eventually, final substantiation.
Treating EOT as a document to be written rather than a position to be managed is where many claims quietly lose strength.
THE SEQUENCE, NOT THE SUBMISSION
A defensible EOT position is normally built through several distinct stages.
Notice — identifying the event and protecting the contractual right within the applicable notice requirements, often before its full impact on completion is known.
Contemporaneous recording — capturing what happened while it is happening: programme status, site records, instructions, correspondence, progress information and the state of the critical path at the relevant time.
Interim assessment — developing an early and necessarily provisional view of the likely time impact as the event and its consequences evolve.
Progressive substantiation — updating the contractual and programme position where the effects of the event continue or become clearer.
Final substantiation — demonstrating the actual impact once the event and its consequences can be assessed with sufficient evidence.
Each stage depends on what happened before it. A strong final submission cannot recreate a notice that was never issued. A well-drafted notice cannot substitute for contemporaneous records that were never maintained. And sophisticated delay analysis cannot compensate for programme evidence that does not reliably show what was driving completion when the event occurred.
The eventual submission is therefore only the final expression of a position that should have been managed throughout the life of the event.
WHEN TO NOTIFY AND WHEN TO SUBSTANTIATE ARE DIFFERENT QUESTIONS
One of the most common mistakes in EOT management is waiting until the full impact is known before taking contractual action.
Many standard contract mechanisms — including FIDIC forms — are built around the opposite principle: early notification followed by progressively developed substantiation as the consequences become clearer.
Waiting for certainty before notifying can jeopardise — and, depending on the applicable contractual time bar and governing law, potentially extinguish — an entitlement before the full impact is even known.
But the reverse problem also exists. Trying to finalise a fully quantified EOT claim too early, while the event is still developing, may produce an assessment based on assumptions that later prove wrong. The critical path may change. Mitigation may alter the outcome. Other delay events may intervene. An effect initially expected to extend completion may later be absorbed, while an apparently minor event may ultimately become critical. A prematurely finalised claim may therefore require substantial revision as the project evolves.
The better principle is simpler: protect the right early, build the evidence progressively, finalise the position when the facts allow.
SUBSTANTIATION IS ABOUT CAUSATION, NOT JUST DELAY
Showing that completion moved by six weeks does not demonstrate that a particular event caused six weeks of delay. That distinction sits at the heart of EOT substantiation.
A credible position normally needs to establish what the relevant programme position was when the event occurred, what was driving completion at that time, how the event affected the critical or near-critical path, whether available float absorbed some or all of the impact, whether mitigation changed the resulting delay, whether other events were affecting the same period, and whether the event actually moved the contractual completion position.
This is particularly important where several delay events overlap. Overlap in time is not automatically concurrent delay. The analysis still needs to establish which events were effective causes of Delay to Completion and how they interacted with the programme position at the relevant time.
Ignoring those interactions does not strengthen an EOT submission. It simply leaves the issue for the other party — or eventually an opposing expert — to identify.
DELAY ANALYSIS METHODOLOGY FOLLOWS THE CONTRACT AND THE RECORDS
EOT strategy and delay analysis are closely connected, but methodology should not be selected simply because one technique appears more sophisticated than another.
Time-impact analysis, windows analysis, as-planned versus as-built analysis and other methodologies answer different questions and require different levels of programme and contemporaneous evidence. The appropriate approach depends on the contractual mechanism, the purpose of the assessment, the timing of the analysis, the quality of the baseline and programme updates, the availability of contemporaneous records, and what causation actually needs to be demonstrated.
A project with well-maintained programme updates, traceable logic changes and properly recorded events may support detailed period-by-period analysis. A project that never maintained that record may leave the analyst dependent on more retrospective reconstruction.
The methodology should therefore be considered as part of the EOT strategy while the project is live. But ultimately, the method must follow the evidence the project can credibly support — not the other way around.
THE ANALYST CANNOT RECREATE A POSITION THAT WAS NEVER PRESERVED
A skilled delay analyst can reconstruct a great deal from incomplete information. That does not make reconstructed evidence equivalent to contemporaneous evidence.
Consider two projects experiencing the same delaying event. On the first, the event is notified when identified, the programme position is preserved, instructions and correspondence are linked to the event, progress records show what happened, programme updates show how the critical path evolved, and interim impacts are periodically reassessed. On the second, the issue is discussed in meetings, the programme continues to be updated without preserving the event logic, correspondence is fragmented, no clear event chronology is maintained, and the contractual position is considered only once a claim becomes necessary.
The underlying entitlement may initially have been identical. The ability to demonstrate it later is not. That difference was created during project execution, not when the final claim was drafted.
THE COST OF TREATING EOT AS A REACTIVE EXERCISE
When EOT is treated as something to prepare only once a dispute becomes likely, several problems often arrive together. Notice requirements may already have become an issue. Programme updates may no longer preserve the original logic. The people who understood the event may have moved to other projects. Site records may describe progress but not causation. Instructions may exist without a clear link to programme impact. Concurrent or overlapping events may have become difficult to separate.
The final submission then becomes an exercise in reconstruction — and reconstruction is usually more expensive, slower and more vulnerable to challenge than preserving the position while the project is live.
None of this necessarily results from one major failure. It is usually the cumulative consequence of many small decisions: a notice left until next week, an update submitted without properly recording the event, an instruction discussed but not linked to its programme consequences, a delay resolved operationally without documenting what caused it, an interim position never revisited. Individually, each may appear minor. Collectively, they determine the quality of the eventual EOT position.
EOT STRATEGY IS A LIVE MANAGEMENT DISCIPLINE
The practical implication is that EOT strategy should run alongside project delivery. It should connect event identification, notice, contemporaneous records, programme impact, interim assessment, updated position, and final substantiation.
This does not mean turning every project problem into a claim. It means recognising that, when an event may affect contractual completion, the project needs enough discipline to preserve the position while the facts are still available.
The same principle applies across contract administration more generally: the position that ultimately matters is usually protected long before anyone knows it will be tested.
THE PRINCIPLE
An EOT claim is not written at the end of a delay. It is built, stage by stage, from the moment the delaying event is identified.
Notice protects the potential right. Contemporaneous records preserve the facts. Programme administration preserves the ability to demonstrate causation. Interim assessments keep the position aligned with the way the event actually develops. Final substantiation brings those elements together into the contractual case.
The strength of the eventual submission is therefore largely determined by decisions made long before anyone starts drafting it.
EOT strategy is not a submission. It is a sequence. And managing that sequence while the project is live is usually far stronger than trying to reconstruct it once the dispute has already begun.
HOW ACC TRUST CAN SUPPORT
ACC TRUST supports contractors, employers and project teams in managing EOT positions from early event identification through to final substantiation, including:
identifying potential delay events and applicable notice requirements;
reviewing contractual programme and record-keeping requirements;
establishing contemporaneous records capable of supporting later causation analysis;
supporting interim EOT assessments as events develop;
reviewing programme position and critical-path impact at the relevant time;
assessing overlapping and concurrent delay events;
selecting delay analysis methodologies appropriate to the contract, purpose and available records;
reviewing EOT submissions before issue;
supporting claim defence where entitlement or causation is disputed.
The objective is not simply to produce a stronger final document. It is to preserve an EOT position that remains defensible at every stage at which it may need to be tested.
ACC TRUST works with live project teams before EOT positions become reconstruction exercises — because protecting the record while the event is happening is usually more effective than rebuilding it after the dispute begins.
For independent support on EOT strategy, claims and contract administration:
Explore ACC TRUST services:
→ https://acctrust.ro/services
Discuss a specific project:
→ office@acctrust.ro
About ACC Trust Insights
ACC Trust Insights is the knowledge centre for Commercial & Contract Governance, Project Delivery and Risk Management in complex construction, infrastructure and energy projects.
Explore all articles:
→ https://insights.acctrust.ro
ACC TRUST
Commercial & Contract Governance Advisory
Property · Infrastructure · Energy
office@acctrust.ro