Issue 2: Whether the Predicted Volumes for Basics in Service Year 4 were 1,000,000 (TCS’s case) or 320,374 (DBS’s case)
Issue 2: Whether the Predicted Volumes for Basics in Service Year 4 were 1,000,000 (TCS’s case) or 320,374 (DBS’s case)
The contractually agreed Predicted Volumes figure for Basics in Service Year 4 was originally 1,000,000, but DBS’s case is that figure was subject to later contractual amendment whereby it was revised to 320,374. In response to an RFI raised by TCS as to how and when such amendment was alleged to have been made, DBS responded as follows:
[DBS] is continuing to investigate the precise circumstances in which the amendment was made. This issue will be addressed in [DBS’s] witness evidence and/or by way of further particulars in due course.
TCS contends that the issue was not the subject of any further particulars and was not addressed at all in DBS’s witness evidence. It says that it is for DBS to establish that the contractually agreed Predicted Volumes were amended as alleged and that, in the absence of evidence on the point, it cannot do so.
DBS contends the change to the predicted transaction volume for Basic Disclosure in SY4 (1 April 2017 – 31 March 2017) can be seen from : ‘Sheet H.2 Cell [D9] in VW1- H {C3/9/1}, Cell E21 of the Method Tab {F/3286/1}; {B2/7/14}’.
I cannot from these documents find the agreement DBS alleges. The first document referred to is a non-contemporaneous document created by DBS’ expert. The second document [F/3286] is a spreadsheet created in 2018. It is correct that at Cell E21 in the two tabs marked ‘TCS Method’ and ‘DBS Method’ there can be seen the number 320,374. There is a comment for each cell which states: ‘Reset as per Clause 2.8.6’. This could suggest that at this time the parties were aligned. Interestingly, this number appears to have been ‘hard’ inserted into the spreadsheet rather than the result of cross-reference to other parts of the spreadsheet (like other predicted documents). The spreadsheet appears to be a TCS document. It was provided to Ms Graves of DBS. Ms Graves was called to give evidence by DBS, but gave no evidence about any such agreement even though her evidence did touch on matters relating to the methodology of varying the transaction charges. The third document referred to by DBS [B2/7/14] is an exhibit to the second witness statement of Ms Graves. Page 14 of this document is referenced at paragraph 7 of her evidence which states that ‘The enclosure to that email (at pages 9-14) explains DBS's interpretation in more detail, and also includes details of the amounts which DBS considered would be due to TCS, including in respect of the Update Service for Service Year 5.’ It does not provide any evidence relating to an agreement (or absence of agreement) related to predicted volumes. In fact page 14 contains an extract from what appears to be a document stating that it is without prejudice and subject to contract.
Mr Croall had no instructions on why Ms Graves gave no relevant evidence. There is therefore no factual evidence at all called by DBS explaining the meaning of the document, or the fact of any agreement it is said to represent. Equally importantly, the individuals named in the document as the author (Subramanian Sankaranarayanan) and the person who last modified the document in 2019 (Kamala C L) both gave witness statements for TCS and were available for questioning on this matter: neither was questioned and the substance of DBS’ case – that this document evidences an underlying agreement – was not put to them.
Whilst it might be that the documents referenced in submissions by DBS were capable of substantiating its case about an amendment, they are not so clear on their face that the fact of such an agreement is inescapable (or even prima facie). Factual evidence from a relevant witness is needed to explain the content of the two contemporaneous documents relied upon; alternatively, DBS could have put its case as to the import of the documents to the relevant TCS witnesses and it did not do so. In these circumstances I do not find, on balance of convenience, that the agreement alleged has been established.
- Heading
- CONTENTS
- IntroductiON
- The Factual Witnesses
- Expert Evidence
- Programming Experts
- Forensic Accounts
- The Parties Submissions
- Principles Applicable to Issues of Construction
- The Defendant’s Obligations and Responsibilities
- Clause 15
- Clause 9.5 which states
- Clause 14.5 of Schedule 2-6 which states
- The Delay and Notice Provisions
- Clause 7
- Conditions Precedent: Clauses 5 and 6
- Conditions Precedent: the authorities
- Clause 5.6
- Clause 6
- Clause 8
- Limitations of Liability
- A single or multiple caps?
- The Delay Damages cap under Clause 52.2.5
- Is TCS’s claim for loss of anticipated costs savings excluded by Clause 52?
- Compliance with Clause 5.3, Agreement and Estoppel Introduction
- Express Agreement
- Estoppel
- Introduction
- R1 B&B Delays
- Mr Britton’s First Analysis
- Mr Britton’s Second Analysis
- Conclusion on Mr Britton’s Analyses
- TCS’s submission based upon Mr Jardine’s analysis
- Responsibilities for Delay on the ‘Infrastructure’ Critical Path
- R1-D
- Compliance with Notice Provisions
- Analysis of Delays
- Up to August 2017
- From August 2017 to 19 September 2018
- Analysis
- Failed to confirm its desired functional scope of R1 Disclosure in relation to the Customer-to-Business portal and Accountable Officer’s Update Service functionality. Such confirmation was a prerequis
- Failed to make available an end-to-end test environment for the Interactive Voice Response system
- Failed to agree upon a data migration approach, without which the Claimant could not complete the build of a data migration environment so that anonymised data could be made available for testing
- Failed to ensure that relevant external stakeholders were available to participate in Final Systems Integration Testing
- Partial Termination
- TCS’s Claims
- Non-Manpower Costs
- Anticipated Cost Savings
- Summary of TCS’s Delay Claim Recovery
- DBS’s Claims
- Delay Payments
- R1-B&B Delay
- Disclosure Scotland Extension Costs – Item 1 of the Updated Schedule of Loss
- Loss of Anticipated Savings – Item 3 of the Updated Schedule of Loss
- R1-D Delay
- R0 Licence Costs – Item 4 of the Updated Schedule of Loss
- R0 Hosting and Infrastructure Costs - Item 5 of the Updated Schedule of Loss
- R0 Technology Refresh – Item 6 of the Updated Schedule of Loss
- R0 N-1 Sustainment Costs – Item 7 of the Updated Schedule of Loss
- R0 Maintenance Costs – Item 8 of the Updated Schedule of Loss
- Savings
- Introduction
- Quality-related Obligations
- Good Industry Practice and Defects
- Digital by Default Standards
- Section 71
- The Basics Portal
- Section 73
- The Barring Portal
- Section 75
- Section 76
- Barring Portal: Loss of productivity - Item 11 of the Updated Schedule of Loss
- LPF Portal
- Siebel Useability Issues
- Redaction
- Document naming, bundle creation and performance
- Adobe Licence (Item 20)
- Document Storage (Item 21)
- Other B1 Barring Quality Issues
- Scan on Demand
- Special Characters
- Letters
- Item 24 : Loss of Efficiency Claims arising out of R1 Barring Quality/Useability Issues
- N-1 Sustainment Costs
- Causation and Loss
- Exit/Service Transfer
- Identification of all services (3.2.2)
- Knowledge Transfer (3.2.6 and 3.2.7)
- Section 95
- Providing all documentation to a replacement contractor (3.2.1 and 3.2.10)
- The identification of all leases, maintenance agreement and support agreements in connection with the provision of the services (3.2.3)
- Providing any other information or assistance reasonably required by a replacement contractor (3.2.14)
- Causation and Loss
- The Security Incidents
- The Charges Variation Dispute Introduction
- Issue 1: How the amount of an ‘over-recovery of the Forecast Revenue’ (Clause 2.8.4) or ‘under-recovery of the Forecast Revenue’ (Clause 2.8.5) is to be measured
- Section 104
- Issue 4: How Clause 2.8.5 of Schedule 2-3 applied to Volume Based Service Charges in Service Year 5
- Issue 2: Whether the Predicted Volumes for Basics in Service Year 4 were 1,000,000 (TCS’s case) or 320,374 (DBS’s case)
- Conclusion on Volume Based Service Charge
- Conclusions
![HT-2020-000448 - [2024] EWHC 1185 (TCC)](https://backend.juristeca.com/files/emisores/logo_yJUntHA.png)