LGR has moved beyond theory. The real test is now delivery
Across England, Local Government Reorganisation (LGR) programmes have, to date, been dominated by business case development.
Councils have invested significant time in building the evidence base: financial models, service demand analysis, and a clearer picture of enabling services such as IT, finance, contracts, and assets.
That work has been necessary and valuable. But recent “minded-to” decisions in Devolution Priority Programme (DPP) areas signal something important:
The policy direction is now clearer. And the emphasis is shifting.
The next phase is not about whether change happens.
It is about how it is delivered.
Transition becomes the critical path
For most areas, the implications are now unavoidable.
Reorganisation will require a combination of:
disaggregation (breaking apart existing county/district arrangements)
aggregation (bringing services together into new unitary structures)
This places transition — the safe, legal and effective movement of services, people, assets and responsibilities — at the heart of delivery.
And this is where the real complexity lies.
Transition is not a single programme activity. It is the sum of hundreds of service-level changes, each with operational, financial, workforce and political dimensions.
It is where strategy meets reality.
The risk: fragmented planning in a system context
As direction becomes clearer, service areas quite rightly begin to plan.
Adult social care considers operating models
Waste teams think about routes and contracts
Planning services consider policy alignment
The instinct is correct, but the risk is significant.
Without coordination, LGR programmes can quickly drift into fragmented, service-by-service planning, where:
assumptions diverge
dependencies are missed
different parts of the system move at different speeds
transition risk increases
In a system made up of sovereign councils, this is not just likely — it is almost inevitable unless actively managed.
Enabling services: necessary, but not sufficient
Enabling services — particularly IT, finance, HR, contracts, and assets — remain critical. They provide the backbone for transition:
baseline data and system architecture
financial frameworks and cost assumptions
contract visibility and constraints
workforce mapping and TUPE implications
However, there is a risk in over-rotating toward these areas.
They inform transition.
But they do not define it.
Real transition planning must be grounded in services: how they operate, how they interact with residents, and how they will function on day one and beyond.
A more deliberate approach to service engagement
The answer is not to slow service engagement; it is to structure it properly.
The most effective approaches tend to include:
1. Early, but coordinated, service mobilisation
Service areas begin planning early, but within a clear programme-led framework.
2. Clear principles and guardrails
For example:
“adopt not adapt” for technology in early phases
a focus on “safe and legal” for vesting day
agreed assumptions on operating model convergence vs. divergence
clarity on decision-making authority
3. Defined transition pathways
Not all services will transition in the same way, and pathways should align with broader disaggregation approaches across the system.
Some services may:
lift and shift into new structures
consolidate quickly into a single model
operate shared arrangements — which may be interim, but in some cases could persist longer-term given financial and organisational constraints
4. Strong central coordination (HPMO / Programme function)
To:
manage dependencies
ensure consistency of assumptions
sequence activity realistically
maintain a single version of the truth
More than re-badging
There is a persistent myth in LGR that transition is largely administrative — a simple “re-badging” exercise.
In practice, that view underestimates both the risk and the opportunity.
Poorly managed transition can lead to:
service disruption
financial leakage
workforce uncertainty
loss of public confidence
Done well, however, transition becomes a platform for:
service standardisation and improvement
digital acceleration
stronger system working
earlier realisation of benefits
A shift in mindset
Business case development is analytical and iterative.
Transition is delivery-focused, time-bound, and unforgiving.
It requires:
clearer decisions
tighter governance
greater tolerance for imperfection in favour of progress
a willingness to operate beyond traditional organisational boundaries, leaving institutional perspectives at the door in favour of system-wide outcomes
The systems that succeed will be those that recognise this shift early and organise themselves accordingly.
In short: the business case may have set the direction, but transition will determine success.
The main game has changed. The question now is who is ready to play it well.