Claims · Methodology

Delay Analysis Techniques: Selecting and Applying the Right Methodology

How to choose between CPM, APAB, TIA, and Windows Analysis. Strengths, limitations, and best practice application in FIDIC arbitration.

7 min read · Updated 24/04/2026

In this article

1. Delay Analysis Techniques: Overview and Application
2. Common Delay Analysis Techniques: Strengths and Limitations
3. Selecting the Right Methodology for Your Dispute
4. Common Pitfalls and Overlooked Issues
5. Best Practice Application in FIDIC Arbitration
6. Expert Witness Assessment and Credibility

Key takeaway

No single delay analysis technique is universally optimal. The choice depends on project complexity, data quality, and the nature of delay events. Different methodologies can yield different conclusions when applied to the same facts. Arbitrators assess not just the methodology, but the quality of data, assumptions made, and reasonableness of conclusions. Expert credibility depends on transparent methodology, honest acknowledgment of limitations, and evidence-based analysis.

1. Delay Analysis Techniques: Overview and Application

Delay Analysis Techniques (DATs) are methodologies used to investigate project delays, identify causation, quantify the time impact of delay events, and allocate responsibility between parties. The choice of technique is critical: different methodologies can produce different conclusions when applied to the same delay data.

The purpose of delay analysis in FIDIC arbitration is to establish:

• Causation: Which party’s acts or omissions caused the delay?
• Time Impact: How many calendar days of delay resulted from each causative event?
• Allocation: Is the delay excusable (no LD), excusable and compensable (EOT + prolongation costs), or culpable (LD applied)?

The selection of methodology should be informed by:

• Quality and completeness of project documentation (schedules, progress reports, correspondence).
• Complexity of the project and number of delay events.
• Presence of concurrent delays.
• Availability of baseline schedules and contemporaneous records.
• Software limitations and functionality.

2. Common Delay Analysis Techniques: Strengths and Limitations

Critical Path Method (CPM)

CPM identifies the longest sequence of dependent activities (the critical path) and any delay to a critical path activity delays project completion. CPM is foundational to most delay analysis.

Strengths: Clearly identifies which activities are critical; provides visual representation of project logic and dependencies.

Limitations: CPM alone does not account for what actually happened (as-built data); it requires comparison to actual progress to assess delay events.

As-Planned vs. As-Built Method (APAB)

APAB compares the original (contract baseline) schedule to what actually occurred (as-built progress). Gaps between planned and actual dates are identified as delays.

Strengths: Simple and intuitive; shows actual project performance against plan; useful for identifying the overall delay and when it occurred.

Limitations: Does not isolate individual delay events or their independent impact; cannot distinguish between concurrent delays; cannot show what would have happened if a specific event had not occurred.

Time Impact Analysis (TIA)

TIA is a retrospective technique that models each delay event individually, updating the schedule to reflect the impact of each event in isolation. The expert calculates the cumulative time impact of each event.

Strengths: Isolates the impact of individual events; provides clear “before and after” comparison for each event; well-suited to multiple sequential delay events.

Limitations: Requires detailed baseline schedule and periodic updates; difficult to apply when contemporaneous updates are unavailable; can understate impacts if activity sequences changed during the project (hindsight bias).

Impacted As-Planned Method (IAP)

IAP modifies the contract baseline schedule to incorporate the effects of delay events, without reference to as-built progress. It assesses how the delay events would have impacted the plan if they had occurred as initially scheduled.

Strengths: Uses the contract baseline (which both parties approved); allows analysis even if as-built data is incomplete.

Limitations: Ignores actual project progress; assumes the original plan would have been followed (which rarely happens); can overstate delay impacts if actual progress diverged significantly from plan; less credible if significant as-built data is available.

Windows Analysis

Windows Analysis divides the project into time periods (months or quarters) and analyzes the critical path, delay events, and delays within each window. For each window, the expert identifies what was critical and what delays occurred.

Strengths: Addresses the reality that the critical path can shift during project execution; accounts for changing circumstances as the project progresses; effective for long or complex projects with many changes.

Limitations: Requires high-quality, detailed monthly updates; can be labour-intensive; requires clear documentation of project status at the end of each window.

3. Selecting the Right Methodology for Your Dispute

There is no universally “best” technique. Selection depends on your specific circumstances:

4. Common Pitfalls and Overlooked Issues

Even with the right methodology, common errors undermine delay analysis:

• Poor Baseline Schedule: If the original schedule is incomplete, illogical, or lacked critical path visibility, all downstream analysis is compromised. Always assess the quality of the baseline.
• Missing or Incomplete As-Built Data: Lack of contemporaneous records (daily site reports, progress photos, meeting minutes) makes it impossible to verify actual project progress. Without good as-built data, delay analysis relies on assumptions.
• Inadequate Handling of Concurrent Delays: Different techniques treat concurrent delays differently. If your methodology does not explicitly address concurrency, conclusions may be unreliable.
• Resource Loading and Levelling Issues: Some delays result not from logic constraints but from resource availability. If the schedule does not reflect resource constraints, delay analysis may be distorted.
• Software Limitations: Scheduling software varies in functionality. Some software may have bugs or limitations in calculating critical path. The expert must understand the tool being used and its limitations.
• Hindsight Bias: Experts must analyse delay as it would have appeared at the time it occurred, not with knowledge of later events. Retrospective analysis can introduce hindsight bias.

5. Best Practice Application in FIDIC Arbitration

To produce delay analysis that will be persuasive in arbitration:

• Document Your Methodology Clearly: Explain the technique chosen, why it was selected for this project, and what assumptions it relies on. Be transparent about limitations.
• Use Multiple Corroborating Techniques: If time and resources permit, use two complementary techniques (e.g., TIA + Windows) and reconcile differences. Agreement between methods strengthens credibility.
• Maintain Empirical Checks: At each step, ask “Does this look right?” Does the baseline schedule reflect the actual project scope? Do the as-built dates align with known events? If something appears inconsistent, investigate and explain.
• Acknowledge Data Quality Issues: If documentation is incomplete or schedules are poorly developed, say so. Explaining how you worked around limitations is more credible than ignoring them.
• Apply Sensitivity Analysis: Test your conclusions by varying key assumptions (e.g., if activity X was 5 days longer or shorter, how would conclusions change?). Show that your conclusions are robust to reasonable variations.
• Engage with the Contract: Base your analysis on FIDIC contract language. Explain how your findings relate to the party’s entitlements under Clause 20 (EOT) or other relevant provisions.

6. Expert Witness Assessment and Credibility

In arbitration, the quality of expert evidence depends not just on the technique, but on the expert’s credibility and the reasonableness of conclusions.

Arbitrators assess expert evidence by considering:

• Independence and Impartiality: Does the expert have a financial interest in the outcome? Has the expert acknowledged competing expert opinions fairly?
• Qualifications: Does the expert have experience in delay analysis, FIDIC contracts, and the specific type of project?
• Methodology Justification: Is the choice of technique well-justified? Are limitations acknowledged?
• Data Transparency: Are the sources of data clearly identified? Can the analysis be reproduced from the documentation provided?
• Reasonableness of Conclusions: Do the conclusions follow logically from the analysis? Are they consistent with common sense and industry practice?
• Resilience to Cross-Examination: Can the expert defend the analysis against challenges? Does the expert avoid overstating certainty?

Experts who acknowledge uncertainty, explain trade-offs between methodologies, and admit limitations are often more credible than those claiming certainty. Arbitrators value honest, measured expert evidence over partisan advocacy dressed in technical language.

Strengthen Your Delay Analysis with Expert Methodology

Different delay analysis techniques can yield different conclusions. The credibility of your claim depends on selecting the right methodology, applying it transparently, and defending your conclusions against expert challenge. Our experienced delay analysts understand the strengths and limitations of each technique and can tailor the approach to your specific dispute. We also review and critique opposing expert analysis to identify methodological weaknesses and provide counter-expert evidence for arbitration.

Book a 30-Minute Case Assessment →

Offices in Dubai · Available for instructions across the UAE and GCC