On this page
Start a delay analysis by writing the question, not by selecting a software button. Are you assessing a new event’s expected effect, explaining how the completion forecast changed over time, or examining a completed project’s history? Those questions need different records and assumptions.
Method names alone can be ambiguous. Explain what information the analysis uses, whether the network is changed, the periods examined and how the controlling work is identified.
Match the approach to the question
| Approach | Useful question | Main evidence need | Important limit |
|---|---|---|---|
| Prospective impact model | What could this event do to the remaining plan? | Reliable contemporaneous update and event model | Depends on forecast assumptions |
| Period or windows review | How did driving work and completion change over successive periods? | Update series and contemporaneous records | Update quality and period boundaries matter |
| Planned-versus-actual comparison | Where does recorded performance differ from the reference plan? | Baseline and reliable actual history | Variance alone does not explain causation |
| Subtractive as-built model | What does a defined model show when selected effects are removed? | Validated as-built sequence and explicit removal assumptions | Counterfactual logic needs careful support |
This table is a practical orientation, not a complete classification or a direction to use a particular method. The SCL Delay and Disruption Protocol is one published reference discussing approaches and the importance of records. Project terms and the purpose of the analysis must still be considered.
A fictional choice between two questions
A late design release occurs during construction. The team has a current update and needs to plan around its expected effect. A prospective model may support that immediate discussion.
Months later, the project finishes and the record shows that procurement recovered some time while another path became controlling. A retrospective review needs to consider what actually happened over that period. Reusing the original prediction as the final historical answer would skip those developments.
Write a method-selection note
Record the question, analysis date, information available at that date, governing requirements, chosen approach, rejected alternatives and significant limitations. Explain why the records support the chosen level of detail.
If updates are missing or unreliable, state the gap and its effect. Reconstructed logic can be useful, but it must be identified as reconstruction rather than presented as a contemporaneous project record.
Test sensitivity without shopping for an answer
Reasonable choices about periods, event boundaries or corrective edits can affect the result. Retain those choices and explain why the selected treatment is justified. Where an alternative materially changes the conclusion, report the sensitivity and the evidence needed to resolve it.
No method name turns a calculated movement into entitlement automatically. Keep the schedule result, causal assessment and contract conclusions distinguishable.
Continue with time impact analysis, concurrent delay and the Schedule Forensics learning paths.
Share this article