New to Routerra Teams, or handing it to a teammate? Here's the vocabulary, defined once. Terms link to the guide where each one does its real work.

Core objects

Plan — the container for one day's work. A plan holds stops, and after optimization it holds the routes built from them. One plan usually equals one day. See A typical morning.

Stop — a single delivery: an address plus its settings (service time, arrival window, load, notes, attachments). See Stop settings.

Route — one driver's ordered path for the day, produced by optimization: their stops in driving order with ETAs. One route per driver. See Assign drivers and optimize.

Depot — a fixed location where routes start and finish (warehouse, store, kitchen). Each driver has a start and finish depot. See Depots.

Zone — a delivery area drawn on the map as a polygon, used to keep drivers in or out of specific neighborhoods. See Zones.

People and access

Owner — the admin who runs billing and the team itself, in addition to dispatching. See Roles.

Manager — a dispatcher: full access to plans, fleet, address book, and activity, but not billing or team deletion.

Driver — a field user who only ever uses the driver app to receive and run routes. Never touches the web app.

Seat / driver slot — one unit of your subscription: one driver who can receive routes. You're billed per seat. See Trial, seats, and billing.

Building and dispatching

Import — getting stops into a plan: Paste List, Upload File, Upload Image, Team Address Book, or Pull from data source. See Import stops.

Geocoding — turning an address into a map location (a pin). Occasionally guesses wrong; fixable via coordinates. See Import problems.

Optimize — building routes from stops with Assign drivers & optimize, respecting every constraint you've set.

Distribution Strategy — how work is split across drivers during optimization: Balance by Stops, Balance by Time, Fastest Overall (recommended default), or Balanced Mix. See Assign drivers and optimize.

Unassigned Stops — stops the optimizer couldn't place without breaking a constraint (a window, capacity, a shift). They wait here instead of ruining a route.

Dispatch / Send routes to drivers — making optimized routes visible in the driver app. Flips the plan to Approved. See Send routes to drivers.

Revoke from Drivers — pulling routes back out of the driver app.

Refine — hand-adjusting a route by dragging its points on the map. Split — breaking one route into several. Reassign — moving stops to a different driver. See Refine routes.

Tracking and evidence

POD (Proof of delivery) — the driver's evidence for a stop: the status they set, plus photos, files, and notes. See Proof of delivery.

Needs attention — the dashboard counter for failed deliveries and stalled routes; the number to keep at zero. See Follow delivery progress live.

Live status visibility — Routerra's model of tracking: you see delivery statuses as drivers check in, not GPS dots on a map.

Offline-first — the driver app keeps working with no signal and syncs when it returns. See Offline: what syncs and when.

Configuration and platform

Address Book — team-wide saved addresses with their settings, reusable in any plan. Autosync keeps a saved address in step with your edits. See The Team Address Book.

Arrival window / Arrival Priority — the time range a stop must be served in, and whether to aim Earliest / Latest / Auto within it. See Stop settings.

Load / Vehicle Capacity / Max Stops — how much a stop consumes, how much a vehicle holds, and the hard cap on stops per route. See Drivers.

Live road data — real-time traffic (TomTom) factored into optimization when enabled. See Route preferences.

API key — a credential that lets your own systems optimize via the Routerra Teams API. Webhook — a signed JSON POST Routerra sends your systems when things change. Data source — an endpoint Routerra pulls stops from. See API keys and Webhooks.

What's next

Plan, route, and stop statuses — the status vocabulary
A typical morning — the terms in action, end to end