Ready for the shift, with nothing extra to do.
TOGL optimises charging in the background. The driver’s experience does not change, with one exception: smart charging is never the reason a vehicle misses its departure.
Readiness is the constraint, not the reward.
Every saving TOGL finds sits on top of the departure schedule, never instead of it. The optimiser is given the time each vehicle must leave and the charge it needs when it does, and it is only allowed to move charging around inside what is left.
That ordering matters more to a depot than any number on a business case. A charging strategy that saves money and strands a vehicle has cost the operator a shift, and no energy saving covers that.
The driver’s view
What the driver sees.
Driver-facing app and depot display, in active development, targeted for H1 2027.
Plug in and walk away
Connect the vehicle at the end of the shift. There is nothing to set, confirm or schedule. Charging starts when TOGL decides it should, not when the cable goes in.
State of charge and target departure
Current charge, the departure time the vehicle is being charged for, and whether it is on track to meet it.
Confirmed ready
A single unambiguous state before the shift starts: this vehicle has the charge it needs for the work it has been given.
Described as designed, not as shipped. This site does not show screenshots of an interface that is still being built.
Nothing new to learn
What the driver never has to do.
No scheduling decisions
Drivers do not choose charging windows, set timers, or decide which vehicles charge first. That is the optimisation problem TOGL exists to solve.
No tariff awareness
Nobody on the yard needs to know what a peak period is, when the cheap window opens, or what the site is paying per kWh tonight.
No manual overrides in normal operation
The override path exists and it works, but a normal week should never need it. If drivers are overriding routinely, the readiness rules are wrong and that is our problem to fix.
No new routine to remember
Charging is managed whether or not anyone opens an app. The driver-facing view reports what is happening; it is not a step in the process.
Exceptions
When the plan changes.
Optimised charging is only credible if it survives a normal week. Shifts move, vehicles come back early, and someone forgets the cable. This is what happens then.
A departure time moves earlier
Update the departure time and TOGL re-plans immediately. If the new time cannot be met within the optimised schedule, charging moves to full available rate and the depot manager is told what the vehicle will actually have at departure, rather than being left to find out at the gate.
A shift is brought forward at short notice
Any authorised user can force charging to start now, for one vehicle or for the whole depot, without waiting for a change to propagate from an office system. Cost optimisation stops; the site capacity limit still applies, because exceeding the connection is not a trade a dispatcher should be able to make by accident.
A vehicle needs an unplanned top-up
Plug in mid-shift and set the time it needs to leave again. Short dwell times simply mean less room to optimise, not a refused charge.
A vehicle is not plugged in at all
The most common cause of a vehicle missing its departure is nobody connecting the cable. TOGL flags it the same evening, while there is still time to act, instead of it becoming the morning problem.
The override path
There is always a way to charge a vehicle now, and it does not require TOGL to be working. Charging control sits on top of the depot’s own equipment rather than replacing it, so the manual path a depot already has stays available.
If TOGL cannot reach a vehicle or a charger, the vehicle is still charged in line with the duty cycle it has to meet. Optimisation is what degrades, never readiness, and never your uptime depending on ours.
Fallback behaviour is confirmed per site during integration and written into the deployment record.
Depot manager
One view of whether the depot is ready.
Drivers should not have to think about charging. Somebody does, and it is usually a duty manager with a yard to run. The depot view is built for that job: readiness at a glance, and exceptions early enough to act on.
Fleet-wide readiness in one view: which vehicles are connected, which are charging, and which are on track for their departure time.
Exceptions surfaced before they matter, not reported afterwards. A vehicle that will not make its departure is an alert tonight, not a gap in tomorrow morning.
Departure times and readiness rules editable per vehicle, per shift pattern, or across the whole depot.
A record of what was charged when and at what cost, so the energy saving is auditable rather than asserted.
| Vehicle | Charge | Departs | Status |
|---|---|---|---|
| VN-014Van | 82% | 06:00 | Ready |
| VN-027Van | 61% | 05:30 | On track |
| TR-003Truck | 44% | 07:00 | On track |
| VN-008Van | 23% | 05:00 | Not plugged in |
| TR-011Truck | 96% | 06:30 | Ready |
What the status labels mean
- Live
- In production with customers or pilot users today.
- In development
- Actively being built, with a target window.
- Planned
- On the roadmap, dependency-gated, no committed date.
See it against your own shift patterns.
The useful version of this conversation uses your departure times, your dwell windows, and your site capacity. Bring those and we will walk through what changes on the yard and what does not.
Running eHGVs or buses? Heavy transport has its own constraints.