A Minister Says the Quiet Part in Parliament
It is rare for a government minister to describe a live supplier relationship as unacceptable on the record, in the House of Commons, while that supplier is still under contract. That is exactly what Cabinet Office minister Sally Jameson did this month, telling MPs that Capita's performance administering the Civil Service Pension Scheme remains unacceptable and that far too many scheme members continue to face uncertainty while waiting for their cases to be resolved. The statement followed Capita's failure to meet an earlier commitment to restore the scheme to contractual service levels by the end of June, a deadline the company had itself agreed to and then missed.
In response, Capita set two new self-imposed targets: clear its backlog of workable stock cases by September 1, and begin processing cases within normal key performance indicators from September 30 onward. Jameson's statement to Parliament was her assessment of how that first milestone actually landed. The government's language, holding Capita firmly to account using all commercial levers available, is the kind of phrase procurement teams reach for when a relationship has moved from performance management into something closer to a formal remediation process with real financial and contractual consequences attached.
What Capita Actually Delivered by September 1
Capita reported meeting its September 1 target across five priority categories, bereavement, death in service, ill health retirement, retirement payments, and retirement quotes, but only for cases it classified as workable stock. Jameson's response to that claim was pointed: meeting a milestone on workable stock alone, she said, is not sufficient progress and does not constitute full service recovery. That distinction matters enormously in practice. A vendor can technically hit a self-defined target while a meaningful share of affected cases sit outside the category the target was measured against, and the headline compliance figure ends up telling you very little about the actual member experience.
This is the exact failure mode enterprise leaders should recognize from their own vendor scorecards. When a supplier is allowed to define the denominator for its own recovery metric, hitting the target and fixing the problem can be two entirely different outcomes. Capita's own spokesperson acknowledged as much, stating the company recognizes there is more to do to restore the service members should expect, while pointing to the next milestone at the end of September as the real test of whether performance has genuinely turned a corner rather than just cleared an easier subset of the backlog.
The Backlog Behind the Headline
The numbers behind the ministerial statement give a clearer picture than the milestone language does. At the end of June, roughly 4,000 retirement-quote cases remained in Capita's backlog, of which 1,500 were classified as complex. Capita committed to clearing that backlog within six weeks and reported issuing 3,087 quotes by the end of August, meaningful progress but still short of full clearance months after the original deadline had already passed. Civil service pensions director Richard Vianello has also been tracking cases open more than 100 days, split between workable and non-workable categories, a level of granular public reporting that is itself notable for a supplier relationship under this much scrutiny.
For enterprise technology and operations leaders, this level of case-aging transparency is worth studying regardless of sector. Most outsourced service relationships never surface backlog-aging data with this much specificity to anyone outside the contracting organization, let alone to a legislature. The fact that this data is public now is a direct consequence of the crisis having escalated past normal vendor management into ministerial accountability, and it is a reminder that the reporting rigor you should be demanding from a critical outsourced provider today is the same rigor that only tends to appear voluntarily once something has already gone seriously wrong.
A Portal Failure Layered on Top
Beyond the case backlog, members have separately struggled to sign into the online portal to access their 2025-26 annual benefit statements. Vianello attributed the problem to Capita choosing a shortened timeframe for the rollout, which produced a surge in website and member portal traffic that the system was not sized to absorb. Around 498,000 of this year's annual benefit statements have been loaded onto the portal so far, with a further 78,000 scheduled to load gradually through the rest of September and into October. Capita has escalated the portal performance issue internally as its highest-priority technical problem.
The detail worth sitting with here is that a capacity-planning failure compounded an already-strained case-processing backlog, at the same organization, in the same program, at the same time. That is a familiar pattern to anyone who has run a major system consolidation or migration under public scrutiny: operational recovery work and technical infrastructure problems tend to surface together rather than sequentially, because the same overstretched teams and the same underlying platform are usually responsible for both. Related reporting has also noted the government is still waiting on Capita's technology rectification plan, suggesting the root cause runs deeper than staffing capacity alone.
The In-House Pivot Is the Real Story
The most consequential line in Jameson's statement was not the criticism of Capita's current performance. It was confirmation that the government is actively shaping a long-term strategy to bring the pension scheme back in-house. That is a direct reversal of the original outsourcing decision, and it does not happen over a single missed deadline. It happens when a client concludes that ongoing vendor management, penalty clauses, and remediation plans cost more in accumulated risk and reputational exposure than rebuilding the capability internally would cost in time and investment.
Whitehall unions have already filed a formal petition calling for the scheme to be insourced, adding organized pressure to a decision the government now appears to be leaning toward independently. Insourcing a system this large is not a fast or cheap undertaking, and the government has been careful to frame it as a long-term strategy rather than an immediate switch. But the fact that it is on the table at all, stated on the record to Parliament, tells you how far this relationship has deteriorated relative to where a normal underperforming-vendor conversation typically ends.
What This Means for Anyone Who Outsources a Critical System
Every enterprise leader who has outsourced payroll, pension administration, benefits processing, or another critical people-facing system to a third party should read this case as a live rehearsal of a scenario their own contract almost certainly does not fully cover. Ask specifically who defines the denominator in your vendor's recovery metrics when performance slips, and whether your contract gives you the right to independent case-aging data rather than a vendor-reported compliance percentage. Capita's workable-stock distinction only became visible because a government minister was answerable to Parliament for it. Most enterprise contracts have no equivalent forcing function.
The deeper lesson is about the insourcing option itself. Very few organizations model, in advance, the actual cost and timeline of bringing a critical outsourced system back in-house if the vendor relationship deteriorates past the point of confidence. The UK government is doing that work now, under public pressure, years into a struggling contract. Enterprise leaders running similarly critical outsourced systems, HR, payroll, benefits, core financial processing, should have a credible, costed insourcing option on file well before a crisis forces the conversation, not after a minister has to say so in public.
