Delay And Disruption In Construction Contracts

Getting Paid for Delays and Disruption: What Nobody Tells You

The difference between delay and disruption in construction contracts matters more than most people realize, and getting it wrong is how companies leave six figures on the table or find themselves in arbitration for three years. I learned this the hard way on a hospital extension project in 2019 where we claimed delay damages for a three-month weather-related hold and got told we had no case because we hadn't actually demonstrated critical path impact. We ended up settling for half what we thought we were owed, and the whole problem traced back to how we'd documented things from day one. Delay means the project completion date has moved. Disruption means the work that was supposed to happen on schedule took longer or cost more, even if the overall completion date hasn't shifted. These are separate concepts with separate evidential requirements, and most claims fail because the two get mixed together into one muddled narrative. A delay claim needs to prove that a specific event pushed the critical path out. A disruption claim needs to show that productive working hours were lost to inefficiency—things like trade stacking, lost momentum, rework, or access restrictions—even if the final date stayed the same. Under standard forms like JCT, NEC, and FIDIC, the contractual mechanisms differ substantially. NEC4 requires compensation events to be notified within eight weeks of becoming aware, and failure to comply can extinguish the right to additional time or money entirely. JCT contracts have different notice periods depending on which edition you're dealing with, and the distinction between regular progress and materially affected progress matters for whether you trigger relief. FIDIC is even more particular about the timing of notices, and the Engineer's determination carries significant weight before it gets challenged.

One thing beginners consistently miss is that prolongation costs and disruption costs are calculated differently. Prolongation is straightforward—it's the time-related expenses that run longer because the project runs longer. Site overheads, plant hire, preliminaries. You multiply your daily rate by the number of days of delay. Disruption is messier because it's about loss of productivity, not just extended time. You might finish on time but have spent more because workers were constantly tripping over each other. The two feed into each other but require different evidence and different calculation methods. I once spent six weeks trying to quantify disruption on a school build where the M&E contractor was working on two floors simultaneously while the fit-out team was below them. The programme showed no delay, but our actual productivity dropped by roughly thirty-two percent compared to the baseline. We used the measured mile approach, comparing actual output rates against a section of the works that proceeded without interference. That section happened to be the ground floor entrance lobby, which had zero conflicts. The contrast between the two areas gave us a defensible figure. The employer's quantity surveyor challenged it on the basis that the ground floor was simpler, so we ended up using three reference points instead and triangulating the numbers. It took longer but held up under scrutiny.

How to Build a Defensible Claim

Start by understanding what your contract actually says about notices and entitlement. Not one person in my experience has ever been penalized for being too careful about contractual deadlines. The most common mistake is assuming that because you've been writing emails about delays, you've satisfied the notice requirement. Most contracts require a specific form of words, submitted within a specific window, to a specific person. An email to the site manager doesn't count if the contract says notices go to the contract administrator. This isn't pedantry—it's often the difference between winning and losing at adjudication. For delay analysis, the time impact analysis method is the most widely accepted approach. You take the as-planned programme, insert the delay event at the point it occurred, and show how the critical path shifts. The problem is that most programme updates in the industry are terrible. If your baseline programme was never properly developed or hasn't been regularly updated with actual progress data, your delay analysis rests on a foundation of fiction. I've seen claims fail because the respondent's expert demonstrated that the claimant's programme didn't reflect reality even before the disputed event occurred. Once credibility goes, everything following it goes with it. Here's a workaround that I use now and wish someone had told me earlier. Before you worry about delay analysis, audit your own programme documentation. Check that every activity has a realistic duration, that logic links make sense, and that the critical path at any given point aligns with what's actually happening on site. Do this weekly, not monthly. When you spot a discrepancy between the programme and reality, update the programme contemporaneously and document why. If you get to the point of making a claim, you'll have a contemporaneous record showing you understood the impact as it was happening, not six months later when you're reconstructing events from memory.

For disruption, the earned value method and the measured mile method are your main tools. Earned value requires a well-developed cost-loaded programme from the start, which most contractors don't have. The measured mile is more accessible but only works if you have an uncontaminated section of work to compare against. When neither is available, you fall back to industry-standard guidelines like the SCL Delay and Disruption Protocol, which outlines accepted methodologies but doesn't guarantee acceptance by courts or arbiters. I've found that judges and arbitrators tend to prefer methods they can understand quickly. A simple measured mile comparison with clearBefore and after productivity figures will often persuade more than a sophisticated but opaque mathematical model. There's a specific edge case that bites people regularly: concurrent delay. This is when two delaying events affect the same path at the same time—one from the employer, one from the contractor. Under English law, the leading case is Henry Boot v Malmaison, which established that concurrent employer and contractor delays entitle the contractor to an extension of time but not to delay damages. The rationale is that the contractor would have been delayed anyway by their own fault, so they shouldn't profit from the employer's delay. This sounds fair but creates serious problems in practice because it's rarely clear which delay was truly concurrent. On a retail fit-out project I worked on, the client delayed the handover of a floor by two weeks while we simultaneously had a labour shortage. The adjudicator found the delays were concurrent and awarded time but no money. The employer then pointed out that our labour shortage was partly caused by their delayed handover reducing available work face, which meant our delay wasn't entirely independent. The decision got complicated enough that both sides settled before going further. Another area where people get tripped up is the difference between weather delay and adverse weather. Most contracts provide for exceptionally poor weather as a relevant event. The question is always what counts as exceptional. The Met Office historical data is your friend here. I keep a spreadsheet of rainfall and temperature data for every project location, plotted against the contract period average. When the actual conditions deviate by more than one standard deviation from the norm, you have an objective basis for a claim. Subjective claims about bad weather get dismissed quickly. Objective data backed by an independent meteorological source carries weight.

Common Pitfalls and What to Do Instead

The biggest pitfall is retrospective analysis. Trying to reconstruct what happened after the fact without contemporaneous records is like trying to remember what you had for breakfast last Tuesday. You'll fill the gaps with assumptions, and assumptions get claims killed. The second biggest is poor programme management. A programme that's just a graphical Gantt chart without proper logic linking, float ownership analysis, or regular updates is essentially decorative. It looks professional but proves nothing. Treat your programme as a living document, not a submission artifact. A third pitfall is claiming for everything that costs more. If a delay event causes your labor rate to go up because workers are sitting idle and then working overtime to recover, you need to demonstrate the causal link clearly. Overtime costs alone don't prove entitlement. You need to show that the overtime was necessary to mitigate the delay, that it was reasonable, and that it wouldn't have happened otherwise. Documentation here is everything. Daily site records, resource histograms, overtime authorizations, and attendance sheets all feed into this. For smaller contractors who don't have dedicated claims departments, the practical approach is to focus on contemporaneous recording from day one. A simple daily site log noting weather conditions, workforce numbers, activities in progress, resources deployed, and any interruptions or access issues is surprisingly effective. Take photos daily. Keep delivery notes. Record meetings with brief written summaries sent to all attendees within twenty-four hours. These documents won't win you a case on their own, but they'll prevent your claim from collapsing when the other side challenges your recollection. Six months after a project ends, nobody remembers what happened on a random Tuesday in March, but a dated photo and a signed meeting summary don't forget.

If you're dealing with a standard JCT contract, the relevant provisions are typically clauses 2.25 through 2.30 in the 2016 edition, covering extensions of time and relevant events. For NEC4, it's clauses 6.3, 6.4, and 6.5 for compensation event notification and assessment. FIDIC 1999 Red Book relies on clause 8.4 for extension of time and clause 13.3 for variations that may constitute disruption. Each has subtle differences in how they treat concurrency, notice requirements, and the assessment methodology. Don't assume that experience with one form translates directly to another. The reality is that delay and disruption claims are as much about process and documentation as they are about technical analysis. The best claim in the world dies if it was never properly noticed, never properly particularized, and never supported by contemporaneous records. The worst claim sometimes survives if the other side can't confidently rebut it due to their own documentation failures. That's not how it should work, but it's how it does work in adjudication and arbitration, where procedure often decides the outcome before the merits are fully explored.