> ## Documentation Index
> Fetch the complete documentation index at: https://docs.alvys.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ETA to Next Stop column (Drivers/Assets table)

> What the ETA to Next Stop column in Dispatch Planner v2 shows for a driver, where the estimate comes from, and why it can be blank or out of date.

Part of the [Dispatch Planner column reference](/en/help/loads-trips/dispatch-planner-columns).

The **ETA to Next Stop** column shows roughly how long a driver needs to reach the next stop on their trip, such as **3 hours, 20 minutes**. Use it to see which drivers are close to finishing a stop without opening each trip.

## At a glance

| | |
| - | - |
| **Table** | Drivers/Assets |
| **Shown by default** | Yes |
| **Sort** | Yes |
| **Filter** | Enter a duration or a range, for example `2d 3h 30m` |
| **Who sees it** | Everyone who can open Dispatch Planner v2 |
| **Edit in the grid** | No |

## Where does the estimate come from?

The planner checks two sources in order and shows the first one that has a value:

1. **The ETA on the driver's active trip.** If Driver 1 has a **Dispatched** or **In Transit** trip with a stop ETA that Alvys calculated for it, the column counts down to that ETA. It uses the first pickup or delivery stop on the trip that is not completed yet. Once that ETA has passed, this source is skipped.
2. **The estimate sent with the driver's last ping.** When a location report arrives, Alvys estimates the driving time from that position to the next stop of the trip the reporting driver, truck, or trailer was on. This is the same report shown in the **Last Ping** column.

The value is shown in its two largest units, such as **1 day, 2 hours** or **45 minutes**.

## Why is the column blank or out of date?

**The driver has no estimate.** The driver has no active trip with a calculated stop ETA, and their last ping did not include an estimate. For example, the reporting device was not on a trip when it last reported.

**The ETA has passed.** A stop ETA in the past is not shown. The column falls back to the estimate from the last ping, or shows a dash.

**An estimate from the last ping does not count down.** It is the driving time worked out when that ping arrived. It only changes when a new ping arrives, and there is no age limit, so it can be out of date if the driver's devices have stopped reporting.

**Only Driver 1 counts.** For a two-driver team, the column follows Driver 1's trip and pings.

## Is it the same as the Trips table column?

Not always. The Trips table shows the ETA for each trip from that trip's own drivers, truck, and trailer, and only uses pings from the last seven days. The Drivers/Assets table follows Driver 1, uses pings of any age, and can fall back to the last ping when the trip's own ETA has passed. The two can show different values for the same trip.

## Related

* [Miles to Next Stop column](/en/help/loads-trips/dispatch-planner-columns/drivers/miles-to-next-stop)
* [Last Ping column](/en/help/loads-trips/dispatch-planner-columns/drivers/last-ping)
* [ETA to Next Stop column (Trips table)](/en/help/loads-trips/dispatch-planner-columns/trips/eta-to-next-stop)
* [Dispatch Planner](/en/help/loads-trips/dispatch-planner)
* [Mileage to Next Stop](/en/help/loads-trips/mileage-to-next-stop)