Edit a route

Open any route from the Routes tab and you land in its drawer — the working view for everything you can do to a route before you send it out. The drawer shows the route's stops in visit order, alongside the actions that reshape it: add or remove orders, reorder stops, move stops to another route, split the route apart, resequence it, recalculate its timing, and assign who runs it. Every action in this article assumes the route hasn't been dispatched yet. Once you dispatch, the drawer's structural actions lock — more on that at the end of this article.

There's no required order to work through these. You might add a couple of late orders, reorder the stops by hand, run Calculate Timing to check the result, then assign a driver — or do all of that in a different sequence. The route stays a draft, open to any of these actions, right up until you dispatch it.

Add or remove orders

Add Order pulls another order onto the route as a new stop. Use it when you've already built or optimized a route and realize one more order belongs on it — you don't have to rebuild the whole thing from scratch.

To take an order back off, remove it. You can do this two ways: from the stop's row inside the drawer, or from that order's row back on the Ready-to-Dispatch list, where a routed order shows a remove-from-route affordance in place of its usual dispatch buttons. Either way, removing an order takes its stop out of the route and frees the order to be routed again, dispatched on its own, or left for later — it doesn't cancel or archive the order itself.

Reorder stops

The sequence stops happen in is yours to set. Drag a stop to a new position in the list, or use Move Up / Move Down on a stop's row for finer control. Reordering only changes the visit order — it doesn't add, remove, or reassign anything. If the new order changes how long the route takes, run Calculate Timing afterward to see updated arrival and departure estimates.

Tell the optimizer where a stop belongs

Dragging a stop sets its position once. To leave a standing instruction for the optimizer instead, open the menu on a drop-off stop's row and choose Edit sequencing. The Sequencing dialog has three fields, all optional:

• Sequence Priority — a whole number from 0 to 499. A stop with a smaller number is visited earlier. Leave it empty for no ordering constraint.
• Sequence Group — limits that ordering to the orders that share the group, and puts every order in the group on the same route.
• Mutually Exclusive Label — keeps orders with different labels off the same route.

Choose Save and you'll see Sequencing saved. Saving doesn't move the stop on its own — the values are used the next time the route is optimized, so resequence the route to see them take effect. Sequence Priority is the one that shapes the stop order on a route; the group and the label mostly decide which orders travel together, so they matter when orders are optimized into routes. To remove a value, clear the field and save again.

A stop with sequencing set shows a badge for each value — Priority, Group, Label — on its row. The same Edit sequencing item is in each order's menu on a route's card in the map view, and the same three fields sit under Advanced (Optional) when you edit the order itself.

Edit sequencing saves to the order, so it needs permission to edit orders, and it's unavailable once the route is dispatched.

Move to Route — how you combine routes

Moving a stop takes it off the route you're viewing and puts it onto a different, existing route. In the drawer, open the menu on an order's row and choose Move to another route, then pick the destination. It's the tool for combining work that started out on separate routes: move the stops that belong together onto the route you want them to end up on, and the source route is left with whatever stops it has remaining.

There's no dedicated "merge" action for routes — the drawer doesn't offer a button that folds two whole routes into one in a single step. Moving stops is how you get the same result: move every stop from one route onto another, and the now-empty route can be left as-is or archived. If you only need to combine a couple of stops rather than an entire route, moving just those stops works the same way without touching the rest of either route.

For example, say two draft routes cover the same neighborhood and it makes more sense as one run: open the route with fewer stops, move its orders to the other route, and they join that route's stop list. Reorder the combined route afterward — a moved stop lands wherever the action puts it, not necessarily where you'd sequence it by hand — and run Calculate Timing to see the combined route's real timing.

Move several stops at once from the map

The drawer moves one order at a time. To move a batch, use the map instead: select Map on the Routes tab, select the drop-off stops you want — click them on the map, tick them on a route's card, or draw around them with Lasso or Polygon — and choose Move to route. The selection can span more than one route, so you can pull stops off several routes and land them all on one destination in a single action. For the map's selection tools in full, see work with orders and routes on the map.

A few things to know about a batch move:

• Where moved stops land. They're added at the end of the destination route, just before its end point. Reorder them afterward and refresh the route's timing. In some organizations, a stop you move or add is instead slotted into the route where it adds the least extra travel — availability varies by organization, so reach out to Nash for access.
• A route can end up empty. Moving every stop off a draft route doesn't remove the route. It stays in your list with no orders on it, ready to take stops again later — archive it if you don't need it.
• Both routes need a compatible starting point. Routes that start at a depot can exchange stops with each other. A route that loads at a pickup stop can only exchange stops with a route that loads at the same place, and a route with several pickup stops can't take part in a stop move at all. If the routes don't qualify, the move is refused.
• Dispatched and archived routes are out. Their stops can't be selected, and they can't be chosen as the destination.

Split — the honest version

Split breaks the route apart, but it's worth being precise about what it actually does, because the name invites you to imagine more than it delivers. The drawer's Split is the legacy one-route-per-order split: it takes every order on the route and gives each one its own route, so a five-stop route split this way becomes as many single-order routes as it had orders. It doesn't let you carve out an arbitrary subset — say, three of five orders onto a new route while the other two stay put. That kind of partial, pick-your-own-stops split isn't something the classic Routes tab drawer offers.

If what you actually want is to move a handful of stops to a different route rather than shatter the whole thing down to one order per route, that's a move, not a split — use Move to another route, or the map's batch move, on the stops you want elsewhere instead of splitting.

Re-solve the sequence and check the timing

Once you've reshaped a route's stops by hand, you'll usually want Nash to re-solve the visit order and refresh the route's timing. Two drawer actions do that — Resequence re-runs optimization on just this route's stops, and Calculate Timing recomputes arrival and departure estimates across them. Both are covered in Resequence a route.

Assign who runs the route

Before you dispatch, decide who carries the route — an outside provider, or a vehicle and driver from your own fleet. That's the Assign Provider action, covered in Assign a route. A route can sit as a draft without an assignment, but it needs one before you can dispatch it, so settle it alongside the stops in whichever order suits your workflow.

The post-dispatch lock

Every action in this article assumes the route hasn't been dispatched. Once you dispatch a route, its structural actions lock: Calculate Timing, Split, and Resequence all disable, along with Dispatch itself, since a route can't be dispatched twice. This isn't just a hidden button — it's enforced on the server, so there's no workaround for editing a route's structure after it's out.

The reasoning is the same one that governs a single order once it's dispatched: a dispatched route is the record of what actually went out, and letting its structure keep changing after the fact would mean that record no longer matched the work. If something needs to change after a route is dispatched, that's a new order or a new route, not an edit to the one that's already gone. See Dispatch a route for what dispatching actually does, and How routes work for the fuller editable-then-locked picture and how a route relates to the orders and job behind it.

If you're still assembling which orders belong on a route in the first place, start at Build a route from orders — this article picks up once you already have a draft route open.

Availability

The Routes tab and its drawer depend on whether your organization has routes enabled. If you don't see a Routes tab, availability varies by org — reach out to Nash.