Multi-Site EV Charging Rollout Planning

Classify sites before designing any

Group sites by the characteristics that change the design: supply headroom, dwell pattern, parking type, public or restricted access, and civil complexity. Most estates resolve into three or four classes.

Designing one solution per class rather than one per site is the whole of the efficiency, and it only works if the classification is done first.

Build the standard design set

• A hardware specification per class, with a deliberately short variant list
• A standard electrical arrangement including protection and earthing approach
• A commissioning checklist that produces the same record everywhere
• A configuration baseline so units arrive on site consistent
• A signage, marking and accessibility standard

Sequence by supply, not by geography

The instinct is to roll out region by region. The better sequence starts with sites that need no supply work, because they deliver capacity while longer supply processes run elsewhere in parallel.

Supply lead time is the constraint that most often determines a rollout's shape, and it is knowable per site early.

Pilot one site per class

Before committing the estate, build one of each class properly and operate it long enough for problems to appear. Rollouts that skip this replicate a mistake across every site and discover it once it is expensive to correct.

Commissioning at scale

Units should arrive pre-provisioned with identity and configuration applied, so on-site work is installation and verification rather than setup. A commissioning process requiring a skilled engineer per unit does not scale, and it is where estate rollouts silently lose their schedule.

Plan for the estate you will have

Firmware update strategy, spares holding, fault escalation and the reporting that tells you which sites underperform. These are estate-level questions that cannot be answered site by site, and deferring them produces the fragmentation the rollout was meant to avoid.

Design for the change you have not thought of yet

A rollout is planned around installation. The cost that arrives later is change: the firmware, configuration or platform change that has to reach every unit after they are all in the ground and scattered across sites.

We learned the weight of this directly. Chargers we had put on a shared third-party platform needed a change that the platform could not make for one tenant without affecting the rest. The only route left was physical, sending people to each charger in turn. At one site that is an afternoon. Across a network it is a programme with a vehicle budget.

So before the first unit goes in the ground, two questions need answers. If either one involves a van, the rollout carries a cost that is not in the plan.

• How does a firmware release reach every charger across every site without anyone visiting?
• How does the fleet move to a different management platform remotely, if the contract or the platform changes?

How we work with you on this

A rollout runs on your programme team's schedule, with your contractors, in your sites. Our engineers work inside that rather than alongside it, and the useful contribution is usually in the first three sites where the process is still being worked out.

After the rollout the relationship continues under a monthly support arrangement, because the questions that matter arrive in the first operating year rather than during installation.