Forensic Delay Analysis — Choosing And Applying The Right Method
ZALBASIREPPM · Planning And Controls
Forensic Delay Analysis — Choosing And Applying The Right Method
A disciplined overview of five commonly used methods, the evidence they require and the limitations that must remain visible.
Forensic delay analysis examines how events affected project timing. It does not begin with a preferred technique or a desired allocation of responsibility. It begins with a defined question, the governing contract, reliable contemporaneous evidence and an honest assessment of what the records can support.
01 · Scope Of The Analysis
Separate Time Measurement From Entitlement
A schedule model may help determine when and how an event affected a completion or milestone date. Contract interpretation, notice compliance, risk allocation, concurrency rules, responsibility and compensation are related but separate questions. They require the applicable contract, facts and jurisdictional advice.
02 · Five Common Approaches
Understand What Each Method Actually Tests
As-Planned Versus As-Built
Compares planned and actual timing at an appropriate level. It can illustrate overall variance but, without deeper analysis, may not explain changing critical paths, causation, concurrency or responsibility.
RetrospectiveHigh-LevelImpacted As-Planned
Adds modeled delay events to an accepted baseline to estimate theoretical effect. Its reliability depends heavily on the baseline, event modelling and whether actual progress and changing conditions matter to the question.
ModelledOften ProspectiveTime Impact Analysis
Inserts an event or fragnet into an appropriate contemporaneous schedule update and recalculates the forecast effect. The update, status, logic, calendars and modelling assumptions must be validated.
DynamicContemporaneousCollapsed As-Built / But-For
Removes selected events from a reconstructed as-built model to estimate when work might otherwise have completed. The reconstruction and removal logic must reflect actual sequencing and constraints.
RetrospectiveSubtractiveWindows / Contemporaneous Period
Divides performance into periods and examines the critical or controlling path and delay events within each. It can reflect path migration but requires disciplined updates and transparent window selection.
RetrospectivePeriod-Based03 · Method Selection
Choose The Method After Defining The Question
| Selection Factor | Question To Resolve | Why It Matters |
|---|---|---|
| Purpose And Timing | Prospective extension assessment, contemporaneous control, or retrospective dispute? | Different questions require different temporal viewpoints. |
| Contract | What method, notices, records or assessment rules are required? | The contractual mechanism may shape or constrain the analysis. |
| Schedule Quality | Are baseline and updates complete, logic-linked, statused and accepted? | A dynamic technique cannot overcome an unreliable model without reconstruction and disclosure. |
| Records | Can events, progress, access, instructions, resources and decisions be dated? | Contemporaneous evidence anchors cause and effect. |
| Project Complexity | Did critical paths, sequencing, constraints and work methods change? | Simple comparisons may conceal path migration and interaction. |
| Proportionality | What level of effort is justified by the issue and available evidence? | The analysis should be rigorous without becoming disconnected from the decision. |
04 · Evidence And Validation
Build A Traceable Factual Record
- Preserve native baseline and update files, calendars, coding, constraints and version history.
- Reconcile schedule status with daily records, correspondence, instructions, approvals, site access, procurement and progress evidence.
- Validate actual dates, remaining durations, out-of-sequence work and logic changes.
- Create an event chronology with source references and avoid retrospective labels unsupported by contemporaneous records.
- Test whether the event affected the controlling path at the relevant time.
- Document every correction, reconstruction, assumption and exclusion.
- Run sensitivity checks where alternative reasonable assumptions could change the result.
05 · Issues Every Analysis Must Address
Delay Is More Than A Number Of Days
Critical Path Migration
The path controlling completion can change as work progresses; analysis must use the relevant period, not a permanent baseline path assumption.
Concurrency
Overlapping delay events require a stated definition and careful examination of independent causation under the governing contract and law.
Pacing And Mitigation
Work may be deliberately paced or resequenced in response to another constraint. Analyze the contemporaneous decision and actual capacity to proceed.
Float And Constraints
Calendar choices, imposed constraints, float ownership and preferential logic can materially affect modeled outcomes.
Actual Causation
A modeled effect should be checked against what happened, including resources, access, productivity and work sequence.
Data Limitations
Missing or unreliable evidence should reduce confidence and be disclosed—not silently replaced with certainty.
06 · Reporting The Opinion
Make The Reasoning Reproducible
A clear report states the instruction and questions, materials relied upon, contractual assumptions, method and reasons for selection, schedule validation, event chronology, calculations, concurrency treatment, sensitivity results, limitations and conclusions. Exhibits should allow another competent reviewer to trace each material finding back to source evidence.
Management Conclusion
The Best Method Is The One The Evidence Can Support
Method labels do not determine reliability. A credible forensic delay analysis is proportionate, contract-aware, fact-led and transparent about assumptions. It tests changing critical paths and causation, confronts contrary evidence and reports limitations with the same clarity as its conclusions.
Discover more from Project Portfolio Intelligence
Subscribe to get the latest posts sent to your email.