Britain Extended Capgemini's Pensions Dashboard Contract to
By the Factrail desk · Method: how we source and score · Last reviewed

TL;DR
A September 2026 contract modification added £6.94m to a government pension-data system. Photo: CC BY 3.0, House of Commons / Roger Harris.
Key graph impact
The article explains graph entities; the causal edges belong to the facts and drivers it links to.
- ArticleBritain Extended Capgemini's Pensions Dashboard Contract to
- mentionsDriverHousehold Purchasing Power
- weakensIndicators (2)Global Consumer Price Inflation (annual %)
Weakens · 40% impact strength
Observed
5.8 annual % change in CPI · 2.3 above the normal line (Dec 2024)
Better than normal5 readings, 2020–2024: rose from 3.3 annual % change in CPI to 5.8 annual % change in CPI.
Moving normal line · Lag ~12 mo
- Better
Weakens · 35% impact strength
Observed
10.4% · 10.2 above the normal line (2024)
Worse than normal7 readings, 2018–2024: fell from 11.1% to 10.4%.
Above normal = worse
Article
Photo: CC BY 3.0, House of Commons / Roger Harris. Image source (opens in a new tab).
Britain Extended Capgemini's Pensions Dashboard Contract to £78.9m. Savers Still Face a 2027/28 Launch.
Factrail investigation | United Kingdom | Contract modification: 21 September 2026 | Statutory connection deadline: 31 October 2026 | Research checked: 2 November 2026
SEO title: UK Pensions Dashboards: Capgemini £78.9m Contract and Delayed Launch
Dek: A September 2026 contract modification added £6.94m to a government pension-data system. The legal connection deadline has passed, but public access is a different decision—and the spending totals require careful accounting.
The finding
The British government required pension providers to connect to a national data system by 31 October 2026, but that deadline did not give the public a working pension dashboard. The Money and Pensions Service says the consumer-facing MoneyHelper service is expected in financial year 2027/28, with the precise launch date still to be set. Meanwhile, a September procurement notice records a £6.94 million modification to Capgemini UK’s central-architecture contract, taking its stated value to £78.92 million excluding VAT. The contractor is a documented beneficiary of the additional authorized work, not evidence of an illicit deal. The deeper accountability question is why ministers can impose a fixed connection deadline on schemes while the launch decision and latest programme-wide costs remain less immediately testable. The record identifies who can decide, which money is a contract ceiling rather than paid cash, and which missing evidence would settle whether the extension delivered value.
The new documentary linkage is between three records that should not be collapsed into one story: the September 2026 procurement modification reproduced from Find a Tender (opens in a new tab), the National Audit Office's earlier investigation of the programme's management and costs (opens in a new tab), and the Pensions Dashboards Programme's current statement about the public launch (opens in a new tab). Read together, they show a statutory duty on schemes, a continuing contract with a named supplier, and a separate ministerial choice over when savers can use the system. They do not prove that the October connection target was missed across the industry: a final, comprehensive post-deadline connection ledger was not independently established in this research.
A contract with three different price points
The central digital architecture is the technical system intended to find pension records, obtain the user's consent and authenticate access. The Money and Pensions Service (MaPS), an arm's-length body sponsored by the Department for Work and Pensions (DWP), contracted with Capgemini UK plc for that infrastructure in 2021. Capgemini said it would work with Origo, a named industry technology partner. The programme's original supplier announcement (opens in a new tab) described the choice as based on quality, value for money and the partners' delivery expertise.
The procurement history matters because a current £78.9 million figure is not the price of a wholly new September 2026 contract. The public notice history (opens in a new tab) presents an original contract value of £56,979,971 excluding VAT, then a £15 million addition published in May 2025, raising the recorded total to £71,979,971. The 21 September 2026 modification adds £4.01 million for the first optional one-year extension of existing services, plus £2.93 million for additional technical services. Together those September components equal £6.94 million, making the published total £78,919,971 excluding VAT. These figures are successive versions of one contract, not three separate contracts whose headline values should be added.
The new technical work is described as supporting public beta, live-service readiness, stability and transition planning. MaPS argues that replacing the incumbent at this stage would require knowledge transfer, parallel staffing and additional management overhead. It says it benchmarked and negotiated the costs and conducted an open-book review. That is a specific and testable public-interest defence, not merely a vague assertion of urgency. But the procurement record does not by itself provide the underlying benchmark, the independent price comparison or an invoice ledger. The £78.9 million total is a recorded contract value; it is not proof that Capgemini has received £78.9 million in cash.
Nor is it accurate to say that the 2021 award was simply an illegal no-bid gift. The notice explains that the original call-off followed a mini-competition under a Crown Commercial Service framework. The later changes were made without a new open procurement and justified by MaPS under Regulation 72 of the Public Contracts Regulations 2015. The original competition and the legality of a later modification are different questions. No court ruling invalidating this modification was located, and none is alleged here. The official 2025 Find a Tender modification PDF (opens in a new tab) provides an additional primary record of the earlier contractual structure. The 2026 official notice URL was identifiable but direct retrieval returned an access error; the September details cited here are from publicly accessible mirrors of that notice.
The deadline that does not unlock the dashboard
The DWP's staged connection guidance (opens in a new tab) says relevant occupational pension schemes and regulated personal pension providers were legally required to connect to the infrastructure by 31 October 2026. That is a duty on providers and trustees to make records findable and respond to requests. It is not a legal promise that every individual could log into a public dashboard the next morning. Some schemes are outside scope; specific statutory exceptions and deferral mechanisms also matter.
The programme's connection page (opens in a new tab) explicitly distinguishes connection from the launch of the public MoneyHelper Pensions Dashboard. The Secretary of State for Work and Pensions will decide the public launch date, and the pensions minister has said the industry will receive six months' notice. The current expectation is financial year 2027/28, which runs from April 2027 to March 2028. As of the research date, this is an expectation, not an announced day on which the public will gain access. A scheme can be technically connected while the consumer interface remains unavailable.
That distinction changes how a claim of success should be judged. If the infrastructure can answer test queries from connected providers, the connection programme may have achieved a significant engineering milestone even before launch. But a saver who wants to find an old pension cannot yet receive the promised public service simply because an industry compliance deadline has passed. Treating either fact as proof of the other would inflate delivery claims.
The documentary timeline
2019: DWP delegated delivery to MaPS. The National Audit Office (opens in a new tab) later concluded that the department did not establish at the outset whether this relatively new body had sufficient capability to run such a large digital programme. That was an institutional choice, not a finding that a particular minister intended the project to fail.
2021: The Capgemini central-architecture contract began. The Pensions Dashboards Programme (opens in a new tab) publicly named Capgemini and Origo and explained the functions they would deliver. The contract included two possible one-year extension periods.
December 2022–June 2023: MaPS informed DWP that the delivery timetable was no longer viable. A DWP review identified shortages of digital skills and weak governance. The then government reset the programme, and amendments established a single final statutory connection deadline in October 2026. This history is documented by the NAO investigation (opens in a new tab) and the 2024 parliamentary ministerial statement (opens in a new tab).
May 2024: The NAO reported that the programme's estimated cost had increased from £235 million in 2020 to £289 million in 2023, while estimated gross benefits had been revised from £437 million in 2022 to £413 million in 2023. These are estimates with differing dates and accounting bases, not a fresh November 2026 outturn. The NAO also noted that the public launch date remained unspecified. Its review is the benchmark against which later progress should be measured, not a substitute for current accounts.
May 2025: A further £15 million was added to the central architecture contract, according to the procurement history (opens in a new tab). PublicTechnology's contemporary reporting (opens in a new tab) described the uplift in VAT-inclusive terms and situated it within the wider programme cost. The difference between inclusive and exclusive VAT must not be misrepresented as a discrepancy in the contract itself.
May 2026: The Pensions Regulator (opens in a new tab) reported that around 75% of member records were connected and launched a data-quality initiative covering 240 defined-benefit and hybrid schemes. This was a progress snapshot months before the final deadline, not proof of the eventual completion rate.
21 September 2026: The contract modification was published, adding £6.94 million and extending existing work to September 2027. The timing matters: the state authorized more work beyond the October 2026 scheme-connection deadline because consumer readiness and system operation continued after connection.
31 October–2 November 2026: The statutory connection date passed. The official programme still describes public access as expected in 2027/28. No independently verified, complete 2 November scheme-by-scheme compliance register or final cost outturn was available to this investigation, so the article makes neither a universal compliance claim nor a universal breach claim.
Who had the power to decide—and who could stop it?
The responsibility chain has several levels. Pat McFadden, the current Secretary of State for Work and Pensions (opens in a new tab), holds departmental responsibility for spending and performance and the statutory role in determining the dashboard launch date. Torsten Bell, the pensions minister (opens in a new tab), has an explicit ministerial oversight portfolio covering MaPS and the pensions regulator. Neither official should automatically be described as the person who signed the September contract modification: the named contracting authority is MaPS. Their accountability is political and supervisory, while contractual decisions sit with the public body acting under its procurement powers.
Parliament created the legal framework and can question ministers, examine estimates and legislate. DWP sets policy and supervises MaPS. MaPS manages the architecture contract and coordinates connections. The Pensions Regulator supervises occupational schemes, while the Financial Conduct Authority sets corresponding rules for regulated personal pension providers and future dashboard operators. Trustees and providers control the quality and timely provision of their own members' records. Capgemini builds and supports the contracted architecture, but it does not set the statutory deadline or decide when the public service opens.
These distinctions prevent a convenient blame transfer. A contractor may be responsible for a defined technical deliverable without being responsible for every provider's poor historical data. Conversely, ministers cannot demonstrate success merely by pointing to a supplier contract if public benefits remain inaccessible. The authority to approve a contract change, the authority to enforce connection and the authority to launch a public service are not interchangeable vetoes.
The money route and named beneficiaries
The clearest direct commercial beneficiary in the disclosed contract is Capgemini UK plc: the additional September work increases the value of services the public authority may purchase from that supplier. Origo is a named partner in the original delivery arrangement, but this research did not establish how the 2026 modification's consideration is divided between Capgemini, Origo or any other subcontractor. Calling the whole £6.94 million a payment to Origo would be unsupported.
The potential public beneficiaries are pension savers who may eventually search across old workplace and personal pension records, rather than having to contact multiple schemes individually. The NAO (opens in a new tab) cited an estimate of 16.3 million prospective dashboard users and noted that the benefits calculation included willingness to pay and possible recovered pension pots. That figure does not mean 16.3 million people have already received a working service or that each has recovered money. A separate estimate of lost pension pots measures a problem the project aims to address; it is not money the government has already returned.
There are also compliance costs for trustees, pension providers, administrators and technology vendors. The programme's guidance (opens in a new tab) notes that many schemes use third-party connection providers. Those firms can earn implementation and administration revenue, but this research does not have an audited register of every contract or its net profit. A genuine accounting would separate the central government architecture budget from private-sector compliance costs and the eventual value of successful matches. Adding every figure into a single dramatic bill would be misleading.
The £289 million programme estimate published by the NAO in 2024 and the £78.9 million contract value published in 2026 are not comparable totals. One is an earlier multi-year estimate for the programme; the other is a specific supplier contract including later changes. It would be wrong to add the contract to the programme estimate without checking whether it was already included, or to infer a current total from an outdated programme estimate. The essential missing evidence is a reconciled 2026 business case with actual expenditure, forecast completion cost, supplier invoices and benefits realized.
The strongest counter-case: continuity can be cheaper than switching
MaPS offers a concrete explanation for staying with Capgemini. Replacing a contractor responsible for central consent, authorization and record-finding systems near a statutory deadline could force expensive duplication, disrupt testing and increase security and delivery risk. The September notice mirror (opens in a new tab) says MaPS performed benchmarking, open-book review and commercial negotiations. It relies on contractual extension rights and the legal provisions allowing certain necessary additional services without a new procurement. Those are relevant safeguards and should be tested rather than dismissed.
The progress evidence also cuts against an unqualified failure narrative. The programme reported more than 1,000 connected providers and schemes and more than 60 million workplace and personal pension records (opens in a new tab) in an earlier 2026 update, while the State Pension had also been connected. The Pensions Regulator (opens in a new tab) emphasized the importance of accurate benefit valuations and warned that wrong data could harm retirement decisions. A delay between technical connection and consumer launch can be prudent if it prevents false matches, security problems or misleading pension figures.
Yet that defence has limits. A legal explanation for modifying a contract is not the same as independently published evidence that the modification was the least costly option. A high connection percentage is not proof that data is accurate for every user. And a future public launch is not a present benefit. The strongest question for MaPS is whether its internal tests, benchmark comparisons and cost forecasts support the claimed value for money, including the counterfactual cost of an earlier supplier transition.
What the available record cannot prove
No documentary evidence reviewed here establishes that Pat McFadden, Torsten Bell or another politician held a personal financial interest in Capgemini's pension-dashboard contract. No improper donation, lobbying exchange, corrupt inducement or unlawful award is alleged. The company is a named contractor, not a demonstrated political patron. The procurement notice states an institutional decision; it does not disclose a minister's private motives.
The publicly mirrored 2026 modification supplies amounts and legal justification, but the official Find a Tender notice could not be fetched directly in this research session. That is an access limitation and should be addressed during independent QA. The original contract, all change orders, the actual invoices and MaPS' confidential benchmarking should be reconciled before an accusation about overcharging. Neither the NAO's 2024 assessment nor a trade-publication account of the 2025 increase establishes that the 2026 modification was unnecessary.
Likewise, no reliable final compliance count as of 2 November was established. The article therefore does not say every scheme connected, or that all failed to connect. A regulator's later enforcement data could materially change the conclusion. This is a documented investigation of the governance and commercial structure, not a finding that any named official or company broke the law.
The accountability test after the deadline
Five records would settle the most important open questions: the final 31 October connection and data-quality figures by provider cohort; the 2026 MaPS business case and total forecast programme outturn; the full Capgemini modification, invoices and independent cost benchmark; the published criteria for deciding the public launch date; and a report on how many users actually find valid pension records after launch. These records should be examined together rather than released as isolated positive milestones.
The public should also be able to distinguish a service that is connected, a service that has passed end-to-end user testing, and a service that is open to consumers. Parliament can ask ministers for those separate measures. The regulator can report compliance and data quality. MaPS can explain what the £6.94 million buys, why the incumbent was retained and whether the added work was delivered. Capgemini can respond on scope, testing and milestones. No direct requests for comment were sent by this research run; the institutions' published explanations are represented instead.
What it moves
The measurable indicators are scheme connection compliance, accurate record-match rates, public launch timing, central architecture contract commitments, actual programme expenditure, and successful recovery of previously unlocated pension information. The September modification moves the disclosed contract ceiling upward by £6.94 million. The October statutory date changes the legal compliance position for in-scope schemes, but it does not automatically change the public launch status. The expected 2027/28 opening moves the anticipated consumer-benefit date later than the scheme-connection deadline. No quantified change in saver wealth, tax receipts or pension outcomes can yet be assigned to the modification.
The central verdict is narrower and more consequential than a claim that the state paid £78.9 million for a website that does not work. The record shows an enlarged incumbent contract, a passed legal connection deadline, and a separately controlled public launch still expected in 2027/28. The political accountability test is whether ministers and MaPS can publish the full spending and service-readiness evidence that connects those three facts.
Source and verification notes
Primary and official material: Find a Tender 2025 modification PDF (opens in a new tab); NAO investigation (opens in a new tab); DWP staged connection guidance (opens in a new tab); Pensions Dashboards Programme deadline and launch page (opens in a new tab); The Pensions Regulator May 2026 release (opens in a new tab); MaPS/Programme 2021 Capgemini announcement (opens in a new tab); Pat McFadden official ministerial remit (opens in a new tab); Torsten Bell official ministerial remit (opens in a new tab).
Independent and public-record intermediaries: September 2026 contract notice mirrored by Tenderline (opens in a new tab); PublicTechnology on the 2025 uplift (opens in a new tab); Pensions Expert on the regulator's connection warnings (opens in a new tab). The official 2026 procurement notice is Find a Tender 089379-2026 (opens in a new tab), but it returned a direct-access error during research; do not label its full text independently inspected. Source URLs in this article are documentary references, not verified Factrail internal links. No image licence or publication approval is claimed.
Related Factrail context
For broader background on the institutions and policy issues, consult keir-starmer (opens in a new tab), rachel-reeves (opens in a new tab), and household purchasing power (opens in a new tab). These background references do not prove direct responsibility for the transactions discussed above.
Evidence
The sources this article cites, claim-bearing material first.
- gov.uk · gov.uk/government/publications/pensions-dashboards-guidance-on-connection-the-staged-timetable/pensions-dashboards-guidance-on-connection-the-staged-timetable
- thepensionsregulator.gov.uk · thepensionsregulator.gov.uk/media-hub/press-releases/2026-press-releases/db-hybrid-schemes-act-now-to-get-data-ready-for-dashboards
- gov.uk · gov.uk/government/ministers/parliamentary-under-secretary-of-state--205
More analysis
Ranked by shared facts, drivers and people — never by publication date alone.
Articles12
- Defra Called a Full Food Emergency Plan Disproportionate. AuShares the driver: Household Purchasing Power · 2 November 2026
- Housing Costs Are Rewriting Three ElectionsShares the driver: Household Purchasing Power · 3 November 2026
- Trump's FEMA Called Disaster Grants Wasteful. A Court ReversShares the driver: Household Purchasing Power · 2 November 2026
- After the Midterms: Who Pays for a Divided Congress?Shares the driver: Household Purchasing Power · 3 November 2026