Coordinating routes, operators and physical activation
Turn campaign scope into routes, service plans and authorized physical work.
On this page
Translate a campaign into bounded routes and work that eligible operators can perform. The planned result keeps route coverage, assignments, execution and evidence connected.
Start with a feasible scope
Provide the approved campaign/territory revision, target membership, service definitions, quantities, timing and proof requirements. Route planning should account for what is covered, excluded and unresolved.
A snapped path or graph route does not prove traversability, operator capacity or actual dispatch. A family of field-service definitions is not nationwide fulfillment proof.
Keep the work durable
Preserve zones, work packets, work orders, assignment identities and status. Customers may see their work-order progress; operator offers, acceptance and scheduling actions require separate partner authority.
For example, a route can be ready for review while an assignment remains unaccepted and no work has begun.
Separate execution evidence
Device/location submission is assignment- and consent-scoped. Proof submitted, reviewed and accepted are different states, as are earning accrual and payout. Customer visibility must not expose private verification documents or unrelated location history.
Availability
Business APIs are planned. Internal queue draining, reconciliation and canonical-map repair are not customer recovery controls. Real dispatch, booking, printing or other external effects require explicit approval, funding and capacity checks.