Concurrent Delay Map Source
Concurrent delay · England, Scotland and the SCL Protocol

Same delays. Different law. Different answer.

Research by Charles Gava

Set up an employer delay and a contractor delay on the programme below. Each legal approach then decides how much extra time the contractor gets, how much of it is paid, and how much the contractor carries as its own delay.

Load a stylised case:

1 · The facts on the programme

Drag a bar to move it. Drag its right edge to change its length. Arrow keys work too.
Employer delay (e.g. a late variation)
starts on day
lasts (days)
Contractor delay (e.g. late façade package)
starts on day
lasts (days)
How the two delayed activities relate
Float before each delay hits completion (days)
employer's path
contractor's path

2 · What the delays did to completion

0days late

3 · Seven legal answers to the same facts

Extension, paid Extension, time only Contractor's own delay (damages exposure)

Adjust the Scottish (City Inn) assumptions
Relative culpability (used to split shared days)
employer
contractor

4 · Where the choice of law matters

Each point is a different employer delay: when it starts (left to right) and how long it lasts (bottom to top). Everything else stays as set above.

Darker means the approaches disagree by more days. Pale means the law you pick makes little difference.

The orange band marks when the contractor's delay is running. The ring is your current employer delay. Click the map to move it.

0 days apart
How each answer is worked out

The programme is treated as a causal model. For any combination of the two delays it gives the delay to completion against the as-planned date. Each legal approach is then a rule applied to the same three numbers: the delay the employer's event would cause alone, the contractor's alone, and both together.

  • Actual-delay test: an employer delay counts only if it causes actual delay to completion as then scheduled (Adyard [2011] EWHC 848 (Comm) paras 279–299; Saga Cruises [2016] EWHC 1875 (Comm) para 251). If it does, the contractor's concurrent delay does not reduce the extension (Malmaison; Walter Lilly [2012] EWHC 1773 (TCC) para 370; Thomas Barnes [2022] EWHC 2598 (TCC) paras 118 and 148). This is the only rule here that matches all five English cases. It was written after reading those judgments, so the match shows consistency, not independent prediction.
  • As-planned impact: impacts the employer's delay on the as-planned programme and ignores timing. Adyard (para 264) and Saga (para 249) reject this kind of theoretical delay.
  • Overlapping windows: any delays whose effects overlap in time are concurrent. A broad reading of the “felt at the same time” wording in Adyard para 279.
  • Strict sequence: only delays that start on the same day are concurrent. Otherwise a later employer delay earns time only for the delay it adds on top. Some commentators attribute this to Adyard, but the judgment states the test above.
  • NEC4 (clause 63.5, reading to verify): each compensation event is assessed prospectively against the programme at the time, and time and money go together.
  • City Inn [2010] CSIH 68 (Scotland): a dominant cause takes the period. Otherwise the shared days are apportioned by relative culpability.
  • Cyden-style clause (North Midland v Cyden Homes [2018] EWCA Civ 1744): the contract excludes concurrent delay, so only days the employer alone caused count. This gives the same number as a but-for test.
  • Money under every approach follows only days that would not have been lost but for the employer (Keating 9-105, adopted in Thomas Barnes para 118).

The case presets are stylised two-path reconstructions. The dates and figures for Adyard, Saga and Thomas Barnes come from the judgments, read on the National Archives' Find Case Law service. Where a delay length is a party's claim or is worked back from the outcome, the preset note says so. Malmaison and Cyden use illustrative figures. City Inn is illustrative and its judgment text has not yet been checked. This is a research tool, not legal advice. The contract always governs.

One Schedule, Many Laws: doctrine-conditioned causal attribution for concurrent delay. Research prototype.