Disruption vs Delay: Claiming for Lost Productivity

Two of your crews worked all year in conditions nobody priced for - constant re-sequencing, trade stacking, out-of-order access, drawings that arrived in dribs and drabs. The programme still hit its dates, so there is no extension of time to claim. But your labour hours ran thirty percent over the estimate and nobody paid for the extra. That is disruption, and it is the most under-recovered head of loss in construction. It is quietly worked into the cost base, absorbed, and forgotten - because most contractors do not understand that it is a distinct claim requiring distinct proof.

Delay and Disruption Are Not the Same Claim

Delay is about time. Specifically, it is about lost time on the critical path - the sequence of activities that, if extended, pushes out completion. When a delaying event hits a critical activity, the project finishes later, and the remedy is an extension of time and, where the event is compensable, the time-related costs of staying on site longer. Delay is measured in days and its currency is the completion date.

Disruption is about productivity. It is the loss of efficiency - work that still got done, but took more labour and plant hours than it should have because the conditions in which it was performed were degraded. Disruption does not necessarily move the completion date at all. You can be disrupted to the tune of thousands of wasted man-hours and still finish on time, because you threw more resource at the problem or reworked the sequence. The currency of disruption is not days but lost output per hour worked. That single difference - time versus efficiency - is why the two claims are proven in completely different ways, and why treating disruption as a species of delay is a recipe for rejection. If you need to ground the time side first, our overview of delay analysis methods sets out how critical-path delay is actually demonstrated.

Why Disruption Is Harder to Prove

Delay has a natural evidential anchor: the programme. You can point to a critical activity, show the event that hit it, and demonstrate the knock-on to completion through a recognised analysis. Disruption has no equivalent. There is no single line on the programme that says here is where efficiency was lost. The loss is diffuse - a bit slower here, some standing time there, a crew that never got a clean run at the work. It shows up in aggregate as more hours than planned, but the raw fact that you overran your labour estimate proves nothing on its own, because you might simply have under-priced the work or managed it badly.

That is the core difficulty. To recover disruption you have to prove three things at once: that productivity was actually lost, that it was lost because of events the other party is responsible for, and that your own performance was not the cause. The last of those is what sinks most claims. A tribunal confronted with a labour overrun will ask the obvious question - how do we know this is disruption and not just inefficiency, poor supervision, or an optimistic tender? Answering that requires you to isolate the employer-caused loss from every other reason your hours might have run high, and that is a genuinely demanding exercise in causation.

The Measured Mile - and What to Do When You Cannot Use It

The most respected method for proving disruption is the measured mile. The logic is elegant: find a period on the same project, doing the same kind of work, where you were not disrupted, and measure your productivity there. That undisrupted period becomes your baseline - your mile. Then measure your productivity during the disrupted period and compare. The gap between the two, applied to the disrupted quantities, is your lost productivity, expressed in the project's own real conditions. Because the baseline comes from your actual performance on this job rather than from a textbook norm, it neutralises the objection that you simply tendered too keenly - your own good weeks set the standard against which your bad weeks are judged.

The measured mile is powerful but it is not always available. It needs a genuinely comparable undisrupted period, and on a project that was disrupted from mobilisation to handover there may be no clean stretch to measure. Where the ideal baseline does not exist, there are other approaches, each weaker and more contestable: an earned-value or planned-versus-actual comparison of budgeted against expended hours; industry productivity studies applied to the disruptive events (blunt, and easily attacked as generic); or a bottom-up factual narrative that ties specific disruptive events to specific pockets of lost output. The hierarchy matters - a measured mile drawn from your own records beats a published study every time, and a study applied honestly beats a total-cost claim that simply blames the employer for the entire overrun. That last approach, the global claim, is the weakest of all and the first thing an opponent will attack.

Records Are the Whole Game

Every method above is only as good as the records feeding it, and this is where disruption claims are won or lost long before anyone drafts them. To run a measured mile you need productivity data granular enough to isolate a period, a location, and a work type - allocated labour hours against measured output, week by week, area by area. Most contractors simply do not capture their hours at that resolution, and by the time the claim is contemplated the raw material is gone. You cannot reconstruct productivity retrospectively from memory. It has to be recorded as the work happens.

The records that matter are the unglamorous ones: timesheets allocated to specific activities and locations, daily labour and plant returns, output and progress measurements tied to the same breakdown, and a contemporaneous log of the disruptive events themselves - the re-sequencing instructions, the late access, the drawing revisions, the trade-stacking - each dated and linked to the crews it affected. This is exactly the discipline set out in our note on the contemporaneous records that make or break a delay claim, and it applies with even more force to disruption, because disruption has no programme to fall back on. The records are not supporting evidence for the claim. They are the claim. Where the events causing the disruption are also compensable under the contract, the same contemporaneous file supports notice and causation - and getting that machinery right is what our claims and recovery service is built to do.

Build the Claim While the Work Is Live

The single biggest predictor of a successful disruption claim is that somebody started building it while the disruption was happening. Because the loss is diffuse and the causation demanding, a disruption claim assembled after handover from incomplete timesheets is almost always vulnerable. The contractor who flags disruptive events as they occur, captures productivity data at the right granularity, and preserves a clean undisrupted period as a potential baseline has an evidenced claim. The contractor who absorbs the pain all year and reaches for a total-cost number at the end has a grievance, not a claim.

Practically, that means treating disruption as a live commercial workstream, not an end-of-job exercise. Notify the events under the contract as they arise. Ring-fence the data. Identify your measured mile early and protect the records that define it. Keep the disruption log current. None of this is glamorous and all of it competes with the pressure of actually building the job - which is exactly why it gets neglected and why so much legitimate lost productivity is never recovered. The work is not proving disruption at the end; it is capturing it as you go.

Frequently Asked Questions

What is the difference between a delay claim and a disruption claim?

Delay concerns lost time on the critical path - an event pushes out the completion date and you claim an extension of time plus the cost of staying on site longer. Disruption concerns lost efficiency - work still gets done but consumes more labour and plant hours than it should because conditions were degraded. Crucially, disruption need not affect the completion date at all; you can finish on time and still have burned thousands of wasted man-hours. Because one is measured in days and the other in lost output per hour, they are proven in entirely different ways.

Can I claim disruption if the project finished on time?

Yes - and this is precisely the situation disruption is designed to capture. Disruption is loss of productivity, not loss of time, so an on-time completion does not extinguish it. If re-sequencing, poor access, trade stacking, or late information forced your crews to work far less efficiently than planned, you absorbed real cost even though the programme held. Finishing on time often means you spent extra resource to overcome the disruption, which is the loss itself. The claim depends on productivity records, not on any movement in the completion date.

What is the measured mile method?

It compares your productivity during a disrupted period against your own productivity during a comparable undisrupted period on the same project doing similar work. That undisrupted period is the baseline - the mile. The difference in output per hour, applied to the disrupted quantities, quantifies the lost productivity. Its strength is that the baseline comes from your actual performance on this job, which neutralises the argument that you simply tendered too low. Its limitation is that it needs a genuinely clean undisrupted period to exist, which a heavily disrupted project may not offer.

Why do disruption claims fail so often?

Two reasons, usually. First, records - disruption has no programme to anchor it, so without granular productivity data allocated to activity and location, there is nothing to measure and the claim collapses. Second, causation - a labour overrun on its own proves nothing, because it could equally be under-pricing or poor management, and the contractor must actively isolate the employer-caused loss from those alternatives. Claims that lean on a total-cost or global approach, simply blaming the other party for the whole overrun, are the most vulnerable of all.

What records do I need to prove disruption?

Granular ones, captured as the work happens. You need labour and plant hours allocated to specific activities and areas, output or progress measured against the same breakdown, and a contemporaneous log of the disruptive events - re-sequencing, late access, drawing revisions, trade stacking - each dated and linked to the crews affected. This resolution is what lets you run a measured mile or a credible planned-versus-actual comparison. It cannot be reconstructed after the fact, so the discipline has to be in place while the crews are on the ground, not assembled at handover.

Disruption is real money hiding in your labour hours - but only the contractor who records it as it happens ever gets to collect it.

Note: This article is general guidance on disruption and productivity claims and is not legal advice on any specific project - the right method and entitlement depend on your contract and records, so seek tailored advice before proceeding.