2024-2025 Global AI Trends Guide
The "Relevant" clause
In North Midland Building Ltd v Cyden Homes Ltd [2018] EWCA Civ 1744, Cyden employed North Midland as contractor to design and build a luxury house under an amended JCT Design and Build Contract 2005.
Clause 2.25.1.3(b) stated:
"any delay caused by a Relevant Event which is concurrent with another delay for which the Contractor is responsible shall not be taken into account".
Relevant Events (those pushing actual completion beyond the contractual completion date and entitling the contractor to an extension of time) included wide-ranging employer acts of prevention and default.
The works were delayed and the contractor applied for an extension of time. A partial extension was allowed. However, relying on clause 2.25.1.3(b), the employer stated that:
"the delays resulting from Delay Events 1 and 9 have been consumed by culpable delays attributable to North Midland Building, thus reducing the entitlement to an award of an extension of time".
In other words, a portion of the extension of time claimed by the contractor was refused as two of the employer-caused delaying events were concurrent with delays for which the contractor was responsible.
The contractor sought the interpretation of clause 2.25.1.3(b) and a declaration as to whether the clause offended the prevention principle (which maintains that where an employer prevents a contractor from meeting the original completion date and the contract gives no extension of time for that delay, the employer cannot insist the contractor meets the original completion date).
The "irrelevant" principle
The first instance judge found no point of interpretation arose. Clause 2.25.1.3(b) clearly allocated concurrent delay risk to the contractor. The contractor's submission on the prevention principle was "off the point" as the principle would not override the wording.
The second ground was that even if clause 2.25.1.3(b) was enforceable, there was an implied term precluding the employer from levying liquidated damages, as it would be odd if the employer could recover them for a period of delay for which it was responsible. The Court rejected this argument. It failed the tests for implying terms and was contrary to the express wording in clause 2.25.1.3(b).
The Court did not address the employer's submission that where there is concurrent delay, it cannot be said the employer has actually delayed the contractor (meaning the prevention principle would not be engaged). This was unnecessary for disposing of the appeal and unwise without full argument.
Should I now draft for concurrency?
This decision encourages parties to agree provisions which clearly and unambiguously allocate concurrent delay risk and gives contract drafters a model clause.
Even if the Cyden wording is not used, parties may feel it is now appropriate to state that concurrent delays will be apportioned reasonably between the parties, even though this creates uncertainty due to subjective views of what is fair and equitable. At the very least, since clear wording trumps the prevention principle, parties may consider making an extension of time more difficult to obtain, perhaps by expressly requiring the contractor to make reasonable efforts to mitigate delay.
The case also means an express condition precedent that a contractor submits notice of its claim in a specified time period or otherwise loses its entitlement to an extension would also be upheld even where concurrent delay occurred, despite eminent construction law commentators in various jurisdictions thinking otherwise.
However, such drafting options will not always work because:
As for contracts not governed by English law, construction lawyers in our global network say the Cyden approach would broadly: