The Contract Changed. The Problem Did Not.

When technology is too slow, too expensive or too difficult to explain, outsourcing can feel like the obvious answer. Bring in a specialist. Move delivery outside the organisation. Let someone else fix what internal teams, or the current outsourcer, have been wrestling with for years.

That is the appeal. It is also the trap. Outsourcing can change who runs a service and bring tools, commercial discipline and specialist skills. What it cannot do is erase years of underinvestment, fragmented architecture, weak controls or unresolved operating problems. Those conditions do not disappear at contract signature. They become the starting point for the new provider.

The issues around Capita and the Civil Service Pension Scheme illustrate the point. The scheme had 1.7 million members at 31 March 2025. Administration transferred from MyCSP to Capita on 1 December 2025 after a two-year transition. By July 2026, the government said Capita had not restored the service to the promised levels and was withholding £9.9 million in payments while deploying independent auditors.[1, 2]

That does not excuse the incoming provider. A supplier taking on a critical service must understand the risk and deliver against its commitments. Nor does a broken service become fixed because a contract changes hands. Official updates recorded 8,063 inherited quotation cases, around 23,000 outstanding pension quotations in April 2026 and 15,000 unread emails that had to be read and triaged. A Cabinet Office letter also described a backlog more than four times the expected normal level, alongside lower-than-expected automation and misjudged assumptions about the productivity of manual processes.[2, 3, 4, 5]

Accountability moves. Reality does not.

Outsourcing works best when the organisation knows what it is transferring. It understands the current demand, the true service baseline, the workarounds in place, the user pain points and the decisions that have been deferred. It can separate supplier accountability from the responsibilities that still sit with the retained business, technology or policy teams.

Without that clarity, outsourcing disguises uncertainty rather than resolving it. The contract describes a cleaner future. The business case assumes savings, better service and lower risk. The transition plan shows a neat path from mobilisation to go-live. But if the baseline is weak, the plan is built on hope.

This is where “transfer of risk” becomes dangerous shorthand. A customer can transfer contractual accountability for delivery. It can define service levels, penalties and remedies. It cannot transfer away poor data, process debt or unclear decision-making. Those unresolved conditions follow the service and reappear as migration defects, failed automation, exception queues, manual rework, unread correspondence and frustrated users.

Outsourcing is a delivery model, not a cure. If the problem is scale, specialist capability or operational discipline, a supplier may help. If the deeper issue is weak ownership, unfunded remediation or poor prioritisation, the supplier inherits the problem rather than solves it.

The baseline follows the service

Most technology problems are not purely technical. They combine old platforms, inconsistent processes, unclear ownership and tolerated exceptions. The system may be fragile, but the deeper weakness usually sits in the operating model around it.

That is why a new portal, supplier platform or managed service can disappoint so quickly. The front door changes, but the foundations remain weak. Users see a new interface while the organisation still carries the inherited debt beneath it.

This is not just a public sector problem. It appears whenever application management, infrastructure, service desk, payroll, HR, finance or pensions administration is moved to a third party without changing the conditions that caused the original failure. Supplier discovery is inevitable. The danger is discovering the scale of the problem only after the commercial model, transition plan and service expectations have been locked.

Fix the starting point before the handover

The answer is not to avoid outsourcing. A specialist provider may be exactly what is needed. The mistake is outsourcing before the organisation has been honest about the condition of the service and what it will take to stabilise it.

Before outsourcing a technology-enabled service, leaders should answer five blunt questions. What is already broken? What must be fixed before transition? What can be fixed during transition? What remains the customer’s responsibility after go-live? And what is the supplier genuinely accountable for?

These questions are often avoided because the answers are inconvenient. They expose unfunded remediation. They weaken the business case. They delay procurement. But avoiding the truth does not reduce the cost. It moves the cost into transition, recovery, user frustration and reputational damage.

A better approach is to treat outsourcing as part of a wider service recovery plan. Establish a credible baseline before contract signature. Be explicit about current volumes, platform readiness, manual workarounds and control weaknesses. Agree what must be fixed before go-live and what belongs in a managed improvement plan. If the service goes live with known defects, recovery will have to happen in public, on a running service, without the option of stopping the clock.[6]

Technology change needs the same honesty. A new platform or portal can improve access and transparency, but only if the underlying service can support it.

You still need a capable retained team

One quiet failure in outsourcing is the hollowing out of the retained organisation. Once a supplier is appointed, internal teams can step back too far. Knowledge drains away. Ownership blurs. The organisation loses the ability to challenge, prioritise, make design decisions or judge whether problems are operational, contractual or structural.

The retained organisation does not need to do everything, but it must remain accountable for the service outcome. It owns priorities, funding decisions, business rules, risk acceptance and user impact. It must know enough to tell the difference between supplier failure and internal constraint. Without that capability, outsourcing becomes a dependency, not a partnership.

This matters most where the service affects people’s lives, finances or work. Pensions, payroll, benefits, healthcare and public services are not abstract systems. If the service fails, the person waiting for an answer, payment or decision does not care which party caused it.

The leadership test

Leaders must say what is broken before the contract is signed, challenge optimistic business cases, fund remediation where needed and keep enough capability in-house to govern the service.

The Capita pensions situation should not be read only as a story about supplier performance. It is also a warning about leverage. Once a flawed transition has gone live, the customer may have penalties, remedies and political pressure available but still lack a safe or practical route out. At that point, the problem is no longer just contractual. It is operational.

For any organisation considering outsourcing as the answer to a technology problem, the lesson is simple. Be honest about the starting point. Define what the supplier is fixing, what the organisation is fixing and what still needs investment. Then outsource if it still makes sense.

Outsourcing can help transform a service. It can bring pace, expertise and accountability. But it is not a magic act. It cannot make old decisions disappear, fix weak foundations through contract clauses or replace the need for service ownership. Before outsourcing a technology problem, the organisation must first admit what the problem really is.

References

1. House of Commons Library, Administration of the Civil Service Pension Scheme, 20 July 2026.
2. Cabinet Office, Civil Service Pension Recovery Plan Update, 13 July 2026.
3. Cabinet Office, Civil Service Pension Recovery Plan Update, 27 April 2026.
4. Cabinet Office, Civil Service Pension Recovery Plan Update, 30 March 2026.
5. Cabinet Office Permanent Secretary letter to the Public Accounts Committee, 22 January 2026.
6. Cabinet Office, The Sourcing Playbook, updated 15 June 2026.