When two or more drivers are active on the same route:
Each driver’s movement is tracked separately
The route path will stay the same color, but will now display a multi-driver icon when more than one driver is active
Hovering over the driver path will show:
Route name
Driver login (ensuring you can see who is who)
Driver speed at that moment
Timestamp for the data point
This makes multi-driver visibility significantly clearer, without the overlapping “garbled” lines seen in older versions.
Important: Drivers Must Use Their Own Login
To maintain accurate visibility:
Each driver must log in with their own unique login
Shared logins will not display separate driver paths
Proper logins ensure the system can differentiate and identify each driver in real time
How the New Driver Path Pop-Ups Work
In Route Manager, move your mouse along the displayed driver path. You’ll now see a pop-up window showing:
Which driver recorded that point
How fast they were moving
When the movement occurred
As you hover across the path, the information updates point-by-point, giving the office a live-style view of speed changes and driver activity throughout the route.
What’s Tracked (and What Isn’t)
This feature stamps the driver path with login, speed, and timestamp data, and this information remains visible in Route Manager moving forward
Reporting on this data is not yet available
Driver path details cannot be exported or queried through reports at this time (not to be confused by the Driver Sequence Report which is available)
All driver path details remain viewable only on the map
If two drivers are on one route (Driver A needs help and Driver B is jumping in) can Driver B see the stops already completed or does Driver A have to sync the data?
Depending on when Driver B jumps in and downloads the route. Also, it depends on if Driver A has internet connectivity and has uploaded all the stop’s data (completed states, etc).
If the following happens:
Driver A finished some stops and has been fully sync with the the server
To know if app is fully sync, the web app should be able to see all the stops info and exceptions (if there’s any)
Driver B log in and download the route
At this point, then Driver B should be able to see the status of the stops that Driver A did. However, if #1 didn’t complete, then Driver B would not be able to see the data