Route-aware scheduling for recurring service teams
Route optimization a dispatcher can audit
SwiftSched’s field-service route optimization compares the current stop order with a proposed order using consistent travel data. Before anything changes, the dispatcher sees expected drive-time and distance impact, moved and skipped jobs, unavailable constraints, data freshness, and the calculation version in a Route Decision Receipt.
- Current route sequence is used as the baseline when available
- Stale route proposals cannot be applied
- Financial savings are hidden until a documented tenant cost model exists
Use a comparable baseline
The baseline and proposed route use the same distance provider and units. When a current route sequence is unavailable, SwiftSched labels the stable schedule order used instead.
Disclose data coverage
The receipt reports skipped jobs, unavailable constraints, coordinate coverage, the provider, whether traffic-aware data was used, and the calculation version.
Apply or dismiss
The dispatcher reviews the proposal. Applied changes update the route atomically and are recorded; dismissed and superseded decisions keep an auditable state.
Frequently asked questions
What should route optimization consider?
At minimum it should disclose the baseline order, locations, scheduled work, service duration, technician or route assignment, provider, skipped stops, and freshness of the proposed plan.
Does SwiftSched use live traffic?
A Decision Receipt states whether traffic-aware data was used. SwiftSched does not present staged or non-traffic calculations as live traffic.
Product information reviewed by the SwiftSched Product Team · Updated 2026-08-10