Loss of Anticipated Savings – Item 3 of the Updated Schedule of Loss
Loss of Anticipated Savings – Item 3 of the Updated Schedule of Loss
DBS claims that it had to retain a number of temporary staff members to perform Barring work between October 2016 and September 2017 due to the delayed delivery of R1 Barring. This is Schedule of Loss item 3. There are also loss of anticipated savings claims relating to R1 Barring Portal Quality Issues (Schedule of Loss item 11) and to R1 Barring Standards/Quality Costs (item 24).
The claimed sum is £1,971,434. Mr Hain’s assessment is £2,424,934.
As explained by Mr Hain in his First Report, DBS’s claims for loss of anticipated savings in respect of R1 Barring rely on two documents: the Workforce Planning Model (or ‘WFPM’) v15.6 and an analysis of staff costs incurred (‘Barring Payroll Analysis’). DBS contends that these two documents provide the Court with (1) DBS’s best estimate of the efficiency savings expected had a compliant Barring Portal and Solution been delivered (the WFPM) and (2) the difference between workload prior to and after delivery of the Barring Portal and Solution.
Mr Hain also explained that DBS had estimated the lost efficiency by carrying out the following assessment:
presented the anticipated removed and decreased FTE savings from the WFPM v15.6;
calculated the total FTEs employed in each year by grade (for 2016/17 this represents the FTEs for the period from October 2016 to March 2017 only);
calculated the proportion of the FTEs employed in each year, by grade, which were expected to be removed (“FTE % Removed”) or decreased (“FTE % Decreased”), e.g. the anticipated removal of 37.9 FTEs at the AO grade represents an anticipated FTE % Removed of 40% when compared to the 96.0 FTEs actually employed in 2017/18;
calculated the total cost incurred in each year by grade (for 2016/17 this represents the costs from October 2016 to March 2017 only);
applied the FTE % Removed to the total costs incurred in each year by grade to calculate the “Removed Cost”; and
applied the FTE % Decreased to the total costs incurred in each year by grade to calculate the “Decreased Cost”.
As such, the FTE %Removed and FTE %Decreased calculated by reference to the WFPM is a fundamental part of the assessment.
In relation to the delay period, the loss is explained as having been calculated as the anticipated savings for the six month period from October 2016 to March 2017, plus 50% of the anticipated savings for April 2017 to March 2018, approximating to the period from April 2017 to September 2017.
In his witness evidence, Mr Gergely, who was a central witness in relation to the WFPM, said as follows (para 34):
‘In around May 2016, some work was started by Dawn Wayman, Head of Service for R1 Transformation in Barring, to try to forecast savings that would be achieved from delivery of R1 in Barring. To do this, the WFPM was looked at with a view to stripping out the functions that would be replaced by the R1 Solution (or transferred to TCS’ back-office processing) and to calculate the anticipated savings. I knew this wouldn’t give us an exact answer as to savings, because the WFPM was not a perfect reflection of existing workloads and the lack of visibility of the R1 solution meant that we did not yet fully understand the additional work that would be created by the changes to our processes. However, I accepted, based upon what I was told by Dawn Wayman, that such an approach would provide us with a usable estimate.’
Whilst accepting it was not ‘a perfect reflection’, Mr Gergely considered that it was nevertheless usable, in his view, for the purposes of the loss of anticipated savings assessment.
No doubt at least in part on the basis of this evidence, there was, as DBS points out in its Written Closing Submissions a measure of agreement prior to Mr Gergely giving evidence at trial as to the expected efficiency savings on the basis of the WFPM. As recorded at Section 6.3.1 of the Joint Statement, Mrs Wall recorded that,
‘Both Mrs Wall and Mr Hain use the WFPM as a sufficiently reliable source for the basis of 64.7 FTE [Full Time Equivalents] on which to estimate the number of staff roles expected to be removed and reduced as a result of R1 going live….’
Mr Gergely was however crossed-examined at some length on the chronological development of the WFPM. The starting point is that in around August 2015 (i.e. before any UAT), DBS performed an initial assessment of the changes which would occur in ways of working within DBS following R1. This was known as the ‘Detailed Level Organisation Design’ (or ‘DLOD’). In around early January 2017, DBS used the WPFM to update the DLOD following R1 Barring Go-Live. A column was added to identify whether a task was expected to be removed, be retained, decrease in effort or increase.
As TCS submits, and I find as a fact, it was known at the time that this was an inadequate exercise. The WPFM included important caveats, all of which were agreed by Mr Gergely:
The changes ‘marked against activities’ were ‘based on limited information’;
‘all changes marked against activities in the 'R1 view' WFPM file (or: DLOD tab) refer to the expected situation ~6m after go-live.’
‘activities marked as ‘removed’ need to be confirmed with the business via validation of relevant R1 processes/ procedures’.
‘activities marked as ‘decrease’ … are known to have a similar activity in R1 with an expected decrease in effort which needs to be confirmed with the business owners and cannot be quantified at this point’.
‘where activities are marked as red the current view is they may require more effort than today however this cannot be confirmed at this point.’
In April 2017, someone called Marta Bergonzini from DBS produced a presentation which stated:

It repeated on slide 5 a number of the caveats and on slide 7 set out planned improvements to the ‘rough view’:

Slide 8 indicated that there had been little validation of duration of activities and ‘the level of confidence is low’. It is particularly relevant that DBS were themselves indicating that using actual data collected from the first few months of operations would improve future headcount estimates. Mr Gergely agreed in cross-examination that it was clear, at this point in time, that a new version of the WFPM needed to be created.
DBS’s Operational Organisation Design Document v0.2 dated 14 June 2017 indicated that it had not been possible to assess the full end to end functionality of R1 for the purposes of workforce modelling, and that DBS anticipated that as it moved into the next phase of R1 delivery (training for staff), it would be possible to better assess the impact on workforce and the ability to realise the theoretical business benefit. It was recorded at this time that this would form the basis of the next review of this document for Operations (Barring).
The DLOD dated 13 July 2017, indicated that, ‘a number of additional processes (or temporary workarounds) will need to be added post R1, until all operational areas have gone live. The exact impact of the decreases (in terms of potential FTE reduction) require further investigation by Business Analysts with the required level of R1 knowledge to determine any time savings. As yet it has not been possible to make any accurate assessments within the testing environment.’
There remained, therefore, a significant amount of uncertainty about the estimates, as explained during cross-examination by Mr Gergely (Day 13/49):
Now, that must tell us, mustn't it: well, you can't
necessarily take the 52 FTEs as being pretty much
the likely position, because in fact what that 52 does
not take into account is what we see at 5.1.7, in other
words, the additional workaround -- the additional
processes or temporary workarounds. Do you see that?
A. I think in terms of what I've said about the 52
previously was that was what we expected to realise by a
task removal in a steady state position. 5.1.7 is
reflecting on the fact that, well, we won't get to that
point until all operational areas have gone live, and at
that point in time also we didn't know whether or not
there was other things that we would need to add. There
was the unknowns in terms of how R1 operated that might
potentially ask us or require us to do additional tasks.
That's what the caveat is being reflected there. That's
my understanding.
In October 2017, an internal DBS presentation indicated the work that it was then anticipated was required in order to revise and correct the DLOD assumptions, as reflected in the following slide:

Mr Gergely accepted that these tasks would need to be carried out in order to work out what the anticipated savings might be (Day 13/64):
So, one thing that we can see from this is that, if
we wanted to work out, or the business, so DBS'
commercial side wanted to work out what the anticipated
savings might be, it would need for these tasks to have
been carried out and reported on in order to do that,
wouldn't it?
A. Yes.
In relation to a review Mr Gergely undertook in October 2017, he also gave the following evidence about the (un)reliability of the document as then perceived contemporaneously (Day 13/55):
Q. So, it's quite clear, isn't it, that you had real
concerns at this time in anybody placing reliance on
version 15.6?
A. Yeah, I think it wasn't just at this time, I think,
prior to Go-Live, I think there was concerns that had
been expressed, as we reflected on before the break. We
were saying that a lot of it was estimate and
assumption, and until we got exposure to the solution,
we wouldn't be able to accurately estimate what our
resource requirement was.
Mr Gergely undertook a review of the WFPM following Go-Live. He was cross-examined in relation to a document produced after Go-Live in which an number of the assumptions in the 19/01/17 WFPM had not been borne out. One of these related to the Disclosure Information Team (or ‘DIT’) in respect of which the document showed an anticipated removal which had yet to occur or, indeed, in respect of which activity effort had increased.
This line of cross-examination led to the following exchange in which Mr Gergely explained that, with the benefit of hindsight, the document did not produce a figure which DBS could rely upon (Day 13/60):
Q. So on any basis, as we know, this is telling us that it
would be wholly inappropriate to use version 15.6 as
a basis of trying to calculate what your anticipated
cost savings would be because of the very things that we
see here that tell us how unreliable 15.6 actually was;
would that be fair?
A. No, I wouldn't agree with that.
Q. Why not?
A. Because we had to make an estimate based on what we
knew. We knew that the requirements that had been
supplied meant that certain tasks should be removed via
automation, via BP -- back office processing being
outsourced. So based on that, what we knew was going to
be removed, that was our estimate. All along in those
documents that were produced prior to Go-Live, we put
those caveats on it to say, "We do not know, because
we've got a lack of visibility of the solution, what new
things R1 might require from us."
MR JUSTICE CONSTABLE: Sorry, I'm not quite -- I understand
your evidence that is you had to do something and things
were uncertain, but in terms of the baseline, do you
think 15.6 is reliable or it needs to be adjusted in
some way given a greater level of knowledge that you
might have now, or something else? What's your ...?
A. If we knew what R1 was going to require of us at
the point in time that we generated those originally
estimates, we would have been able to have a clearer
understanding of what we needed to do in terms of using
15.6 was the previous state. If we'd had that
greater knowledge, we would have been able to modify it
to go beyond just the removed tasks. As part of that
exercise, we did highlight the ones which we thought
would be impacted, but from a potential future --
additional saving as opposed to an additional cost or
effort, and we couldn't -- we couldn't assess those
additional costs or efforts at that point in time.
MR JUSTICE CONSTABLE: Yes, but I think the question that's
being asked of you is: we are where we are now.
A. Yes.
MR JUSTICE CONSTABLE: And knowing what you know now, do you
think it's a reliable document to use? And that doesn't
necessarily imply any criticism of it at the time at
which it was produced, it's just with the benefit of
hindsight.
A. Yes, with the benefit of hindsight, and I think
potentially that's what I was pointing out in
October 2017.’
MR JUSTICE CONSTABLE: When you say, "Yes, with the benefit
of hindsight", what are you saying "yes" to?
A. I'm saying: yes, it wasn't a -- it didn't produce
a figure that we could rely upon.
This fair evidence merely reflects, in my judgment, the view expressed by Mr Gergely’s email of 15 November 2017, following his contemporaneous review, when he wrote:
‘Following that work I have written separately to Jenny on the R1 impact (current and future). I think it is wrong to focus on the removed tasks and a more holistic approach is required. Persisting in discussion with PCS around FTE reductions based on removed tasks, when their members are experiencing greatly extended timescales and increased effort in key processes is possibly not the best approach. Experience now shows that the previous analysis that informed the DLOD was very much guess work with no timings produced for existing or new processes in R1.
There is therefore an urgent need for the completion of a WFPM for Barring for R1 based on timings / effort in R1 to produce an accurate picture re: any savings / required staffing.
Jenny will obviously have a view on how to approach the meeting on the 20th however I have no longer have any confidence in the DLOD figures and would not want to persist in offering them as an accurate assessment of R1 impact.’
Equally important was Mr Gergely’s evidence confirmed that it was after DBS had a live system that they could properly assess the work required to produce Barring Case work (Day 13/65):
…this is you
saying, "Well, look, hang on a minute, the approach that
was taken before in relation to DLOD is not really
the approach that we ought to be taking for the reasons
that you identify in this document." That's what you
were conveying, wasn't it, to Mr Cookson?
A. Yes, we -- we have a -- at this point, we've got a live
system, we can accurately -- or more accurately assess
the effort required to -- to produce Barring case work.
Q. And that's why you say, isn't it, in the next paragraph:
"There is therefore an urgent need for
the completion of a WFPM for Barring for R1 based on
timings/effort in R1 to produce an accurate picture
re: any savings/required staffing."
A. Yes.
I accept the submission of TCS that, on the basis of this factual evidence, Mr Gergely effectively disavowed the evidence in his witness statement that the WFPM was a ‘usable estimate’, at least in the context of the claim DBS is advancing. On any view, in my judgment, it is clear that, even as a working or rough estimate at the time, it suffered from considerable uncertainties and was shown, shortly after Go-Live, to have contained flaws, none of which have been addressed or corrected by DBS in its use of the document to underpin its claim. It is right that Mr Gergely had already accepted at paragraph 36 of his witness evidence that post Go-Live, he was concerned that the WFPM was not a suitable baseline to calculate the R1 impact because the processes were so different: however, this does not mean that the Court should conclude, as DBS contend, that the WFPM nevertheless is an appropriate basis upon which to calculate a delta which reliably represents a loss of anticipated savings. In my view, it plainly is not.
Whilst the foregoing conclusions apply to all the loss of anticipated savings claims, the particular context of Updated Schedule of Loss item 3 is the delay claim. In the context of a delay claim, the use of an estimate of savings is particularly problematic, even if it were reliable (which in this case, it was not). This is because, as Mr Gergely accepted, there would exist better evidence as to the actual time taken by tasks post-Go Live which can be compared with actual data about the amount of time taken in relation to the R0 system. The starting point for the quantification of the actual loss caused by the delayed introduction of savings can (and should) be calculated by reference to the actual savings that were, because of the delay, not (actually) generated as soon as they would have been. Taking a simple example, if post Go-Live the evidence demonstrated the efficiencies from the introduction of R1 actually generated an ability to reduce the workforce by 10 FTEs, then this is the lost actual saving caused by the delay for the relevant period of delay (no doubt taking into account the fact that the actual savings may not have been immediate). Even if the WFPM was not of itself unreliable as an estimate (as it plainly was), a claim for actual losses caused by a delay should be assessed by reference to actual, not estimated, losses when the evidence plainly exists to have permitted such an assessment.
Moreover, it is plain that even if (contrary to my conclusion) it would have generally been appropriate to advance an analysis based upon the (unreliable) WFPM in order to generate a percentage expectation of reduction which is then applied to actual costs, the evidence of what actually happened during the period of the claimed delay demonstrates that it is clearly the wrong approach on the facts.
Mr Gergely confirmed in his witness evidence (at paragraph 35) that DBS had already allowed staff numbers to drop by around 48 people in anticipation of making savings, as shown in the WFPM v15.6 as at 31 October 2016 (i.e. the commencement of the period of delay). Mr Gergely also confirmed in cross-examination that the figures of actuals within the WFPM were accurate. Although, as he continued to explain in his statement, DBS considered taking on short term agency staff in the lead up to Go-Live in order to make up for the reduced headcount, DBS decided to stick with the numbers they had, and to rely upon DBS’s fixed-term appointments and staff overtime in order to meet the workload. There is no evidence, therefore, that any people were hired due to the delays, in circumstances where DBS had already put into effect what it anticipated to be the staff savings. Mr Gergely’s factual evidence was that 12 people were then added after Go-Live rather than before.
There is no basis, given these facts, to attempt to assess delay prior to Go-Live by anticipated savings by reference to the theoretical percentages applied to actual costs derived from the WFPM. The evidence is that anticipated staff savings had already been made. One basis of claim could have been, on the basis of this factual evidence, based upon the overtime paid to the (reduced) workforce because efficiencies did not commence as soon as anticipated. That was, after all, the manner in which DBS actually sought to address the problem caused by delayed introduction of the new systems. But no such claim has been advanced and the Court has no proper basis upon which it could carry such an exercise out.
In the circumstances, because of, but also irrespective of, the unreliability of the WFPM in terms of its forecasts, I conclude that the claim for anticipated savings as a result of R1-B&B as advanced by DBS is fundamentally flawed and fails.
Updated Schedule of Loss Item 2
DBS’s claim for Loss of Basics Contribution has not been pursued.
- 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)