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
  • Ray, happy to help clarify this! Route optimization in FieldPulse considers several factors in sequence:

    1. Job time windows — Hard constraints like "must arrive between 9-11am" take priority

    2. Technician skills and certifications — Won't assign plumbing jobs to an electrician, for example

    3. Drive time estimates — Based on historical averages, not live traffic

    4. Job priority — Emergency and high-priority jobs get weighted heavily

    5. Service duration — Longer jobs may be placed earlier to protect the schedule

    What it doesn't currently factor in: live traffic conditions, technician preferences, or customer "ease of access" (like gated communities that slow arrival).

    The "20 minutes north then back south" pattern you describe usually happens when a middle job has a tight time window that forces the sequence. If you want more manual control, you can pin specific jobs to time slots and let the optimizer fill around them.

    See Route Optimization: How It Works for the full breakdown.

Reply
  • Ray, happy to help clarify this! Route optimization in FieldPulse considers several factors in sequence:

    1. Job time windows — Hard constraints like "must arrive between 9-11am" take priority

    2. Technician skills and certifications — Won't assign plumbing jobs to an electrician, for example

    3. Drive time estimates — Based on historical averages, not live traffic

    4. Job priority — Emergency and high-priority jobs get weighted heavily

    5. Service duration — Longer jobs may be placed earlier to protect the schedule

    What it doesn't currently factor in: live traffic conditions, technician preferences, or customer "ease of access" (like gated communities that slow arrival).

    The "20 minutes north then back south" pattern you describe usually happens when a middle job has a tight time window that forces the sequence. If you want more manual control, you can pin specific jobs to time slots and let the optimizer fill around them.

    See Route Optimization: How It Works for the full breakdown.

Children
No Data