Routes
A route's detail view shows the planned run on a map alongside its stops, their status and the delivery evidence the driver collected. When reality drifts from the plan — the route runs late, an electric vehicle won't make it on one charge, or a vehicle drops out mid-route — the system proposes a new plan on its own, and the dispatcher decides whether to accept it.
Who uses it
The dispatcher and fleet manager manage a route: re-optimizing it, assigning a driver and vehicle, and accepting or rejecting re-route proposals. The compliance specialist and executive have read-only visibility. The driver sees their own route and captures proof of delivery from the mobile app (see Driver workflows).
Key concepts
- ETA (Estimated Time of Arrival) — the predicted arrival time at the next stop, recalculated automatically from the vehicle's live position.
- Dynamic re-route — an automatically generated proposal to re-sequence a route's remaining, not-yet-served stops after a disruption is detected.
- Proof of delivery (POD) — the evidence captured at a stop: the recipient's signature, a photo, a note, and — for EU carriage — an e-CMR reference.
Map, stops and route status
A route moves through draft (not yet assigned), assigned and completed. The detail view pairs the map with an ordered stop list — each with its kind (a job, or a break/charging stop the optimizer inserted), the planned and actual arrival time, a live ETA, and whether proof of delivery has been captured yet. Infeasibility (capacity exceeded, a missed time window, HOS or EV charging) is spelled out above the list. A single click re-optimizes the route from scratch; jobs the new plan can't fit fall back into the pool.
Live ETAs and dynamic re-routes
As long as a route is assigned and its vehicle has a live telematics signal, each remaining stop's ETA is computed from the vehicle's current position rather than just the original plan. When a stop's ETA slips far enough past plan, the system proposes re-optimizing the remaining stops — accounting for the driver's live HOS clocks and the vehicle's state of charge, exactly as the original plan did. The same mechanism fires when an electric vehicle no longer has enough energy left to finish the remaining stops above the configured reserve, and when a vehicle drops out of service mid-route — flagged not roadworthy or taken out of service while running. Every proposal shows its reason and the diff between the current and proposed stop sequence; the dispatcher accepts it (the new plan takes over and the driver is re-notified of the assignment) or rejects it. At most one open proposal is kept per route and reason at a time.
Proof of delivery
The driver — or the dispatcher on their behalf — confirms delivery at a stop: the recipient's name, an e-signature (stored as a hash, never as the raw image), a photo from the delivery site, and a note; carriage under EU rules adds an electronic consignment note (e-CMR) reference. Capturing proof completes the stop and its job; the route completes once every job stop has been evidenced.
In the background
Every assigned route's ETAs are refreshed every five minutes from the latest telematics position, and right after the refresh the system checks whether any stop has slipped past a configured threshold — if so, it raises a re-route proposal. A separate job checks EV routes' remaining charge every ten minutes. A vehicle dropping out (losing roadworthiness or being taken out of service) triggers the check immediately, without waiting for the schedule.