The Register reported this week that former Number 10 data-science director Laura Gilbert and Institute for Government executive director Alex Thomas warned MPs that the reshuffle could drive experienced staff away and create a damaging diffusion of responsibility. Those concerns have a stronger factual footing than a normal round of civil-service unease: the Commons Science, Innovation and Technology Committee had already found that the previous GDS move, from the Cabinet Office to the Department for Science, Innovation and Technology in July 2024, caused operational delays and hampered the government’s digital-delivery plans.
The latest move was formally announced by the Cabinet Office on July 22, 2026. That date matters. The government’s official fact sheet confirms GDS is now part of DCMS, alongside telecoms, media, online-safety, and misinformation functions, while AI strategy, public-sector AI adoption, and the AI Security Institute were moved into the Cabinet Office. The hearing has exposed the unresolved operational consequence almost two months later: GDS’s remit remains cross-government, but its institutional home is no longer at the centre of government.
A third home before the last move had settled
GDS was established in 2011 to make UK public services work more like coherent digital products rather than a collection of departmental websites and bespoke IT programmes. It spent much of its life in the Cabinet Office, where proximity to the Prime Minister and central functions gave it leverage over departments that otherwise controlled their own budgets, suppliers, and delivery timetables.
In 2024, the Labour government transferred GDS to DSIT and combined it with the Central Digital and Data Office and the Incubator for AI. The stated intent was to create a stronger “digital centre of government.” That model was still being built when DSIT itself was dismantled in July 2026 and its responsibilities spread among the Cabinet Office, DCMS, and the renamed Department for Business, Innovation, Science and Trade.
The Commons committee’s June report is particularly awkward context for the new arrangement. It concluded that the 2024 move had created operational delays and, along with changing priorities, had constrained delivery of the government’s own modern-digital-government blueprint. MPs stopped short of demanding a reversal because another reorganisation so soon would itself be disruptive. Instead, they recommended that ministers empower GDS with clear political and technical leadership, commission an urgent review of its powers, appoint a cabinet-level minister for public-sector digital transformation, and publish a detailed delivery plan and live progress dashboard.
The July reshuffle delivered none of those specific safeguards in the published machinery-of-government plan. DCMS has a junior ministerial digital portfolio, but the cabinet-attending AI role now sits jointly across the Cabinet Office and BIST. The official announcement says DCMS will “continue to drive the modernisation of government and public services via the GDS.” It does not identify a cabinet minister who owns that delivery mission, publish new accountability arrangements, or state how GDS will resolve disputes with departments.
That omission is central. Cross-government digital authority works only when departments believe an escalation will reach somebody who can make a binding decision.
The procurement issue is bigger than a reporting line
The move lands while GDS is expected to become more than a service-design shop. The government’s prior digital blueprint gave the expanded GDS responsibility for central spend assurance and digital spend controls, including review of proposed contracts worth £5 million or more. Its remit includes setting standards, sharing reusable platforms, improving data practices, and giving departments the capability to replace fragile legacy technology.
That function affects the suppliers and platforms familiar to enterprise administrators: Microsoft 365, Azure, AWS, Google Cloud, Oracle, systems integrators, managed-service providers, and the long tail of specialist vendors used by central government and arm’s-length bodies. In a large organisation, procurement assurance is where architecture principles become enforceable. A common cloud standard, identity policy, security baseline, or data-classification scheme means little if a department can commit to a major platform before the central team has the staff or authority to challenge it.
The Commons committee found that digital spending was already difficult to manage coherently. It said departments had insufficient visibility into digital expenditure, that public-sector funding structures rewarded capital projects over day-to-day service operation, and that this could encourage inefficient purchasing. Its recommendation was that GDS and HM Treasury receive explicit responsibility for changing that balance and reporting progress annually.
The government also created a Digital Commercial Centre of Excellence to improve public-sector buying power. The Register reported in July that the unit moved to DCMS with GDS. The policy is intended to improve the government’s bargaining position with large technology suppliers and create more openings for UK firms. Whether it can do that from a department whose other major priorities include broadcasting, sport, culture, telecoms, and online safety remains untested.
There is no evidence yet that the departmental move has cancelled any procurement controls, postponed active projects, or changed an existing software contract. But the lack of a published transition plan leaves departments, suppliers, and civil servants without an answer to a basic question: who has final authority when GDS’s commercial or technical advice conflicts with a department’s delivery deadline?
AI has moved closer to power while delivery has moved away
The division between GDS and AI policy is the clearest architectural choice in the Burnham government’s reorganisation. The Cabinet Office will lead public-sector AI adoption; the Office for the Prime Minister and Cabinet will host an AI Taskforce; and AI strategy and the AI Security Institute are being brought into that central orbit.
GDS, meanwhile, retains the task of modernising the services and systems that AI initiatives would have to use. That includes the unglamorous work: data quality, identity, interoperability, service ownership, procurement controls, cloud migration, legacy-system remediation, cyber-resilient operations, and workforce capability.
The risk is that AI becomes a centrally sponsored programme while the underlying delivery machinery is governed elsewhere. A generative-AI pilot can be announced quickly. Integrating it safely into a benefit system, case-management platform, contact-centre workflow, or records environment depends on durable technical standards, procurement discipline, data controls, and staff who understand the existing estate.
The committee’s June report made a related warning before the latest reshuffle. It said public-sector digital transformation required clear standards, approval processes, and accountability, and that fragmented oversight could weaken the state’s ability to bargain with suppliers. It also noted that only a minority of public-sector leaders surveyed believed the then-current arrangements enabled effective investment in and operation of digital services.
This is why Gilbert’s warning about talent loss should not be dismissed as routine organisational anxiety. The hardest people to replace are rarely generalist programme managers. They are technical leaders who understand the relationship between procurement rules, service architecture, security obligations, departmental politics, and operational reality. If they leave during a transition, the immediate vacancy may be filled; the institutional memory usually is not.
What GDS needs published now
The government has framed the restructure as a way to make the state more strategic and to place science and technology across the economy rather than inside a single department. That is a legitimate political choice. It does not answer how GDS will exercise its cross-government responsibilities after being placed in DCMS.
A credible transition plan would set out several operational facts that are currently missing:
- It should name the senior official and minister accountable for GDS’s authority over digital standards, spend controls, and departmental delivery.
- It should state whether the planned review of digital spending above the £5 million threshold remains in force and whether its timetable has changed.
- It should confirm the governance relationship between GDS, the Cabinet Office’s AI adoption work, HM Treasury, the National Cyber Security Centre, and the Digital Commercial Centre of Excellence.
- It should publish retention, recruitment, and succession measures for GDS’s technical leadership during the departmental transfer.
- It should give departments a clear escalation route for decisions involving shared platforms, cloud contracts, data standards, and legacy-system remediation.
These are not bureaucratic niceties. They are the mechanisms that determine whether “whole-of-government” digital transformation becomes a workable operating model or a series of disconnected departmental programmes.
The committee had asked for an urgent GDS review to report by the September sitting of Parliament. With GDS now in its third departmental home in little more than two years, that review cannot simply restate the old roadmap. It needs to show whether the unit can still stop poor technology purchases, enforce common standards, and retain the people who make those interventions credible.