Route optimization order logic — how does it decide?

dispatch has been using the route optimization button and the order it spits out makes... questionable sense sometimes. like it'll have a tech drive 20 minutes north then back south past the starting point to hit a job that could've been first.

what's the actual logic here? is it just straight-line distance or does it factor in drive time, traffic, job priority, window times? the docs say "intelligent routing" but that's not exactly a technical spec.

asking because i've got techs grumbling about the sequences and i'd like to know if i'm defending an algorithm that actually makes sense or if i should just be drag-and-dropping everything manually.

Parents
  • Pro tip: if you're seeing weird backtracking, check whether someone set up recurring jobs with fixed time windows. Those act like anchors and can drag the whole route around them.

    We used to fight this constantly until we switched most recurring maintenance to "anytime during business hours" instead of specific slots. Route efficiency jumped maybe 15-20%.

    Also worth noting: the optimizer runs once when you hit the button. If a technician finishes early or gets delayed, the rest of that day's route doesn't automatically reshuffle. Some dispatchers will re-optimize midday if the morning goes sideways.

Reply
  • Pro tip: if you're seeing weird backtracking, check whether someone set up recurring jobs with fixed time windows. Those act like anchors and can drag the whole route around them.

    We used to fight this constantly until we switched most recurring maintenance to "anytime during business hours" instead of specific slots. Route efficiency jumped maybe 15-20%.

    Also worth noting: the optimizer runs once when you hit the button. If a technician finishes early or gets delayed, the rest of that day's route doesn't automatically reshuffle. Some dispatchers will re-optimize midday if the morning goes sideways.

Children
No Data