The Royal Devon and Exeter NHS Foundation Trust v ATOS IT Services UK Limited  EWHC 2197 (TCC)
The Royal Devon and Exeter NHS Foundation Trust v ATOS IT Services UK Limited  EWCA Civ 2196
The English Technology and Construction Court (TCC) and Court of Appeal have considered the enforceability of an ambiguous two-tier aggregate cap provision. In the TCC, the judge also examined an unusual argument concerning the meaning of a clause purporting to exclude the recovery of lost profits, lost revenues and lost savings. While the rulings were given on preliminary issues only and the balance of the case remains to be decided, the TCC judgment provides a rare ruling on the court’s approach to damages in the context of a non-profit generating contract, and both judgments serve as a useful reminder of the need for careful drafting in constructing multi-level caps on liability.
The Trust engaged ATOS under an IT project contract, the main obligation under which was to implement an Electronic Medical Records (EMR) system. The Trust was unhappy with the system delivered, and terminated three years into the contract alleging a material breach by ATOS on the basis that it had failed to remedy various defects. It subsequently brought a claim for damages of c.£7.9m.
The issues in dispute between the parties included the meaning and effect of the limitation and exclusion provisions in the contract. Both judgments assume – for the purposes only of deciding these preliminary issues – that the Trust will be able in due course to establish its case on both liability and quantum at the final trial.
The Clauses and the Parties’ Arguments
Exclusion of Liability
The project contract’s exclusion clause followed a common formulation, as follows:
(a) Without prejudice to the generality of sub-clause 8.1.1 neither party shall be liable to the other for:
(i) loss of profits, or of business, or of revenue, or of goodwill, or of anticipated savings; and/or
(ii) indirect or consequential loss or damage; and/or
(iii) specific performance of the Contract unless expressly agreed by the parties to be applicable in schedule G."
The calculation of damages sought by the Trust was based on its costs incurred in connection with the project, and included sums paid to ATOS, the cost of purchase of hardware and software in connection with the project, procurement costs, and costs of internal IT and specialist contractors.
ATOS argued that – notwithstanding the Trust's description of its losses - the Trust’s claims (aside from its mitigation costs) should properly be characterised as loss of revenue, profits or other benefits which would have defrayed its project costs; and that the language “loss of profits, or of business, or of revenue, or of goodwill, or of anticipated savings” therefore prevented the Trust from recovering those sums.
ATOS' argument was a technical one, as follows:
- Damages for breach of contract are designed to put the innocent party into the position it would have been in, had the contract been properly performed. The innocent party frequently seeks damages by reference to the profit, revenues or anticipated savings that it would have made from the contract. This is often known as “expectation loss” or “loss of benefit”.
- However, the Trust used a well-established alternative approach of claiming damages based on its amount of wasted costs. This is often known as “reliance loss”.
- The legal theory underpinning the alternative approaches is that expectation loss and reliance loss are not in fact different measures of damages for breach of contract, rather that they are two ways of measuring the same loss. Under that theory, a claim for wasted costs is permissible in connection with a breach of contract claim because there is a (rebuttable) presumption that the innocent party must have expected to recover from the contract at least as much benefit as it invested into it (the "Presumption").
- ATOS argued that this Presumption means that the Trust's claim for wasted costs should properly be characterised as a claim for loss of profit, business or revenue.
"9.1 The aggregate liability of [ATOS] in accordance with sub-clause 8.1.2 paragraph (a) shall not exceed the sum of two million pounds.
9.2 The aggregate liability of [ATOS] in accordance with sub-clause 8.1.2 paragraph (b) shall not exceed:
9.2.1 for any claim arising in the first 12 months of the term of the Contract, the Total Contract Price as set out in section 1.1; or
9.2.2 for claims arising after the first 12 months of the Contract, the total Contract Charges paid in the 12 months prior to the date of that claim." (Bird & Bird emphasis)
The wording of the cap had been specifically negotiated by the parties. The Trust submitted that the wording of paragraph 9.2.2 was insufficiently clear and therefore unenforceable. It argued that it was not possible to identify to what the parties were referring as “that claim”, and that it was not clear whether two caps existed (under 9.2.1 and 9.2.2 respectively) for the lifetime of the contract, or one. Both the Trust and ATOS agreed however that the references to “claims” should be construed as references to “Defaults”, a term defined in the contract.
Part 1: The Exclusion Clause and Wasted Expenditure
The TCC judge, Mrs Justice O'Farrell, ruled that ATOS had not understood the Presumption correctly. ATOS had wrongly assumed that the Trust's contractual benefit must represent profits, revenues or savings; and noted that in most commercial cases, there would indeed be an expected financial benefit from the contract that would defray the costs incurred. However, the Presumption applied equally to the non-monetary contractual benefit that the Trust expected to receive from the project: in this case, the Presumption was that the EMR was worth (in non-financial terms) at least the money spent.
In other words, the Trust was expecting its expenditure would be repaid in non-financial advantages that it expected to receive from the functionality provided by the EMR system.
The Presumption could not, therefore, in this instance help ATOS to argue that the Trust's claim for wasted costs should properly be treated as a claim for loss of profits, revenue or savings. On that basis, the contractual exclusion of ATOS' liability for these types of losses did not affect the Trust's claim.
Neither party appealed Part 1 of the TCC decision.
Part 2: The Enforceability of the Cap
The judgments remind parties that when interpreting limitation of liability clauses, provided the words are clear, the court will give effect to the commercial allocation of risk in the contract; but the words used must be clear and unambiguous in order to limit liability. The court will also be reluctant to find that a contract provision is void for uncertainty, and will strive to give it meaning.
The TCC judgment
The TCC judge found that the limitation language in the cap could be read with sufficient clarity and declined to treat it as unenforceable. She held that the language of paragraph 9.2.2 could be made sense of by reading the references to “claims” in the singular. Both parties had already accepted prior to the hearing that “claim” should itself be taken as a reference to a Default (as defined in the contract).
As regards whether the parties intended there to be one or two caps, the TCC judge found that reading the provision as imposing two caps, or caps which were multiples of the contract price, would render it devoid of real purpose and was an uncommercial interpretation. The court is entitled, when faced with an interpretation that makes commercial sense and one which does not, to adopt the commercially reasonable reading. The cap was held to be a single aggregate cap, and the level of the cap was to be determined by the date of the first Default relied upon by the innocent party.
The Court of Appeal judgment
Both parties appealed Part 2 of the TCC decision. In its appeal, the Trust abandoned its argument that the cap should be treated as unenforceable, but argued that - contrary to the TCC judgment - paragraph 9 comprised two separate caps. ATOS meanwhile argued that the words "the date of that claim" (which appear at the end of paragraph 9) were ambiguous, and should be construed as "the date when that claim was notified [to ATOS]".
The Court of Appeal agreed with the Trust that paragraph 9 should be construed as comprising two caps. Therefore if defaults occurred in both the first year of the contract and subsequently, the liability cap for those defaults which occur in the first year is as set out in 9.2.1; and the liability cap for subsequent defaults is as set out in 9.2.2.
The reasons for the Court of Appeal's disagreement with the TCC judge were that:
- The Court of Appeal considered that the reference to "aggregate liability" – which the TCC judge found influential - did not point to a single cap; rather, it could equally well refer to the aggregate of the sums calculated under each of paragraph 9.2.1 and 9.2.2.
- The word "or" between paragraph 9.2.1 and 9.2.2 pointed to discrete periods of time, rather than to mutually exclusive approaches to calculating the cap.
- There was nothing surprising in the parties agreeing a high value cap for defaults in connection with high value work in the first year, then a lower cap for lower value work in subsequent years.
- The TCC judge's interpretation ran the risk that if a major default occurred during year 1, the cap would be "used up"; meaning that ATOS would have a free ride (from a liability perspective) for the remaining contract term.
- Although the TCC judge determined that the date of the first default was the critical factor in deciding which of 9.2.1 and 9.2.2 to apply, there was nothing in paragraph 9.2 to support that approach.
ATOS' cross-appeal, meanwhile, failed. The Court of Appeal found that – as the parties had already agreed - the words "claim[s] arising" should be treated as references to defaults occurring. As such, the words "the date of that claim" were an unambiguous reference to the date on which the default occurred.
What this means for you
The TCC judgment does not affect the law on whether damages on the “reliance” basis are available to a claimant. It certainly does not decide that when parties agree to exclude the recovery of lost profits, revenues or anticipated savings they also are agreeing to exclude recovery of wasted costs. However, the reasoning in the TCC judgment is carefully tied to the not-for-profit nature of the contract in question. It leaves open the question of whether ATOS' argument could succeed in relation to a profit/revenue generating contract.
The TCC judgment is also a useful reminder that the courts will be slow to treat a limitation of liability or exclusion clause as unenforceable for uncertainty. As shown by both judgments, a court will go to some pains to interpret a potentially ambiguous clause and give it a commercially sensible meaning.
However, each contract will be interpreted on its own language and in its own context. In the Court of Appeal Robert Jackson LJ noted that "[both parties] suggested hypothetical scenarios in which their opponent’s construction would lead to odd results. I accept that. Paragraph 9.2 of schedule G is a homemade clause which, however it is interpreted, will yield some odd results." As the parties had accepted that the clause was valid and enforceable, the court had adopted "the natural meaning, and the meaning which yields the least bizarre consequences". It remains important to assess at the time of drafting whether the clause is clear enough to be operated in practice without this type of dispute arising.
To read more articles related to this topic or to view other know-how material relevant to dispute resolution please visit our dedicated know-how portal Disputes+.