FOR THE DISPATCHER

Route Builder

Route re-sequencing that writes itself back.

The Dispatcher's planning day no longer runs on a spreadsheet. The route book is already worked out on screen, with the drive-time change named for each Route, ready to review and lock in on the schedule.

Illustration of Route Builder
Time back
10 min
per route
Cost
30¢
60 Rivets per route

How it works.

5 steps, and your team only touches the ones that need a person.

  1. 1.

    The route book is pulled in

    At the start of each planning cycle, every recurring Route is loaded into one workspace, one Route per row. Each row shows who is running it, what stops it has, and when each stop happens today.

  2. 2.

    Each Route is optimized automatically

    Every Route gets a better-ordered version worked out for it, shown next to the current one. Each row shows how much drive time and how many miles the new order saves, and a before-and-after map is available for any Route.

  3. 3.

    The plan is open for edits

    The Dispatcher can adjust any Route before it goes live: dragging stops into a different order, locking stops that should stay put, and re-running the suggestion on just the Routes that were changed. The running totals at the top update as edits are made.

  4. 4.

    The approved plan is saved back

    Once the plan is approved, the new stop orders, technician assignments, and start times are written back into the company's scheduling system on a set schedule, by default the Saturday night after approval. This happens on its own, with nothing to watch.

  5. 5.

    Any Route can be undone

    For a set period after approval, any Route can be returned to exactly how it was before the cycle. The earlier version is written back into the scheduling system the same way the new one was.

Try it.

A small working model of Route Builder. Nothing here touches a real customer.

Route BuilderDemo

Lock the stops that have to stay put, then ask for a suggestion and see the new route order.

A day for the Dispatcher.

  1. 8:00 AM

    Coffee, second monitor, the planning spreadsheet kept in a tab. Exports today's schedule out of the system of record one Route at a time.

  2. 10:30 AM

    Re-sequencing stops by hand in the spreadsheet, eyeballing the map in a second tab. The drive-time change is a number calculated on the side.

  3. 1:00 PM

    Two techs have texted asking to keep the same Monday stops they have been working. A note goes on the sticky pad next to the keyboard.

  4. 3:00 PM

    Re-keying the new sequences back into the system of record, one Route at a time, watching for the field that does not save right if you tab through it too fast.

  5. Next morning

    Two techs call the office because their Monday stops moved without warning. The Dispatcher fields the calls.

What it won't do.

So nobody's surprised later.

  • Plans on a cycle, not in real time during the day.
  • Does not push the new Routes to technician mobile devices.
  • Does not notify customers when their visit day or window changes.
  • Does not validate skill matches during optimization; locked stops and tech-Route assignments come in as inputs the optimizer respects.
  • Does not track GPS or live technician location.
  • Does not replace the field service management dispatch board.
  • About 220,000 calls a month analyzed across 31 shops
  • 139 shops use Graphite Lab tools
  • 108 ServiceTitan data types synced, including for multi-location operators
  • 66 to 93 mobile PageSpeed, from a contractor's old site to the preview we built in under 10 days

Let’s talk about your shop.

No slide deck. Tell us how your team runs today and we'll show you what we'd build first. If it's a fit, we send you a quote.

ELI waving goodbye