Why delay analysis is not the same as advanced planning

 

Forensic delay analysis plays a critical role in the resolution of construction disputes. However, a material risk arises when practitioners approach forensic analysis with a mindset rooted primarily in project planning rather than contractual interpretation.

This article examines a recurring failure mode, referred to here as "the Planner’s Trap", in which technically proficient schedulers are appointed as forensic delay experts without making the necessary cognitive transition from programme development to contractual analysis.

The article sets out why forensic delay analysis is fundamentally a contractual exercise supported by technical evidence, rather than a technical exercise supplemented by contractual reference.

It explains how over-reliance on programme “correction” can undermine entitlement arguments and weaken expert evidence under legal scrutiny.

1. Introduction

 

The increasing sophistication of planning software and scheduling methodologies has significantly improved programme management across the construction industry. However, this technical advancement has also contributed to a misconception that forensic delay analysis is simply an extension of advanced planning practice.

While there is overlap in skillsets, the objectives of planning and forensic delay analysis are materially different. Failure to recognise this distinction can lead to expert evidence that is technically elaborate yet contractually unsound.

2. The "Planner’s Trap" 

 

When questions of delay, responsibility, or entitlement arise, the natural and well-intentioned response of an experienced planner is to return to the scheduling software.

Focus is placed on the internal integrity of the programme: reviewing logic paths, addressing missing or broken relationships, reassessing durations, and resolving negative float or open-ended activities. From a planning perspective, these are legitimate deficiencies that must be corrected before the programme can be relied upon as a management tool. In a live project control environment, this approach is appropriate and often necessary.

In a forensic context, however, this technical focus can lead to what is described here as the Planner’s Trap. Entitlement is assumed to flow from the technical quality of the schedule, rather than from the contractual framework within which the programme was submitted, accepted, and relied upon.

However, the contract may limit or override the relevance of retrospective schedule correction or the schedule itself. 

Forensic delay analysis is therefore not not primarily concerned with producing an optimised or “corrected” programme. Its purpose is to interpret events through the contractual rules in force at the time, using the programme as supporting evidence rather than as an objective standard in its own right.

That said, accepted forensic methods may require limited, transparent schedule intervention. For example, repairing obvious broken logic solely to allow a demonstrable model to run, provided it is (a) necessary, (b) minimal, (c) evidenced, and (d) sensitivity-tested. Recognised forensic guidance (including AACE recommended practice) cautions against analytical bias and emphasises that any intervention must be justified, documented, and tested to demonstrate it does not predetermine the outcome.

 

3. The central misconception: Where delay “resides”

 

A recurring assumption beneath the Planner’s Trap is that delay is embedded within programme logic and can be objectively “revealed” through technical refinement.

In forensic terms, this assumption is incorrect.

Delay only acquires legal meaning through the contract. The programme’s evidential value depends on how it aligns with contractual definitions and mechanisms such as completion obligations, baseline/accepted programme status, notice and assessment requirements, records expectations, risk allocation, float treatment, concurrency approach, and the time extension provisions.

Absent this framework, programme analysis risks becoming speculative and vulnerable.

 

4. Contractual mechanisms that override technical analysis

 

There are numerous scenarios in which contractual provisions may significantly limit or negate the relevance of technically correct schedule analysis. Some have been listed below.

4.1 Risk allocation and agreed assumptions

Where a contractor has agreed to a baseline programme containing optimistic durations, incomplete logic, or flawed assumptions, the contract may allocate the risk of those deficiencies to the contractor.

In such cases, retrospective correction of the programme risks being characterised as an attempt to revise a binding agreement rather than interpret it.

 

4.2 Conditions precedent and procedural compliance

Many contracts impose strict notice and substantiation requirements as conditions precedent to entitlement.

A technically demonstrable critical delay may have no contractual value if those requirements were not satisfied at the relevant time.

 

4.3 Deemed acceptance provisions

Where programmes are deemed accepted following a defined review period, their technical deficiencies become contractually entrenched.

Forensic effort expended on correcting those deficiencies after the fact may add little value and may distract from more relevant contractual issues.

 

4.4 Prospective vs retrospective assessment

Some contractual regimes expect delay and time impact to be assessed prospectively when events arise (for example NEC3/NEC4), optionally with later true-up where appropriate (FIDIC). A purely retrospective “perfected” model may be criticised as inconsistent with how the contract required the parties to administer time. At the same time, even under contracts with prospective change assessment regime, tribunals determined that retrospective assessment may be appropriate.

4.5 Float and concurrency

Disputes frequently turn on float ownership/treatment and concurrency definitions. A technically elegant model can still fail if it does not align with the contract (or governing law/tribunal approach) on how float and concurrency should be handled. For example, English law typically follows the "Malmaison approach" granting contractors a full extension of time but no loss and expense. Conversely, Scottish law (via City Inn) allows for apportionment, where time and costs are shared based on responsibility.

 

5. Planning expertise vs forensic expertise

 

The distinction between planning expertise and forensic delay expertise is not one of quality. It is one of function.

Planning is primarily concerned with improving future delivery. Its focus is operational. Strengthening programme quality, applying recognised good practice, and supporting the project team in managing sequence, resources, and risk as the works progress. In that context, the planner’s role is forward-looking.

Forensic delay analysis serves a different purpose. It is concerned with assessing entitlement, not optimising future performance. Its focus is evidential. Interpreting the contractual consequences of events that have already occurred, and doing so by reference to the rules the parties agreed at the time.

Accordingly, forensic analysis does not begin with the question of how the programme could have been improved. It begins with the question of what contractual framework governed the programme. The task is not to apply abstract best practice, but to apply the agreed contractual mechanisms to the facts.

 

6. Characteristics of a forensic approach

 

A forensic delay expert will typically:

• Begin with a detailed review of the contract, paying attention to time, notice, and change provisions

• Identify contractual assumptions that were locked in at the time

• Establish procedural compliance or non-compliance

• Use programme analysis as supporting evidence, not as the primary driver

• Limit technical intervention to what is necessary and defensible supporting the steps taken with recognised guidance from recognised professional bodies guidance.

• Where limited schedule intervention is unavoidable, document the rationale, record the changes, and run sensitivity checks to demonstrate the conclusion is not an artefact of modelling choices.

This approach ensures that the analysis aligns with legal principles and remains robust under cross-examination.

 

7. Implications for appointments and disputes

 

Incorrectly conflating planning expertise with forensic expertise presents tangible risks:

• Weakening entitlement arguments

• Inflating costs without improving evidential value

• Producing analyses vulnerable to legal challenge

• Undermining credibility of expert evidence

Careful consideration should therefore be given to the analytical mindset being appointed, not merely the technical qualifications.

 

8. Conclusion

 

Forensic delay analysis is not a technical pursuit of delays within the schedule. It is a contractual analysis supported by technical evidence.

Practitioners who prioritise programme correction over contractual interpretation risk falling into the Planner’s Trap, producing work that may appear rigorous but lacks legal durability.

At ViViAD, programmes are treated as evidential tools, not determinants of entitlement. The governing instrument is always the contract, and forensic analysis is anchored accordingly.

 

Best, Radek Makar Planning Director | ViViAD radek@viviad.co.uk

ViViAD is an independent consultancy specialising in Planning, Project Controls, Power BI Reporting, and Construction Claims Support. We work across the UK - typically on NEC contracts in defence, nuclear, renewables, and infrastructure - embedding with project teams to bring structure, clarity, and commercial control. Interim or longer-term, we fit around what you need.