Delay Analysis and Extension of Time

Introduction

Delays are an unavoidable feature of construction projects. When they occur, the contract must determine who bears the risk — and the mechanism for doing so is the extension of time (EOT) process. An EOT extends the contractual completion date to account for delays that are not the contractor’s fault, preserving the employer’s right to recover liquidated damages while protecting the contractor from liability for events beyond its control. For the quantity surveyor, delay analysis and EOT are where programme management meets commercial reality: the QS must understand the contractual framework, the analytical methods used to demonstrate delay, and the cost implications of time extensions.

What Is an Extension of Time?

An extension of time is a contractual entitlement that moves the completion date forward when qualifying delay events occur. Without a valid EOT mechanism, an employer who causes or contributes to delay could lose the right to deduct liquidated damages entirely — because the original completion date, against which LADs are calculated, would no longer be enforceable. The EOT clause therefore protects both parties: the contractor is relieved of liability for delays it did not cause, and the employer retains its LAD entitlement for the adjusted completion date.

EOT Under JCT

Under JCT SBC 2024, the contractor is entitled to an EOT where a relevant event (Clause 2.26) causes delay to the completion date. The list of relevant events includes variations and employer’s instructions, exceptionally adverse weather, statutory undertaker interference, force majeure, civil commotion, and — new in the 2024 edition — epidemics and changes in law. The contractor must give notice of delay as soon as practicable, and the Contract Administrator must assess the EOT on a fair and reasonable basis within eight weeks of receiving sufficient information.

The CA’s role is quasi-judicial: the assessment must be objective, not discretionary. The CA cannot refuse an EOT for a qualifying relevant event without legitimate grounds. If the CA fails to grant an EOT that is due, the employer’s right to liquidated damages may be compromised — a point the QS should flag whenever EOT applications are outstanding.

EOT Under NEC4

NEC4 handles delay differently. There is no separate EOT mechanism — instead, compensation events that affect the completion date automatically adjust it. When a compensation event occurs, the contractor’s quotation assesses both the cost and time impact, using the accepted programme as the baseline. The Project Manager assesses the delay to planned completion caused by the event (Clause 63.5), and the completion date moves accordingly. The assessment is prospective — based on the programme impact, not what actually happened subsequently.

This approach is more integrated than JCT (time and cost are assessed together) but depends entirely on having a valid accepted programme. Without one, the PM must make their own assessment — a process that is inherently more contentious.

Delay Analysis Methods

When delay disputes arise, the parties must demonstrate which events caused which delays. Several analytical methods exist, each with different strengths and levels of acceptance by courts and tribunals.

As-planned vs as-built is the simplest method: it compares the original programme against what actually happened and identifies the net delay. It is easy to understand but does not demonstrate causation — it shows that delay occurred, not which events caused it. Courts accept it as a starting point but rarely as the sole basis for apportioning liability.

Impacted as-planned takes the original programme and inserts delay events to show their theoretical impact on the critical path. It demonstrates causation more clearly but is increasingly criticised because it applies events to a plan that may never have reflected actual site conditions. Tribunals have described retrospective versions of this method as unreliable.

Time impact analysis (TIA) is the preferred prospective method. Delay events are inserted into the current accepted programme at the time they occur, and the forward impact on completion is calculated. Prospective TIA — prepared contemporaneously during the project — is highly favoured. Retrospective TIA, applied after completion using historical data, is less reliable and subject to the same criticisms as impacted as-planned.

Collapsed as-built (but-for analysis) works in reverse: it takes the actual as-built record and removes delay events to determine when the project would have completed but for those delays. It is useful when the original programme is unavailable but carries a risk of manipulation through subjective logic tie insertion.

Windows analysis divides the project timeline into discrete periods (typically monthly) and examines the actual critical path within each window. It is the most comprehensive and fact-based method, capable of identifying concurrent delays, critical path shifts, and float consumption. UK courts and tribunals increasingly favour windows analysis for its rigour, though it is resource-intensive and requires extensive contemporaneous project records.

Concurrent Delay

Concurrent delay occurs when two or more delay events overlap in time and both affect the completion date — one being the employer’s risk (a relevant event) and the other the contractor’s risk. The leading authority is Henry Boot v Malmaison [1999], which established that where a relevant event and a contractor delay run concurrently, the contractor is still entitled to an EOT for the relevant event. The employer cannot deny the extension simply because the contractor was also causing delay at the same time.

This principle was refined in Adyard v SD Marine [2011], which emphasised the need to prove causation in fact — the relevant event must actually cause delay to the completion date, not merely occur at the same time as the contractor’s delay. For the QS, the practical implication is that concurrent delay does not automatically mean the contractor receives both time and money — the EOT may be granted (protecting the contractor from LADs) but the associated prolongation costs may not be recoverable if the contractor’s own delay would have caused the same period of overrun.

Float

Float is the amount of time an activity can be delayed without affecting the project completion date. Under JCT, float ownership is not expressly addressed — it is generally consumed on a first-come-first-served basis. Under NEC4, float must be shown on every submitted programme, and it belongs to the project timeline rather than to either party. The contractor’s time risk allowances (TRA) — risk contingencies within individual activity durations — are distinct from float and are owned by the contractor.

The distinction matters for delay analysis: a delay event that consumes available float does not extend the completion date. Only delays that affect the critical path — the longest sequence of dependent activities with zero float — entitle the contractor to an EOT.

Liquidated Damages

Liquidated damages are a pre-agreed sum payable by the contractor to the employer for each day or week of delay beyond the contractual completion date. They replace the need for the employer to prove actual loss. The EOT mechanism directly affects LAD liability: every day of EOT granted reduces the contractor’s LAD exposure by moving the completion date forward.

Following the Supreme Court’s decision in Cavendish Square Holding v Makdessi / ParkingEye v Beavis [2015], a liquidated damages clause will be upheld provided it is not a penalty — meaning it must represent a genuine pre-estimate of loss or a legitimate commercial interest of the employer in the contractor completing on time. The 2024 JCT edition also incorporates the principle from Triple Point v PTT [2021] that LADs cannot be recovered for the period after termination of the contract.

The SCL Delay and Disruption Protocol

The Society of Construction Law’s Delay and Disruption Protocol (2nd edition, 2017) provides industry-standard guidance on how delay should be analysed. Its core principles include: delay analysis should be carried out prospectively where possible; the method chosen should be appropriate to the circumstances; float is not owned by either party; and concurrent delay should not reduce the contractor’s EOT entitlement. While not legally binding, the Protocol is widely cited by tribunals and arbitrators and provides a practical framework that the QS should follow.

The QS Role

The QS’s involvement in delay and EOT sits at the intersection of programme and cost. When an EOT is granted, time-related preliminaries increase — site supervision, plant hire, scaffold hire, welfare facilities, and other ongoing costs extend proportionally. The QS must calculate the prolongation cost associated with the EOT period, distinguishing between costs that genuinely increase due to the delay (additional crane hire weeks, extended site management) and costs that would have been incurred regardless.

The QS also assesses loss and expense claims (JCT) or compensation event costs (NEC4) arising from delay events. This requires detailed analysis of the contractor’s actual costs during the delay period, supported by contemporaneous records. On the employer’s side, the QS advises on whether the EOT application is valid, whether the delay analysis methodology is sound, and what the cost implications are for the project budget.

Common Mistakes

Failing to issue notices on time. Both JCT and NEC4 require timely notification of delay events. Under NEC4, the eight-week time bar means late notification results in complete loss of entitlement. Under JCT, late notice may weaken the claim even if it does not bar it entirely.

Confusing delay with disruption. Delay extends the completion date; disruption reduces productivity without necessarily extending the completion date. They require different analysis and different cost assessment methods. The QS must distinguish between the two.

Ignoring float. A delay event that consumes float but does not affect the critical path does not entitle the contractor to an EOT. Failing to account for available float in the delay analysis overstates the contractor’s entitlement.

Using the wrong analysis method. Choosing an analysis method that does not suit the project records or the dispute complexity undermines the claim. The QS should select the method that best fits the available data and the level of detail required.

Practical Tips

Keep contemporaneous records. Delay analysis depends on project records — daily logs, progress reports, correspondence, photographs, labour allocation sheets. Without them, even the best analytical method cannot produce reliable results.

Assess EOT cost implications immediately. When an EOT is granted, update the project cost forecast to reflect the additional time-related preliminaries. Do not wait until the final account.

Understand the programme. The QS must be able to read a programme, identify the critical path, and understand how delay events affect it. Programme literacy is not optional for QS professionals working on delay claims.

Engage a delay analyst early on complex disputes. For significant delay claims, specialist delay analysts bring programme expertise that complements the QS’s commercial skills. Early engagement produces better results than retrospective analysis after the dispute has escalated.

APC Relevance

Delay analysis and EOT fall within the RICS APC competencies of Contract Practice (understanding EOT mechanisms under JCT and NEC, administering delay claims, assessing prolongation costs), Dispute Resolution (applying delay analysis methods, understanding concurrent delay principles, using the SCL Protocol), and Quantification and Costing (calculating time-related preliminaries and prolongation costs). APC candidates should be able to explain the main delay analysis methods, describe the EOT process under JCT and NEC4, and discuss the cost implications of extensions of time.

Further Reading on ProQS

Contract Administration: JCT vs NEC — how EOT processes differ between JCT and NEC contract families.

Construction Law for the Quantity Surveyor — the legal framework governing delay claims, liquidated damages, and time-at-large.

Variation Valuation and Claims — how delay-related claims interact with variation valuation under JCT and NEC.

Dispute Resolution in Construction — how delay disputes are resolved through adjudication, arbitration, and litigation.

Key References

SCL Delay and Disruption Protocol (2nd Edition, 2017) — the industry-standard guidance on delay analysis methodology and best practice.

Designing Buildings Wiki: Extension of Time — comprehensive reference covering EOT principles, contract provisions, and case law.

Fenwick Elliott — specialist construction law firm with extensive guidance on delay claims and dispute resolution.

RICS Black Book — professional standards for contract administration, including delay and disruption assessment.

HKA — global construction claims consultancy with published research on delay analysis methods and best practice.