+27 11 648 9500   +27 31 764 0811
 

Concurrent Delays under the Gcc 2010

28 February 2018

Clause 5.12.1 of the GCC 2010 entitles the Contractor to an extension of time “for circumstances of any kind whatsoever which may occur that will, in fact, delay Practical Completion of the Works” [emphasis added]. These circumstances are limited to what may be termed ‘Employer Risk Events’. The question is often asked, however, how such extensions of time is impacted by ‘Contractor Risk Events’ which occur concurrently.

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, the effects of which are felt at the same time. True concurrent delay is rare and the phrase “concurrent delay” is more commonly used to mean two or more delay events which arise at different times but have effects which are felt at the same time. [SCL Delay and Disruption Protocol (2nd edition) Guidance on Core Principles, paragraph 10.4]

The GCC 2010 Guide (first edition) (2010) recommends reliance upon the Delay and Disruption Protocol of the Society of Construction Law (SCL) when assessing extensions of time due to the Contractor in terms of Clause 5.12 of the GCC 2010.

Core Principle 10 of the SCL Delay and Disruption Protocol (2nd edition) makes it clear that “[w]here Contractor Delay to Completion occurs or has an effect concurrently with Employer Delay to Completion, the Contractor’s concurrent delay should not reduce any EOT due [emphasis added]. “The Protocol’s position on concurrent delay is influenced by the English law ‘prevention principle’, by virtue of which an Employer cannot take advantage of the non-fulfilment of a condition (for example, to complete he works by a certain date), the performance of which the Employer has hindered”.

This is the position reflected in, among others, the English cases of Wells v Army and Navy Co-operative Society (1903) Hudson’s BC (4th Edition, Volume 2) 346 at 354 – 355, Henry Boot Construction (UK) Ltd v Malmaison Hotel (Manchester) Ltd (1999) 70 Con LR 32 at 37 and De Beers v Atos Origin IT Services UK Ltd [2011] BLR 274.

Float, which is the difference between the time available for executing an activity and the planned duration to execute it, must be taken into account. [GCC 2010 Guide] Concurrent delay only arises where the Employer Risk Event is shown to have caused delay to Completion or, in other words, causes critical delay (i.e. it is on the longest path) to completion. [SCL Delay and Disruption Protocol (2nd edition) Guidance on Core Principles, paragraph 10.10]

This is good news for Contractors, as far as it applies to extensions of time.

Author: Michelle Kerr, Senior Associate