Forum Discussion

BlueSkies's avatar
BlueSkies
Contributor 3
14 days ago

Routing

Again asking for a proper routing algorithm that doesn't run off geocode. I don't know how that is useful. I have to keep moving every single week properties around. If i had a crew, that doesn't realize the route...they would be wasting over an extra 3 hours due to poor routing that doesn't pay any real attention to driving.

Again...i should never be told that i should leave a court with 4 properties on it to go to another proeprty around the corner and come back because from a a cooridinates persepective one is "further" away despite being around the corner. I shouldn't be sent to a different zip code just to come back because again of geo coding. the routing...is honestly not good. The reason to use it, is to speed up the scheduling, not creating more work. I shouldn't HAVE to review KNOWING that it is off.

1 Reply

  • krista's avatar
    krista
    Jobber Support Team
    11 hours ago

    Hi BlueSkies​ 

    I appreciate the additional context here, especially in light of your earlier comments on recurring route consistency. Together, it paints a much clearer picture of the operational pain point you’re running into.

    What you’re describing sounds less like general “optimization” issues and more like the current logic prioritizing coordinate proximity in ways that don’t reflect real-world driving flow, neighborhood grouping, or practical crew movement.

    The examples you gave around:
    • leaving a court mid-route
    • crossing zip codes unnecessarily
    • looping back into the same area later

    All make sense as frustrating outcomes, especially in recurring lawn routes where efficiency and consistency are everything.

    I’d be really interested in learning a bit more about your workflow and seeing a few examples of where the routing consistently breaks down for you. I’d be happy to share that feedback internally with the team because concrete, real-world routing examples are incredibly valuable context.