Descartes GroundCloud shows an estimated time of arrival (ETA) for every pending stop on a route. Drivers use ETAs to see whether they will make a stop's time window, and managers use them to spot a driver who is running behind and step in before a window is missed.
This article explains where ETAs appear, what their colors mean, when GroundCloud recalculates them and how to tell when an ETA may be out of date or is being updated.
What an ETA Is
An ETA is the time GroundCloud expects the driver to arrive at a stop. It is calculated from the route's stop sequence, the travel time between stops and the time expected at each stop before it. ETAs are estimates: traffic, breaks and time spent at earlier stops can all move the actual arrival.
Note: ETAs are being rolled out to GroundCloud accounts in stages. If you don't see ETAs in the web or mobile application, it hasn't been turned on for your account yet.
Where You See ETAs
ETAs appear in the same places on the web and in the GroundCloud Mobile app, so drivers and managers see the same estimate for a stop.
Driver app stop cards: each pending stop card shows an ETA pill. Managers see the same stop cards in the manager view of the app.
Route Details page: ETAs appear on the stop cards in the sidebar, in the stop popup on the map and in the ETA column of the Stop List table.
P&D Time Commits page: each stop row shows its ETA, so you can review time-committed stops across your routes in one place.
ETA Colors
The color of the ETA tells you how the stop is tracking against its time window. A stop without a time window always shows a blue ETA.
Color |
Status |
What it means |
|---|---|---|
Blue |
On track |
The driver is expected to arrive more than 15 minutes before the time window closes, or the stop has no time window. |
Yellow |
At Risk |
The driver is expected to arrive within 15 minutes of the time window closing. |
Red |
Late |
The driver is expected to arrive when the time window closes or after it. |
Tip: A yellow ETA is your early warning. If a driver will not make a time-committed stop, call the driver, change the stop order or send another driver to cover the stop before the window closes.
After a Stop Is Worked
Once a stop is completed, its card no longer shows an ETA. It shows the time the stop was completed instead.
When ETAs Are Updated
GroundCloud calculates ETAs once a route has been sequenced, then recalculates them during the day as the route progresses. Each recalculation starts from the driver's most recently completed stop and updates the ETAs for the stops still ahead.
ETAs are recalculated when:
The route is resequenced, by the driver or by a manager.
The driver completes a stop much earlier or later than its ETA predicted.
When a Driver Works Out of Sequence
If a driver works stops in a different order than the planned sequence, for example to make a time window, ETAs keep updating. They are less accurate while the driver is away from the planned order.
Stale ETAs
When a route has had no driver app activity and no resequence for 15 minutes, every pending ETA on that route becomes stale. A driver on a break is the most common cause. A stale ETA keeps its last estimated time, but the pill changes so it no longer reads as a live estimate: it turns white with a dashed outline, and a tilde (~) appears before the time, for example ETA ~9:15 AM.
The outline keeps the color the ETA had when it was last calculated, so a stale ETA with a yellow outline was At Risk at that time. If the current time passes a stale ETA, GroundCloud shows ETA overdue in a gray dashed pill instead of a time that has already gone by.
Live ETA |
Stale ETA |
What it means |
|---|---|---|
Blue, ETA 9:15 AM |
Blue dashed outline, ETA ~9:15 AM |
The stop was on track when the ETA was last calculated. |
Yellow, ETA 9:52 AM |
Yellow dashed outline, ETA ~9:52 AM |
The stop was At Risk when the ETA was last calculated. |
Red, ETA 10:21 AM |
Red dashed outline, ETA ~10:21 AM |
The stop was Late when the ETA was last calculated. |
Not shown |
Gray dashed outline, ETA overdue |
The last estimated time has passed and the stop has not been worked yet. |
Stale ETAs recover on their own. As soon as the driver uses the app again or the route is resequenced, GroundCloud recalculates the ETAs and the pills return to normal. You don't need to do anything.
Note: Only pending stops show an ETA, so only pending stops can go stale. Completed times, attempted times, time windows and attempt codes are actual records, not estimates, and they don't change when a route's ETAs go stale.
Tip: If a route stays stale and its stops have time windows coming up, contact the driver to check on progress before relying on the last estimates.
Updating ETAs
When a route is resequenced, its existing ETAs belong to the old stop order and are known to be wrong. From the moment the new sequence is saved until the recalculated ETAs arrive, every pending stop on the route shows Updating ETA in place of a time. Time windows stay visible while ETAs update.
When No ETA Is Shown
A pending stop shows no ETA when GroundCloud cannot give a reliable estimate for it. This happens when:
The route has not been sequenced yet.
The ETAs for the route have not been calculated yet.
The stop does not have a valid map location.
The driver's progress has moved too far from the planned order for an estimate to be calculated.
Resequencing the route is the quickest way to get ETAs back on its stops.