How Execute works

Execute is a live queue of your dispatched routes. Each row is one route that has already gone out — to an outside provider or to your own fleet — and the queue keeps that row current as the field reports progress back to Nash. Where the Routes tab is the place you build a route and send it, Execute is the place you follow it and change it while it runs. Everything below — which routes appear, what their statuses mean, why some edits are locked — follows from that one idea: Execute shows routes after dispatch.

Note

This is a beta feature. Reach out to Nash if you'd like early access.

The sidebar item reads Execute; the page itself is headed Operations. They're the same page.

The queue: which routes appear

A route appears in Execute when three things are true:

• It has been dispatched. Routes that are still drafts on the Routes tab don't appear here. Dispatching is what moves a route into the queue.
• It isn't archived or deleted. Archived routes don't appear in the queue.
• It falls inside the date range you've picked. The range defaults to today.

The date range is matched against the orders on the route, not the route itself. Each order is dated by the first time it carries — its pickup window start, then its pickup window end, then its drop-off window start, then its drop-off window end — or, if it has no window at all, the time it was created. A route is in range when any of its orders is. In practice, a route shows on the day its work is scheduled, which is usually the day you want to watch it. Widen the range to look back at earlier routes or ahead at routes dispatched in advance.

Within that range, the queue shows routes in every status: ones that are just assigned, ones in progress, and ones that already completed, failed, or were canceled. Finished routes stay in the queue for the rest of the range, so the day's history is in the same place as the day's live work. Use the Route Status filter when you only want the routes that are still running.

Order of the queue. When exception handling is on for your organization, the queue sorts routes with the most severe open exceptions first, so the routes that need you rise to the top. Without exception handling, the newest routes come first.

Keeping current. The queue refreshes itself every 30 seconds, along with the counts in the page header. Use Refresh in the toolbar to pull the latest state right away.

Three ways to look at it. The same queue renders as a Table (the default, and always available), a Map of routes and courier positions (up to 1,000 routes), or a Timeline of each route's day (up to 200 routes). The map and timeline views are on by default but can be turned off for an organization. Whatever view you're in, your date range, search, and filters carry across, and they're kept in the page's link — so a link you copy opens the same slice of the queue for a teammate. See Find routes in Execute and Save and share Execute views.

Route and stop statuses

The Status column speaks one of two vocabularies, depending on the shape of the route.

Multi-stop routes show route status. A route with more than one pickup or more than one drop-off shows where the whole route is:

Status	Meaning
Created	The route has been dispatched but isn't assigned to a driver or provider yet.
Assigned	A driver or provider has the route and hasn't started it.
In Progress	The driver has started the route and is working its stops.
Completed	Every stop on the route is finished.
Failed	The route ended without completing.
Cancelled	The route was canceled.

Point-to-point routes show stop status. A route with exactly one pickup and one drop-off is really a single delivery, so the Status column shows where that delivery is instead — Pending, then Pickup Enroute, Pickup Arrived, Pickup In Progress, then Dropoff Enroute, Dropoff Arrived, Dropoff In Progress, and finally Completed, Failed, or Canceled. If the delivery is being returned, you'll see Return Enroute, Return Arrived, and Return In Progress.

The route panel's header always shows the route status, whatever the route's shape. So a point-to-point route can read Dropoff Enroute in the queue and In Progress in its panel — both are correct, at different levels.

None of these statuses are set from Execute. They move as the driver app, or the provider carrying the route, reports progress to Nash. The Stops column and the panel's Route progress bar count stops as they complete, so you can see how far along a route is without opening it.

Time in status

Hover over a route's status badge — or move keyboard focus to it — and a card opens beside it showing the route's time in status: each status the route has been through, how long it spent in each, and the total. Use it to answer "how long has this been sitting at pickup?" without opening the route. The card reads the route's status history the first time you open it and catches up on its own if the route moves on while you're looking.

Who canceled a route

When Nash knows who canceled a route, its status reads with the source attached — for example Cancelled · Customer, Cancelled · Provider, Cancelled · Merchant, Cancelled · Nash, or Cancelled · Reassigned (a point-to-point route reads Canceled · Customer and so on, in its stop-status spelling). You'll see this in the Status column and in the route panel's header. Routes canceled before Nash started recording the source show a plain status with no suffix.

Reassigning a live route to a different provider or driver ends the old assignment, but the route itself keeps going — so a reassignment never makes a running route read as canceled.

Who's running the route decides what you can change

The single biggest factor in what you can do to a live route is who's carrying it: your own fleet, or an outside provider.

Your own fleet. When the route is assigned to your internal fleet, Nash owns the physical route, and you can reshape it while it runs:

• Resequence the pending drop-offs into a new order.
• Split uncompleted stops onto a new route.
• Move stop to send one drop-off to another route.
• Change the driver or vehicle — inline in the queue's Driver and Vehicle cells, or from the route panel's More menu.

An outside provider. When a provider is carrying the route, the provider owns the run — its sequence, its driver, its vehicle. Nash owns the order side. So on a provider-run route:

• Resequence and Split are disabled, with the hint "Route is managed by a 3rd-party provider. Switch provider to regain control."
• The Driver and Vehicle cells are read-only. They show what the provider has shared, or Not shared by carrier when it hasn't.
• Reassign driver and Reassign vehicle in the More menu are disabled.

What stays available on a provider-run route is changing the provider itself. Reassign Provider (or the Provider cell in the queue) gathers fresh quotes and re-tenders the route to the carrier you pick. That's the route back to the full set of edits: move the route to your own fleet, and resequencing and splitting come back.

A route with no provider yet. A dispatched route that hasn't landed with a provider shows Assign Provider in its Driver cell. Pick a provider first; driver and vehicle choices follow from it.

What finishing a route locks

Status also gates the edits, independent of who carries the route:

• Completed routes hide Resequence and Split entirely — there's nothing left to reorder.
• Completed and Cancelled routes can't be re-tendered or canceled, so Reassign Provider and Cancel route disappear, and the Provider cell reads as plain text.
• Failed routes can still be re-tendered: sending a failed route to a fresh provider is a valid recovery.
• Per-stop actions — Move stop and Split stop on a drop-off — are available only while the route is still active (not completed, failed, or canceled) and only on stops that haven't completed.

Rename route and Open route page are always available.

For each change, see the task pages: Reassign a live route, Resequence a live route, Move and split stops on a live route, and Rename or cancel a live route.

Inside a route: the route panel

Select a row to open its route panel. The header names the route, shows where it starts and the region it's heading to, and carries its route status. Under the header, an action bar holds the edits — Resequence and Split up front, with everything else in More: Reassign driver (or Assign Driver when nobody has the route), Reassign vehicle, Reassign Provider, Rename route, Open route page, and Cancel route. Below that, the Route progress block shows completed stops against the total, distance, the projected end time, and how many items have been scanned.

The panel's tabs split the route's story by kind:

• Stops — every stop in order, with pickup scan progress. Each drop-off has a Stop actions menu (View details, Move stop, Split stop). Selecting a drop-off opens that order's own panel.
• Activity — a timeline of what has happened on the route: assignments, status changes, and route events, with who did what.
• Notes — free-text notes on the route, when route notes are on for your organization. See Add notes to a route.
• Issues — the route's exceptions, when exception handling is on.
• Customers — the customers on this route, when there are any, with each one's driver notes and preferences and their recent orders.
• Refunds — refund requests on the route's orders, when there are any.

Some organizations also see an Agents tab; it relates to Nash Agent and isn't covered here.

The full list of fields on the panel is in the Execute fields reference.

How Execute relates to Routes and Deliveries

Three surfaces show the same route at different points in its life:

Surface	What it's for	Which routes
Routes tab (on Orders)	Building, editing, assigning, and dispatching routes	Routes that haven't been dispatched yet
Execute	Watching dispatched routes and changing them while they run	Dispatched routes in your date range
Deliveries	The delivery record for each route's job — tracking, events, and the provider's side of the run	Every job, including the one a route becomes on dispatch

Dispatching is the hand-off between the first two. On the Routes tab, a dispatched route's structure locks: you can't resequence or split it there. Execute is where those changes move after dispatch — for routes your own fleet carries — because it works on the live route, not the draft. See How routes work for the before-dispatch side.

Dispatching a route also creates one batch job that carries all of its stops. That job is what you see in Deliveries. From the route panel, Open route page opens it, and the copy menu's Detail Link copies a link to it. Use Deliveries when you want the delivery's own record — see How deliveries work.

Where exceptions fit

An exception is a problem raised on a live route: a late departure, a vehicle breakdown, a customer who wasn't home, or one of your organization's own exception types. Each has a severity, a status, and an owner. Exception handling is an add-on within Execute — exceptions appear only when exception handling is on for your organization. Reach out to Nash if you'd like it.

When it's on, Execute gains a layer built around them:

• The page header shows whether any critical or high-severity exceptions are open, with a one-line summary, and you can show KPI cards that count routes by severity.
• A severity strip above the queue filters it to one severity in a click.
• The queue sorts by severity and adds the Assignee and Exception columns, plus checkboxes for assigning many routes' exceptions at once.
• The route panel gains the Issues tab, where you triage and resolve a route's exceptions.
• The filters gain an Exceptions group.

How exceptions are raised, triaged, assigned, and closed is covered in the exceptions pages — start with Exceptions at a glance and How exceptions work.

Who can see and act

Execute is turned on per organization. Within an organization, each person needs a role that includes access to Execute and to orders; the queue is built from your orders, so both are required. Some actions need more — requesting an order's cancellation and changing an exception each need permissions that not every role includes. If an action you expect isn't there, ask an admin to check your role; see Manage users and roles.

One thing to carry through all of this: Nash dispatches the route and hands it to a provider or your own fleet — the provider or fleet carries out the delivery. Execute is where you see what's happening to that work and steer it: who's carrying it, in what order, and what's gone wrong.