Skip to content
The Measure
Briefing

Proving Disruption: The Hardest Claim in the Final Account

May 2026|7 min|4 parts
Key Takeaways
  1. KT.01Disruption is lost productivity, not lost time. It can exist without any delay to completion, and it is recovered as loss and expense or damages, with the burden squarely on the claiming party.
  2. KT.02The measured mile remains the most persuasive method, but it demands a clean comparator. Where none exists, alternative methods succeed only when applied with the same bottom-up rigour.
  3. KT.03Tribunals reward causation built from contemporaneous records. Global assertions of overspend fail, however large the number and however sophisticated the presentation.

Ask any quantum practitioner which head of claim is hardest to prove and the answer rarely varies: disruption. It appears in nearly every substantial final account dispute, it is frequently the largest single figure on the schedule, and it fails more often than any other. The reason is structural. Disruption is a claim about productivity, and productivity is invisible until it is measured.

PT.01

Lost productivity, not lost time

The two are routinely conflated, and the distinction matters. Delay is about time: the works finished later than they should have. Disruption is about efficiency: the works cost more to build than they should have, because labour and plant achieved less per hour than the contractor was entitled to expect. The SCL Delay and Disruption Protocol draws the line precisely, recognising that disruption can occur without any delay to completion at all.¹ A contractor can hold the completion date by flooding the site with additional resource and still carry a substantial disruption loss for the cost of doing so.

That is also why the compensation route differs. There is no extension of time to claim. Disruption is recovered as loss and expense under the contract, or as damages for breach, and the claiming party bears the full burden of establishing cause, effect, and quantum.

PT.02

The measured mile and its limits

The most persuasive method remains the measured mile: identify a period or section of the works unaffected by the events complained of, measure productivity there, and compare it with the impacted work. Done properly, the comparison strips out matters that sit at the contractor's own risk: tender optimism, poor supervision, defective workmanship. The logic has judicial pedigree reaching back to Whittall Builders v Chester-le-Street District Council, where output achieved in an undisrupted period provided the yardstick for valuing the disrupted one.²

The difficulty is that the method presumes a clean comparator, and complex projects rarely offer one. Where the whole site was impacted from the first week, or the works are too heterogeneous to compare, the analysis must reach for alternatives: earned value analysis, work sampling, programme-based studies, or, at the bottom of the evidential hierarchy, published industry productivity factors.³ None of these is illegitimate. Each is judged by the same test: does it demonstrate, rather than assert, the causal link between the event and the lost productivity?

A disruption claim is won or lost in the project records, long before an expert touches it.

PT.03

Where these claims die

The case law is a catalogue of self-inflicted wounds. In Van Oord v Allseas, claims presented with apparent sophistication collapsed on contact with the contemporaneous record: the witness evidence was contradicted by the documents, and the quantum evidence had taken the pleaded figures largely on trust.⁴ The judgment remains the standard citation for what happens when a disruption claim is built top-down from the overspend rather than bottom-up from the records.

Authority
Walter Lilly & Company Ltd v Mackay
[2012] EWHC 1773 (TCC) | Technology & Construction Court

Akenhead J's treatment of global claims: a total-cost presentation is not automatically barred, but the claimant assumes the evidential risk that any significant cause of the overspend was its own responsibility. That risk materialises with regularity.⁵

Read the source

The pattern repeats because the arithmetic is seductive. Actual cost minus tender allowance equals claim. But that formula assumes the tender was adequate, the site was otherwise efficient, and every unproductive hour traces to the respondent. Tribunals do not extend that courtesy, and opposing experts are retained precisely to withhold it.

PT.04

Building the claim bottom-up

What the evidence base requires
  • 01A baseline: tender build-ups, productivity norms, or an unimpacted comparator, established before the impacted analysis begins
  • 02Resource records: allocation sheets, timesheets, and plant returns showing where labour actually went, week by week
  • 03Cause-and-effect mapping: each disruptive event tied to the specific work fronts, trades, and periods it affected
  • 04Contemporaneous corroboration: site diaries, progress photographs, and correspondence recording the disruption as it happened, not as reconstructed for the dispute
The Meritus View

At Meritus Via, disruption analysis starts with the records, not the pleaded number. Our platforms ingest timesheets, allocation sheets, daily diaries, and progress data at scale, then reconstruct where resource was deployed and what it achieved, period by period. Where a measured mile exists, it is identified from the data rather than asserted from recollection.

The result is a productivity analysis a tribunal can interrogate: every figure traced to a source document, every impacted period tied to a cause. Claims built this way settle more often than they fight, because the opposing expert can verify them rather than merely dispute them.

The views expressed in this article are those of the author and are intended for general information only. They do not constitute legal advice and should not be relied upon as such. Specific professional advice should be sought in relation to any particular matter.

Discuss your position

Direct access to a partner. No intermediaries.

Discuss Your Matter
100GB+
Per matter. In hours.