Plan, route, and stop statuses
Every status you'll see in Routerra Teams — on plans, on routes, on live tracking, and on individual stops — what each one means, and what moves it to the next.
Statuses are how Routerra tells you where everything stands. This page is the answer key: every status on a plan, a route, a live-tracked driver, and a stop, in plain language.
Plan statuses
A plan moves through these as you build and dispatch it:
| Status | What it means |
|---|---|
| Created | The plan exists; you're adding stops. |
| Importing... | Stops are being imported (paste, file, or photo). |
| Import failed | An import didn't process. A dialog tells you why — for a file, for example, more than 250 rows, more than 100 columns, more than 500 characters in a row, or an empty file. Fix the file and try again. |
| Dispatching... | Optimization is running; routes are being built. |
| Dispatched | Routes are built — but not yet visible to drivers. Review them, then send. |
| Dispatch failed | Optimization didn't complete. A Dispatch failed dialog opens with the reason — see below. |
| Approved | You pressed Send routes to drivers; routes are now live in the driver app. The dispatch button becomes Revoke from Drivers. |
| Has Changes | You edited a plan that was already sent — the drivers' copy is now stale. Re-optimize if needed and send again. |
| Cancelled | The plan was cancelled. It shows a Cancelled banner with the time and a Restore button, and it's hidden from the plans list unless you tick Show cancelled. |
- Created goes to Importing... on import stops.
- Importing... goes to Import failed on import error.
- Import failed goes to Importing... on try again.
- Importing... goes to Dispatching... on optimize.
- Dispatching... goes to Dispatched on routes built.
- Dispatching... goes to Dispatch failed on optimization error.
- Dispatch failed goes to Dispatching... on adjust and re-run.
- Dispatched goes to Approved on send routes.
- Approved goes to Dispatched on revoke.
- Dispatched goes to Has Changes on edit stops.
- Approved goes to Has Changes on edit stops.
- Has Changes goes to Dispatching... on re-optimize + send.
Teal marks the two statuses people mix up and the single step between them — pressing Send routes to drivers is what turns routes the office can see into routes drivers can see.
Driving Routerra from your own system rather than the dashboard? The API calls these same states by different names — DISPATCHED, APPROVED, HAS_CHANGES — and knows a couple the dashboard never shows. Same machine, different vocabulary: Plan lifecycle & statuses is the developer-side version of the diagram above.
Why a dispatch fails
The Dispatch failed dialog opens when the optimization fails, and again whenever you open a plan that's still in that state. It shows one of these reasons:
- "One or more driver locations could not be connected to the road network." — despite the wording, this usually means stops the optimizer couldn't reach by road. Those stops are marked Location is outside of transit area in the stop list; fix or remove them first.
- "The route optimizer could not find a valid solution for the given stops and drivers." — the constraints can't all be met at once.
- "An unexpected error occurred during route optimization." — try again; if it repeats, contact support.
If Routerra has no specific reason, the dialog says "Please try again later." Fixes for each reason are in When routes won't optimize.
Cancelled plans
You can't cancel a plan from the web app. A plan becomes Cancelled when your own system or a connected AI assistant cancels it through the Routerra Teams API, or when someone presses Apply on a Cancel plan change that an assistant proposed (see Proposals). Press Restore on the banner to bring the plan back. More in Create, find, and manage plans.
A restored plan always returns as Created. Its routes were removed when it was cancelled, so optimize it again before you send it.
Route statuses
Each driver's route carries its own state. The web app and the driver app name the first state differently:
| Web app | Driver app | What it means |
|---|---|---|
| Not started | Optimized | The route was built and sent, but the driver hasn't started yet. On the dashboard it turns red when the driver's shift has begun and they still haven't started — an idle route. |
| In Progress | In Progress | The driver tapped Start and is working the route. |
| Completed | Completed | The driver finished all stops (and pressed Finish Route). A finished route can be reopened if the day changes. |
| Overdue | — | Dashboard only: a route from an earlier day that is still open. It appears under Not closed from previous days, where you can close it with Mark as completed. |
On the plan's Routes tab, a route that hasn't started shows no status label at all; In Progress and Completed show as badges. The dashboard's Needs attention card counts overdue routes, idle routes, and failed stops. See Follow delivery progress live.
Live tracking statuses
With Live driver tracking on, a route that's in progress shows a tracking chip instead of In Progress. Hover over the chip for the full explanation.
| Status | What it means |
|---|---|
| Moving | The driver's phone is sending fresh locations. |
| Parked | The driver is stopped. A parked phone sends nothing until it moves again, so its last position stays trustworthy for up to 30 minutes. |
| Signal delayed | No new location for more than 2 minutes while the driver was moving — the puck on the map may be behind. |
| Connection lost | No new location for more than 5 minutes while moving, or 30 minutes while parked. The phone may have lost signal, or the app was closed. |
| Not tracking | No tracking session for this route. The chip says Not tracking: permission or Not tracking: location off when the driver needs to fix a setting on their phone. |
The route list header counts how many routes are live: Tracking X of Y. What each status means for your day, and what to do about it, is in Live driver tracking.
Stop statuses
Individual stops carry one of three outcomes:
| Status | What it means |
|---|---|
| Pending (no label) | The stop is in the plan and hasn't been delivered or skipped yet. |
| Delivered | Delivered successfully — shown as "Delivered at H:MM" in green, often with proof-of-delivery photos. |
| Skipped | The driver couldn't deliver — shown in red as "Skipped · <reason> at H:MM" with a structured reason. |
Stop warnings
Some stops also show a coloured strip under the address. These are warnings, not statuses:
| Warning | What it means |
|---|---|
| Outside its time window | The stop is on a route, but the route now reaches it outside its arrival window — for example after a driver changed the stop order, or after you restored the planned order. |
| Cannot be visited at selected time | On an unassigned stop: the optimizer couldn't fit it into its arrival window. |
| Location not found. Click to edit address or move the pin. | The address couldn't be placed on the map — see Import problems. |
| Location is outside of transit area | The address is outside the area Routerra can route in. |
Skip reasons
When a stop is Skipped, the driver picks one of these:
Customer not available · Wrong address · Customer refused · Business closed · Access restricted · Other reason
Failed stops surface immediately in the dashboard's Needs attention — see When a delivery fails.
Subscription statuses
Not a plan/route/stop status, but you'll see it on the team:
| Status | What it means |
|---|---|
| Trial | "Trial — N day(s) left." Full product; card on file. |
| Active | Subscription in good standing. |
| Past Due | A payment failed — update the card. A banner warns dispatchers. |
| Expired / Cancelled | Data stays visible, but creating and optimizing plans is blocked until you resubscribe. |
Details in Trial, seats, and billing.
What's next
- Glossary of Routerra Teams terms — the words behind the statuses
- Follow delivery progress live — statuses in motion
- Live driver tracking — the tracking statuses on the map