Delay Analysis: Definition, Theory, and an Example from Practice

What is delay analysis?

Delay analysis is the systematic examination of delays to a construction project to establish when the delay occurred, what caused it, how it affected the project completion date, and which party may be contractually responsible for its consequences.

Construction projects rarely proceed exactly as planned. Design information may arrive late, approvals may take longer than expected, materials may not be delivered on time, or site activities may be affected by unforeseen conditions. Some delays arise from the employer’s actions, others from the contractor’s performance, and others from circumstances for which neither party is responsible under the contract.

The important question is not simply how many days the project was delayed. It is how the delay affected the program and whether it changed the date by which the project could reasonably have been completed.

For example, a contractor may report that a delayed architectural drawing held up a building’s external façade for 20 days. That does not automatically mean the project completion date was delayed by 20 days. The façade work might have had available float, another activity might have controlled completion, or the contractor might have been unable to proceed for an independent reason.

Delay analysis investigates these relationships using construction programs, progress records, correspondence, design information, and other project evidence.

It is therefore both a technical scheduling exercise and an investigation of project events. The analysis can inform decisions about extensions of time, delay damages, compensation, and disputes, but contractual entitlement must also be assessed against the applicable contract and governing law.

 Why was delay analysis developed?

Construction contracts establish obligations concerning the completion of works. When a project finishes later than planned, the parties may disagree about the cause, the consequences, and who should bear the resulting risks and costs.

A completion date alone cannot resolve these questions. A project might finish six months late because the employer delayed approvals, because the contractor failed to provide sufficient labour, because several events occurred together, or because the original program was unrealistic.

Delay analysis was developed as a means of examining these competing explanations systematically. Its purpose is to connect identifiable events with their effects on the construction program and to provide a reasoned basis for assessing responsibility.

Three questions are particularly important.

First, what happened? This requires identifying the relevant events and establishing their dates using contemporary records.

Second, what effect did those events have on the program? This requires examining activity relationships, available float, progress, the critical path, and the projected or actual completion date.

Third, how should the consequences be allocated? This requires distinguishing the technical findings from the contractual provisions governing extensions of time, compensation, and delay damages.

The methods have evolved alongside the use of critical path method (CPM) scheduling, digital planning software, and more systematic project records. However, better software does not automatically produce a better analysis. The result remains dependent on the quality of the program, the accuracy of the records, and the reasonableness of the analyst’s assumptions.

Nuhu Braimah’s academic review, Construction Delay Analysis Techniques—A Review of Application Issues and Improvement Needs, examines the limitations of established techniques and explains why different methods can produce different results when applied to the same delay scenario.

 What is the theory, method, and technique behind delay analysis?

These terms are related, but they describe different things.

Theory concerns the principles used to understand how delays affect a project. In CPM scheduling, activities have durations and logical relationships. The critical path is the sequence of activities that determines the earliest achievable project completion date under the model’s assumptions. A delay to an activity on the critical path may delay completion, whereas a delay to an activity with available float may not.

Method refers to the overall analytical approach used to investigate the delay. An analyst might compare the planned and actual progress, insert delay events into a program, examine successive schedule updates, or reconstruct the critical path using as-built records.

Technique refers to the practical procedures used to implement the method. These may include preparing a fragnet to represent a delay event, updating a CPM program, checking activity relationships, calculating changes to the forecast completion date, and comparing the results with contemporaneous records.

For example, Time Impact Analysis is a method. Constructing a fragnet for a late design instruction, inserting it into an appropriate program update, recalculating the schedule, and evaluating the resulting completion-date movement are parts of its implementation.

The distinction matters because an analyst can select an appropriate method but apply it poorly. Conversely, technically correct calculations cannot compensate for an unreliable baseline program or incomplete records.

The Society of Construction Law’s Delay and Disruption Protocol provides professional guidance on delay and disruption, including extensions of time and compensation. Its emphasis on transparency and the disclosure of the analytical basis is important: a conclusion should be capable of being understood, tested, and challenged by other parties.

How many delay-analysis methods are there?

There is no single universally accepted number of delay-analysis methods. Different professional bodies and authors classify approaches differently, and some distinguish between a method’s broad family and the particular procedure used to apply it.

The Society of Construction Law’s second-edition Protocol identifies six principal approaches:

1. Impacted As-Planned Analysis.
2. Time Impact Analysis.
3. Time Slice Windows Analysis.
4. As-Planned versus As-Built Windows Analysis.
5. Retrospective Longest Path Analysis.
6. Collapsed As-Built Analysis.

Other technical literature also discusses approaches such as Total Time Assessment and month-to-month comparisons of program updates. These should not simply be added to the six SCL approaches as though every classification were identical. They belong to a broader range of analytical procedures and may be grouped differently by different authors.

The Delay Analysis in Construction Contracts reference by P. John Keane and Anthony F. Caletka is another useful technical source. It examines the principles, assumptions, and practical application of delay-analysis techniques.

The more useful question for a practitioner is not how many methods exist, but which method is suitable for the project, the available evidence, the purpose of the analysis, and the contractual and legal context.

 What are the principal methods, and how do they work?

Total Time Assessment

Total Time Assessment compares the planned completion date with the actual completion date to establish the overall delay. It may be expressed as a difference between the original contractual completion date and the actual completion date.

For example, if a project was contractually due to finish on 30 June but was completed on 30 September, the project finished three calendar months later than the contractual date.

This comparison establishes the overall outcome, but it does not explain why the project finished late. It does not, by itself, identify the critical activities, establish the effect of individual events, or distinguish employer-caused delay from contractor-caused delay.

It can provide a useful starting point or a broad overview when records are limited. However, it is weak as a standalone method for allocating responsibility because the same overall delay may result from several different causes.

Impacted As-Planned Analysis

Impacted As-Planned Analysis starts with the original planned program and introduces identified delay events into it. The analyst models the events and calculates how they would affect the planned completion date.

For example, a late employer instruction might be represented by a group of activities showing the work required to incorporate the instruction. The activities are inserted into the baseline program with appropriate logic, and the program is recalculated.

The method can be useful when assessing the potential effect of events against the original plan. It is comparatively straightforward when the baseline program is reliable, and the relevant events can be modelled clearly.

Its principal limitation is that the original plan may no longer represent the actual state of the project. Actual progress, changes in sequencing, later program revisions, and intervening events may have altered the critical path. A model based on the original program can therefore produce a theoretical impact that differs from the delay that ultimately occurred.

Time Impact Analysis (TIA)

Time Impact Analysis models a delay event within a suitable program update representing the state of the project before that event. The event is typically represented by a fragnet: a linked set of activities describing the work or sequence associated with the event.

The analyst inserts the fragnet into the program, recalculates the schedule, and examines the change in the forecast completion date. Depending on the circumstances, the process may be repeated for several events and program periods.

For example, if an employer’s design instruction prevents a critical installation from proceeding, the analyst can model the instruction, the resulting design work, and the installation sequence. The analysis then tests whether and to what extent the event affects the forecast completion date.

TIA is particularly useful when reliable program updates and event records are available. It can show how the expected effect of a delay event was assessed at a particular point in the project.

However, its result depends on the program selected, the quality of the logic, the accuracy of progress information, and the assumptions used to model the event. A modelled impact is not automatic proof that the same number of days was ultimately lost. The analyst must also investigate what happened after the event and whether other delays affected completion.

Month-to-Month Update Analysis

This approach examines successive program updates to understand how the forecast completion date, activity progress, and critical path changed over time.

The analyst compares one update with the next, identifies the activities and events associated with changes, and investigates whether those changes reflect actual progress, new delay events, revisions to logic, altered durations, or changes to the program itself.

For example, if the forecast completion date moves from August to September and then to October, the analyst investigates what caused each movement rather than treating the final two-month change as a single unexplained delay.

This approach is valuable for examining the development of delay over the life of a project, particularly where regular, reliable updates exist. It can also reveal whether schedule changes resulted from progress or from revisions to the planning model.

Its limitation is that the difference between two forecasts does not, by itself, establish causation. A program may have been revised for legitimate reasons, and the analyst must distinguish changes in the model from actual events affecting the works.

Time Slice Windows Analysis

Time Slice Windows Analysis divides the project into periods, or windows, and examines the program and progress within each period. The analysis considers how the critical path and forecast completion date changed as the project progressed.

For example, one window might cover the foundations, another the structural frame, and another the building envelope and internal works. The actual windows should be selected to suit the project’s records and significant changes, rather than being divided mechanically into equal periods.

The analyst investigates the delay events, progress, and critical activities relevant to each window. The results are then brought together to explain how the project’s delay developed over time.

This method can be effective when contemporaneous updates provide a credible record of the changing program. It helps avoid the assumption that the same activity or cause controlled the project throughout its duration.

Its reliability depends on the quality and consistency of the updates, the way the windows are selected, and the evidence supporting the critical path in each period.

As-Planned versus As-Built Windows Analysis

This method compares planned and actual performance within selected periods of the project. The planned program provides a reference point, while as-built records establish what actually occurred.

The analyst identifies differences in activity sequence, duration, and progress, then investigates their relationship to the overall completion delay.

For example, if the planned structure was to be completed within a particular period but the actual structural works took longer, the analyst examines the reasons and considers whether the delay affected the completion path.

The method can be useful when detailed contemporaneous CPM updates are unavailable, but sufficiently reliable as-built information exists. However, the comparison must go beyond identifying that an activity took longer than planned. It must examine the activity’s relationship to completion and the causes of the difference.

Reconstructing the critical path and assessing concurrent or overlapping delays may be difficult when the original program or the supporting records are incomplete.

Retrospective Longest Path Analysis

Retrospective Longest Path Analysis reconstructs the actual sequence of activities and relationships that governed project completion. Rather than relying solely on the original planned critical path, the analyst examines the completed project using as-built evidence.

The aim is to identify the sequence that ultimately controlled completion and then investigate the events that affected it.

This can be important when the actual construction sequence differed substantially from the original plan. For instance, a contractor may have changed the order of work, or a planned critical activity may have gained float while a different sequence became controlling.

The method requires a credible reconstruction of the actual sequence, activity relationships, and relevant durations. Where records are incomplete, the reconstruction may depend on assumptions that must be explained and tested.

Collapsed As-Built Analysis

Collapsed As-Built Analysis starts with a reconstructed as-built program and removes or adjusts selected delay events to model a hypothetical scenario in which those events did not occur. The analyst then compares the modelled completion date with the actual completion date.

This is often described as a “but-for” analysis: what might the completion date have been if the selected event had not occurred?

For example, an analyst might remove a particular employer-caused delay from the reconstructed program to assess the potential effect of that event on completion.

The result is counterfactual. It represents what the model predicts under specified assumptions, not an alternative project history that can be observed directly. The findings therefore depend on the accuracy of the reconstructed program, the logic of the activities, and the way the removed events are treated.

It is not inherently suitable only for linear projects, nor is it automatically conclusive simply because it starts with as-built information. Its usefulness depends on the evidence and the soundness of the reconstruction.

 Which method is the most widely used, and which is best?

It is difficult to identify one method as universally the most widely used. Practices vary between countries, contractual frameworks, types of project, dispute forums, and the records available. A method frequently used in one jurisdiction or type of dispute may not be the preferred method elsewhere.

Time Impact Analysis is an important approach, particularly where the project has reliable program updates and the parties need to examine the effect of delay events as they arise. Window-based approaches can be useful for retrospective analysis where the program and critical path changed over time.

However, no method should be selected merely because it is popular or familiar to the analyst. The choice should consider:

• Purpose: Is the analysis intended to assess an extension of time during the project or investigate a completed project retrospectively?
• Records: Are there reliable baseline programs, updates, progress reports, and event records?
• Program quality: Do the schedules contain credible activity relationships and reflect the work?
• Project history: Did the sequence of work and the critical path remain relatively stable, or did they change significantly?
• Complexity: Are there overlapping delay events, disputed causes, or significant changes to the original program?
• Contract and law: What requirements apply to notice, extensions of time, delay damages, and proof of entitlement?

The AACE International Recommended Practice 29R-03, Forensic Schedule Analysis, also stresses that the method and its implementation depend on the facts, contract, applicable law, and quality of the available documentation. A sound analysis therefore requires professional judgment rather than mechanical adherence to a single procedure.

The best method is the one that answers the relevant question transparently and defensibly using the evidence available.

 Who benefits from delay analysis?

Delay analysis can benefit several participants in a construction project, although their interests may differ.

The employer or client can use it to assess requests for extensions of time, understand the reasons for late completion, and evaluate potential claims for delay damages where the contract permits them.

The contractor can use it to substantiate an extension-of-time application, demonstrate the effect of events outside its responsibility, and distinguish those events from delays attributable to its own performance.

The project manager and contract administrator can use program analysis and contemporary records to assess delay events and support timely decisions, provided they act within their contractual authority.

The architect and design consultants may need to establish when information or instructions were issued, whether they affected construction activities, and how the resulting events interacted with the wider program.

The planning or delay analyst reconstructs the program history, tests the evidence, and communicates the technical findings. Depending on the assignment, the analyst may work for an employer, contractor, consultant, law firm, or as an independent expert.

The adjudicator, arbitrator, or court may use delay-analysis evidence when resolving a dispute. The analyst’s role is to explain the technical assessment; the decision-maker determines the contractual or legal consequences.

The same analysis may be used by parties with opposing positions. Its credibility depends on the quality of its reasoning and evidence, not on which party commissioned it.

What books, qualifications, and career opportunities are relevant?

A useful starting point is P. John Keane and Anthony F. Caletka’s Delay Analysis in Construction Contracts. The book examines delay-analysis principles and methods, including their assumptions and practical implications. Readers should check the edition they use because the chapter numbering differs between editions.

The Society of Construction Law’s Delay and Disruption Protocol is another important professional resource. It provides guidance on delay and disruption and is useful for understanding how program analysis relates to extensions of time and compensation.

For a research-oriented introduction, Nuhu Braimah’s 2013 review provides a comparative discussion of delay-analysis techniques and their practical limitations.

Relevant professional skills include:

• Understanding CPM scheduling, activity logic, float, critical paths, and program updates.
• Using planning software such as Primavera P6 or Microsoft Project.
• Reading construction contracts and understanding the distinction between delay, disruption, extension of time, and compensation.
• Analysing correspondence, progress records, drawings, instructions, site reports, and other contemporaneous evidence.
• Producing transparent calculations, explaining assumptions, and preparing clear technical reports.

Professional certifications may support a career in planning, scheduling, or project controls. For example, AACE International offers the Planning & Scheduling Professional (PSP) credential. Such a qualification demonstrates professional knowledge in its relevant field, but it is not a universal license to practice delay analysis or a guarantee of expertise in forensic claims.

Career opportunities include planning engineer, project controls engineer, delay analyst, claims consultant, and—after gaining suitable experience—specialist consultant or expert witness. The required experience varies by role and jurisdiction.

There is no single reliable salary figure for delay analysts worldwide. Earnings depend on location, professional experience, employer, project sector, technical responsibility, and whether the work involves routine project controls or specialist dispute analysis. A salary comparison should therefore use current vacancies in the country and role being considered, rather than treating one international estimate as representative.

 A documented example from practice: a covered swimming pool in Ankara, Türkiye

A useful example is Songül Dayı’s 2010 postgraduate thesis, Schedule Delay Analysis in Construction Projects: A Case Study Using Time Impact Analysis Method, held in the institutional repository of Middle East Technical University.

The study examines the construction of a covered swimming-pool building in Ankara. It applies Time Impact Analysis using Primavera scheduling software to investigate construction delays, assess their effect on the project completion period, and consider responsibility among the project participants.

The case is useful because it illustrates the application of a scheduling method to a real project rather than simply explaining the method in abstract terms.

The reported findings

The thesis reports that delays to critical activities extended the project duration by a total of 57 days, equivalent to 15.4% of the estimated construction period.

The study classified 31 days as non-excusable contractor delay. It also recommended a 26-day extension of time, comprising 22 days classified as excusable and compensable and four days classified as excusable but non-compensable.

The causes discussed included organisational deficiencies on the employer’s side, municipal bureaucracy, missing detailed drawings during the municipal application process, the contractor’s lack of experience, material procurement problems, adverse weather, and shortages of qualified subcontractor employees.

These findings illustrate why simply measuring the total delay is insufficient. Different events can affect the same project, and the analysis must consider their relationship to critical activities and the completion date before responsibility can be assessed.

What does the example demonstrate?

First, the study used a program-based method rather than relying solely on the difference between the planned and actual completion dates.

Second, it attempted to distinguish delays attributed to different causes and participants. This is an essential part of evaluating a delay claim, although the classifications themselves depend on the evidence, the contractual framework, and the assumptions used in the analysis.

Third, the case illustrates that a delay may involve both employer-related and contractor-related circumstances. Establishing the effect of each event requires more than identifying who was involved; it requires a reasoned examination of the schedule and the records.

Finally, the reported 57 days should not be interpreted as proof that every event contributed independently to the completion delay. The result is the thesis author’s reported analytical finding, based on the study’s method and assumptions.

The thesis recommended a 26-day extension of time. That recommendation should not be presented as proof that the extension was ultimately granted, that delay damages were actually imposed, or that the parties reached a particular settlement. Those outcomes are not established by the repository’s abstract.

Source: Read the full Ankara swimming-pool case study by Songül Dayı (2010).

Conclusion

Delay analysis is a structured investigation into the relationship between construction events, program logic, progress, and project completion. It helps explain not only how late a project finished, but also how the delay developed and which events may have affected the completion date.

Different methods provide different ways of investigating that relationship. Total Time Assessment describes the overall outcome; Impacted As-Planned Analysis models delay events against the original plan; Time Impact Analysis evaluates events against an appropriate program update; window-based methods examine the changing program over time; and retrospective approaches reconstruct the sequence that governed actual completion.

None should be treated as universally superior. The choice depends on the purpose of the analysis, the quality of the program and records, the project’s history, and the applicable contractual and legal requirements.

The central professional task is to build a transparent chain of reasoning from the evidence to the schedule impact, and from the schedule impact to a carefully qualified conclusion. A defensible delay analysis does not merely calculate days: it explains why those days matter, what the evidence supports, and where the limits of the conclusion lie.