Module guide

Route Planner

Plan, review, approve, and inspect field routes. This module covers the planner itself, the daily plan workspace, and historical route replay where that capability is supported.

2026-07-20Field execution/routes · /routes/replay

Runtime availability

Route planning is customer-visible. Historical replay analytics can be unavailable in customer-hosted runtime and may show a managed-only notice.

Who uses this module

representativesmanagersadministrators

What users can do

  • Generate or refine daily plans and open the dated planning workspace.
  • Review route status, stop sequence, and approval posture.
  • Inspect execution replay when your runtime supports it.

Access and approval limits

  • Manager approval remains the gate for governed route changes.
  • Representatives can review assigned plans but do not widen route visibility outside granted scope.
  • Replay and managed overlays can depend on hosted analytics capabilities.

Key workflows

These workflows describe how the visible customer workspace is intended to be used.

Review and approve a route

Use the route planner to evaluate stop order, coverage, and readiness before the day starts.

  1. 1Open Routes and select the plan date or representative.
  2. 2Review stop order, plan status, and visible exceptions.
  3. 3Approve, re-optimize, or send the route back for adjustment.

Inspect execution replay

Open historical replay to compare the planned route with execution evidence when supported.

  1. 1Open the replay lane from Routes.
  2. 2Select the historical route and compare planned and actual evidence.
  3. 3If replay is unavailable in your runtime, continue with tracking, visit history, or reports instead.

Core concepts

Approved route

The route that can be executed in the field and reflected consistently across agenda, tracking, and notifications.

Reference

Covered screens

`/routes`, `/routes/plan/*`, `/routes/replay`

Troubleshooting

A route is still missing on the rep device.

  • Confirm the route cleared the approval gate.
  • Ask the rep to refresh agenda or notifications after approval.

If the approved plan still does not propagate, provide the route date, rep, and organization to support.

Connected modules

These areas usually carry the next action, source record, or downstream evidence.

Route Planner | FieldOrchestrator