Concurrent Delay: Why the Contractor's Burden Is the Trap
In US federal practice, concurrent delay is a rule of proof, not substantive law: where both parties contribute to a delay, neither recovers unless the evidence permits clear apportionment, and it is the contractor, not the owner, who bears the burden of separating its own delay from the government's.
At a glance
- United States, federal practice principally
- FAR
- Case law and FAR clause references from secondary sources this pass (clause numbers/dates via acquisition.gov)
Key facts
- 01
Governing rule
Neither party recovers for concurrent delay unless the proof supports a clear apportionment of the delay and expense.
- 02
Nature of the rule
A rule of proof (evidentiary), not a rule of substantive law.
- 03
Sollitt's two-part test
Temporal (same delay period) and causation (each cause independently sufficient) aspects must both be present.
- 04
Burden most often missed
Separating the contractor's own delay from the government's. This is the contractor's burden, not the owner's.
- 05
Practical effect of concurrency
Converts a compensable delay into excusable-but-non-compensable: contractor keeps the time, loses the money.
- 06
Alares result
765 days claimed, 218 days of VA-responsible compensable delay awarded, apportioned period by period.
- 07
Alares and reservation of rights
Board upheld the contractor's reservation in mod. P00005. The claim was then cut down on the schedule evidence, a separate, independent ground.
- 08
Suspension routing risk
The CBCA's "sole cause" gloss (Lusk, Quality Trust) makes Changes (52.243-4) the safer vehicle over Suspension of Work (52.242-14) where any independent cause is present.
Where both parties contribute to a delay, neither recovers for it unless the evidence permits a clear apportionment of the delay and the expense attributable to each. That is the whole rule, and it is a rule about what the proof shows, not a substantive bar on either party's underlying entitlement. Blinderman Construction Co. v United States, 695 F.2d 552, 560 (Fed. Cir. 1982)1 supplies the canonical sentence. Sauer Inc. v Danzig, 224 F.3d 1340, 1352 (Fed. Cir. 2000), restates it almost verbatim two decades later. Where apportionment is genuinely supported, both sides recover pro rata for their severable periods. Where it is not, the practical effect is that concurrency converts a compensable delay into an excusable-but-non-compensable one: the contractor gets the time and loses the money, and the owner loses liquidated damages for that period but recovers nothing either.
The two-track result, in one 2025 case
ECC International Constructors, LLC, ASBCA No. 59586 (18 April 2025)2 is now the cleanest illustration of the concurrency rule in US practice, and it should be the first case cited on the point. Of 389 days of government-caused design delay, 205 were concurrent with contractor-side entry-control-point delays. Because the concurrent non-government delay (205 days) exceeded the government-caused design delay (119 days), the board held ECCI was not entitled to any compensable delay. Yet liquidated damages were still remitted for 119 days at $2,338.99/day ($278,339.81) on the separate excusable-delay footing.
That is the two-track result international practitioners routinely miss: concurrency defeats money but not necessarily time. A federal claimant should always plead the excusable-delay/LD-remission case in the alternative to the compensable-delay case, because it survives concurrency even when the primary claim doesn't: in ECC International the alternative case was the only recovery, and it was worth over a quarter of a million dollars.
The same decision is also a warning on quantum and on experts. An Eichleay overhead claim multiplies a daily rate by days of delay, so a concurrently-delayed day that isn't compensable can't feed the Eichleay arithmetic either. The quality of an Eichleay claim is only as good as the concurrency analysis underneath it. And the board rejected the contractor's delay expert as "not credible… not helpful… intrinsically unpersuasive" for deliberately omitting one of 23 delay events while running fragnets on the other 22, a reminder that a concurrency defense is won or lost on the completeness of the schedule analysis, not just its conclusions.
Sollitt's two-part test
George Sollitt Construction Co. v United States, 64 Fed. Cl. 229, 239 (2005), gives the working definition courts actually apply. Concurrent delay has both a temporal and a causation aspect3: the competing delays must affect the same delay period, and each must be independently sufficient, on its own and without the other, to cause the days attributed to it. A delay that merely overlaps in time with another, without being independently capable of causing the same days of critical-path slippage, is not concurrent in the Sollitt sense. It is just coincidental in timing. The Sollitt court itself conceded that "the exact definition of concurrent delay is not readily apparent from its use in contract law", an unusually candid admission that the term carries more analytical weight than its own definition supplies.
The burden allocation: where the common assumption goes wrong
The common assumption is that the owner proves concurrency as a defence to the contractor's claim. That is only half right in federal practice. The government does typically raise concurrency and evidence it, usually through its own scheduling expert, but the persuasion burden on severability sits with the contractor throughout, on every issue that matters to recovery:
| Issue | Whose burden | Authority |
|---|---|---|
| Excusability, to defeat default or liquidated damages | Contractor | Sauer, 224 F.3d at 13474 |
| Extent of excusable delay, for LD remission | Contractor | Sauer at 1351 |
| Compensability (government caused it, critical path, harm) | Contractor | Sollitt, 64 Fed. Cl. at 238–39 |
| Separating its own delay from the government's | Contractor | Sauer at 1354 |
| Raising concurrency as an affirmative defence | Government raises and evidences it | Blinderman at 560, Sauer at 1354 |
The fourth row is the one that catches contractors: it is not the government's job to prove the contractor was concurrently at fault. It is the contractor's job to prove it wasn't, or, more precisely, to prove that the delay it is claiming was caused by the government and was not concurrent with delay of the contractor's own making. A contractor that proves a government-caused delay and says nothing about its own potentially overlapping delays has not proven a compensable claim. It has proven half of one.
Alares: the worked example
The "sole cause" gloss on suspension claims
A distinct 2024–25 development narrows the Suspension of Work route specifically. The CBCA has begun applying a sole-cause requirement to FAR 52.242-14 Suspension of Work6 claims that functions as a concurrency defence against both suspension costs and Eichleay recovery:
- In Lusk Mechanical Contractors, Inc. v GSA, CBCA 7759 (30 April 2024)7, a Governor's COVID stay-at-home order was held an equal cause of the suspension alongside the Contracting Officer's own suspension order. Because the government was not the sole proximate cause, the suspension claim failed.
- Quality Trust, Inc. v Department of the Interior, CBCA 7451 (4 April 2025)8 denied suspension and Eichleay recovery on the same reasoning, compounded by the contractor's own prior agreement to the suspensions.
Sources and authorities
- *Verification, unless noted
Secondary source. Case law in this cluster is not independently re-verified this pass
- 1Blinderman Construction Co. v United States695 F.2d 552, 560 (Fed. Cir. 1982)
Where both parties contribute to a delay, neither can recover damage unless there is in the proof a clear apportionment of the delay and the expense attributable to each party.
- 2ECC International Constructors, LLCASBCA No. 59586 (18 April 2025)
205 days of concurrent contractor-side delay exceeded 119 days of government-caused design delay, so no compensable delay was awarded, yet liquidated damages were remitted for 119 days at $2,338.99/day ($278,339.81) on the separate excusable-delay footing. The board also rejected the contractor's delay expert as not credible for deliberately omitting one of 23 delay events from the fragnet analysis.
- 3George Sollitt Construction Co. v United States64 Fed. Cl. 229, 239 (2005)
Concurrent delay has both a temporal and a causation aspect: the delays must affect the same period, and each must be independently sufficient to cause the days attributed to it.
- 4Sauer Inc. v Danzig224 F.3d 1340 (Fed. Cir. 2000)
Sets the federal burden allocation: the contractor bears the burden of excusability, of the extent of excusable delay, and of separating its own delay from the government's (at 1347, 1351 and 1354 respectively).
- 5Alares Construction, Inc. v Department of Veterans AffairsCBCA 6149, 7071, 7597 (21 March 2025)
765 days of delay claimed against the VA, 218 days awarded as VA-responsible compensable delay, apportioned period by period. The Board upheld the contractor's reservation of rights and the claim was then cut down on the schedule evidence, an independent ground.
- 6FAR 52.242-14: Suspension of WorkFAR 52.242-14
The Suspension of Work vehicle. Its adjustment excludes profit and is now subject to the CBCA's emerging sole-cause gloss.
- 7Lusk Mechanical Contractors, Inc. v GSACBCA 7759 (30 April 2024)
A Governor's COVID stay-at-home order was an equal cause of the suspension alongside the CO's order. The government was not the sole proximate cause, so the suspension claim failed.
- 8Quality Trust, Inc. v Department of the InteriorCBCA 7451 (4 April 2025)
Suspension and Eichleay recovery denied on the same sole-cause reasoning as Lusk, compounded by the contractor's own prior agreement to the suspensions.
- 9FAR 52.243-4: ChangesFAR 52.243-4
The Changes clause vehicle for a delay claim. Its equitable-adjustment mechanism includes profit, unlike Suspension of Work.
General information, not legal advice. Reviewed Oct 6, 2026. Spotted an error? info@storiatechnologies.com
The notice brief
One email a month on claims, notices and the cases that decided them.
This month: three notice clocks and their judgments.
- 01Notice and time bars in OntarioIn Ontario a contractual notice of delay is a condition precedent: miss it and the claim is…
- 02Notice and time bars in AustraliaAustralian EOT time bars are enforceable conditions precedent everywhere, subject to the…
- 03Delay notice templates for AS 4000, FIDIC 2017 and CCDC 2A delay notice puts one fact on the record in time: that something has delayed, or will delay,…
Each issue links to the full articles in the Storia Library.