> ## 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.

# Next planned at column (Drivers/Assets table)

> What the Next planned at column in Dispatch Planner v2 shows, when a driver's next trip or driver event starts, and why the column can be blank.

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

The **Next planned at** column shows when a driver's next commitment starts after their free time. The commitment can be a trip or a driver event such as Hometime. Use it with **Available at** to see the window you have to fit a trip into.

## At a glance

| | |
| - | - |
| **Table** | Drivers/Assets |
| **Shown by default** | Yes |
| **Sort** | Yes |
| **Filter** | Pick a date or date range |
| **Who sees it** | Everyone who can open Dispatch Planner v2 |
| **Edit in the grid** | No |

## How is the time worked out?

**Next planned at** is the start of whatever ends the driver's free stretch, the same stretch that **Available at** starts:

* For a trip, it is the time the driver arrived at the first stop, if that has been recorded. Otherwise it is the first stop's scheduled time: the appointment for an appointment stop, or the start of the window for a first-come-first-served stop.
* For a driver event, it is the event's start date.

**Next planned in** shows where that commitment begins and **Next planned event** shows what it is. All three always describe the same commitment.

The time is shown in 24-hour format, in the local time of the **Next planned in** location, followed by the time zone abbreviation. The year appears only when it is not the current year.

## Why is the column blank?

**The driver has nothing planned after their free time.** If no trip or driver event follows **Available at**, the driver is free with no end, and the column shows a dash. **Available for** and **Next planned in** are blank too.

**The driver has no availability.** When **Available at** shows a dash, so does **Next planned at**. That happens when the driver has no trips and no driver events on record, or belongs to an outside carrier.

## Why does the filter not match a time I can see?

**The date filter uses Coordinated Universal Time (UTC).** The cell shows the local time of the **Next planned in** location, but the filter compares calendar days in UTC. A commitment that starts in the evening in North America can fall on the next day for the filter. If a driver is missing from a single-day filter, widen it by a day.

**Drivers with a dash never match.** A date filter only returns drivers that have a next commitment.

## Related

* [Next planned in column](/en/help/loads-trips/dispatch-planner-columns/drivers/next-planned-in)
* [Next planned event column](/en/help/loads-trips/dispatch-planner-columns/drivers/next-planned-event)
* [Available at column](/en/help/loads-trips/dispatch-planner-columns/drivers/available-at)
* [Available for column](/en/help/loads-trips/dispatch-planner-columns/drivers/available-for)
* [Dispatch Planner](/en/help/loads-trips/dispatch-planner)