Reoptimize a route

Once a route exists, you'll often change it — add a late order, drop one, move a few stops around — and then want the sequence and timing to catch up with those changes. Two actions in the route drawer do that: Reoptimize re-solves the stop order, and Calculate Timing refreshes the arrival and departure estimates. Both live on the Routes tab and both work on a route that hasn't been dispatched yet. For the hands-on edits that come before them, see Edit a route.

Reoptimize

Reoptimize re-runs optimization on just this route's stops, looking for a better sequence than the one it currently has. It's the right move after you've added, removed, or moved stops by hand and would rather have Nash re-solve the ordering than work it out yourself. Where the original optimization worked across a whole set of orders, reoptimize is scoped to the one route you're looking at.

Reoptimizing runs in the background, so it may take a moment to come back with a result rather than updating instantly. The route keeps its current stop order until the reoptimized result is ready, so nothing changes out from under you mid-edit.

Reoptimize changes the sequence, not who's carrying the route or which orders are on it — it's purely about finding a better order to visit the stops you've already got.

Calculate Timing

Calculate Timing computes arrival and departure estimates across every stop on the route, based on its current sequence. Reordering, adding, or removing stops doesn't recalculate timing on its own, so run Calculate Timing after you've changed a route — including after a reoptimize — so its timing reflects what the route will actually look like once it's out.

Think of it as the check step: reshape the route, then Calculate Timing to see the real arrival and departure picture before you commit to dispatching it.

Both lock after dispatch

Reoptimize and Calculate Timing are structural actions, so they lock the moment you dispatch a route — along with Split and Dispatch itself. A dispatched route is the record of what went out, and re-solving or re-timing it after the fact would mean that record no longer matched the work. Do your reoptimizing and timing checks while the route is still a draft. See Dispatch a route for what dispatch commits, and How routes work for the fuller editable-then-locked picture.

Availability

These actions depend on whether your organization has routes enabled. If you don't see the Routes tab or the Reoptimize and Calculate Timing actions, availability varies by org — reach out to Nash.