Disruption Claims in GCC Construction: How Contractors Quantify and Recover Loss of Productivity

The Most Overlooked Source of Margin Loss on GCC Projects

Most GCC contractors know how to claim for delay. They file extension of time claims, reference their daily construction reports, and argue about critical path float. But disruption is different and far more contractors lose money on it than they realize.

Disruption does not push completion back. It makes everything on the programme more expensive. Workers move slower because access keeps changing. Rebar fixers are mobilized and stood down three times in a week because the preceding trade is behind. Tower cranes are tied up moving materials to zones that are not ready. No individual event is catastrophic enough to file a claim. But the cumulative effect is real: productivity drops 20%, 30%, sometimes more and no one has a clear picture of why or how much it cost.

In GCC construction, disruption often goes uncompensated not because contractors do not have entitlement. FIDIC Clause 17 and employer-risk events under Clause 8.5 create clear liability pathways. But contractors cannot quantify the impact in a way that survives scrutiny.

What Is Disruption? (And Why It Is Not Delay)

Extension of time (EOT) claims are about time. Disruption claims are about cost.

An EOT compensates a contractor for completing late. A disruption claim compensates a contractor for the additional cost of doing the same work under impaired conditions.

The three elements of a disruption claim:

• Causative event: An employer-risk event that changed planned working conditions such as late access, variations instructed mid-sequence, late design information, or client-instructed workforce mobilizations
• Effect: Reduced productivity below the planned rate
• Quantification: Measurable difference between what the work should have cost and what it actually cost

FIDIC Yellow and Silver Book Clauses 17.2, 8.5, and 13.1 all create entitlement pathways. But entitlement is not enough. GCC dispute adjudication boards expect a specific quantification method and contemporaneous evidence behind it.

The Three Methods GCC Arbitrators Actually Accept

1. Measured Mile Analysis

The most accepted method in international construction arbitration and the one most GCC contractors cannot run because they do not have the underlying data.

Measured mile analysis compares productivity in an unimpacted period against productivity in the disrupted period.

Example: A rebar fixing crew on a SAR 220M Riyadh residential tower achieves 3.8 tonnes per gang-day in the first 10 weeks, when the work sequence is undisturbed. After the client instructs structural changes on Level 7 that force repeated standdowns across three floors, the same crew drops to 2.3 tonnes per gang-day over the following 8 weeks.

The disruption impact: (3.8 minus 2.3) divided by 3.8 = 39.5% productivity loss.

For this to stand up in a DAB or arbitration, you need:

• Daily work confirmation records showing actual quantities completed by crew per day
• Crew composition records from daily logs or timesheets
• The causative events documented with dates and scope
• Evidence that external factors such as weather or contractor-caused issues are excluded from the disrupted period

Without the daily data, measured mile becomes an estimate. Arbitrators discount estimates heavily.

2. Earned Value / Planned vs Actual

Where measured mile requires two comparable periods, earned value analysis compares the programme-planned productivity rate against actual performance.

Planned rate: 2,800 tonnes rebar for Levels 7 to 14 in 12 weeks = 233 tonnes/week. Actual rate: 2,800 tonnes completed in 19 weeks = 147 tonnes/week.

The disruption factor: (233 minus 147) divided by 233 = 37% productivity loss.

The limitation: this method is only as credible as the baseline programme. GCC clients especially Aramco and NEOM scrutinize the baseline hard. If it was optimistic at tender, the impacted period looks worse than it should. A formally accepted, resource-loaded Level 3 Primavera baseline, archived at contract award, is a prerequisite for this method to carry weight.

3. Industry Study Method (MCAA / AACE)

When neither measured mile nor earned value is available, contractors fall back on industry productivity studies such as MCAA Factor tables or AACE International guidelines which assign productivity loss percentages to specific disruptive events including stacking of trades, overcrowding, overtime, and out-of-sequence work.

GCC arbitrators accept this method, but treat it as corroborating evidence rather than primary proof. It works best when combined with contemporaneous records showing the disruptive condition existed.

The Data You Need and When to Start Collecting It

Disruption claims are lost because data collection starts after the disruption, not during it. By the time the contractor assembles a claim, they are reconstructing history from memory and email chains.

Five records that build disruption claims passively:

• Daily Construction Reports with structured constraint fields. Not free-text notes but a forced dropdown of constraint categories (access, design, materials, concurrent trades, weather, client instruction) with start time, duration, and accountable party per event. A DCR capturing a specific standdown with cause and location is evidence. A note saying disrupted is not.
• Trade-level headcount records. The disruption calculation needs to know who was on site, in which zone, doing what. A gate-level biometric record capturing subcontractor and trade provides the foundation. Work orders tied to daily attendance make the productivity calculation possible.
• Work confirmation quantities by location. If your work confirmations record only a lump total, you cannot run a measured mile analysis by floor or zone. Location-coded quantities are the unit rate data that makes the comparison possible.
• Equipment standby records. Cranes, man-lifts, and formwork systems have a daily hire or ownership cost. When they stand by because a zone is occupied or design has not been issued, those costs are recoverable but only if the standby reason is documented with a reason code.
• FIDIC Clause 20 notices. A disruption claim submitted without contemporaneous notices is immediately questioned. The notice does not need to quantify the impact. It needs to identify the event and state an intent to claim. Filing a Clause 20.2.1 notice within 28 days of becoming aware of a disruptive event protects entitlement even if the full claim comes months later.

The GCC-Specific Challenge: Concurrent Disruption

NEOM, ROSHN, and Aramco mega-projects run multiple prime contractors on the same footprint. Disruption claims on these projects hit an immediate counter-argument: concurrent disruption.

If a contractor is simultaneously disrupted by a client-caused event (late access) and their own issues (insufficient crew), the claim value is reduced proportionately. GCC dispute panels are sophisticated enough to split the apportionment and they will.

The contractor defence: structured DCRs that distinguish employer-caused standdowns from contractor-caused slowdowns. Without that distinction in the contemporaneous record, apportionment goes against the contractor.

What a Quantified Disruption Claim Looks Like

A defensible disruption claim has four components:

• Causation narrative: The sequence of employer-risk events with dates, FIDIC reference, and correspondence trail
• Productivity impact analysis: Measured mile, earned value, or industry study in that order of preference
• Cost calculation: Actual labour cost in the disrupted period minus the planned cost at the planned productivity rate, plus equipment standby costs
• Notice register: Every Clause 20.2.1 notice sent during the disruptive period, indexed to the causation narrative

A unified construction platform builds this passively. Work confirmations capture daily quantities by location. Timesheets allocate actual labour hours to WBS codes. Equipment logs record standby with reason codes. DCRs classify constraint events to accountable parties. When the claim needs to be assembled, the data already exists. The exercise becomes analysis, not reconstruction.

Five Practical Starting Steps

• Add constraint categories to your DCR template now. Not after the disruption. Define 6 to 8 categories with accountable parties. Capture it daily, including when nothing unusual happens.
• Configure work confirmations with floor and zone codes. If your system records quantities at work package level only, you cannot run a measured mile. Location-coded quantities are the foundation.
• Set up equipment standby reason codes. Idle crane time costs money. If it is employer-caused, it is recoverable. Document the reason in the system, not in a chat message.
• Open a disruption notice tracker. Map every employer-risk event to a Clause 20.2.1 notice. Build a tracker that flags the 28-day deadline automatically.
• Lock the baseline programme before work starts. A resource-loaded Level 3 Primavera baseline, formally accepted by the client, turns a productivity comparison from a guess into a calculation.

Disruption is the claims category most GCC contractors lose not because they lacked entitlement, but because they lacked data. The records that build a disruption claim are the same records that run an efficient project: daily logs, confirmation quantities, timesheet codes, equipment standby. The only question is whether your system captures them at the granularity a DAB or arbitration will accept.