Route-aware scheduling for recurring service teams
How SwiftSched calculates route impact
SwiftSched compares a baseline stop order and a proposed stop order with the same routing provider and units. A Decision Receipt records distance, drive time when available, moved and skipped jobs, unavailable constraints, traffic-awareness, calculation version, and freshness. Estimates are decision support, not guaranteed savings.
- A current route sequence is preferred as the baseline
- Incomplete route data is disclosed, not silently imputed
- Only applied plans contribute to the Value Ledger
Baseline
SwiftSched uses the current route sequence when it is available. Otherwise, the receipt labels the stable schedule order used as the comparison baseline.
Comparable calculation
Baseline and proposed orders use the same routing provider and units. Distance and drive-time fields remain unavailable when the provider cannot return a comparable result.
Coverage and constraints
The receipt reports how many jobs were optimized or skipped and lists constraints that were unavailable. A result with partial data is not presented as complete.
Freshness and control
A proposal is marked stale or superseded when the underlying schedule changes. Stale plans are blocked from application and must be recalculated.
Value limitations
The Value Ledger counts estimated distance and drive time from applied plans. Dollar savings remain hidden until the tenant configures a documented cost model; estimates are not a promise of realized financial results.
Frequently asked questions
Are route savings guaranteed?
No. Route metrics are estimates based on the disclosed inputs and provider. Actual travel can differ because of traffic, field conditions, customer changes, and incomplete data.
Why can a route proposal become stale?
A job, assignment, time, or route input may change after calculation. SwiftSched blocks the old proposal so the dispatcher can generate a current comparison.
Product information reviewed by the SwiftSched Product Team ยท Updated 2026-08-10