Amey Birmingham Highways Ltd v Birmingham City Council

Factual and Procedural Background

This appeal concerns the interpretation of a Private Finance Initiative ("PFI") contract between Birmingham City Council ("BCC" or "the Authority") and Amey Birmingham Highways Limited ("ABHL" or "the Service Provider"). The contract, dated 6 May 2010, required ABHL to rehabilitate, maintain, manage, and operate Birmingham's road network for 25 years. The contract is extensive, comprising over 5,000 pages, including schedules and annexures.

Central to the dispute are two issues: whether ABHL was obliged to update inventory data in a database known as the Project Network Model ("PNM"), specifically the MSEC and MINV tables, and whether four milestone completion certificates (numbers 6 to 9) could be set aside for manifest error.

Initially, the parties used a database document "DRD0626" as the PNM, containing six tables, four of which ABHL updated regularly (MSURV, MECSURV, MCON, MSCRIM), while they ceased updating the inventory tables MSEC and MINV from 2014 onwards. BCC contended this was a breach of contract as the inventory data was partly based on default data rather than actual measurements.

The dispute was first referred to adjudication, where the adjudicator ruled in favor of BCC, declaring ABHL must update the entire PNM inventory and that milestone certificates 6 to 9 should be set aside or revised. ABHL challenged this in the Technology and Construction Court ("TCC"), where the judge reversed the adjudicator's decision on the first two issues and did not decide on the third.

BCC then appealed to the Court of Appeal, seeking to reinstate the adjudicator's decision on all issues. Permission to appeal was granted, and the appeal was heard over two and a half days.

Legal Issues Presented

1. Whether the PFI service provider (ABHL) was required to update inventory details in the Project Network Model (specifically the MSEC and MINV tables) beyond the four tables it acknowledged updating.
2. Whether ABHL's obligations to rehabilitate and maintain the road network extended only to the assets originally recorded in the DRD0626 database or to the actual road network as it existed on the ground.
3. Whether milestone completion certificates 6 to 9 could be set aside for "manifest error" given the dispute over the inventory data.

Arguments of the Parties

Appellant's Arguments (Birmingham City Council)

• Clause 19.2.1 of the contract imposes a general obligation on ABHL to keep all six tables of the PNM updated, including the inventory tables MSEC and MINV.
• The PNM is not a static document but requires regular updating to reflect the actual road network rather than default data.
• Failure to update the inventory data breaches the contract and undermines the accuracy of condition indices and milestone certifications.
• The contract’s clauses on surveys, inspections, and indemnities support the position that ABHL must maintain accurate and up-to-date inventory data.
• Milestone certificates 6 to 9 should be set aside for manifest error because they were issued based on inaccurate inventory data, contrary to the contract’s requirements.

Respondent's Arguments (Amey Birmingham Highways Limited)

• The obligation to update the PNM inventory data is limited to four tables (MSURV, MECSURV, MCON, MSCRIM); there is no duty to update MSEC and MINV.
• The contract’s detailed provisions for updating the Management Information System ("MIS") contrast with the absence of similar provisions for the PNM, indicating no general obligation to update the entire PNM.
• The last 16 words of clause 19.2.1 require only accuracy of information, not continuous updating of inventory data.
• The milestone certificates are final and binding in the absence of fraud or manifest error, which they deny.
• The contract’s end-of-term handback provisions do not impose a general duty to update the PNM throughout the contract term.

Table of Precedents Cited

Precedent	Rule or Principle Cited For	Application by the Court
Arnold v Britton [2015] UKSC 36; [2015] AC 1619	Principle that courts should not rescue parties from bad bargains; interpretation must respect the contract's language.	The court recognized the principle that the contract must be interpreted as written, even if it leads to a seemingly bizarre result.
IIG Capital LLC v Van Der Merwe [2008] EWCA Civ 542; [2008] 2 All ER (Comm) 1173	Definition and test of "manifest error" in certificates as being obvious or easily demonstrable without extensive investigation.	The court applied the test to determine whether milestone certificates could be set aside for manifest error.
North Shore Ventures Ltd v Anstead Holdings Inc [2011] EWCA Civ 230; [2012] Ch 31	Manifest error can invalidate a certificate if it is manifestly incorrect, even if conclusive demonstration requires court intervention.	The court found the milestone certificates to be manifestly erroneous on the facts, allowing them to be set aside.
IG Index v Colley [2013] EWHC 748 (QB)	Court may consider extrinsic evidence in determining whether a manifest error exists.	The court considered extrinsic evidence to assess the manifest error issue in the milestone certificates.

Court's Reasoning and Analysis

The court undertook a detailed textual and contextual analysis of the contract provisions, focusing primarily on clause 19.2.1 and related schedules. It rejected the respondent's argument that the obligation to update the PNM was limited to four tables, emphasizing that the contract, read as a whole, imposes a duty on ABHL to keep the entire PNM updated, including the inventory tables MSEC and MINV.

The court found seven strong contract-based indications supporting this duty, including clauses requiring ABHL to satisfy themselves about the extent of the project network, to conduct surveys in accordance with the Highways Maintenance Code, and to provide accurate inventory data to the Authority.

The court distinguished between regimented procedures for adding or removing roads and routine updating of inventory data, noting that the latter was a modest, ongoing obligation. It also noted that the contract's sole remedy list and payment mechanisms did not preclude the requirement to update inventory data but rather limited financial remedies to specific breaches.

Regarding the milestone certificates, the court held that clause 13.5.1 made such certificates final and binding except in cases of fraud or manifest error. Since no fraud was alleged, the question was whether manifest error existed. Applying the legal test from relevant authorities, the court concluded that the certificates 6 to 9 were based on erroneous data and thus constituted manifest error, justifying their setting aside.

The court acknowledged the complexity and length of the contract and cautioned parties against exploiting contractual infelicities to disrupt the long-term project. It emphasized the importance of a reasonable approach consistent with the contract's purpose.

Holding and Implications

The Court of Appeal, with Lord Justice Jackson delivering the judgment and Lords Justice Moylan and Tomlinson concurring, ruled as follows:

The appeal by Birmingham City Council is allowed.

The court declared that ABHL was under a contractual obligation to update the entire Project Network Model, including the inventory tables MSEC and MINV, with actual inventory data as it became available. Consequently, ABHL's obligations extend to rehabilitating and maintaining the actual road network existing on the ground, not just the hypothetical network recorded in the initial PNM.

The court further held that milestone certificates 6 to 9 issued by the Independent Certifier should be set aside for manifest error because they were based on inaccurate inventory data contrary to the contract.

No new precedent beyond the application of established principles on contract interpretation and manifest error was set. The decision directly affects the parties by reinstating the adjudicator's declarations and requiring recalculation of milestone certificates based on accurate inventory data.