Why we built fleet management into Volta

The screenshot problem

Most EV fleet managers in the UK still operate the same way they did with petrol vans: they assume the driver will handle fuel (or, now, charging) and sort out the receipt later. Except with EV charging, there's no pump receipt. There's an app notification, a PDF email maybe, and a lot of guessing about what was actually spent.

When we launched Volta, we focused on the individual driver experience. Show them the real cost before they arrive. That was the win. But pretty quickly, we started hearing from people running fleets of five, ten, twenty vehicles. They didn't care much about journey planning. They cared about consolidation. They wanted to know: across all our vehicles, across all our drivers, across all our charging networks, what are we actually spending? And right now, they were doing it manually.

That's when I realised we weren't building for a future problem. We were watching a real one happen in real time.

Cost visibility breaks down on the spreadsheet

Here's what I learned talking to fleet managers: every charging network has a different billing system. Some charge per kWh, some per minute, some add parking fees on top. Idle fees vary wildly. Some networks don't publish their rates until you've actually charged. A driver in Birmingham paying 35p per kWh might have no idea their colleague in Liverpool is being charged 42p for the same service, because they're on different networks.

And the tax angle is something people rarely mention until you ask directly. Most fleet managers I spoke to couldn't tell me if they were paying VAT on their fast-charging, or whether their home charging was reclaimed differently. They were losing money without realising it.

We built fleet management into Volta to solve that. Consolidated billing across all 40+ networks your drivers use. Policy controls so you can set rules (maybe you only want fast-charging for journeys over 100 miles, to keep costs sensible). Cost-centre reporting so if you've got different business units, you can split the bill properly. Receipt history that actually exports, so your accountant doesn't ring you at 9 p.m. on a Tuesday asking where last month's charging data went.

The fleet features we didn't expect to build first

When we started designing the fleet section, we thought the core ask would be straightforward. Consolidate the costs, show the trends, done. But listening to a few hundred fleet managers and transport coordinators, we realised the features that mattered weren't the obvious ones.

One operator asked us: 'Can I control which chargers my drivers use?' Not all chargers are reliable, and some networks charge more than others. If you're running 200 vehicles, you want guardrails. Policy controls let you do that now. Another asked: 'Can I set cost alerts?' So if a driver's monthly charging suddenly spikes 30 percent above normal, someone in the office knows, and they can ask why. Arrive-to-check-in means the system knows when someone actually plugged in, not just when they said they would.

These aren't flashy features. They're just the things that make a fleet operation actually function without spreadsheets and phone calls.

Why fleet management matters for the wider EV transition

Fleet operators in the UK are the canary in the coal mine for EV adoption. They don't care about brand loyalty or range anxiety talking points. They care about total cost of ownership, predictability, and not getting caught out. If fleets can't work out their charging costs quickly and honestly, a lot of them are going to stick with diesel longer than they otherwise would.

So building fleet management wasn't just a business decision for us. It was a way to make the data on UK EV charging actually useful to the people who operate the most vehicles. Right now, a lot of them see EV fleets as a gamble because the cost picture is so murky. If Volta can make that picture clear, we're not just building a better app. We're helping the transition happen faster.

What we got wrong at first

When we shipped the first version of fleet management, we assumed fleet managers would want the same level of detail that our individual drivers loved. Route planning, accessible bay filters, that kind of thing. They didn't. They wanted the opposite. They wanted a dashboard. One number. Cost per vehicle per month. Cost per mile. Trend line. Done.

We learned to build for simplicity when you're managing multiple people instead of yourself. A driver needs granular control. A fleet manager needs clarity. Those are different products, even though they share the same data.