The Barring Portal
The Barring Portal
It is Dr Hunt’s view that the Barring Portal (which, subject to changes that have been made since Go-Live, is still available to access) provides a very poor experience for organisational and individual users. It is her view that the portal is not ‘clear, intuitive and optimised for efficient use’ nor ‘customised for each type of user’.
Dr Hunt presents the basis for these conclusions in her Appendix E. This identified 6 complaints, of which 6 were designated ‘High’ impact, 3 were ‘Medium’ impact and 5 were ‘low’ impact. Of the ‘low’ impact items, DBS indicated that it does not maintain its complaint in relation to two of them (items 9 and 12).
TCS’s denial of breach in its Closing Submissions related solely, and in reality with limited vigour, to its reliance upon the fact that DBS had been involved in a collaborative manner in relation to the development of the screens. Similarly, Mr Britton referred often in his cross-examination to the fact of UAT, and that the complaints made by DBS had not been picked up by DBS testers during that phase of testing.
I accept DBS’s case, supported by Dr Hunt, that in reality the sort of problems complained of by DBS would probably have been picked up in effective usaebility testing, which should have been conducted but which, as accepted by Mr Argawal of TCS, was not. Mr Britton also accepted that useability testing to enhance the design should have taken place during the design phase.
In the circumstances, I find that the matters of which Dr Hunt makes complaint are instances in which, by reason of a failure to have complied with GIP, the Barring Portal did not comply with the specification, in that it was not clear, intuitive and/or optimised for efficient use’ nor ‘customised for each type of user’.
DBS also relies upon the Barring Portal failure to have delivered a system which would support DBS’s strategic goal of having at least 50% of barring referrals being only by Year 2 and 90% by Year 5: as identified by Dr Hunt, take up was around 25% after 2 years (there is no comparator for Year 5). The difficulty of making a finding in this regard is that, for obvious reasons, take up of the website relates to a whole range of factors, of which the useability of the site is just one, including the extent to which the site was promoted by DBS. In this regard, DBS’s internal assessment in October 2020 identified that 100% of those referral organisations who continued to make referrals using the paper service would move to an online system to make barring referrals, and of that cohort, 49.1% said they ‘would unequivocally use the online service if they were aware that it existed’ (emphasis in the original). The remaining percentage said they would use the online service if the current offering had been improved, because they had tried but essentially given up. Thus, the reason for lack of usage was pretty evenly split between lack of profile (DBS responsibility) and quality of the site (TCS responsibility). In circumstances where the requirement upon TCS was to provide a product that ‘supported’ the target take up, and a product which was clearly putting people off would comply with the obligation relied upon given that the useability issues were at least a material contributory factor failure to meet the take up targets. TCS were therefore also in breach of this part of Schedule 3.
Perhaps for these reasons, TCS focussed principally on causation. The first point made is that the complaints made by Dr Hunt, and adopted as breaches by DBS, did not align wholly with the issues identified by DBS itself and which, logically, can have been the extent of the matters in mind when DBS decided to re-design the portal. The difference is in part, also, explained (as Dr Hunt accepted) by the fact that useability complaints will always have a degree of subjectivity to them (Day 20/174).
The DBS assessments of the Portal were dated April 2019 and October 2020. For the April assessment, 4 participants took part in Testing Sessions to determine if the portal itself contained reasons for the low usage, and 3 key issues were found that had a 4 or 5 severity rating, and further issues with lower severity were found.
The first key issue was the requirement to enter an authorisation code to allow end users/applicants to use any services linked to their certificates. This was Dr Hunt’s complaint at item 2. Complaints were being made about this by users as early as December 2017, as set out in DBS’s ‘R1 Basic Portal Complaints – TCS analysis’ presentation. DBS recorded:
- 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)