A practical, structured guide to retrospective delay analysis for EPC, construction, and complex delivery projects.
Focus | How Window Analysis is used to assess Extension of Time entitlement in a defendable and practical manner. |
Includes | Methodology, common challenges, key deliverables, and how AHPMC can support claims and forensic schedule reviews. |
Introduction
In complex EPC and construction projects, delays are almost inevitable. What often determines the outcome, however, is not merely the occurrence of delay, but how effectively it is analysed, demonstrated, and communicated.
Extension of Time (EoT) assessments require a methodology that is structured, evidence-based, and defensible. Among the recognised retrospective delay analysis techniques, Window Analysis remains one of the most reliable approaches for understanding how delay evolved over the life of the project.
This guide explains the concept of EoT Window Analysis, outlines the practical methodology, and highlights the key deliverables that project teams, planners, and claims professionals should expect from a professional study.
What is Extension of Time (EoT)?
An Extension of Time is a contractual mechanism that allows the completion date of a project to be extended when delay occurs due to reasons beyond the contractor’s control, or for reasons that contractually entitle a time adjustment.
Typical causes include scope growth during execution, delayed approvals, client-driven changes, late information, interface issues with other parties, supply chain disruption, and force majeure events.
Without a proper delay analysis, EoT claims can quickly become subjective, disputed, or rejected. This is why the chosen methodology matters as much as the events themselves.
What is Window Analysis?
Window Analysis is a retrospective delay analysis technique in which the project timeline is divided into defined time periods, called windows, and delay is assessed sequentially from one window to the next.
Rather than viewing the project as one single block of time, this method studies how the status of the works changed during each period, what the critical path was at that point, what delays occurred, and how those delays influenced the forecast completion date.
Because it reflects actual progress and changing project conditions over time, Window Analysis is widely regarded as more realistic than simplistic before-and-after comparisons.
Why Window Analysis is Preferred
- It reflects actual project progress as the job unfolded, instead of relying only on hindsight.
- It captures dynamic changes to the critical path from one period to another.
- It helps allocate delay responsibility on a fact-based and sequential basis.
- It is widely used in claims preparation, dispute resolution, and arbitration support.
- It can be adapted for projects where there are multiple updates, frequent changes, and evolving priorities.
Step-by-Step Methodology for Window Analysis
1. Establish the Approved Baseline
The starting point should be the approved baseline schedule, normally at Level 3 or Level 4, with clearly defined milestones, logic links, calendars, and the original contractual completion date. This forms the reference against which subsequent delay is assessed.
2. Define the Analysis Windows
The total duration is divided into logical analysis windows. These may be monthly, milestone-based, phase-based, or aligned to the project’s regular reporting cycle such as weekly or monthly progress reporting. The window selection should suit the project’s reporting rhythm and the availability of records.
3. Update the Schedule for Each Window
For each period, the schedule should be updated to reflect actual progress, revised remaining durations, status dates, approved changes, and any relevant logic revisions. This creates a realistic snapshot of the project status at the end of each window.
4. Identify Delay Events
Within each window, the analyst identifies the delay events that affected progress. These may include late approvals, procurement delay, design changes, access restrictions, interface problems, or disruption caused by external events. Each event should be linked to supporting records and assessed for contractual relevance.
5. Track Critical Path Changes
A key strength of Window Analysis is that it recognises the critical path may change over time. An activity that was non-critical earlier may become critical later. The analysis therefore needs to identify the driving path in each window before assigning time impact.
6. Perform Window-wise Impact Assessment
The delay effect in each window is evaluated by comparing planned progress against actual status and examining how each relevant event influenced forecast completion. This helps quantify delay incrementally rather than as one global assumption.
7. Assess Concurrency and Calculate Net EoT
Once window-wise effects are established, overlapping delays and concurrent events should be reviewed carefully. The final recommendation should identify the net extension of time entitlement after considering concurrency, overlap, and contractual principles.
Key Deliverables for Window Analysis
A professional Window Analysis should not end with a conclusion alone. It should produce a set of structured, reviewable, and defendable outputs that can support internal management decisions, client submissions, and formal claims discussions.
Deliverable | Purpose / Content |
1. Delay Analysis Report | Executive summary, project background, methodology adopted, assumptions, limitations, and detailed findings. |
2. Window-wise Analysis Summary | Defined windows, planned versus actual progress, delay events identified, and milestone impact for each period. |
3. Critical Path Evolution Report | The critical path for each window and how the driving activities changed over time. |
4. Delay Event Register | A structured log of delay events showing dates, responsibility, classification, and documentary references. |
5. EoT Entitlement Calculation | Window-wise quantification of delay, concurrency review, and the final recommended EoT in days. |
6. Schedule Comparison Outputs | Baseline versus updated schedule comparisons, impacted schedules, and Primavera P6 support files or PDF outputs. |
7. Narrative Justification Report | A clear explanation of what caused the delay, when it happened, and how it affected completion. |
8. Supporting Documentation Dossier | Supporting records such as approved baseline, progress updates, correspondence, variation records, and site evidence. |
9. Visual Dashboards | Optional but valuable charts showing delay trends, milestone slippage, or cumulative impact by window. |
10. Final EoT Recommendation Statement | A concise closing statement summarising total entitlement, reasoning, and any commercial or contractual implications. |
Why These Deliverables Matter
A strong Window Analysis is not only about technical calculation. It is also about clarity, traceability, and defendability.
Well-prepared deliverables help decision-makers understand the delay story quickly, improve the chances of client acceptance, and provide a stronger basis during negotiations, claims reviews, or dispute proceedings.
Practical Challenges in Real Projects
In many live projects, the analysis is complicated by missing updates, unrealistic baselines, poor progress records, undocumented logic changes, and overlapping delays.
In such situations, the analyst may need to reconstruct schedule history, validate records from multiple sources, and clearly document assumptions and limitations before issuing conclusions.
When Should You Use Window Analysis?
Window Analysis is particularly useful for long-duration EPC and construction projects, jobs with frequent scope changes, projects with multiple schedule updates, disputed delay claims, and matters heading toward formal review or arbitration.
How Agile and Hybrid PMC Can Support
Agile and Hybrid PMC supports clients with EoT Window Analysis, schedule reconstruction, Time Impact Analysis, forensic schedule review, and claim narrative preparation.
Depending on customer needs, support can be provided through remote planning services or through an embedded planning resource model integrated with the project team.
Conclusion
Window Analysis is more than a scheduling exercise. It is a structured approach to uncovering the true sequence of delay and demonstrating its effect on project completion in a professional and defensible way.
When executed properly, it strengthens EoT claims, improves transparency, and reduces avoidable disputes. In complex modern projects, robust delay analysis is no longer optional; it is essential.
Call to Action
Facing delay-related challenges in your project? Need support in evaluating EoT entitlement, reconstructing schedule history, or preparing a professional delay claim? Agile and Hybrid PMC can support your team with practical, flexible, and project-focused planning expertise.
Categories
- Project Planning
- Project Initiation
- Monitoring and Controlling
