The cheapest break is one the vehicle was already going to take

A mandated break costs a fixed number of minutes, set by law or by contract, and that part isn't negotiable. What is negotiable, without anyone deciding it on purpose, is where those minutes land. Planners, fleet managers, and anyone running EV routes all run into the same gap eventually, a break that's fully compliant and fully wasted, because nobody planned where it should happen.

Compliance says the break has to happen. It says nothing about whether it costs you anything.

The same minutes, priced two different ways

A break inserted into a gap the vehicle already had, waiting to charge, staged at a dock, on the way to a stop that was coming regardless, costs nothing beyond the required minutes. A break inserted as a standalone stop costs those minutes plus the drive there and the drive back. The same rule gets satisfied either way. The bill doesn't look the same.

An unplanned break doesn't wait for a good moment

Break thresholds are tied to hours driven, not hours of the day, so the break lands whenever the threshold hits, whether or not that's a convenient moment. Take a stop promised between 11am and noon. If the driver's mandatory break threshold hits at 11, the break doesn't wait for the window to close, it eats the window from the front. That single stop slips, and because the rest of the route was sequenced around it arriving on time, every stop behind it inherits the same delay. The requirement was met. The commitment wasn't.

Compliance is whatever was negotiated, not a generic minimum

Break rules also stack. A route long enough might owe a driver fifteen minutes after four hours behind the wheel, then another ten after three more hours, cumulative, not one flat threshold. Union and contract terms add their own layer on top, specific durations, specific triggers, and specific exceptions, such as skipping a break on the final leg back to the depot when there's nothing left on the route to protect. Matching the general legal minimum isn't the same as matching what was negotiated, and the gap between the two is where a planner ends up patching by hand what should have been configured once.

EV charging is the clearest version of this. A charging stop already idles the vehicle for a set stretch, and a driver's mandatory break idles the driver. Planned together, those two idle periods overlap and only one of them costs anything. Planned apart, they stack, and the operation pays for both in full.

Picture the same break requirement handled two ways on an EV route.

• Route A. The vehicle needs 25 minutes of charging mid-shift regardless of any break rule. The driver's required 15-minute break is planned to land inside that same stop. Total dead time added beyond the charging the vehicle needed anyway, zero.
• Route B. Same vehicle, same break rule, planned as two separate events. Charging happens first. The break gets scheduled 40 minutes later, whenever the drive-time threshold is next hit.
• Both routes meet the same two requirements, a charge and a break. One pays for them once. The other pays for them twice.

Among operations juggling multiple constraints inside one shift, charging windows, delivery commitments, driver hours, break placement is rarely optimized on its own. It tends to get treated as a rule to satisfy after everything else in the route is set, which is exactly how the same required minutes end up costing different amounts on different days.

The takeaway

Check whether break planning and charging-stop planning run as one decision in your system or two. If they're two, the same required minutes are probably getting paid for twice.