Overview
Your field rep walks the same beat every week — 12 shops, in a set order, collect orders and dues at each. Today that plan lives in his head or on a paper chit. Route management turns the beat into a saved list of stops you can dispatch to the rep's phone, then see exactly which shops he hit, which he skipped, and which turned into an order.
Opt-in Capability · off
Route Management is switched offRoute Management
You can read the guide. An owner or manager flips this Capability on in settings — it then lights up across the app.
This is an opt-in Capability — the Owner enables it per tenant. Be honest with yourself before you lean on it: route management is built but not yet switched on in the live app. The screens and tRPC procedures exist in the codebase, but the router is not mounted and capability.route-management is not a seeded catalog row, so no role — not even Owner — holds its permissions yet. Treat this page as the shape of the feature; enablement lands in a later release.
Where to find it
There is no live route-management screen in the app today. When the Capability is wired up, route planning sits on the desktop admin shell and per-stop recording happens on the field rep's mobile app (the rep's load-bearing action is recording a stop outcome from the phone). It builds on the field rep master — you assign each route to a rep, and route performance rolls up into that rep's scorecard.
Key concepts
- Route — a reusable template: a name, the field rep who walks it, a schedule, and an ordered list of stops. This is the plan, not a single day's walk.
- Planned stop — one customer on the route, with a sequence number and an optional planned visit time. Each customer appears once per route.
- Route execution — one actual day's run of a route. When you dispatch a route, Neev forks one execution and freezes a copy of the stops into it, so editing the plan tomorrow never reshuffles a walk already in progress.
- Stop outcome — what happened at a stop. Four values:
pending(not reached yet),visited,skipped,failed. A visited stop can carry a note and link to the order it produced. - Route lifecycle — every route moves through five states: draft → published → in_progress → completed, with cancelled reachable from any non-terminal state. Completed and cancelled are final.
Common workflows
Route performance — completion rate per route, visited-stop rate, and a per-rep summary — rolls up across executions so a manager can read the whole beat at a glance.
Role notes
This Capability is Owner-only by default. All six permissions — read routes, create/update routes, edit planned stops, dispatch (lifecycle), complete, and record a per-stop outcome — bind to Owner when the Capability is turned on. No other role gets them by default; the Owner can grant individual keys to a Manager or field rep through the role editor once the Capability is live.
Tips & time-savers
Dispatch snapshots the stops into the day's execution, so you can keep tidying the master route for next week without disturbing the walk already running.
Gotchas
A recorded stop is final too. Marking a stop visited, skipped, or failed locks that stop — the rep can't flip it afterwards, so make sure he records the real outcome the first time.