PR-3601 · Live
Route Book Builder
Route Book Builder is an in-app multi-week route planner for the Dispatcher that pulls the FSM schedule, runs a Vehicle Routing Problem optimizer, previews per-Route deltas, and bulk-commits assignments back to the FSM, billed per Route processed.
The promise
When the next planning cycle comes around, the Dispatcher opens an in-app planner that optimizes every Route, previews the deltas on side-by-side before/after maps, and bulk-writes the new tech assignments, recurring start times, and route tags back to the FSM. The 1 to 3 hours she used to spend exporting the schedule to a spreadsheet, re-sequencing stops by hand, and re-keying the changes back into the FSM is no longer part of her cycle.
How it works
The path from input to value.
- 01
Pull the FSM snapshot into a planning instance
The configured FSM adapter pulls the current schedule for your allowlisted Territories and Job Types: Routes, Jobs, Tech assignments, recurring start times, arrival windows, stop coordinates. Each enrolled Route is recorded as one Route processed for this planning cycle. Repeating the snapshot pull within the same planning cycle is safe and won't duplicate Routes.
- 02
Run optimization with configured objective and constraints
A deterministic route-optimization solver runs against the planning instance. The configured objective (drive-time minimization or time-window adherence) sets what the optimizer minimizes; configured constraints (workday window and buffers, max stops per day, locked stops, multi-tech-day rules) are applied as hard constraints. Each Route's optimization is recorded with the proposed sequence, the prior sequence, the objective, the constraint set, and the before/after metric delta. If the solver does not converge for a given Route, the run is recorded with the prior sequence and a no-feasible-solution reason so the Dispatcher can relax a constraint.
- 03
Preview the proposed plan
The planning instance transitions into preview state, recording the finalized proposed state for each Route. The preview surface renders side-by-side before/after maps, per-Route metric deltas, and plan-level rollups (total drive-miles change, total drive-minutes change, per-tech utilization change). The Dispatcher can drag-and-drop manual edits, lock specific stops, and re-run optimization on subsets. Exit-back-to-planning is non-destructive.
- 04
Commit the previewed plan to the FSM
The platform writes new tech assignments, recurring start times, and route tags back to the FSM through the configured adapter, honoring your configured commit window (immediate / next-Saturday-after-hours / next-Sunday-night / custom-cron; default next-Saturday-after-hours, in your local time zone). Writes are bulk and respect the FSM's rate limits. Each Route's commit is recorded with FSM-side write status; failures land in the exception queue with retry actions on a post-commit validation surface.
- 05
Revert as the safety path
Within the configured revert window (default 7 days), the Dispatcher can revert any committed Route at the per-Route level. The platform restores the pre-commit snapshot and writes the prior state back to the FSM through the same adapter. The revert is recorded against the Route.
What it doesn’t do
The edges we drew on purpose.
A product that tries to do everything ends up doing nothing well. Here’s what we left out, and why we don’t feel bad about it.
- ×Does not perform daily real-time route adjustment for mid-day exceptions; the FSM dispatch board owns real-time changes.
- ×Does not push routes to technician mobile devices.
- ×Does not send notifications to customer-end recipients.
- ×Does not validate skill matches during optimization. Skill assignments are read as constraint inputs only
- ×Does not track GPS or live technician location.
- ×Does not score, rank, or coach technicians.
- ×Does not function as a replacement for the FSM dispatch board. This Product is a planning layer on top of FSM truth.