AI Route Planning for Landscaping Crews: Time and Fuel Savings

It depends on how scattered your routes are now, so measure rather than trust a vendor figure: log a normal week's miles and drive time, re-plan the next week, and compare. On a mowing and maintenance round, the bigger saving often comes from grouping customers by area and day, before any software reorders the stops.

For a sense of scale, the illustrative two-crew firm worked through below cut about a fifth of its weekly miles, roughly 165 miles and 7.5 crew-hours a week, and most of that came from moving customers onto the right day. That's a realistic outcome for a round that grew one customer at a time. A round that was planned by area from the start will save far less, and that's a good result too: it tells you not to pay for software you don't need.

Follow me on Instagram@sagnikteaches

Measure a normal week before you change anything

Without a baseline, any saving is a guess. Pick a week that's typical for the season (not the first cut of spring or a rain-hit week) and record, per crew per day:

Connect on LinkedInSagnik Bhattacharya

• Miles driven, from the odometer, a fuel card report or vehicle tracking
• Drive time, from tracking or a phone's location history
• Stops completed and time on site at each
• Non-customer trips: green-waste tip runs, merchant pickups, fuel, returns to the yard
• Finish time and any overtime

Also work out your fuel cost per mile, because it varies a lot between a small van and a pickup towing a trailer: take a month's fuel spend and divide by that month's miles. The figures below use $0.40 a mile purely as an illustration. If your vans have tracking, automating fleet admin, services and fuel records covers pulling these numbers without manual logging.

Subscribe on YouTube@codingliquids

The saving most crews miss: which day a customer is on

Stop order within a day gets all the attention, but if Monday's customers are spread across the whole service area, no routing tool can make Monday efficient. The fix is area-days: each crew works one area per day, and every customer in that area is on that day.

A general AI assistant is good at proposing the first draft of these zones from a customer list. Export customers with their street and neighbourhood, visit frequency and typical service minutes, then:

Here is our customer list: area, street, visit frequency (weekly or
fortnightly), service minutes. We run 2 crews, 5 days a week, about
7.5 hours of service time per crew-day.
Group customers into 10 crew-days so each day covers one compact
area and the service minutes are roughly balanced.
Keep fortnightly neighbours on the same day and week.
List any customer who doesn't fit a zone well, with the reason.
Don't calculate driving distances; I'll check those in a map tool.

An illustrative extract of the reply:

Crew A Mon  Riverside and old centre   14 stops  7.2 service hrs
Crew A Tue  North estate               15 stops  7.4 service hrs
Crew B Mon  Hillside villages          12 stops  7.6 service hrs
...
Doesn't fit well:
- Customer 112 (fortnightly, 50 min): far from other Monday stops.
  Nearest cluster is Crew B Thursday (industrial side). Needs the
  customer to agree a day change.
- Customers 45 and 46 are neighbours on different days; move 46
  to Wednesday to match.

That last kind of line is where money hides. Two neighbours on different days means driving to the same street twice. Check the zones on a map before announcing anything, and remember that the AI's sense of "close" comes from names, not road layouts: a river with one bridge can make two "neighbouring" areas twenty minutes apart.

Reordering stops inside a day: the tools and their limits

Once each day covers a compact area, a routing tool puts the stops in the best order using real road distances. The options, as of September 2026:

Two points from that table matter for landscapers. The Google Maps help page caps a route at nine stops and leaves the order to you, so a 14-stop day won't fit and won't be optimised. And Jobber's route optimisation only moves visits with no fixed time, so if you've booked every customer at a set time out of habit, switch the flexible ones to anytime visits first.

For two crews doing about 140 stops a week, roughly 600 a month, Routific's $150 plan or two OptimoRoute Lite drivers at about $70 a month are the obvious stand-alone candidates; if you already run Jobber on an eligible plan, try its optimiser before paying for anything. Wider fleet options are compared in route planning for small fleets and mobile teams.

Constraints the optimiser needs to know

A route that's shortest on a map can be wrong on the ground. Give the tool, or your planning prompt, the constraints your crews live with:

• Service time per stop, which varies with property size and season; spring cuts take longer than midsummer ones.
• Time windows: commercial sites before opening, schools outside hours, customers who want to be home.
• Tip and yard hours: where green waste goes and when it closes. A crew arriving at 15:50 to a tip that shuts at 16:00 loses the day's last hour.
• Trailer realities: narrow lanes, turning space and parking with a trailer attached.
• Equipment: which crew has the ride-on mower, which has the hedge cutters.
• Breaks and fuel stops.
• Access notes: gate codes, dogs, side access only.

Two crews, one season: the numbers worked through

Here is an illustrative landscaping firm running two crews of two on weekly and fortnightly mowing and maintenance, 14 stops a crew-day. The round grew over six years, with new customers slotted in wherever there was space.

Of crew A's 90 saved miles, about 65 came from regrouping area-days and 25 from reordering stops within each day; crew B's split was similar. Across both crews, that's 165 miles and 7.5 crew-hours a week.

• Fuel: 165 miles x $0.40 = $66 a week, or about $2,640 over a 40-week season.
• Time: 7.5 crew-hours is 15 labour hours a week, because each crew is two people.

The fuel figure is real money straight away. The time figure is only worth something if you use it, which is the next section.

Turning saved hours into money, or not

Saved drive time has no value if crews simply finish their 14 stops earlier and go home on the same pay. There are three ways to bank it:

1. Add stops. In the example, 7.5 crew-hours at about 40 minutes per extra stop (including short drives within the zone) is room for roughly 10 more weekly customers without adding a crew. At an illustrative $45 a visit, that's about $450 a week of capacity, if the sales are there.
2. Cut overtime. If crews regularly run past their paid hours, the saving shows up as lower overtime.
3. Protect quality. Some firms use the time for edging and tidying that was being rushed. It's harder to measure, but it shows in fewer complaints and better renewals.

Decide which before the new routes start, or the hours quietly disappear. If extra stops are the plan, make sure the price per stop covers the cost of the visit; how landscapers stop underpricing jobs shows how to check.

Checking the saving after four weeks

One good week proves little; traffic, weather and a couple of cancelled visits can swing miles by 10% on their own. Run the new routes for four weeks and compare them with four comparable weeks before, per crew, on the same measures as your baseline. Then paste both sets into a chat and ask for a plain comparison:

Here are 4 weeks of crew data before the route change and 4 weeks
after: miles, drive hours, stops, overtime hours, tip runs.
Compare the averages per stop, not just the totals, and point out
anything that might explain the difference other than the routes
(fewer stops, shorter days, weather notes).

Asking per stop matters. If crews did fewer stops after the change because of a wet fortnight, total miles fall for reasons that have nothing to do with routing. An illustrative reading: "Miles per stop fell from 3.0 to 2.3 for crew A and from 2.7 to 2.2 for crew B. Stops were within two of the baseline each week, so the change isn't explained by lower volume. Tip runs were unchanged."

If the saving turns out small, say under 5% of miles, that's useful news: your round was already well organised, and the money is better spent elsewhere. If it's large, lock the area-days in before the next season's new customers start pulling them apart.

Keeping routes tight as customers come and go

Zones erode. Every new customer slotted into "whichever day has space" pulls a route apart a little. Make placement a rule instead, and let AI apply it:

New customer: [area, street], weekly, about 35 minutes.
Using our current crew-days, which crew and day adds the least
driving, and does that day have room for 35 more minutes of service?
Give the two best options and why.

An illustrative reply: "Best: Crew B Wednesday, whose nearest existing stops are on the next street; that day currently has 6.9 service hours, so there's room. Second: Crew A Tuesday, one area over, which would add more driving." Check the suggestion in your routing tool before telling the customer their day. The same placement habit is used by mobile businesses in other sectors, such as mobile dog groomers planning routes and rebookings.

Rain days: a catch-up rule the AI can apply

A lost day is where good routes fall apart, because the catch-up gets planned in a hurry on a phone at 7 a.m. Write the rule down once, in the order you'd apply it:

1. Commercial contracts with fixed days move first, to the next day their site allows.
2. Weekly domestic customers move next, to the nearest crew-day with room in the same or a neighbouring area.
3. Fortnightly customers may slip a week if they agree, rather than overloading a day.
4. No day gets more than 45 extra minutes of service time; anything left over goes to the following week.

Then the morning prompt is short: "Tuesday was rained off for crew A (15 stops). Apply the catch-up rule across Wednesday to Friday for both crews and list who needs a text." In an illustrative run, the AI spread the fifteen visits sensibly but put a small business park on Friday afternoon. That site only allows access before 10:00, a fact that lived in the office manager's head rather than the customer list. The fix was a time-window column in the list, not a better prompt. The customer text it drafted needed only a light edit:

Hi, yesterday's rain meant we couldn't cut your lawn. We'll be with you on Thursday instead; no need to be in. Reply if Thursday doesn't suit and we'll find another day.

Customers outside the zones: price the drive or let them go

Once the zones exist, a few customers always sit awkwardly outside them. Put a number on each one before deciding. Take customer 112 from the zoning example: about 11 miles from the nearest Monday stop, so roughly a 22-mile detour and 35 minutes of extra crew time per visit.

• Fuel: 22 miles x $0.40 = $8.80
• Labour: 35 minutes x 2 people x an illustrative $25 an hour = about $29
• Extra cost per visit: about $38, against a visit price of $45

That customer barely covers the drive, before mowing a blade of grass. The options are to move them to a day when a crew is nearby anyway, to add a travel charge, or to give notice politely at the end of the season. Ask your routing tool for the extra distance each stop adds, list the worst ten, and run the same sum for each. The AI can then draft the day-change or price-change messages, which are awkward to write and easy to get wrong in tone.

One person, one van: the same logic, smaller numbers

A sole-trader gardener doing six to eight gardens a day gets the same benefit on a smaller scale. The day-grouping step still matters most: moving from "whoever rang first" to two or three areas across the week can save a noticeable share of weekly miles on its own. With seven or eight stops a day, Google Maps' nine-stop limit often fits, and ordering the stops by hand on the map is quick.

If you'd rather have a tool order them, watch the free tiers: Routific's free plan covers up to 100 orders a month, and a sole trader doing six visits a day, four days a week, reaches about 103 in a typical month. In that position it's worth deciding whether the $150 plan is justified or whether a few minutes with the map each evening does the job. For one person, it usually does.

Where route optimisation disappoints

• It ignores what it isn't told. In one illustrative week, an optimiser sent a crew through a busy junction where turning across traffic with a trailer takes ten minutes at school-run time. Add a time window or a note, and re-run.
• Customers who won't move day. Plan around them rather than fighting; they're fixed points in the zone.
• Weather reshuffles. After a rain day, the catch-up plan matters more than the perfect plan. Keep a rule for which customers move first.
• Season changes. Autumn leaf clearance and hedge work have different durations and tip runs from mowing. Re-check the zones when the work mix changes.

For how routing fits alongside job scheduling and dispatch more broadly, see AI job scheduling and dispatch for field service teams, and if you're deciding where AI should come first in a landscaping business, why most landscapers haven't adopted AI yet, and where to start.

Route planning questions from landscaping firms

Can ChatGPT or Claude plan my crews' routes on their own?

They're useful for grouping customers into area-days and for checking a plan against your rules, but they aren't routing engines. Unless they're connected to a mapping service, their mileage and drive-time figures are estimates that can be badly wrong. Use a general AI for the grouping and the reasoning, and a routing tool or your job software for the actual stop order and distances.

Will customers accept a change of day?

Most will if you ask early, explain that it keeps prices steady, and offer a choice of two days. Expect a handful who insist on their current day; keep them, and plan the rest of the zone around them. Change days at the start of a season rather than mid-season, and confirm each change in writing so crews and customers work from the same list.

How often should routes be re-optimised?

Re-group area-days once or twice a year, typically before the main mowing season and again when the work shifts to autumn clear-ups and hedges. Re-order stops weekly or whenever the day's list changes, which a routing tool does in seconds. Place new customers into the best existing day as they join, so the zones don't erode between the bigger reviews.

Further reads

• Can a Small Courier Firm Use AI to Plan Delivery Routes? — How a delivery business approaches the same routing problem.
• Jobber, Housecall Pro, and ServiceTitan AI Features Compared — Compare field-service tools if routing pushes you to change software.
• AI Garden Design Visuals in Quotes: Do They Help Close Jobs? — Use the time saved to win design-and-build work.
• Why AI Saves Time but Not Money, and How to Capture the Gain — Why saved hours only count when you convert them into something.
• What Tradespeople Actually Use AI For: 12 Real Jobs It Handles — Other everyday jobs AI handles for trades and outdoor businesses.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Google Maps Help on multiple stops; Jobber help article on route optimisation; OptimoRoute and Routific pricing pages. Checked September 2026.