How to Handle Construction Project Delays (UK Guide)

Dealing with construction delays UK-wide is less about avoiding them altogether - on most projects that's unrealistic - and more about spotting them early, controlling the damage and protecting your contractual position while you do it. Weather, late design information, subcontractor capacity and material lead times all conspire against even well-run programmes, and a 2024 industry survey found that the majority of UK construction projects finish later than their original completion date.

This guide is written for quantity surveyors, commercial managers and contract administrators who need a practical playbook rather than a textbook definition. It sets out how to recognise a delay forming before it hits the critical path, how to mitigate and accelerate to claw back time, how to build a credible recovery programme, and how to meet the contractual notice deadlines that so often decide whether a claim succeeds or fails.

We'll also cover the record-keeping habits that make or break a delay claim months later, and the point at which a live programme issue needs to be escalated - to senior management, to the client, or through formal dispute procedures. Throughout, we link out to our dedicated guides on extension of time claims and delay analysis methods, which go deeper into the technical mechanics once you've got the immediate situation under control.

Whether you're managing a live delay on site this week or building a process for the next one, treat this as a working reference: read it end to end once, then come back to the sections on notice obligations and evidence whenever a new delay event lands on your desk.

Common Causes of Construction Delays in the UK

Before you can manage a delay, you need to name it correctly - the response to a weather delay is completely different from the response to a client-instructed variation, and mixing them up in your notice or your programme narrative will weaken your position later.

Design, information and approvals

Late or incomplete design information remains one of the most persistent causes of delay on UK projects. Where a contractor is working to a design-and-build or traditional programme that assumes information will land on a fixed date, any slippage in that information release cascades through procurement, fabrication and installation. Statutory approvals - building control sign-off, utility connections, planning discharge of conditions - sit in the same category: they're outside the contractor's direct control but need to be tracked and chased as if they were a critical path activity in their own right.

Resources, materials and access

Labour and subcontractor shortages are a well-documented pressure across the UK construction sector, and when a specialist trade fails to resource a package properly, the effect on a tightly sequenced programme can be disproportionate to the size of the package itself. Material and supply chain delays - price fluctuations, extended lead times on structural steel, cladding, mechanical plant and specialist joinery - have become one of the single biggest disruptors since 2020, and they're frequently outside either party's immediate control. Finally, access and possession delays, where the employer fails to hand over a site or phase on the date the contract assumes, can halt a programme before it has even started.

• Design and information release running behind the information release schedule
• Adverse weather beyond what a reasonable contingency allows
• Subcontractor and labour shortages on specialist packages
• Material price volatility and extended supplier lead times
• Delayed statutory approvals, utility connections or building control sign-off
• Late or restricted site possession and access
• Client-instructed variations affecting critical path activities

Early Warning Signs of a Delay

The projects that recover fastest from delay are rarely the ones with the best contingency budget - they're the ones where someone spotted the problem two or three weeks before it became visible on the master programme. Waiting for a missed milestone to show up in a monthly report is usually too late to do anything but react.

What to monitor weekly, not monthly

A short-term look-ahead programme, reviewed weekly against the baseline, will surface slippage long before it reaches the critical path. Watch for activities repeatedly slipping from one look-ahead to the next, float on non-critical paths being consumed faster than planned, subcontractor resource levels falling below what the programme assumes, and procurement or submittal approvals running later than the information release schedule allows. Any one of these on its own may be noise; two or three appearing together on the same package is usually a genuine early warning sign.

• Activities slipping repeatedly on the two- or three-week look-ahead
• Float being consumed on paths that were previously non-critical
• Subcontractor labour and plant levels below the resourced programme
• Material orders or approvals overdue against the procurement schedule
• Rising RFIs or unanswered information requests on a single package
• Site diary entries repeatedly noting the same recurring issue

The practical response is to hold a standing weekly risk review with the site team, procurement and design lead, specifically looking for these indicators rather than waiting for the formal monthly progress report. Once a genuine delay is confirmed, the clock starts on your contractual notice obligations - covered in detail further down this guide - so early detection isn't just good practice, it protects your ability to claim an extension of time later.

Mitigation and Acceleration Strategies

Once a delay is confirmed, there are two distinct levers available: mitigation, which reduces the effect of the delay without materially increasing cost, and acceleration, which spends money to recover time. Confusing the two - or applying acceleration without agreeing who pays for it - is one of the most common sources of dispute at final account stage.

Mitigation: reduce the damage, not the cause

Mitigation is typically achieved through resequencing rather than resourcing. Modifying the logic of the programme so that delayed activities run in parallel with unaffected work, reallocating existing labour to keep other fronts moving, and tightening coordination between trades all fall under mitigation. Most standard-form contracts expect the contractor to take reasonable steps to mitigate delay - but reasonable does not mean unlimited, and a contractor is not expected to incur significant additional cost mitigating a delay it did not cause unless acceleration has been expressly instructed.

Acceleration: crashing and fast-tracking

Acceleration usually takes one of two forms. Crashing shortens the duration of critical path activities by adding resources - extra labour, plant or shifts - typically at increased direct cost. Fast-tracking overlaps activities that were originally planned in sequence, which can recover time without necessarily adding cost, but increases coordination risk and the chance of rework. A recovery programme built around fast-tracking alone is often optimistic; most genuine recoveries combine a limited amount of crashing on the true critical path with fast-tracking on activities that tolerate more risk.

• Resequence non-critical work to run in parallel with delayed activities
• Reallocate existing labour before committing to additional resource
• Reserve crashing for activities confirmed to be on the critical path
• Use fast-tracking selectively - it increases coordination and rework risk
• Agree in writing who bears acceleration costs before instructing extra resource
• Focus every recovery measure on the critical path - non-critical acceleration wastes money

Building a Recovery Programme

A recovery programme is a revised schedule showing how the project will return to, or move towards, its contractual completion date after a significant delay. It's a formal document, not an aspiration, and it needs to be built on the same rigour as the original baseline programme - otherwise it becomes a source of dispute rather than a route out of one.

The starting point is always to resolve any live contractual disagreement about the cause of the delay before building the recovery plan around it. Trying to accelerate a programme while the parties still disagree on entitlement and responsibility tends to produce a recovery plan nobody actually trusts. Once that's settled, a robust baseline re-programme identifies the current critical path - which may have shifted since the original programme was issued - and recovery efforts should be concentrated exclusively on activities that sit on that path. Time and money spent accelerating non-critical work delivers no benefit to the completion date.

• Confirm the current critical path before modelling any recovery options
• Prioritise recovery measures with clear evidence they affect the completion date
• Cost each option before it's approved - not after it's implemented
• Keep all stakeholders aligned on the recovery logic and reporting cadence
• Track productivity closely - crashing can reduce output per worker if overused

Contractual Notice Obligations: Notify Early, Notify Properly

Every UK standard-form contract builds delay provisions around a notice mechanism, and getting this wrong is the single most common way a genuine delay claim fails. Missing a notice deadline can weaken - or in some contracts completely defeat - a contractor's right to an extension of time, regardless of how strong the underlying cause was.

JCT contracts

Under JCT contracts, the contractor must notify the contract administrator as soon as it becomes reasonably apparent that progress is being or is likely to be delayed. Under JCT Design and Build 2024 specifically, that notice is now an express condition precedent: if the contractor fails to give it, the right to claim an extension of time is lost even where the delay itself was genuine and outside the contractor's control.

NEC contracts

The NEC family works on compensation events rather than extensions of time, but the principle is the same, applied more strictly. The contractor must notify the Project Manager of a compensation event within eight weeks of becoming aware of it. Miss that window and the contractor loses entitlement to additional time or cost for that event - there is very little room for a court or adjudicator to excuse a late notice under NEC's clear drafting.

Whichever form you're working under, the practical discipline is the same: as soon as a delay event is identified, issue notice in writing, in the format and timeframe the contract specifies, and don't wait for a full assessment of impact before doing so - most contracts allow the notice to be updated as the effect becomes clearer. Our full guide to extension of time claims sets out the notice-to-award process step by step, including how loss and expense interacts with an EOT once the completion date has moved.

• Read the specific notice clause in your contract - don't rely on general industry practice
• Treat notice deadlines as condition precedents unless you've confirmed otherwise
• Issue notice on becoming aware of a delay, then update it as the impact becomes clear
• Copy notices to the correct contractual recipient, not just a site-level contact
• Keep a log of every notice issued and the date it was received

Record-Keeping and Evidence for Delay Claims

A delay claim is only as strong as the contemporaneous record behind it. Assessors, contract administrators and adjudicators consistently give more weight to records created at the time of the event than to a narrative reconstructed months later, however accurate that reconstruction might be.

What to keep, and how

The baseline programme and every subsequent revision should be retained and version-controlled, so the effect of a delay event can be measured against the programme that was current when it occurred. Site diaries need to record cause and effect specifically - not just "delayed due to weather" but which activities were affected, for how long, and what alternative work (if any) was available. Progress photographs, dated and cross-referenced to programme activities, are inexpensive to collect and carry significant weight in a delay analysis. Correspondence - RFIs, instructions, notices and responses - should be filed by package and by date, not left scattered across email threads.

• Baseline programme plus every subsequent revision, version-controlled and dated
• Site diaries recording specific cause, activities affected and duration
• Dated progress photographs cross-referenced to programme activities
• All notices, RFIs, instructions and responses filed by package and date
• Labour and plant returns showing actual resourcing against the programme
• Minutes of progress meetings where delay was discussed or reported

When it comes to actually assessing the effect of a delay on the completion date, the method matters as much as the records. As-planned versus as-built, time impact analysis and windows analysis will produce materially different results from the same set of facts, and the right method often depends on what the contract requires and what records are available. Our dedicated guide to delay analysis methods walks through each approach and when to use it - read it alongside this guide before you commit to a methodology for a live claim.

When and How to Escalate

Most delays are resolved through the ordinary contract administration process - notice, assessment, extension of time or agreed recovery plan. But some situations need to be escalated beyond the site team before they cause lasting damage to the programme or the commercial position.

Escalate internally when a delay is likely to affect the critical path by more than a few days, when the cause is disputed, and the notice deadline is close, or when a recovery programme requires resource or budget beyond what the site team can authorise. Escalate to the client or contract administrator formally - in writing, referencing the relevant contract clause - when a response to a notice or extension of time request is overdue, or when access, information or an instruction the contractor needs is being withheld.

• Escalate internally once a delay threatens more than a few critical-path days
• Escalate formally when a contractual response deadline has passed
• Involve commercial/legal support before agreeing to acceleration cost you can't recover
• Consider adjudication where entitlement to an extension of time is genuinely disputed, and the relationship allows for it
• Keep escalation communications factual, dated and referenced to the contract clause relied on

Adjudication remains the most common formal route for resolving a live delay dispute in UK construction, precisely because it's designed to produce a decision within weeks rather than months. It doesn't have to mean the end of the working relationship - many disputes are resolved through adjudication and the parties continue on the same project afterwards - but it does require the same disciplined record-keeping described above. A well-documented delay claim, notified on time and supported by contemporaneous records, is far more likely to be resolved by agreement long before it reaches that stage.

Frequently Asked Questions

What counts as a construction delay under UK contracts?

A construction delay is any event that pushes activities on the critical path later than the current programme allows, extending the contractual completion date. Not every slippage counts - only delays affecting the critical path typically justify an extension of time, which is why an accurate, regularly updated programme is essential.

What is the difference between mitigation and acceleration?

Mitigation reduces the impact of a delay without materially increasing cost, typically through resequencing and better coordination. Acceleration spends money - extra labour, plant or shifts - to recover lost time. Contractors are generally expected to mitigate reasonably, but are not expected to accelerate at their own cost unless instructed to do so.

How quickly must I notify the contract administrator of a delay?

This depends entirely on your contract. JCT typically requires notice as soon as delay becomes reasonably apparent, and under JCT Design and Build 2024 this is an express condition precedent. NEC requires notification of a compensation event within eight weeks of the contractor becoming aware of it, with strict consequences for missing that window. Always check the specific clause rather than relying on general practice.

Can the client deduct liquidated damages if I don't get an extension of time?

Yes. If the completion date passes without an agreed extension of time, the employer can typically deduct liquidated and ascertained damages (LADs) for every day or week the project overruns, up to any contractual cap. This is why timely notice and a well-evidenced extension of time claim matter commercially, not just administratively.

What evidence do I need to support a delay claim?

At minimum: the baseline programme and all revisions, contemporaneous site diaries recording cause and effect, dated progress photographs, all relevant correspondence and instructions, and labour or plant returns showing actual resourcing. The strongest claims combine this evidence with a recognised delay analysis method applied consistently.

Who is responsible for concurrent delay?

Concurrent delay - where a contractor-caused delay and an employer-caused delay both affect the critical path at the same time - is one of the more contested areas of UK construction law. Many contracts and much case law support the contractor still receiving an extension of time in genuine concurrency, but not usually loss and expense for the concurrent period. The specific contract wording and the facts of the case both matter significantly.

When should I escalate a delay dispute to adjudication?

Consider adjudication when entitlement to an extension of time is genuinely disputed, informal discussions have stalled, and the financial or programme impact is material enough to justify the process. Adjudication is designed to deliver a decision within roughly 28 days, making it a faster route than litigation or arbitration for live delay disputes.

Final Thoughts

Dealing with construction delays in the UK is rarely about avoiding them entirely - it's about building the habits that let you catch delay early, respond proportionately, and protect your contractual position while you do it. The projects that experience a serious delay with the least commercial damage are almost always the ones where notice was given on time, records were kept as the delay unfolded rather than reconstructed afterwards, and recovery efforts were focused squarely on the critical path.

None of this replaces a proper extension of time claim or a formal delay analysis once the dust settles - those are specialist exercises worth getting right, and our dedicated guides below go into both in detail. But the groundwork covered here - early warning signs, mitigation versus acceleration, recovery programmes, notice obligations and record-keeping - is what determines whether that later claim has the evidence it needs to succeed.

Want the full picture? The EOT and delay analysis process end-to-end?

For the technical side of extending the completion date and proving delay after the event, read our guides on Extension of Time (EOT) in Construction: A QS Guide, Delay Analysis Methods in Construction: A Practical Guide, and Construction Adjudication Explained: Your Rights and the Process.