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
  • I'll add something Priya touched on but didn't emphasize: skills matching can really mess with perceived efficiency.

    If you have three techs and only one is certified for refrigeration work, that job might get placed oddly in the sequence because the optimizer is also trying to keep that tech's total drive time reasonable across their whole day. You're seeing one tech's route in isolation, but the algorithm is balancing all of them.

    We audit our skill assignments quarterly — found we had people tagged for things they hadn't done in years, which was constraining the optimizer unnecessarily.

Reply
  • I'll add something Priya touched on but didn't emphasize: skills matching can really mess with perceived efficiency.

    If you have three techs and only one is certified for refrigeration work, that job might get placed oddly in the sequence because the optimizer is also trying to keep that tech's total drive time reasonable across their whole day. You're seeing one tech's route in isolation, but the algorithm is balancing all of them.

    We audit our skill assignments quarterly — found we had people tagged for things they hadn't done in years, which was constraining the optimizer unnecessarily.

Children