System integration is often presented as the silver bullet to joined-up digital services in local government.
Connect the website to the CRM, link forms to back-office systems, share data across services etc etc. In theory, integration should reduce duplication, improve efficiency, and create smoother experiences for residents.
In practice, many councils discover that technical integration alone does not deliver the outcomes they expect. Systems connect, data flows, and yet services remain fragmented, brittle, and difficult to change.
But the reason is rarely technical capability - it is almost always governance. That’s because, without clear ownership, standards, operating models and integrations become another source of risk and complexity rather than a foundation for joined-up services.
The pressure to integrate systems is understandable. Residents expect services to just know who they are and what they have already provided. Staff want to avoid re-keying information across multiple systems. Digital teams are asked to reduce manual effort while improving accuracy and speed.
Integration promises to solve all of this. By connecting systems directly, councils hope to remove friction and improve outcomes without redesigning services end-to-end.
This expectation places a great deal of weight on integration as a solution. When it fails to deliver, the disappointment is often significant.
Yes, council integrations can succeed on a technical level. Data moves from one system to another. Forms submit successfully. Records are created or updated as expected. On paper, the integration works. But problems can start to emerge over time.
This happens especially when the ownership of the integration is unclear. Changes in one system are made without considering downstream effects. Exceptions and edge cases accumulate and when something breaks, it is not obvious who is responsible for fixing it.
Gradually, integrations become fragile and teams start to treat them with caution. Changes slow down and the very connections intended to enable joined-up services become constraints.
Integration is often framed as a data problem. In reality, it is a decision-making problem.
For services to work together, councils need shared answers to questions such as:
Without agreed answers, integrations encode assumptions that are rarely documented or revisited. Over time, those assumptions drift away from organisational reality.
Technical connections remain in place, but the confidence in them starts to erode. This is when governance becomes so important.
Governance is sometimes seen as slowing delivery. But in the context of integration, it does the opposite.
Clear governance allows councils to integrate systems safely because it defines responsibility and limits ambiguity. It establishes:
This does not require heavy bureaucracy. It requires clarity that survives staff changes, supplier transitions, and service redesign.
Without governance, integrations depend on institutional memory. When that fades, risk increases.
Many councils have built integrations incrementally, responding to immediate needs. Over time, this creates a dense web of point-to-point connections. Each one is understandable in isolation but together it can make it harder to change.
When governance is missing, this integration estate becomes opaque. Digital teams hesitate to touch it. Service improvements are delayed because no one is confident about the impact of change.
The cost is not just technical. It is organisational.
Councils often invest in new platforms with better integration capabilities. APIs, middleware, and cloud services make connections easier than ever. But better tools do not compensate for that missing governance.
Without shared standards and ownership, modern platforms can accelerate the creation of unmanaged integrations just as easily as legacy ones. The result is faster accumulation of risk, not better services.
Platforms need to be paired with governance models that define how integration is approached, reviewed, and maintained across the organisation.
When integrations fail, the impact is rarely contained. Digital teams absorb the pressure of incident response, manual fixes, and emergency workarounds. Service teams lose confidence in systems they rely on. Residents experience delays, errors, or repeated requests for information.
Over time, this positions integration as something to be feared rather than enabled. Digital teams become cautious. Innovation slows. Joined-up services remain an aspiration rather than a reality.
This is not a failure of skill or effort. It is the predictable outcome of building connections without the structures needed to sustain them.
Effective integration governance does not mean centralising every decision.
It means agreeing a small number of principles that guide behaviour, such as:
These principles reduce risk while allowing teams to move faster with confidence.
Councils often recognise governance gaps through experience rather than audits.
Common warning signs include:
These are signals that technical integration has outpaced organisational readiness.
For councils, integration remains essential. Joined-up services are not optional. Residents expect them, and organisational efficiency depends on them.
But integration alone does not create joined-up services - governance does.
When councils invest in shared standards, clear ownership, and sustainable operating models, integrations become assets rather than liabilities. They support change instead of resisting it.
The most effective digital leaders recognise that integration is not just a technical exercise. It is an organisational commitment to working differently.
At Axistwelve, we support UK councils to design integration approaches that combine technical capability with practical governance. The result is joined-up services that are resilient, understandable, and able to evolve over time. If you want to see how we can help, get in touch for a quick chat.