There is a quiet revolution happening inside Britain’s town halls and NHS trust back offices. Not the kind that comes with press releases or ministerial photo opportunities, but the kind where a digitally curious project manager discovers Microsoft Power Apps on a Tuesday afternoon and, six months later, has replaced a process that previously required three spreadsheets, two email chains and a contractor invoice for £40,000. No-code local government UK adoption has been growing steadily for several years, largely under the radar of the national tech conversation that tends to fixate on AI labs and billion-pound defence contracts.
The numbers make the motivation obvious. According to the Local Government Association, English councils face a cumulative funding gap running into billions. NHS trusts are no different. When you are managing services on a budget that has been squeezed for over a decade, paying a systems integrator £200 per day to build a bespoke case-management tool is not a serious option. No-code and low-code platforms, the likes of Microsoft Power Platform, Salesforce Platform, Airtable, Mendix and the open-source favourite Appsmith, offer something genuinely attractive: the ability to ship functional internal tools without writing a line of code and without going through a full procurement cycle that can take the better part of a year.
What councils are actually building
The use cases emerging across the UK are more practical than glamorous. Hertfordshire County Council has used Power Platform to automate parts of its adult social care referral workflow. Several London boroughs have built internal request-tracking tools on Airtable to manage housing repair queues. NHS trusts in the Midlands have used low-code environments to build staff rostering apps that connect directly to existing HR systems, cutting down on the manual reconciliation that previously ate enormous amounts of time each week.
A recurring pattern is that these projects tend to start with a single motivated individual, usually someone with a technical background who has found their way into a policy or operations role and is quietly frustrated with legacy processes. They prototype something, it works, word spreads, and suddenly the IT department is playing catch-up trying to govern a platform they did not formally sanction. That dynamic is both the strength and the weakness of the whole movement.
Why procurement is the real driver here
Public sector procurement in the UK is genuinely painful. Under the Public Contracts Regulations, anything above a certain contract value threshold triggers a full competitive tender process. For complex digital projects that threshold is a significant brake on speed. Low-code and no-code tools allow teams to sidestep this by operating within existing enterprise licence agreements. If a council already pays for Microsoft 365, Power Apps comes bundled in certain tiers. That means a team can build and deploy a workflow tool without raising a new purchase order, without engaging a supplier and, critically, without waiting for legal and procurement to sign off.
The Procurement Act 2023, which came into force in February 2024, made some improvements to how public bodies can engage with innovation, but the fundamental tension between speed and compliance remains. No-code platforms offer an escape valve that the rulebook has not yet properly addressed.
Where these projects quietly fail
This is the part that does not make it into the conference presentations. For every Hertfordshire success story, there are multiple projects that stall, sprawl or quietly get switched off after eighteen months. The failure modes are consistent enough to be worth naming explicitly.
The first is what you might call the single-person bus factor. When one person builds a tool and that person leaves, moves departments or goes on long-term sick leave, nobody else can maintain it. No-code does not mean zero knowledge requirement; it means the knowledge is tacit rather than documented. The council ends up with a tool they depend on and nobody who understands how it works.
The second failure mode is data governance. UK public sector bodies are subject to UK GDPR, administered by the ICO, and to sector-specific data-sharing rules. A well-meaning team building an internal case-management tool on a no-code platform can inadvertently create a data flow that breaches data-sharing agreements, stores personal information in a jurisdiction outside the approved list or skips mandatory data protection impact assessments. The ICO has been clear that the controller remains responsible regardless of the tools used. Ignorance of the platform’s data handling is not a defence.
The third is shadow IT at scale. Once one team successfully ships something on Power Apps, the appetite across a council or trust explodes. Without central oversight, you end up with dozens of disconnected tools that cannot talk to each other, duplicating data and creating a maintenance overhead that eventually outweighs the original saving. Several NHS trusts have described this pattern to me informally: initial enthusiasm, rapid proliferation, then a quiet rationalisation programme that feels embarrassingly similar to the procurement cycles they were trying to avoid.
The governance question nobody wants to answer
The Local Digital Declaration, signed by over 230 councils and supported by the Department for Science, Innovation and Technology, commits signatories to working in the open and building shared services where possible. The spirit of no-code adoption fits neatly within that commitment. The practice often does not. Tools get built in isolation, not shared, not documented and not contributed back to any common library.
What is missing is a structured framework for Local Digital communities to share no-code templates, governance standards and failure post-mortems. Some of the more forward-thinking digital teams inside DLUHC-adjacent bodies are starting to think about this, but progress is slow. The irony is that the tools to build that governance layer probably already exist inside a Power Platform licence somewhere.
What good looks like in 2026
The councils getting this right share a few characteristics. They have appointed a formal low-code lead or centre of excellence, even if that is just one person with a clear remit. They run a registry of tools built on no-code platforms so there is visibility of what exists. They do data protection impact assessments before deployment, not after. And they build with decommissioning in mind, keeping documentation as part of the build process rather than an afterthought.
Greater Manchester Combined Authority has been one of the more structured adopters, using low-code tooling as part of a broader digital transformation strategy rather than as a scrappy workaround. That distinction matters. Scrappy workarounds produce scrappy outcomes. Structured adoption produces genuine capability.
The no-code local government UK story is not a simple good-news piece about councils modernising against the odds. It is a more complicated story about what happens when genuinely useful technology meets an institutional environment that was not designed for it. The technology is not the limiting factor. The governance, the culture and the accountability structures are. Fixing those is harder than learning Power Apps, but it is the part that determines whether any of this sticks.
Frequently Asked Questions
What no-code platforms are UK councils using most?
Microsoft Power Platform (particularly Power Apps and Power Automate) is the most widely adopted, largely because many councils already hold Microsoft 365 licences that include it. Airtable and Salesforce Platform are also used, particularly in larger combined authorities and NHS trusts with existing Salesforce contracts.
Is it legal for councils to build their own tools using no-code platforms?
Yes, provided they comply with UK GDPR, conduct appropriate data protection impact assessments and operate within their existing procurement frameworks. Building within an existing enterprise licence avoids triggering new procurement thresholds, but data governance obligations still apply in full under ICO guidance.
How much money can no-code tools actually save a council?
Savings vary enormously by use case, but replacing a single bespoke-built workflow tool with a no-code equivalent can save anywhere from £20,000 to £150,000 in initial development costs. The ongoing saving depends heavily on whether the tool is properly maintained and documented, as poorly governed tools can generate hidden costs over time.
What are the biggest risks of no-code adoption in local government?
The main risks are: over-reliance on a single individual who built the tool, data governance failures (particularly around UK GDPR and data-sharing agreements), and uncontrolled proliferation of shadow IT that creates a fragmented, unmaintainable tool landscape. Governance frameworks and documentation standards are the most effective mitigations.
Leave a Reply