Execute at a glance

Execute is where you watch your routes once they've been dispatched. It's a live queue of every dispatched route in the date range you pick, one row per route, with its status, stop progress, projected finish time, and who's carrying it. When something on a route needs to change while it's running — a different driver, a new stop order, a stop moved to another route, a route canceled — you make that change from here.

Note

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

Select Execute in the sidebar. The page opens with the heading Operations — that's the same page; the sidebar and the page header just use different names for it.

Where Execute fits

A route has two working lives. Before dispatch, it's a plan you build and reshape on the Routes tab of the Orders page — see Routes at a glance. Dispatching turns it into one batch job that a provider or your own fleet carries out. From that moment, the route shows up in Execute, and Execute is where you follow it and act on it until it finishes.

Nash dispatches the route and hands it to a provider or your own fleet; the provider or fleet carries out the delivery. What you manage in Execute is the route's assignment, its stop order, and its status as the field reports it back.

What you can do in Execute

Monitor live routes

• Find routes in Execute — narrow the queue by date range, search, and filters, and switch between table, map, and timeline views.
• Save and share Execute views — keep the slices of the queue you use every day, and share them with your team.

Change a live route

• Reassign a live route — change the driver, vehicle, or provider on a route that's already out.
• Resequence a live route — put the remaining drop-offs in a new order.
• Move and split stops on a live route — send a stop to another route, or split uncompleted stops onto a new one.
• Rename or cancel a live route — relabel a route, or cancel the deliveries that are still pending.
• Request an order cancellation on a live route — ask for one order to come off a route that's running.
• Add notes to a route — leave context on a route for the next person who opens it.

Handle exceptions

Exceptions are the problems raised on live routes — a late departure, a vehicle breakdown, a customer who wasn't home — with a severity, a status, and an owner. They appear in Execute only when exception handling is on for your organization; reach out to Nash if you'd like it. See Exceptions at a glance for everything you can do with them.

Learn how it works

The task pages tell you what to click. For the model behind them — which routes appear in the queue and when, what each status means, why some edits are locked on routes a provider is carrying, and how Execute connects to Routes and Deliveries — see How Execute works.

For every column, control, and panel on the page, see the Execute fields reference.

Who can use Execute

Execute is turned on per organization. Once it's on, each person also needs a role that includes access to Execute and to orders — the queue is built from your orders, so both are required to load it. If Execute is on for your organization but you don't see it in the sidebar, ask an admin to check your role; see Manage users and roles.

Some parts of the page are optional per organization: the Map and Timeline views, route notes, and the exception-handling layer (exception columns, the Issues tab, severity counts, and KPI cards). If you don't see one of them, availability varies by organization — reach out to Nash.