Capita Business Services Limited v IBM United Kingdom Limited

In construing a detailed commercial agreement, specific provisions addressing a particular situation take precedence over general service obligations. Contractual language and its immediate context may establish a fixed cessation date, even where that date was selected on the assumption that a replacement service would then be operational. Evidence of pre-contract negotiations is generally inadmissible and unhelpful, save for limited matters such as objectively ascertainable commercial purpose. Appeals to business common sense must be assessed at the date of contracting and must reflect consequences objectively apparent to both parties. Where a contract provides for a change-control mechanism, that mechanism may offer protection against the consequences of a service ending, but does not alter the agreed construction.

Capita sought declarations concerning the meaning of Condition 2 to Table B in Annex 2 to Schedule 2 of its amended agreement with IBM. IBM had subcontracted substantial elements of the relevant services to Kyndryl.

Condition 2 stated that the contractor’s obligations for managed services relating to the existing Relevant Service would cease at 30 August 2023, while work concerning a replacement service would be handled through change control at Capita’s expense. The replacement service had not become operational by that date.

The central issue was whether IBM’s support obligations ceased on 30 August 2023 or continued until a replacement service became operational, subject to the contractual long-stop date.

1. Capita’s application for the declarations sought was refused. IBM’s contingent application for equivalent declarations against Kyndryl did not arise.

2. The language of Condition 2 was significantly more consistent with IBM’s construction. The words “as such” linked cessation to the contractual assumption and date stated in the preceding sentence. The use of “assumption”, without provision for revisiting it, supported the conclusion that 30 August 2023 had contractual effect.

3. The immediate contractual context was decisive. Conditions 1, 2 and 3 were introduced together to address anticipated changes to existing systems. Conditions 1 and 3 provided for continued support and price adjustment where anticipated changes were delayed or did not occur. Condition 2 instead expressly provided a cessation date and contained no equivalent mechanism requiring IBM to continue supporting the existing Relevant Service after that date.

4. General obligations in the main agreement and Schedule 2 yielded to the specific treatment of the Relevant Service in Table B and Condition 2. The existence of exit and smooth-transfer provisions did not require a different construction, since those provisions contemplated partial cessation and both parties accepted that they applied.

5. Evidence of the parties’ negotiating objectives was not admissible or helpful in construing the final agreement. The court applied the approach in Prenn v Simmonds, subject to the limited relevance of an objectively ascertained commercial purpose. Pricing evidence was too opaque to assist.

6. Arguments based on business common sense did not displace the contractual language. The relevant assessment was made at the date of contracting, concerned consequences objectively apparent to both parties, and had to meet the limits identified in Arnold v Britton. Capita retained the ability to invoke change control, although that would involve a variation and potential additional charges.

First instance decision. The judgment does not state any prior appellate decision.