When a project slips, the real fight usually starts after the missed milestone. That is when parties move from site records and revised schedules to a harder question: which delay actually changed the completion date, and who carries the risk? Any serious guide to delay analysis methods has to start there, because delay disputes are not won by broad claims of disruption. They are won by proving causation with a method the tribunal, court, or dispute board can trust.
For contractors, developers, and project owners, delay analysis is not just a technical scheduling exercise. It is often the backbone of extension of time claims, liquidated damages defenses, prolongation cost arguments, and termination disputes. The right method can clarify entitlement. The wrong method can weaken a strong case by overstating certainty, ignoring poor records, or analyzing the wrong critical path.
Why a guide to delay analysis methods matters in disputes
Delay analysis sits at the intersection of planning, contract administration, and evidence. In major construction and infrastructure disputes, especially under FIDIC-based contracts, the analysis method chosen will shape the story of the case. It affects how experts build opinions, how counsel frames causation, and how decision-makers test credibility.
That choice is rarely neutral. Some methods work best when records are detailed and baseline programs are reliable. Others are used because the project data is incomplete and the parties need a retrospective reconstruction. The method must fit the facts, not the preference of the side advancing the claim.
This is where many disputes go off track. A party selects a method because it appears sophisticated, not because it matches the evidence. Tribunals tend to see through that. They are usually more persuaded by a disciplined, proportionate analysis grounded in contemporaneous records than by a complex model built on weak assumptions.
The main delay analysis methods
As-planned versus as-built
This is one of the simplest approaches. It compares the original planned schedule against what actually happened on site. The attraction is obvious: it is accessible, relatively fast, and easy to explain.
Its weakness is just as obvious. It often treats the baseline program as if it remained valid throughout the project, even when scope changed, sequencing shifted, or logic links were revised in practice. For that reason, it can be useful as a high-level starting point, but it is often too blunt to carry a high-value delay claim on its own.
Where records are limited, this method may still have value. But if the dispute turns on critical delay, concurrency, or shifting critical paths, the analysis usually needs more rigor.
Impacted as-planned
This method starts with the planned schedule and inserts delay events into it to model the effect those events would have had on completion. It is often used prospectively, particularly when assessing time entitlement close to the events in question.
The commercial appeal is that it can isolate the effect of employer-risk events in a structured way. The problem is that it often assumes the original program was realistic and that later project performance issues do not matter. In a live project, that may be acceptable for interim contract administration. In a final dispute, it may be heavily challenged if actual performance diverged sharply from the plan.
Impacted as-planned analysis tends to be more persuasive where the baseline schedule was sound, updates were limited, and the delaying events occurred relatively early. It is less persuasive where the project evolved substantially or where contractor default later became a major issue.
Collapsed as-built or but-for analysis
This is a retrospective method. It starts with what actually happened, then removes identified delay events to ask a hypothetical question: but for those events, when would the works have finished?
Used carefully, it can be powerful because it is anchored in actual project history rather than forecast logic. That said, it also depends on a credible reconstruction of what would have happened in an alternative scenario. Critics often attack it for being overly theoretical, especially where multiple causes were interacting at the same time.
It may work well in disputes with strong as-built data and a reasonably clear sequence of delaying events. It becomes harder to defend when productivity loss, resequencing, and concurrent issues are widespread.
Time impact analysis
Time impact analysis is often treated as one of the more disciplined methods because it inserts delay events into the schedule updates that existed at the time those events occurred. In principle, that makes it sensitive to the project status known at each relevant moment.
For contract administration, this is frequently a strong choice. It aligns with the idea that extensions of time should be assessed based on contemporaneous information, not hindsight. In dispute proceedings, it can also be compelling if the schedule updates are reliable and consistently maintained.
The catch is practical. Many projects do not have trustworthy updates. Logic is manipulated, progress is entered inconsistently, and critical path reporting becomes more political than technical. If the updates are poor, time impact analysis can look precise while resting on unstable foundations.
Windows analysis
Windows analysis breaks the project into periods and examines delay across those periods using schedule updates and project records. It is a retrospective method that often gives a more nuanced picture of how the critical path changed over time.
In complex disputes, this method is often favored because projects do not remain static. Critical activities shift. Mitigation efforts change outcomes. New employer instructions intersect with contractor performance issues. A windows approach can capture that movement better than a single global comparison.
Its downside is cost and complexity. It requires substantial data, disciplined expert work, and careful explanation. For smaller claims, it may be disproportionate. For large infrastructure or technically dense disputes, it is often worth the effort.
Choosing the right method depends on the evidence
There is no universal winner in any guide to delay analysis methods. The right choice depends on the contract, the project records, the scheduling practice on site, and the issues in dispute.
If the case involves interim entitlement under a live contract, a prospective method may be more appropriate. If the dispute is final and retrospective, the decision-maker may expect an analysis that reflects what actually happened, not just what the baseline predicted. If schedule updates are unreliable, any method that depends heavily on them may be vulnerable. If the baseline itself was flawed, methods built around that baseline may also fail.
This is why legal and expert strategy should be aligned early. Delay analysis is not just an expert appendix prepared near the hearing. It should influence document collection, witness preparation, notice positions, and the framing of causation from the start.
Common points of attack in delay disputes
Even technically sound analyses can fail if they do not address the issues that actually decide entitlement. Concurrency is the most obvious example. If both parties contributed to delay during the same period, the contractual and legal treatment of concurrency matters. An analysis that ignores this will usually be exposed quickly.
The same applies to float ownership, mitigation, and pacing. Some parties assume any movement in completion automatically proves compensable delay. It does not. The claim still has to show that the event affected activities on the critical path, that the contractor complied with contractual notice and record obligations where required, and that the claimed period was not overtaken by another independent cause.
Another frequent weakness is overreliance on scheduling software outputs without enough reference to site reality. Programs matter, but contemporaneous records matter just as much. Daily reports, instructions, meeting minutes, procurement logs, manpower data, testing records, and correspondence often determine whether the expert model reflects the actual project.
Delay analysis in FIDIC and major project contracts
Under FIDIC and similar contract structures, delay analysis often becomes central to extension of time and cost entitlement. The contract may not prescribe a single acceptable methodology, but it does reward disciplined notice, current records, and reasoned demonstration of cause and effect.
That creates a strategic point for both employers and contractors. The party with the cleaner records and the more credible analytical framework usually starts ahead. In practice, disputes are rarely decided by methodology alone. They are decided by the fit between methodology, facts, and contract language.
For cross-border projects and arbitration, that fit matters even more. Different experts may arrive with different methodological preferences shaped by their training and jurisdictional background. Decision-makers are less interested in methodological branding than in whether the approach is transparent, repeatable, and fair to the actual project history.
What decision-makers usually want to see
Courts, tribunals, and dispute boards generally respond well to analysis that is clear about its assumptions and honest about its limits. Overclaiming is dangerous. If records are incomplete, say so and explain how the gaps were addressed. If there are competing critical paths or disputed updates, confront that directly.
A credible delay case does not need to pretend the project was perfectly documented. It does need to show a disciplined chain from event to impact to entitlement. That is where experienced legal and expert teams create value. They do not just select a method. They build a case theory that the method can support under pressure.
On high-stakes projects, delay analysis is not a box to check. It is a core strategic decision with financial consequences that can reshape the dispute. Choose the method that fits the evidence, test it early, and make sure your case can still stand when every assumption is challenged.