Route fields & settings reference

This is a field-by-field reference for the Routes tab: the columns on the table, the fields a route carries, and the statuses you'll see used both loosely and precisely. It doesn't cover how to build, edit, or dispatch a route — for that, see How routes work and the task articles linked at the bottom.

The Routes tab columns

The Routes table lists every route your organization has, one row per route. These are the columns you'll see across it.

Column	What it tells you
Color	A swatch used to tell routes apart at a glance — no meaning beyond that.
External ID	Your own reference ID for the route, if one was set.
Name	The route's name.
Pickup / drop-off location & time	Where the route's stops start and end, and the times attached to them.
Pickup zone	The zone the route's pickups fall in.
Planned ETA	The estimated time the route is expected to complete.
Value	The combined declared value of everything on the route.
Route details	A summary of what's on the route, including item count.
Provider	Who's carrying the route — an outside provider or your own fleet. Reads Select provider until one is chosen.
Driver	The driver assigned to the route, for own-fleet routes. Reads Carrier managed when an outside provider is carrying the route.
Vehicle	The vehicle assigned to the route, for own-fleet routes. Reads Carrier managed when an outside provider is carrying the route. This column may not appear for every organization.
Shift	The shift the route is scheduled against, if your organization uses shifts.
Tags	Labels attached to the route for filtering and reporting.
Actions	The row-level menu — open, dispatch, archive, and the rest.
ID	Nash's identifier for the route.

Provider, Driver, and Vehicle are separate columns, and each one is editable in place until the route is dispatched — you don't have to open the route to change who runs it:

• Select the Provider cell to choose or change the provider or driver group carrying the route.
• On an own-fleet route, select the Driver cell to search for and assign a driver — the list is narrowed to the route's driver group and vehicle — or choose Clear driver assignment to take the current driver off. If the route has no provider yet, selecting the Driver cell asks you to choose one first.
• On an own-fleet route, select the Vehicle cell to pick a vehicle.

When an outside provider is carrying the route, its driver and vehicle are the provider's to assign, so those two cells are read-only. The same three controls sit on each route's card in the map view, and the card's three-dot menu adds Reassign Provider and Reassign driver. See Assign a route for how assignment works, and work with orders and routes on the map for the map view.

Route fields

Open a route and its drawer carries a smaller, deeper set of fields than the table row does:

Field	What it does
Name / External ID	The route's identity — the same name and external ID as the table columns, editable from the drawer.
Stops and their order	The ordered list of pickups, drop-offs, returns, and any waypoints the route is made of — see Edit a route for reordering them.
Travel metrics	The route's total distance and duration, computed from its current stop sequence.
Assigned vehicle & driver, or provider/contract	Who's set to run the route — your own fleet's vehicle and driver, or the outside provider and contract carrying it.
Optimization provider	Which engine, if any, produced the route's stop sequence.
Tags	The same tags shown in the table column, editable from the drawer.
Timestamps	When the route was created and last updated.

Route status

A route's status describes where it sits in its life cycle, but the Routes tab itself only really shows you one line of that: not dispatched versus dispatched. Everything you do from the tab — building, editing, assigning — happens on the not-dispatched side; dispatching is the one action that crosses it.

Underneath that binary, a fuller set of statuses exists and does apply to every route — it just isn't something you drive from the classic Routes tab:

Status	Where it applies
Created	The route exists as a draft — this is "not dispatched" from the tab's point of view.
Assigned	The route has been dispatched and handed to a driver or provider.
Started	The driver has begun the route.
In progress	The driver is actively working stops.
Completed	Every stop on the route has been finished.

A route can also end in Failed or Canceled instead of Completed, if the run doesn't finish cleanly.

Assigned, Started, In progress, and the two end states are driven by real signal from the field — a route only advances once a driver genuinely makes progress at a stop. That progress surfaces on the driver app and the live delivery view that follows the job a dispatched route produces, not as a status you'll watch tick over on the Routes tab. Expect the tab to be where you build a route and send it out, and expect its field-by-field progress to live on the surfaces built to show it.

Stop status and stop types

Stop types describe what a stop is for:

Stop type	What it is
Pickup	Picking something up.
Drop-off	Delivering something.
Return	Bringing something back.
Break, route start, route end	Waypoints the route needs but no customer sees — a scheduled driver break, or the fixed points a route starts and ends at.

Stop status is the field-side counterpart to route status — the progress of one stop, rather than the whole route, again driven by the driver working it rather than anything set from the Routes tab:

Status	Meaning
Pending	Not yet started.
Enroute	The driver is traveling to the stop.
Arrived	The driver has arrived at the stop.
In progress	The driver is actively working the stop.
Completed	The stop is finished.

A stop can also end as Canceled, Failed, or Skipped instead of Completed.

What locks after dispatch

Once a route is dispatched, its structural actions lock: Calculate Timing, Split, Resequence, and Dispatch itself all disable, and the route stops accepting new orders. This is enforced on the server, not just hidden in the interface — there's no workaround for editing a dispatched route's structure. See Edit a route for what you can still do before that point, and How routes work for why the lock exists.

Availability

The Routes tab depends on whether your organization has routes enabled. Availability varies by org — if you don't see a Routes tab, reach out to Nash.

A newer routes surface exists elsewhere

A newer Plan/Execute routes experience is rolling out as a separate, product-gated surface with its own controls for moving and resequencing stops. It isn't covered in this reference, and the only part of it documented in this section is Add notes to a route — if your organization is on that surface, some of what's described here may look different.

Related

• How routes work — the object model, the editable-then-locked lifecycle, and how optimization builds a route.
• Edit a route — reshaping a route's stops and assignment before it's dispatched.
• Dispatch a route — sending a route out, one at a time or in bulk.