Data is the currency of decision-making. A reliable, high quality national data infrastructure (that is, the network of open platforms, standards, and services that make high-value public data accessible, usable, and trustworthy at scale) is essential to deliver this Government's 'decade of national renewal'. The UK's Modern Industrial Strategy devoted a whole chapter to catalysing the value of data, "enabling the use of high quality data across private and public sectors".
For central government to make sound decisions about investment, policy and infrastructure, it needs insight into what’s happening on the ground—at neighbourhood, local, and regional levels. Much of that insight comes in the form of geospatial data: where housing is approved, where roads are constrained, where energy capacity is, where biodiversity must be protected, where it might flood, where people live and work.
And this national data infrastructure will enable high quality data which needs to be the foundation for AI tools to accelerate and potentially enhance the quality of decision making.
Yet here’s the challenge: central government does not hold most of this data — local authorities do. But the way central government requests, funds, or supports its collection remains inconsistent, fragmented and contradictory.. It’s a model that needs streamlining to make the best of limited local data capacity and capability so that local data can power the missions to “rebuild Britain”, “make Britain a clean energy superpower”, and “kickstart economic growth”. If the government is serious about delivering its five national missions it must first fix the poorly designed data relationship between local and central government. Without this, the state lacks the basic insight it needs to act coherently.
One-way street
Government gathers local data in two main ways. First, via statistical surveys, like the census or labour force surveys run by the Office for National Statistics (ONS). Second—and more problematically—by asking local authorities to collect, standardise, and submit data directly.
This second model is where things get tricky. Different departments ask for different datasets, on different timelines, in different formats. Sometimes these are mandatory (such as the collection and publication of brownfield land, as set out by regulation 4 of the Town and Country Planning (Brownfield Land Register) Regulations 2017). Sometimes they’re softly suggested through guidance. Sometimes, the request comes with funding; sometimes not.
Some examples:
The MHCLG Planning Data Platform supports local planning authorities to publish standardised datasets (mandated via regulations in the Levelling Up and Regeneration Act) via standard-compliant web endpoints. This is supported by co-designed standards and a self-service validation tool. Importantly, many authorities have received funding to do this, helping them hire GIS experts or backfill planners.
HM Land Registry’s Local Land Charges programme provides for third parties to handle data cleaning and structuring. Councils are left with the data and tools but not necessarily the skills to use or maintain it, meaning the exercise improves national data quality but hollows out local capability.
The Department for Transport mandates local authorities to supply spatial data on Traffic Regulation Orders (TROs). The D-TRO data schema is open and well-designed, but not every council gets the funding to implement it.
Even where Councils might not be required to collect data directly, there are multiple documents and strategies, such as Local Growth Plans, Nature Recovery Strategies and Local Plans where they are often paying consultants to collect administrative spatial data to submit to central government.
The result? An inconsistent patchwork. Some departments fund the work; others just expect it. Some provide schema validation tools; others send a PDF. Some publish transparent guidance and co-design standards; others let a council work it out themselves.
The hidden cost of uncoordinated data demands
Each department performs “new burdens assessments” before mandating data collection. But these are done in isolation, with no sense of the cumulative load placed on councils or similar data requirements for different purposes. Assessments often ignore the “tough trade-offs” councils face in a stretched fiscal environment.
A local authority team might simultaneously be implementing new energy data requirements from DESNZ, responding to DfT traffic data requests, and rushing to publish a brownfield register update - all in incompatible formats, to uncoordinated deadlines, via different platforms.
In addition, central government doesn't coordinate the delivery models. Sometimes councils are funded to publish. Sometimes a private contractor swoops in, fixes the data, then leaves. Sometimes the data must be published openly on council websites; other times it’s sent directly into a national register.
There’s no shared business model, and therefore no way for councils to plan forward. It creates confusion, duplication, and frustration.
Local data creation and sharing must be treated as part of the public service “reform” agenda, not just as an afterthought or a means to measure local authority compliance.
The stakes: infrastructure, AI and accountability
Data infrastructure underpins real infrastructure. The Government has committed to “rebuilding Britain” by delivering 1.5 million homes and fast-tracking major economic infrastructure. None of this is achievable without trusted spatial data—on land use, on infrastructure, on emissions, on need. Just as economic stability is recognised as a foundation for growth, a reliable national data infrastructure is foundational for effective government. Without consistent and trusted local data, national policy is built on sand.
Countries with better data ecosystems will be better placed to respond to current challenges (e.g. in COVID lockdown, councils that used standard identifiers for property were able to respond faster to support the vulnerable) and exploit emerging technologies like AI. Improving how data flows between local and national government is not a digital side-project - it’s a core part of reforming how the state delivers for people. Standards, funding models, and shared accountability must evolve together.
The current system fails to build long-term capability. When councils lack the staff and tools to manage data strategically, they contract it out to consultants. Each Local Plan or biodiversity study becomes a one-off commission, duplicating costs and eroding institutional memory. Critically, the inconsistent funding models that underpin data at the local level makes it hard for councils to invest in data capacity and capability; capability that is multi-purpose as it can be applied to all manner of local challenges and opportunities.
Worse, national policies—like the requirement to assess employment land - get implemented 300 different ways, meaning that comparisons and benchmarks are impossible or inaccurate. When data from across local areas is standardised and shared meaningfully, central government can track progress against national goals- and local communities can hold it to account. Without this, accountability is limited to press releases, not performance.
Fixing the fundamentals: a four-point plan
We need to fix the fundamentals of how central and local government work together on data. Fixing this data disconnect isn’t about blame. It’s about building a clear and functional partnership between central and local government that builds clarity, capacity and capability. Here are four suggestions for a way forward:
1. A coordinating body for standards
There should be a central point of coordination for local government-related data standards within central government. Which department this is housed in doesn't hugely matter but MHCLG or GDS (as part of the national data library) seem to make most sense, working closely with the Local Government Association. This department should maintain a live view of all current and candidate data standards that are likely to require collection by local government, and play the role of a librarian to help maintain consistency and minimise the burden on local authorities. It should also look to understand the cumulative burden of data requirements on local authorities, identifying overlaps and sequencing requests.
2. A consistent model for data design and collection
The coordinating body should help departments coalesce around a common model (taking advantage of global initiatives such as overture maps) e.g. co-designed data standards, published under open licenses, validated by shared tools, underpinned by user focused guidance and support to promote adoption by software vendors and ideally funded through grant. Where possible the coordinating body should seek to design, build and maintain common tooling that can be reused by other departments to define data standards, validate data or enable local authorities to publish their data consistently.
3. Invest in local data capability
If government wants better data, it must help build the teams that create and maintain it. That means core funding for data engineers, GIS specialists, and digital officials in local authorities so that they can better produce high quality data and make broad use of it locally. The coordinating body should commission research to understand the value of locally produced data (to central and local government), the cost of current duplication and non-provision and seek to make a business case for further funding for local authority data capacity and capability.
4. Reduce the burden on local authorities
As well as increasing local data capability, could some of the data collection burden be reduced by reallocating it regionally or centrally? Could the ONS or another central body be mandated and funded to collect certain dataset once, nationally? Could regional combined authorities take more of a role in collecting administrative data on behalf of local authorities? Such arrangements already exist in health with Integrated Care Boards (ICBs) managing health data regionally—take on infrastructure data roles?
When data flows both ways
Data isn’t a by-product of government - it’s its backbone. If data is to be treated as national infrastructure, then the systems that generate and maintain local data must be treated as infrastructure too.
A better deal means giving local authorities not just obligations, but agency -insight, tools, funding, and feedback loops - so they can both contribute to, and benefit from, national platforms. When data flows both ways, it becomes leverage rather than burden.
Fixing central–local data relationships takes time and hard work: co-design at the start, investment in people and processes, and a relentless focus on shared value. But without it Government’s AI, Industrial and Infrastructure strategies will rest on shifting sands.
Our recent insights
Transformation is for everyone. We love sharing our thoughts, approaches, learning and research all gained from the work we do.
-
Budget 2025 reveals how digital funding really works
Read insight -
Unlocking the benefits of AI for charities
Read insight -
What's the future for open data in the UK?
Read insight -