Start with a complete contract baseline
Before making commercial decisions, councils need a clear and shared understanding of existing contracts. Many councils report that this information is not centrally available at the start of LGR.
Create a consolidated view of contracts across all participating councils. This baseline should include:
- supplier name
- service or system provided
- contract start and end dates
- notice periods and break clauses
- contract value and licence commitments
- procurement route used
- hosting arrangements
- integration dependencies
- data ownership and export rights
- data residency and hosting location, particularly for systems handling personal data
- assignment, novation and change-of-control terms, so suppliers cannot use the formation of the new authority to renegotiate without challenge
- the contract owner, decision-maker, business stakeholder and named contract manager
- the legacy council that owns the contract
- cyber assurance status, including:
- whether the supplier has completed a security questionnaire
- relevant assurance is held by the supplier
- key supply-chain risks
- incident notification and escalation arrangements
- software version, as councils using different versions of the same product can complicate convergence
- access method and network dependencies where users sit on different networks or infrastructure
This information helps councils identify:
- contracts approaching renewal
- systems critical for day one operations
- opportunities for convergence
- areas where supplier lock-in risk may exist
- the complexity of transitioning to a new solution
Where possible, build this view jointly across digital, procurement and finance teams.
Treat this as a forward-looking pipeline as well as a baseline. Understanding activity over the next 12, 18 and 24 months, and beyond vesting day, lets councils smooth demand, avoid contract clustering expiries and plan post-vesting capacity. Councils that have been through LGR describe this as one of the valuable commercial preparations you can make.
Consideration for disaggregation
Where a shared system will continue to support more than one new council, capture the impact on licensing terms, costs and access. Suppliers often respond by increasing per-council charges.
Identify contracts that need to be split or novated, and the order in which changes need to happen to avoid service interruption.
Pay particular attention to how security responsibilities, access controls and monitoring will be managed.
The playbook should really start with contracts. What we need to know first is when they start, when they end, what the notice periods are, who the suppliers are, how much we’re paying and what procurement route was used. Once you have that information you have a baseline for the conversation about where to start. Without that visibility, it’s very hard to make sensible decisions about consolidation.
Council Head of Digital and IT
UK Ministry of Housing, Communities and Local Government (MHCLG) 