Concurrent Delay is otherwise known as the “misery loves company” concept. Ask any forensic scheduling Experts across the globe what they consider to be the most inflammatory aspect of delay analysis; they will probably say, “Concurrent delay”
The Society of Construction Law (SCL) stated in its recently updated Delay and Disruption Protocol:[1]
Concurrency is a contentious issue, both because there are differing views on the correct approach to dealing with concurrent delay when analyzing entitlement to EOT [Extension of Time] and because there are differences about the meaning of concurrent delay itself [10.1, p. 29]..As it is in relation to EOT, concurrency is one of the most contentious issues in the determination of recoverable prolongation compensation. [14.1, p. 39]
Why concurrencies create such strife in the project parties? It boils down to money. If concurrent delay is proven, a contractor will not be entitled to recover extended overhead costs during the period in which the concurrency exists. But let’s back up a bit and define concurrent delay.
DEFINITION:
The SCL protocol simplifies the definition:
True concurrent delay is the occurrence of two or more delay events at the same time, one an Employer Risk Event, the other
a Contractor Risk Event, and the effects of which are felt at the same time. For concurrent delay to exist, each of the Employer Risk Event and the Contractor Risk Event must be an effective cause of Delay to Completion (i.e. the delays must both affect the critical path).
RELEVANCE OF THE CONCURRENT DELAY CONCEPT:
Where Employer Delay to Completion and Contractor Delay to Completion are concurrent and, as a result of that delay the Contractor incurs additional costs, then the Contractor should only recover compensation if it is able to separate the
additional costs caused by the Employer Delay from those caused by the Contractor Delay. If it would have incurred the
additional costs in any event as a result of Contractor Delay, the Contractor will not be entitled to recover those additional costs.
KEY DELAY EVENTS MUST BE AS BELOW TO BE CONSIDERED “CONCURRENT”:
Unrelated and independent.
Contractual responsibility of different parties.
Involuntary (i.e. no delay event could be a reaction to the other event and therefore contractor is pacing).
Substantial and not easily curable.
Occur during the same schedule analysis time period
Independently delay the critical path(s) or cause a near critical path to become critical (i.e. float erosion).
WHAT IS THE PROBLEM WITH “PROVING” CONCURRENCY?
Here are some issues that usually encountered to defend or dispute a concurrency argument:
Lack of Consistent Schedule Updates.
Schedules Do Not Have Integrity
Lack of Adequate Documentation for Causation
Lack of Experience of the Project Team
Inadequate Schedule Analysis Methodology
CONCLUSION:
Concurrent delay will continue to be a contentious topic because it is intrinsically tied to money. Is the owner entitled to
assess liquidated damages, or is the contractor entitled to recover extended overhead costs? The answer depends on
concurrency.
About Author
Shishir Kant
Shishir Kant is a Director with Masin Projects and has over 17 years of experience in engineering and construction management, contract management, arbitration and litigation support, and expert testimony.