The commute you didn't budget for: how Volta changes daily charging
Last October, a driver messaged us. She'd spent £4.80 on a fifteen-minute charge at a motorway services station. Fifteen minutes. The charging itself cost £2.10. The idle fee and parking took the rest. She'd checked the network operator's app first, which showed only the per-kWh rate. That's when she called.
Why network apps don't tell the full story
Most UK EV drivers own a phone full of apps. There's the Ionity app, the BP Pulse app, the Tesla app (if you're lucky enough), and three or four others depending on where you travel. Each shows a different number for what charging costs. One shows only electricity. Another doesn't include parking. A third buries the idle fee in the terms and conditions.
That's the problem we set out to solve. We unified 40+ of those networks into one map. But more importantly, we made the total cost visible before you arrive. Charging, parking, idle fees, taxes - the lot. You see £4.80 before you commit, not after.
For daily commuters, this changes the calculus. Some chargers near your workplace might look cheap at 35p per kWh but cost twice as much once you factor in standing charges. Others look pricey until you realise parking is free and the idle window is generous. You don't find that out by visiting five apps.
The journey planning piece nobody talks about
A commute isn't a single charge. It's a route. If you're driving from Leeds to London twice a month, you need to know where you'll stop and what it'll cost before you leave your driveway. But planning a 200-mile journey with forty-plus networks to choose from is exhausting.
That's why Volta includes journey planning with route-level charging visibility. You plot your destination. The app shows you viable stops along the way, ranked by total cost and location logic. For a daily commuter working thirty miles from home, this is straightforward - your closest charger, sorted by total outlay. For someone doing longer runs, it's the difference between planning and guessing.
We found that drivers using the journey planner made different decisions about which chargers to use. They'd pick a slightly pricier stop that broke up the drive better, or a cheaper one further ahead if time wasn't tight. That flexibility only works if you can see the full picture in advance.
The arrive-to-charge moment
You've found a charger. You've driven to the car park. Now what? Too many drivers arrive at a pin on a map only to find the bay occupied, the network app won't connect, or the price they saw twenty minutes ago has changed (or wasn't actually available). We built an arrive-to-charge check-in feature that confirms the charger is live, the bay is likely available, and the price you're about to lock in matches what was shown.
It sounds simple. It's not. It required us to sit with drivers and understand the moment when confidence turns to dread. That's the moment between pulling into a car park and plugging in. A one-minute check that says "yes, this charger works" is worth more than any notification later.
For commuters hitting the same chargers on the same days of the week, this becomes muscle memory. You arrive, check-in, plug in, and go about your day. The app handles the proof. Your expense history, all your receipts, all the running costs for the month - that feeds into your company reports or your own spreadsheet.
Accessibility and the detail that sticks
We added accessibility filters because disabled drivers told us they had to scout chargers twice: once to find a location near their route, again to confirm there was an accessible bay. Some networks bury that information or don't update it. We pull it out as a filter. You can search for chargers with accessible bays, same as you'd search by network or cost.
This isn't a feature that makes headlines. But for the drivers who need it, it's the feature that makes daily commuting possible. A driver with mobility needs shouldn't have to phone ahead or arrive and discover the single accessible bay is broken. The app handles that visibility upfront.
What commuters do with the data they gather
Here's what we didn't expect: commuters wanted to export their charging history. Not as a screenshot. As a CSV or PDF they could drop into an expense claim or fuel card system. Some were claiming back mileage. Others were tracking costs for budgeting. One user was testing whether home-charging overnight plus one public charge per week beat daily public charging.
So we built receipt history and expense export. Now you can pull a month of charging costs, totalled by charger, by network, or by payment method. It becomes a record. Not just of where you charged, but of how much the commute actually costs. That's the number you can take to your employer or your accountant.
For commuters doing this every working day, this data is gold. You'll see which chargers you use most, which cost most, and which are most reliable. You can make decisions about where to live, which office to use, or whether a slightly further charger makes financial sense if it's consistently cheaper.
The map is just the start
We often describe Volta as a map. That's not wrong. But the map is where the story begins, not where it ends. Behind that map are 40+ network feeds updating in real time, cost calculations running every few seconds, and user data showing us which chargers are used most, which are broken most often, and which disappear without warning.
For a daily commuter, the app becomes part of your commute planning. You check it before you leave work, the same way you check the weather or the traffic. Over a few weeks, you know which chargers you trust, which ones have shade or shelter, and which ones have power sockets in the waiting area. That's the behaviour the app supports. Not the occasional long trip. The daily rhythm.
If you're charging the same car at the same chargers three, four, or five times a week, how much do you actually know about what you're paying? And if you don't know, how would you?