Whitehall framing, council-shaped problem
On 3 June 2026, the House of Commons Science, Innovation and Technology Committee published Rewiring the state: Delivering digital government — a report with a deceptively narrow-sounding title. On its face it's about the new Government Digital Service, digital ID, DSIT's machinery. But read past the Westminster framing and it's one of the clearest, most practically useful documents to land on a council Procurement Officer's desk in some time. Three of its four "barriers to effective digital transformation" — vendor lock-in, legacy systems, and technology sovereignty — are not central government problems. They are council procurement problems, showing up in exactly the same shape at local level: multi-year IT contracts, ageing case management systems, and a handful of suppliers who dominate the market. The Committee's evidence sessions included direct local government witnesses — West Berkshire Council's Digital Services Manager, a Sutton councillor, the LGA — so this isn't a central-government story dressed up as locally relevant.
A quick note on what this report isn't
It's worth correcting a piece of social media shorthand that's circulated widely: the claim that "Parliament has told the government to get rid of Palantir." That overstates it. The Committee's actual recommendation is narrower — exercise the February 2027 break clause in the NHS Federated Data Platform contract and develop an in-house or UK-based alternative, not remove Palantir from public sector work wholesale. The report's real value for procurement teams is in its method — how it reasons about lock-in, exit clauses and supplier dependency — not a blanket verdict on any one company.
Vendor lock-in: the core procurement lesson
The Committee's headline case study is the NHS's £330 million Federated Data Platform contract with a Palantir-led consortium, running up to seven years with a break clause in February 2027. One campaign group told the Committee that over the life of such a contract, a supplier can end up "attempting to burrow so deep" into an institution "that they cannot be migrated away from and can name their fee." That's not a Palantir-specific dynamic — it's what long, poorly-exited technology contracts do generally. The Committee's conclusion: vendor lock-in "should not be viewed as inevitable," and dependence on a small number of suppliers "does not automatically lead to better delivery of public services or better use of public money."
Three practical lessons follow. Build exit terms in at signature, not at renewal — break clauses, data portability and defined exit costs need negotiating when a council has the most leverage, before signature. Treat single-bidder outcomes as a flag, not a formality — the report highlights a ten-year, £472 million HMRC cloud migration contract for which AWS was the sole bidder. And borrow the diversification mindset the Committee wants GDS to adopt centrally — tracking supplier concentration across a council's own technology contract book is a reasonable, low-cost governance step that doesn't need to wait for a national mandate.
Legacy systems: a budget conversation, not just an IT one
Central government doesn't actually know the scale of its own legacy IT estate — 153 systems flagged across 16 departments as far back as 2023, and 15% of surveyed public bodies unable even to estimate their legacy footprint. Maintaining legacy systems runs three to four times more expensive than modern alternatives, yet spending consistently skews toward new programmes over remediation. The practical discipline: at the point of any new technology contract, ask what it's replacing and what the true cost of not replacing it is. That question turns legacy remediation from an IT backlog item into a procurement and budget-setting question — squarely in s151 territory.
Sovereignty and the opening for SMEs and open source
The Committee wants government to use its promised update to the Procurement Act 2023 to require public bodies to prioritise open-source tools over proprietary offerings where practicable, and recommends a defined minimum share of technology procurement budgets be ring-fenced for UK-based and UK-owned start-ups and SMEs. Neither is yet binding policy, but procurement officers who start building open-source and SME-inclusive criteria into tenders now will be better placed if and when this direction firms up.
Money: the resource-versus-capital problem
Only one in five public sector leaders surveyed felt current funding models "enabled effective investment" in digital services. Capital funding is consistently easier to secure than resource (day-to-day) funding, which the report says drives "inefficient buying behaviours such as end of year purchasing decisions." The Committee's target: 75% of digital and technology spend from resource budgets by the end of the current Spending Review period, up from an estimated 43–46% in 2021 — a capital/resource distinction that sits at the heart of s151 duties under the Local Government Finance Act 1988.
A 2023 Information Security Review, whose existence only became public after Committee pressure, found three recurring causes behind public sector data breaches: insufficient controls over ad-hoc downloads of sensitive data; information sent to the wrong recipients, or group membership exposed via visible address fields; and hidden personal data embedded in spreadsheets released externally. A useful checklist against any council's own data-sharing practices and supplier agreements.
The takeaway
HC 61 was written with Whitehall in mind, but its diagnosis travels well. Vendor lock-in, legacy system risk, sovereignty and SME access, capital-versus-resource budgeting, and data hygiene are recurring features of any large, long-running technology procurement relationship, council or department alike. Reading this as a procurement and financial governance document, not only a Whitehall progress report, is where its real value lies for local government.
Source: Rewiring the state: Delivering digital government, House of Commons Science, Innovation and Technology Committee, First Report of Session 2026–27, HC 61, published 3 June 2026.