Local authorities have quietly become one of the most important forces in UK charging: on-street schemes for residents without driveways, car park networks, fleet depots for their own vehicles — often funded through schemes like LEVI and delivered under intense public scrutiny.
The uncomfortable part: a charging network is an operated service, and most councils are procuring one for the first time. The difference between a scheme residents rely on and one that becomes a local newspaper story is rarely the chargers — it's the operating model wrapped around them. Here's what we'd want every council evaluation team to know.
Decide what you're buying: chargers, or a service?
The single most consequential choice in the procurement isn't a product — it's the operating model:
- Concession models hand delivery and operation to a CPO, minimising council effort and risk — at the cost of control over tariffs, coverage decisions and data, and with contract lengths that outlive several political cycles.
- Own-and-operate keeps control and revenue with the council, but makes the council responsible for the operational reality this article is about.
- Hybrids — council-owned assets, contracted operations — are increasingly common and shift the critical skill from operating to specifying and verifying.
There's no universally right answer. But every model shares one need: the council must be able to see the truth independently. Whoever operates, insist on direct access to performance data — dashboards and API access named in the contract, not quarterly PDFs from the supplier being measured. You cannot verify a 99% claim through the claimant.
Write reliability in, with its measurement method
Public chargers 50 kW and above carry a legal 99% reliability requirement; residents hold councils to a stricter standard — the charger outside their house, working tonight.
The procurement mistake is specifying the number without the method. "99% uptime" invites creative accounting; what stands up is a defined measurement — connector-level, outcome-based, counting a charger that can't actually deliver a charge as down — plus repair-time commitments (MTTR, not just availability) and evidence exports the council can pull itself. Put the definitions in the contract schedule and the verification in your own hands.
On-street is its own discipline
Residential on-street charging — the core of most LEVI-funded schemes — behaves differently from destination or rapid hubs, and the software has to reflect it:
- Overnight is the duty cycle. Utilisation concentrates in long evening-to-morning sessions; success is a resident's car ready by morning, which makes it cousin to depot readiness charging, not forecourt retail.
- Grid connections are shared and modest. Lamppost and pavement schemes live inside tight local supplies — load management isn't an optimisation, it's what makes the scheme installable at all.
- The fault experience is personal. A broken hub charger inconveniences a driver; a broken on-street charger strands a specific resident who reported it last Tuesday. Fault detection, honest status on public maps, and visible repair follow-through carry disproportionate reputational weight.
- Scale arrives in waves. Schemes grow ward by ward, funding round by funding round, often across multiple hardware suppliers — the mixed-fleet, phased-commissioning story from day one.
Plan for the decade, not the launch
Charging contracts age in ways launch-day procurement rarely considers:
- Suppliers change. Operators consolidate, platforms get replaced, some vendors exit. The council's protection is portability: open-protocol hardware (OCPP), council access to data, and a contractually clean exit — because switching platforms is very doable if the contract didn't sign the possibility away.
- Multiple schemes accumulate. The car park pilot, the on-street rollout, the leisure centre rapids, the fleet depot — procured separately, they become operational silos with separate logins and irreconcilable reports. A multi-tenant platform can hold them as one estate with delegated control — worth specifying before the second scheme exists, not after the fourth.
- Residents' expectations rise. Contactless today; roaming apps, clearer pricing and accessibility standards tomorrow. Favour suppliers with a visible, dated record of shipping improvements — the roadmap slide is free, the release history is evidence.
A short list to take into the evaluation room
- Whichever operating model wins: independent data access for the council, in the contract.
- Reliability with its measurement method defined — and repair times alongside availability.
- Open protocols and a written exit story for both data and hardware.
- On-street specifics: overnight scheduling, shared-supply load management, fault-to-fix visibility residents can trust.
- One platform view across all schemes present and future.
- Evidence over adjectives throughout: status pages, published performance, release histories, referenced deployments.
Councils that procure this way don't just avoid the newspaper story — they build the thing LEVI money was actually for: charging that residents without driveways can organise their lives around.
AmpNexus works with public-sector operators on exactly these requirements — evidence-backed reliability, open protocols and multi-scheme operation on one platform. Talk to us or start with the 12 vendor questions.