FieldproxyAI-native field service software

Routing

How do I route 1,000 lawns a week across my crews?

Split your service area into one zone per crew-day first, so each crew mows one tight cluster per day, then give every property a fixed mow day inside its zone, and only then put the stops in drive order. Size each zone by mow-hours, not by stop count: add up the measured mow time of every property plus the drive between them and keep it inside the crew's working day. Then keep it balanced: slot new customers into the zone that has room, rebalance the zones once a month, and keep a planned flex day for rain and skips.

  • Order of work: zones, then fixed mow days, then stop order. Optimizing stop order alone cannot fix scattered zones.
  • Capacity is mow-hours plus drive minutes per crew-day, not stops per day.
  • Measure drive minutes per stop and drive share of the day for every crew, every week.
  • Gate codes, dogs, time windows and equipment fit are constraints on the route, not notes on the job.
  • Plan rain: one flex day a week and a written rule for which stops move first.

Book your demo

A video call with our team

Number of employees

This page is about building and keeping a weekly mowing route for many crews. Fitting one new customer into an existing route is a smaller job, covered on our page about slotting a new job into a recurring route.

Facts checked as of November 2026. Sources at the end of the page.

Step by step

How to route a full week of mowing, step by step

At 1,000 lawns a week the hard part is not the order of stops inside one day. It is which crew mows which neighborhood on which day. Work from the top down.

1. Decide fixed day or dynamic

Fixed day means every property is mowed on the same weekday each week, by the same crew where possible. Dynamic means software rebuilds the week from whatever is due. Weekly mowing usually suits fixed days: customers know when to leave the gate unlocked, crews learn the properties, and the route only changes when you change it. Dynamic routing suits rounds that are not weekly, like fertilizer and weed control applications, and it is useful for rebuilding a day after rain.

2. Build zones before anything else

Draw the boundary of where you will work, then cut it into zones, one per crew-day. With 10 crews and 5 mowing days that is 50 zones of roughly 20 stops each. Use roads that crews actually drive, rivers and highways as natural borders, and keep each zone near the yard or the crew lead's start point. A property outside every zone is a pricing or a selling decision, not a routing one.

3. Give each zone a day of the week

Pair zones that sit next to each other on neighboring days, so a crew that runs late on Tuesday finishes in a zone that borders Wednesday's. Put the zones farthest from the yard on the days least likely to be rained out in your area, if you have a pattern, and keep the closest zones for the flex day.

4. Size each zone in mow-hours

For every property, record the real mow time for its crew size: mow, trim, edge and blow. Add the drive between stops and the drive out from and back to the yard. That total must fit the crew's working day with a margin (e.g. 30 minutes) for breaks and fuel. A zone of 15 large lots can be fuller than a zone of 30 small ones.

5. Match equipment to property size

Record the narrowest gate and whether a property needs a walk-behind or push mower, so a crew with only wide-deck riders is never routed to a backyard behind a 36 inch gate. Group large open properties into zones for crews with larger decks, and small lots into zones for crews with smaller mowers, so the time estimate per stop holds.

6. Add the constraints that break routes

Gate codes, dogs that must be in, no-mow-before times at schools or offices, HOA rules, and customer time windows. Put each one in a field on the property, not in a free text note, so the route can respect it and the crew sees it at the stop.

7. Only now, put the stops in order

Within each zone and day, order stops by drive time from the start point and back. This is where a route optimizer earns its keep, and where it is quickest to run. Keep the order stable from week to week unless something changes, so customers see the crew at about the same time.

8. Slot new customers, and rebalance monthly

A new customer goes into the zone that already passes their street and still has mow-hours left (see the related page on slotting a new job). Once a month, compare each zone's planned hours with its actual hours and move border properties from the fullest zones to their neighbors. That keeps the routes from drifting the way they do when they were built years ago.

9. Plan skips and rain

A skip (gate locked, customer asked to skip, too wet) is recorded at the stop with a reason, so the office can decide whether it moves or waits a week. For rain, write the rule down: e.g. a rained-out day shifts forward one day and the flex day absorbs the overflow, with time-window customers moved first.

10. Measure drive time against mow time

Each week, for every crew-day, compare the drive minutes with the on-site minutes from check-in and check-out. Track drive minutes per stop and drive share of the day. RealGreen's own routing guide suggests keeping drive time below 20 percent of total paid hours. Whatever target you choose, the zone with the worst number is the next one to redraw.

Failure modes

Why lawn routes go wrong

Routes built years ago, never redrawn

The routes made sense when they were made. Then customers cancelled in one area and signed up in another, and each new customer was added to whichever crew had a gap. The zones now overlap, and two crews drive past each other every day.

Optimizing stop order inside bad zones

Running an optimizer on each day's list puts the stops in a better order, but it cannot fix a day that covers three neighborhoods across town. Most drive time is lost between clusters, not inside them.

Stops per day as the capacity number

When the rule is 20 stops a day, a crew with three large commercial lots in its 20 runs late and a crew with 20 small lots finishes early. Mow-hours are the real capacity.

Constraints that live in someone's head

The gate code, the dog, the customer who wants the crew after 10 am. When only the crew lead knows them, every new or covering crew loses time at the stop or skips it.

Rain turns into a rebuild

With no flex day and no written rule, two days of rain mean the office rebuilds the whole week by hand while customers call to ask when they will be mowed.

Nobody measures the drive

If drive minutes are not compared with mow minutes per crew-day, the routes only get looked at when a crew complains or overtime jumps.

Options

Ways to do it

Real tools, as their own help pages and announcements describe them in November 2026. Most are fine at putting stops in order. Ask each one how it handles zones, fixed mow days, mow-hour capacity and rain.

ApproachHow routing worksWatch for
Service AutopilotService Autopilot announced AI route optimization through its NextBillion.ai integration, used through the Optimized Stops feature in the Dispatch Board or its Smart Maps feature. The announcement says it analyzes traffic patterns, service locations and other constraints.We could not find a public help article with the steps or limits, so ask for a demo on a full week of your own properties and crews.
RealGreen Dynamic RoutingBuilds a day's route automatically and honors technician skills, licensing, vehicle capacity and customer time windows, using road data and historical traffic. Planners can draw around stops with a polygon tool and add stops with a lasso on the map. Unfinished work becomes loose work that can be moved in bulk.Built mainly for application rounds (fertilizer, weed control). Check how it holds a fixed weekly mow day for each property.
Jobber route optimizationArranges anytime visits in the best order for one team member, a group or the whole team, up to 7 days at once. Available on Connect, Grow and Plus, run by admin users on the web.Visits with a set start or end time cannot be optimized, so time-window customers sit outside the route. It orders stops; zoning is up to you.
GorillaDesk Mantis AI routing (beta)Clusters jobs by proximity and respects service hours, max jobs per day, travel limits per shift, technician regions, a freeze window for jobs that must not move, and start and end addresses. On the Growth plan.Its help article says applying changes to the live calendar is not yet available; you test in a sandbox first.
Aspire route scheduling and optimizationSeparates route scheduling (which crew and day) from route optimization (stop order). Routes can be reordered by hand on the route scheduling map, and optimization uses a start and end point set per day by the route manager.Aspire's guide says route optimization is limited to 25 visits and needs the Route Optimization permission. Enough for one crew-day, not a whole week in one run.
A standalone route planner (OptimoRoute, Routific)OptimoRoute plans up to 700 orders at once on Lite and up to 1,000 on Pro, with weekly planning on Custom (contact them to activate on Pro). Routific's API minimizes driving time and working hours by default and can insert a new order into existing routes.A second system next to your CRM and billing. Properties, skips and completions have to move between the two every week.
FieldproxyRecurring visits per property, route planning for each crew's day, a drag-and-drop board, and drive time and best order calculated for the stops. Crews see their route on the phone, with offline mode and GPS check-in. AI agents can rebuild a day around weather or a missing crew, and a person approves before anything changes.Set up around your routes and rules, so bring your current routes and decide your capacity margin and rain rule before the first test.

Vendor facts come from each vendor's own help pages, pricing pages or announcements, linked in Sources. Features change; confirm in a demo with a full week of your own properties.

Worked example

A worked example: 1,050 lawns, 10 crews, 5 days

This is an illustrative calculation with made-up but realistic inputs, not data from any company. Say you mow 1,050 properties a week with 10 crews over 5 days. That is 50 crew-days, and 1,050 / 50 = 21 stops per crew-day on average. Average on-site time is 17 minutes per stop, and the drive out from the yard and back is 50 minutes a day.

Before zoning, the routes were built years ago and each crew-day covers two or three neighborhoods. Measured drive between stops averages 8 minutes per stop. After the area is redrawn into 50 zones, one per crew-day, drive between stops falls to an assumed 5 minutes per stop, because most stops are now a few streets apart.

Per crew-dayBefore zoningAfter zoning
Stops2121
On-site time (21 x 17 min)357 min357 min
Drive between stops21 x 8 = 168 min21 x 5 = 105 min
Yard out and back50 min50 min
Total drive218 min155 min
Total day575 min (9 h 35 min)512 min (8 h 32 min)
Drive share of the day218 / 575 = 37.9%155 / 512 = 30.3%

Illustrative calculation. The 8 and 5 minute drive figures are assumptions for the example; measure your own from GPS check-ins.

Each crew-day saves 63 minutes of driving. Across 50 crew-days that is 63 x 50 = 3,150 minutes, or 52.5 crew-hours a week, without a single stop being dropped.

You can spend that time two ways. Either crews finish about an hour earlier, which takes most days out of overtime, or each zone takes on more work: at 17 minutes on site plus 5 minutes of drive, one more stop costs 22 minutes, so 63 minutes is room for about 2 more stops per crew-day, around 100 more properties a week with the same crews.

The stop order inside each day barely changed in this example. Almost all the saving came from step 2, the zones. That is why the order of work matters: zones, then days, then stops.

Before you buy

What to check before you choose a tool

Good signs

  • Each property has a recurring visit with a fixed mow day and crew, not a copy of last week's job.
  • Zones or territories are a real record you can draw, name and assign to a crew-day.
  • Capacity is counted in mow-hours plus drive time, with a margin you set.
  • Gate codes, dogs, time windows and mower size are fields the route respects and the crew sees at the stop.
  • You can optimize the stop order of a whole crew-day without moving properties to other days.
  • Skips are recorded at the stop with a reason, and a rained-out day can move in one action.
  • A weekly report shows drive minutes per stop and drive share for each crew.
  • Crews get their route on the phone and it works with no signal.

Red flags

  • The only routing action re-optimizes everything and moves customers to new days.
  • Visits with a time window cannot be included in the optimized route.
  • Optimization has a small stop limit that does not cover a full crew-day.
  • Routing lives in a separate planner, and completions and skips are typed back by hand.
  • Capacity is a stop count per day, so a large lot and a small lot count the same.

In Fieldproxy

Setting it up in Fieldproxy

Fieldproxy is set up around how your routes work today, so setup starts from your current customer list and crew routes. Settings marked e.g. are examples.

Recurring visits per property

Each property carries its recurring mowing visit with its frequency, mow day, crew, measured mow time, and fields for gate code, dogs, time window and mower size (e.g. Walk-behind only). Your current routes are imported as they are, so crews start on the routes they know.

Route planning for each crew's day

Each crew-day is planned on a drag-and-drop board, with drive time and the best order calculated for the stops. The day total shows mow-hours and drive time against the crew's working day, so an overloaded day is visible before the crew leaves.

Crews on the phone

Crews see their route on the Android or iOS app, with offline mode for areas with no signal and GPS check-in and check-out at each stop. Those times update each property's real mow time and give you drive time against mow time per crew-day. See the mobile app page.

Rain days and crew changes

When rain or a missing crew breaks a day, AI agents can rebuild it around your rule (e.g. move the day forward and fill the flex day, time-window customers first). In the Command Center (/agents/command-center) you ask for it in plain English, and every change comes as a confirm card a person approves, with Undo.

New customers and drift

The Dispatch agent (/agents/dispatch-agent) suggests the crew by distance and skills when a new property is added. The Watcher agent (/agents/watcher-agent) flags crew-days that go over the day limit and properties that are due but not on a route.

Weekly route report

The Scheduler agent (/agents/scheduler-agent) can email a weekly report (e.g. drive minutes per stop and drive share by crew), so the next zone to redraw is obvious. One price per company with unlimited users, so every crew lead has a login; see /pricing.

How switching works

How switching to Fieldproxy works

We move your data over and set the system up to the way you already work. Fieldproxy replaces the old tool; it does not run alongside it.

  1. Send your customer list and routes

    Every property with address, frequency, mow day, crew and price, plus your yard locations. Free, assisted migration: we import it for you.
  2. We set up your rules

    Crews and mower sizes, working day and margin, property constraints, skip reasons and your rain rule.
  3. We run one real week

    Your current week next to a zoned version, with drive minutes per stop for each crew-day, so you can see the difference on your own properties.
  4. Crews go live

    Live within a day: crews get the app with their routes, and the office runs the board from there.

FAQ

Questions people ask

What is the best way to route lawn mowing crews?
Zones first, then a fixed mow day for each property, then stop order inside each day. Most wasted drive time is between neighborhoods, so stop-order optimization alone recovers little if the zones are scattered.
Should lawn care routes be fixed or dynamic?
Weekly mowing usually works best on fixed days, because customers and crews know when each property is mowed. Dynamic routing fits application rounds that are not weekly and is useful for rebuilding a day after rain.
How many lawns can one crew mow in a day?
It depends on property size, crew size, mower deck and drive time, so count mow-hours, not stops. Measure the real on-site time per property from check-ins and fill each crew-day to its working hours with a margin.
How often should I rebalance routes?
Compare planned and actual hours per zone every month and move border properties from the fullest zones to their neighbors. Redraw the whole map at the start of a season, and tell affected customers before their day changes.
What happens to a route when it rains?
Have a written rule and a flex day. A common rule is that a rained-out day shifts forward one day, the flex day takes the overflow, and customers with time windows are moved first.
Do I need a separate route planner, or can my field service software do it?
A standalone planner can plan large numbers of stops at once, but properties, skips and completions then have to move between two systems every week. If your field service software can zone, hold fixed days and order stops, keeping it in one place saves that work.
How do I add a new customer without breaking my routes?
Put them on the zone and day that already passes their street and still has mow-hours left, and insert the stop without reordering the others. Our page on slotting a new job into a recurring route walks through it.

Sources

Competitor details on this page come from the vendors' own pages and documentation, checked as of November 2026. Plans and prices change, so check the vendor's current page before you decide.

See it built on your workflow

Tell us how your jobs run today. We build a demo on your stages, forms and pricing before the call.