Choosing the right delay analysis method can determine whether your claim succeeds or fails. Time Impact Analysis (TIA) and Windows Analysis are the two most widely used prospective and retrospective methods in GCC construction disputes. Each has distinct strengths, limitations, and ideal use cases.
This article provides a clear, practical comparison to help project managers, planners, and claims professionals select the most appropriate method for their specific situation.
What is Time Impact Analysis (TIA)?
Time Impact Analysis is a prospective method that models the impact of each delay event by inserting it into the project schedule at the point in time it occurred. The analysis uses the contemporaneous programme — the schedule as it existed at the time of the event — and adds a delay activity (a "fragnet") representing the event. The resulting impact on the critical path and completion date is then measured.
TIA is considered the most robust delay analysis method when reliable schedule updates are available. It respects the sequence of events and reflects the schedule conditions that actually existed when each delay occurred. The SCL Delay and Disruption Protocol identifies TIA as one of the preferred methods for prospective analysis.
What is Windows Analysis?
Windows Analysis divides the project duration into discrete time periods (windows) — typically aligned with schedule update periods, milestone dates, or significant events. Within each window, the analyst compares the planned progress with actual progress to determine what delays occurred, who was responsible, and whether the delay impacted the critical path.
This method is particularly effective for complex projects with multiple delay events from different parties. By isolating each time period, it avoids the "but for" trap of trying to assess all delays at once. Windows Analysis is widely accepted in international arbitration and is endorsed by both the SCL Protocol and AACE Recommended Practices.
Key differences
The fundamental difference is in approach. TIA is event-driven — it analyzes each delay event individually by inserting it into the schedule. Windows Analysis is time-driven — it analyzes all events within defined time periods. TIA requires reliable baseline and updated schedules with proper critical path logic. Windows Analysis can work with less perfect schedule data because it relies on comparing planned versus actual progress within each window.
TIA is generally considered more precise because it models each event at the exact point it occurred. Windows Analysis provides a broader view of delay responsibility over the entire project but may not capture the precise impact of individual events as accurately.
When to use TIA
TIA is the preferred method when reliable contemporaneous schedule updates exist throughout the project, the number of delay events is manageable and each can be clearly defined, the contract requires or the dispute forum expects event-by-event analysis, and you need to demonstrate the precise impact of specific employer-caused delays. It is particularly effective for claims involving a small number of significant delay events — such as late access to site or major design changes — where the event can be clearly modeled as a schedule fragnet.
When to use Windows Analysis
Windows Analysis is the better choice when schedule records are incomplete or inconsistent, there are numerous concurrent delay events from multiple parties, the project experienced significant re-sequencing or acceleration that makes event-by-event insertion impractical, and a fair allocation of delay responsibility between parties is needed. This method is especially useful for complex mega-projects in the GCC where multiple subcontractors, design packages, and procurement streams create overlapping delay events that are difficult to isolate individually.
Can you combine both methods?
Yes, and experienced claims professionals often do. A common approach is to use Windows Analysis as the primary method to establish the overall delay picture and allocate responsibility, and then use TIA for specific high-value delay events where precise quantification is critical. This combined approach is accepted by tribunals and is consistent with the SCL Protocol's guidance that the choice of method should be driven by the available records and the nature of the delays.
What about other methods?
Other methods include As-Planned vs As-Built (simple comparison but does not consider critical path), Collapsed As-Built (removes delays from the as-built schedule), and Impacted As-Planned (adds delays to the baseline). Each has specific use cases. As-Planned vs As-Built is useful for a quick initial assessment. Collapsed As-Built works well when the as-built schedule is well documented but baseline updates are unavailable. However, for formal claims under FIDIC contracts in the GCC, TIA and Windows Analysis remain the most widely accepted and credible methods.
Practical recommendations
Always start by assessing what schedule records are available before selecting a method. Document your methodology selection rationale — tribunals and Engineers want to understand why you chose the method you did. Follow the SCL Protocol and AACE Recommended Practices regardless of which method you select. If in doubt, consult a specialist claims consultant who can assess the records and recommend the most appropriate approach for your specific project.
Related services: Claimetrica provides expert forensic delay analysis using all recognized methodologies, in accordance with the SCL Protocol and AACE Recommended Practices. Request a free consultation →