London Underground Ltd v Metronet Rail BCV Ltd & Anor

Commercial contracts are construed by giving their words their natural and ordinary meaning in the context of the agreement as a whole and its relevant background. Commercial purpose and business common sense are relevant, particularly where the literal construction produces an unreasonable or absurd result, but they do not justify rewriting clear language. A complex or unusual drafting structure is not itself unreasonable or absurd. Where a contractual scheme begins with a general limitation on remedies and then provides exceptions, the exceptions must be given their ordinary meaning. A court should not read down an express reference to defined categories merely because the resulting allocation of remedies appears unusual.

London Underground Limited sought declarations concerning its entitlement to issue Corrective Action Notices under the service contracts governing the London Underground infrastructure arrangements. Metronet Rail BCV Limited and Metronet Rail SSL Limited had failed to complete specified station upgrades within the contractual timescales. An adjudicator had decided that LUL was not entitled to issue a Corrective Action Notice.

The dispute concerned the interaction between clause 22 and paragraph 7 of Schedule 2.1. Paragraph 7.1 generally limited remedies for specified failures to payment adjustments, while paragraph 7.3 stated that LUL was not restricted from taking clause 22 and clause 23 remedies, subject to specified conditions. The central issue was whether paragraph 7.3 applied to all failures in paragraph 7.1(a) to (g), including failures under paragraph 7.1(g) concerning Specific Projects.

1. Construction principles. The natural and ordinary meaning of the contractual words had to be considered in the context of the Service Contract as a whole and against the background known to the parties. Commercial purpose and business common sense were relevant. An unreasonable or absurd result could indicate that the apparent meaning was not intended, but the court could not rewrite the contract merely because its drafting was tortuous or its allocation of remedies was unusual.
2. Meaning of paragraph 7.3. Paragraph 7.1 imposed a blanket limitation of remedies for failures in sub-paragraphs (a) to (g), subject to the words “Except as otherwise provided in this clause 7”. Paragraph 7.3 expressly referred to failures in all of paragraphs 7.1(a) to (g). The conditions following “provided that” imposed additional thresholds for failures under paragraphs (a), (d), (e) and (f), but did not remove failures under paragraphs (b), (c) or (g) from the opening words of paragraph 7.3.
3. The defendants’ construction would require the court either to read down the express reference to paragraphs (a) through (g), or to treat “provided that” as imposing a limitation not expressed by the provision. That would involve rewriting the contract. The resulting scheme was unusual, but it was not unreasonable or absurd. The parties could choose to impose thresholds for some categories of failure but not others.
4. Paragraph 7.4 supported this construction. It repeated the payment-adjustment limitation for Facilities Faults and Fault Rectification Faults, while allowing the clause 22 and clause 23 remedies to apply in the circumstances specified. Paragraphs 7.6 and 7.8 supplied further qualifications to the remedies restored by paragraph 7.3.
5. LUL was therefore entitled to issue a Corrective Action Notice under clause 22.1(b) and paragraphs 7.1(g) and 7.3 in respect of failures to meet the requirements relating to Specific Projects. The judgment records the final declaration as subject to further argument on its wording.

First-instance decision. The judgment states that the proceedings were a rehearing of an adjudicator’s decision, which had found that LUL was not entitled to issue a Corrective Action Notice.