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 Reply Children
  • Another way to think about this: the optimizer is solving a traveling salesman problem with time windows, which is computationally expensive. FieldPulse uses a heuristic that prioritizes schedule feasibility over pure distance minimization.

    That means it will accept a slightly longer drive to guarantee all time windows are hit, rather than risk a breach for marginal fuel savings. From a service level perspective, that tradeoff usually makes sense, even if individual routes look suboptimal.

    Our approach is to use optimization for the initial morning dispatch, then manually adjust based on real-time conditions. The hybrid method has worked well for a 40-tech operation.