DWP Leak Torches £370M Capita Deal as Sopra Steria Sues

A bid manager I had coffee with in Holborn last autumn told me the most dangerous file in any government procurement was never the bid itself. It was the side document. The pros-and-cons sheet someone on the transition team puts together to make a Tuesday morning easier. "It always exists," she said. "And it always says more than the bid does." She was talking about a different deal. The principle holds. Today's filing in the Sopra Steria v. DWP case is, as far as I can tell from the court papers, the textbook example of why.

The Deployment

The Department for Work and Pensions awarded Capita a Business Process Service contract worth £370 million over ten years earlier this year. The original earmarked maximum was £958.7 million. The BPS sits inside the wider Synergy programme, the cross-departmental HR-and-finance rebuild that IBM and Oracle won the £711 million build contract for in 2024.

Sopra Steria bid for the BPS work and lost. In January it began a legal challenge alleging Capita's price was abnormally low and that the procurement broke UK public procurement rules. Capita and the DWP both deny the claim.

The piece that turned the lawsuit from a price-fight into something else is what the court papers call the Comparison Document. Per the DWP's own defense filing, a Project Support Manager inside the department wrote a comparison sheet that referenced both bidders by name. It was, the DWP says, intended for transition planning, a way to pull anonymised generic detail from both bids into shared planning assumptions. In August 2025, a link to that document was sent to one employee and one contractor at SSCL, the Sopra Steria subsidiary that runs DWP's existing Oracle-based HR and finance back office. The DWP says this was "inadvertent," that the document was "confidential and had clearly been shared in error," and that SSCL passing it up to its parent breached the Ethical Wall Agreement the two had signed precisely to prevent that.

Sopra Steria, in its claim, says the document contained summaries of its bid alongside details of Capita's, and that it was circulated to at least eleven DWP staff, including evaluators on the procurement. It also says the document showed plans between the DWP, Oracle and IBM to alter the Synergy timeline and scope, and that the DWP renegotiated Capita's tender after Capita had been picked as preferred bidder, to align with those changes. That, Sopra Steria says, is the breach.

Why It Matters

The lazy read on this story is "government leaks document, government embarrassed." That's not the read. The read is that a procurement that has been politically defended at every step is now turning on a single internal artifact that nobody at the centre of the project will admit to having authorized.

Look at the structural problem. SSCL, a Sopra Steria subsidiary, runs the back office of the very department running the procurement Sopra Steria is bidding into. That arrangement is endemic in UK shared-services. The fix is the Ethical Wall, the contractual promise that the services side and the bidding side don't talk about the live procurement. The DWP's defence is that SSCL got a link it shouldn't have and then breached the wall by passing the document up. Sopra Steria's counter is more interesting: the document came from inside DWP, it was circulated to evaluators, and it described plans that materially changed Capita's tender after preferred-bidder selection. If the court agrees the document was procurement-relevant rather than transition-relevant, the DWP's "we sent it in error" framing collapses, because then the question isn't who saw it, it's why it existed.

The vendor pattern this echoes is the Fujitsu Post Office Horizon procurement-litigation cycle and, before it, the long Crown Commercial Services rerun fights of the late 2010s. Same shape: a side document, written for benign reasons, becomes evidence that the formal evaluation process and the actual decision were not the same process. Operators in the public-sector buyer-side world know this. Sellers know it too. The reason ethical-wall paperwork has gotten thicker every year is because the case law has gotten more specific about what counts as a procurement document.

The third thing to notice is the price. Capita's bid came in at £370 million against an earmarked maximum of £958.7 million. That's a 61 percent discount on the ceiling. Sopra Steria's claim that the price is "abnormally low" is, on its face, the kind of pleading you'd expect from a losing bidder. But abnormally-low pricing is a defined concept in UK public procurement rules, and DWP's renegotiation of Capita's tender post-selection, if the document shows what Sopra Steria says it shows, is exactly the kind of conduct courts have intervened on before.

I am not predicting an outcome. I am noting that the Comparison Document is now the load-bearing piece of evidence on three different threads of the lawsuit at once: the leak itself, the abnormally-low pricing, and the post-selection renegotiation. That is a lot of weight for a transition-planning sheet to carry.

What Other Businesses Can Learn

If you run, sell into, or buy from a UK shared-services arrangement, this case is not abstract. It is the next twelve months of your conflict-of-interest register being read more carefully than it has been in five years. Three things land for operators on either side of that table.

First, the ethical wall is an audit, not a document. The DWP and Sopra Steria signed an Ethical Wall Agreement specifically because SSCL was already inside DWP and Sopra Steria was bidding into the same department. The agreement existed. The breach happened anyway, because the link landed in a SharePoint inbox that wasn't gated. If you are running a shared-services contract for a client you also sell to, the test isn't whether the EWA exists. The test is whether someone at director level can produce, on a Wednesday afternoon, the access-control list that enforces it. If they can't, the wall is rhetorical.

Second, internal "transition planning" documents that name bidders are procurement documents. The DWP's filings work hard to argue the Comparison Document was for "internal transition planning" and not for evaluation. That distinction may matter to a project manager. It will not matter to a judge if the document materially compares two bidders' content. The lesson for any procurement team: assume any artifact created during a live procurement that names bidders will be discoverable and will be treated as procurement-adjacent. Mark it accordingly. Lock it down accordingly. If you can't justify a sentence's existence to a judge, don't write the sentence.

A document that 'reflects the content of a tender' is the tender, in the eyes of a court, regardless of which internal process commissioned it.

Third, post-selection renegotiation is the silent killer. Sopra Steria's most pointed allegation is not that it lost. It is that DWP changed Capita's tender after Capita was picked as preferred bidder, to align with timeline and scope changes the department was negotiating in parallel with Oracle and IBM. Public-sector buyers do this all the time. It is almost always defensible. It is almost never legally bulletproof, because the rules require a procurement to evaluate the tender that was submitted, not the tender as renegotiated. If you sit on a procurement panel for a contract above the threshold, the rule of thumb is simple: any change to the winning bid that would have affected another bidder's price or scope is a change that has to come back through the process. Otherwise, the unsuccessful bidders' lawyers, and Sopra Steria has clearly decided to be one, will frame it as the actual decision and the formal evaluation was theatre.

Looking Ahead

The court will set a timetable. The DWP will continue not commenting on an ongoing legal matter. Capita has already said it stands ready to deliver. None of that tells you whether the procurement gets rerun, which is the only thing operators inside the Synergy programme actually want to know.

When I asked the procurement specialist in Holborn what she thought happened in cases like this, she didn't talk about the law. She talked about the meeting where the side document gets commissioned. "There's always one person in the room who says we shouldn't write that down," she said. "And there's always one person who does it anyway, because the spreadsheet is faster than the conversation." The Comparison Document, whatever the court decides about its purpose, was that spreadsheet.

Sources

• The Register, UK govt dept sent a document 'in error.' Now it's being used in a £370M contract lawsuit, accessed 2026-04-28