Disruption Cost Claims: How to Prove and Calculate Lost Productivity
The job finished roughly on programme — no overrun to point to, no Extension of Time to hang a cost claim on — yet the crew worked flat out for three months and produced far less than planned. That gap is disruption, one of the hardest claims to get paid because it never shows up as a missed date. This guide shows how to prove it and calculate what it is worth.
What a Disruption Claim Is — and What It Is Not
A disruption claim is a claim for lost productivity. An event outside the Contractor's control — a late instruction, a redesign, restricted access, out-of-sequence work — makes the same labour and plant produce less output than it would have, undisturbed. The crew is on Site the whole time; it is just working less efficiently.
That is what makes disruption different from almost every other claim here: the completion date can stay exactly where it was, with no Extension of Time at all, and still leave a real, provable loss sitting in the labour and plant accounts.
What it is not: a disruption claim is not a complaint that the job was harder than expected, nor the gap between the tender allowance and what actually happened. Normal risk and ordinary site friction stay the Contractor's own risk. A disruption claim isolates the loss caused by one identifiable event — not general bad luck.
Key Takeaway: Disruption is lost productivity, not lost time. The crew stays on Site and the completion date can even stay the same — the loss is that the same resources produced less output because of a specific event, not general bad luck.
Disruption vs Prolongation — Keep Them Apart
Disruption gets confused with prolongation constantly, and the confusion is expensive, since the two are proven in completely different ways.
- Prolongation — the Works took longer. The claim is the time-related cost of the extra duration: overheads, retained staff, standing plant.
- Disruption — the Works became less efficient. The claim is the lost output during a period, whether or not the end date moved.
A single cause can trigger both — a late design issue might extend the programme (prolongation) and also force out-of-sequence working beforehand (disruption). Treat them as two claims sharing a root cause, each proven on its own evidence, never one blended number. See the companion guide on prolongation cost claims for the time-related side.
Key Takeaway: Prolongation is about duration; disruption is about efficiency. The same event can cause both, but they need separate evidence and separate figures — never one combined "delay and disruption" lump sum.
Which FIDIC Clause Covers Disruption?
None, by name. FIDIC has no sub-clause titled "disruption." The entitlement rides on whatever clause gives the Contractor Cost for the underlying event, with the loss measured as reduced productivity instead of extra duration.
- Variation (Sub-Clause 13) — a late or disruptive instruction forcing re-sequencing. Time and Cost both available. The clock runs from the instruction date, not from when the disruption was felt.
- Unforeseen Physical Conditions (Sub-Clause 4.12) — ground or hydrological conditions forcing a slower method. Time and reasonable Cost, no profit.
- Access to Site (Sub-Clause 2.1) — restricted or partial access forcing a disrupted sequence. Time and Cost.
- Employer's Risks (Sub-Clause 17.3) — an Employer-risk event disrupting the method of working without stopping it outright.
One clause matters precisely because it does not give Cost: exceptionally adverse climatic conditions under Sub-Clause 8.4(c) give time only. If weather is what disrupted the crew, there is an Extension of Time argument, but no cost head to attach a disruption figure to.
Whichever clause applies, the claim is notified the same way: through the general claims procedure in Sub-Clause 20.1 (1999) or 20.2 (2017). Disruption has no notice track of its own — it travels inside the notice for the underlying cause.
Key Takeaway: No standalone "disruption clause" exists. The entitlement comes from the underlying cause — Variation, Unforeseen Conditions, Access, or an Employer risk — notified through the ordinary Clause 20.1/20.2 procedure. Weather under 8.4(c) gives time only, so weather-driven disruption carries no cost.
The Measured Mile Method, Step by Step
The measured mile method is the most widely accepted way to prove and quantify disruption, because it uses the Contractor's own project data, not a generic industry average. Find a period on the same job where the same activity ran undisturbed, and compare it to the disrupted period.
- Pick the activity. Choose a repetitive, measurable activity — formwork, blockwork, cable pulling — performed both during and outside the disrupted period.
- Establish the undisturbed rate. Measure output per labour-hour during a representative period unaffected by the event — the "measured mile."
- Measure the disrupted rate. Measure the same metric, same activity, during the disrupted period.
- Calculate the loss. The gap between the two rates, applied to the quantity done in the disrupted period, gives the lost productivity.
- Check the comparison is fair. Confirm both periods used similar crew composition and work content, or the Engineer will argue the drop reflects something else.
Where no clean undisturbed period exists, published industry productivity studies can substitute as a fallback, though they persuade far less than the Contractor's own numbers.
Key Takeaway: The measured mile method compares actual output on the same activity, undisturbed versus disrupted, using the Contractor's own records — which beats an industry study every time.
Why the Total Cost Method Gets Rejected
The shortcut everyone is tempted by is the total cost method: take the final labour cost, subtract the tender allowance, and call the difference the loss. It is fast, and it is also the single most common reason a disruption claim is thrown out wholesale.
The problem is that the final cost reflects everything that happened on the job — the Contractor's own inefficiencies, tender pricing errors, and the disrupting event, all mixed into one number with no way to separate them. The Engineer only has to point to one plausible non-claimed cause to undermine the whole figure.
Use total cost only as a last resort, stripping out every cost not attributable to the event first. An activity-level comparison survives scrutiny that a subtracted lump sum will not.
Key Takeaway: Total cost — final cost minus tender allowance — gets rejected because it bundles the Contractor's own inefficiencies with the claimed event. Use an activity-level comparison instead, and treat total cost as a last resort only.
Records That Make the Claim Credible
A disruption claim is won or lost on contemporaneous output records, since the whole argument is a before-and-after comparison.
- Daily output records — quantities completed per activity, per day, broken down by crew.
- Labour and plant allocation sheets — who and what was deployed, and when.
- The baseline programme and planned productivity rates — the output assumed at tender.
- Site diaries and photographs — contemporaneous evidence of the conditions causing the slowdown.
- The notice and correspondence — showing the event was flagged at the time, not reconstructed afterwards.
Reconstructing output records months later, from memory or a final account exercise, is a poor substitute that reads that way to an Engineer who has seen it before.
Key Takeaway: Daily output records, allocation sheets, the baseline productivity assumption, and contemporaneous site diaries carry the claim. Records built after the fact are the weakest evidence and the first thing an Engineer discounts.
Notice and Particulars for a Disruption Claim
Disruption travels inside the ordinary notice for whatever clause triggered it. Serve the notice within 28 days of becoming aware the event is causing loss — or, for a Variation, within 28 days of the instruction, since that date starts the clock rather than awareness.
Keep the notice short — name the clause, describe the event, and flag that the Works are disrupted, without trying to prove the measured mile calculation on day one. That proof belongs in the particulars, due within 42 days under FIDIC 1999 (84 days under the 2017 Second Edition), stated as a specific number of days, never a vague reference to "the period prescribed by the Contract."
Getting that first notice out correctly, with the right clause already attached to the right facts, is the gap ChatNotice closes for the Contractor's general claims notices — the productivity analysis still has to be built separately, but the entitlement-protecting notice goes out on time.
Key Takeaway: The notice follows the underlying clause's clock — 28 days from awareness, or from the instruction date for a Variation. Keep the notice short; save the measured mile analysis for the particulars, due within 42 days on FIDIC 1999 or 84 days on the 2017 edition — never the 28-day figure.
Frequently Asked Questions
What is a disruption claim in construction?
A disruption claim is a claim for the lost productivity caused by an event that is not the Contractor's fault — the crew worked slower or produced less output than planned, even if the completion date did not move. It is a claim about efficiency, not duration, which separates it from a prolongation claim.
Is there a specific FIDIC clause for disruption claims?
No. FIDIC has no clause named "disruption." The entitlement comes from the underlying cause — a Variation under Sub-Clause 13, Unforeseen Physical Conditions under Sub-Clause 4.12, late Access to Site under Sub-Clause 2.1, or another Employer-risk event — assessed as lost productivity rather than extended duration, and notified through the general claims procedure in Sub-Clause 20.1 (1999) or 20.2 (2017).
What is the measured mile method?
The measured mile method compares the Contractor's actual productivity rate during a period unaffected by the disrupting event to its rate during the affected period, on the same or a comparable activity. The gap between the two rates, applied to the quantity done in the affected period, gives the lost productivity. It is widely accepted because it uses the Contractor's own project data rather than an industry average.
Do I get disruption costs for a weather delay?
No. Under the FIDIC 1999 Red Book, exceptionally adverse climatic conditions under Sub-Clause 8.4(c) give an Extension of Time only, with no entitlement to Cost. Disruption cost is a cost head, so it follows the same rule as any other cost claim under that clause — no cost clause, no disruption money, however badly productivity was hit.
Can I claim disruption and prolongation for the same event?
Yes, provided they are kept separate and each is proven on its own evidence. Prolongation is the time-related cost of being on Site longer; disruption is the lost productivity during the period the Works continued, whether or not the end date moved. The same event can cause both, but bundling them into one round figure is the fastest way to have the whole claim rejected.
Authoritative Sources
This guide reflects the FIDIC Conditions of Contract and established construction-law authority. For the primary materials, see:
- FIDIC Conditions of Contract — the official contract suite published by the International Federation of Consulting Engineers, which sets out the Sub-Clause 20.1 claims procedure that carries a disruption claim.
- SCL Delay and Disruption Protocol — the Society of Construction Law's protocol, which sets out the measured mile method and the other accepted approaches to quantifying disruption.
About the Author
Muhammad M. Jiwani is a Project Director with 15 years' experience on major infrastructure and energy projects administered under FIDIC contracts. He writes from first-hand experience serving notices and managing contractual claims on live projects.