The Complete Guide to Recurring Lawn Care Scheduling and Crew Routing

Recurring lawn care looks simple from the outside. A customer signs up, a crew shows up every week or two, the grass gets cut, and an invoice goes out. Anyone who has actually run a route through a full season knows the reality is messier. Grass does not grow on a fixed calendar. It grows on soil temperature, daylight, rainfall, and fertilizer, and it ignores whatever your spreadsheet says. Crews get sick, mowers throw belts, a rainy Tuesday pushes forty stops into Wednesday, and a customer who was comfortable on a ten day cycle in early May suddenly needs weekly service by June. The recurring schedule is the spine of the business. When it bends too far, everything attached to it bends with it: cash flow, customer trust, crew morale, and your own weekends.

This guide is our attempt to lay out the whole system in one place. We build scheduling and routing software for lawn care companies, which means we spend most of our days talking with operators about what breaks and why. What follows is organized into seven themes: the agronomy that sets your cadence, how to build the recurring schedule itself, how to route crews efficiently across many properties, how to handle weather and rain days without losing the week, how to keep property knowledge from living in one person's head, how to price recurring plans, and finally how to think about software without letting it run the business. Each theme links to deeper articles on this blog. Read it straight through before the season, or jump to the part that is hurting you this week.

The Agronomy That Sets Your Cadence

Grass growth rate drives everything else in this guide, so it is worth understanding before touching a calendar. The rule most turf professionals follow is the one third rule: never remove more than a third of the leaf blade in a single mowing. If a lawn is maintained at three inches, you want to cut it when it reaches roughly four and a half inches. During the spring flush on a cool season lawn, that can happen in five to seven days. In the heat of midsummer, the same lawn may take ten to fourteen days to reach the same height, and an unirrigated lawn may barely grow at all. A recurring schedule that ignores this curve ends up doing one of two things: scalping lawns when growth is slow, or leaving customers with shaggy, clumpy yards when growth is fast.

Mowing height matters as much as frequency, and it is the setting most crews get wrong for the sake of speed. Taller grass shades the soil, keeps the crown and roots cooler, shades out germinating weed seeds, and tolerates drought and foot traffic far better than a short cut. Most cool season turf does best somewhere in the three to four inch range through summer. Many warm season varieties are kept shorter, often between one and two and a half inches depending on the species and how the customer wants the lawn to look. Operators who standardize deck height across an entire route create a slow disaster: lawns scalped in July thin out, weeds move in during August, and by September the customer is blaming the service for a problem the service caused. Mowing height should be a per property setting that is recorded and followed, not a crew habit.

Cool season and warm season grasses need genuinely different recurring calendars, and it helps to treat them as two different products. Cool season lawns (tall fescue, Kentucky bluegrass, perennial ryegrass) across the northern half of the country have two growth peaks, one in spring and one in fall, with a summer slowdown in between. Warm season lawns (bermuda, zoysia, St. Augustine, centipede) across the South have one long peak that runs from late spring through early fall, then go brown and dormant in winter. Transition zone operators in places like Kansas City, Nashville, or Raleigh frequently handle both types on the same route. Build your service tiers around these curves rather than around a flat weekly template, and the schedule will match what the grass is actually doing.

Building a Recurring Schedule That Holds Up

A recurring schedule is a promise made to dozens or hundreds of customers at once, so the interval decision deserves more thought than it usually gets. The common options are weekly, every ten days, biweekly, or a seasonal blend of all three. Weekly is the easiest to route and the easiest for customers to understand, and it keeps clippings small enough to mulch back into the lawn without clumping. Ten day cycles are agronomically sensible in many regions, but they are hard to route because the day of the week drifts and the customer never knows when to expect you. Biweekly is popular with budget conscious customers, but during peak growth it usually means removing far more than a third of the blade, which stresses the lawn, slows the crew, and produces a cut that looks worse than the price savings justify.

Seasonal ramping is what separates a real schedule from a template copied off a calendar. Many operators run a spring ramp (weekly from April or May depending on latitude), a summer plateau (weekly for irrigated lawns, every ten days for unirrigated ones in hot regions), and a fall taper (every ten to fourteen days down to the final cut of the year). The important part is deciding these transitions in advance and writing them into the service agreement, rather than negotiating every change over text messages in June when both you and the customer are frustrated. Customers accept a schedule change gracefully when it was part of the plan from day one. They resist it when it feels like a surprise, even if the agronomy is on your side.

The last piece is capacity math, and it is where most schedule failures actually begin. Count the productive crew hours you have per week, subtract realistic drive time, loading, fueling, and a buffer for breakdowns, and you get the number of stops you can actually complete. Every recurring customer consumes a slot every cycle, forever. Overbooking by even a handful of stops in May means the schedule slips a day each week, and by mid June the Monday route is quietly running on Thursday. Leave room for weather days and for the one week a year when everything grows at once. As a working rule of thumb, a schedule with slack holds together; a schedule booked to the last hour breaks the first time it rains.

Routing Crews Across Many Properties

Drive time is unpaid time, and it is the single largest hidden cost in recurring lawn care. Picture a crew that completes twenty five stops in a day with an average of eight minutes of driving between them. That is well over three hours of the workday spent in the truck, and none of it appears on an invoice. Cut the average gap to four minutes and the crew gets back most of two hours, which is typically four to six more properties or an earlier finish and a happier crew. Route density is the biggest lever on profitability that most operators control, and it is worth more than a modest price increase per cut. A tight route at an average price beats a scattered route at a premium price nearly every time.

The practical routing principles are not complicated, but they require discipline. Cluster customers by neighborhood and assign service days by geography, never by the order customers happened to sign up. Put the largest or most equipment heavy properties at the start of the day when the crew is fresh and the trailer is fully loaded. Sequence the day to minimize backtracking and left turns across busy roads, and keep the last stop near the shop or near the dump site if you haul clippings. When a new customer signs up outside an existing cluster, either price the drive into the quote or politely decline. Growth by density beats growth by geography, and saying no to the wrong customer is one of the most profitable decisions an operator can make.

Routes decay over time, which is why routing is a recurring task and not a one time setup. Customers churn, new ones join, a crew member leaves and takes their local knowledge with them, and a route that was tight in April is scattered by August. Put a quarterly route review on the calendar and use it to rebalance crews and days. Routing software can optimize the stop sequence within a single day, but the decision about which day each neighborhood belongs to is still a human decision, and it is the one that matters most. Make that decision carefully and the daily optimization becomes almost trivial. Skip it and no algorithm will save the week.

Weather, Rain Days, and Rescheduling

Wet grass is the scheduling enemy. Mowing saturated turf leaves ruts from the mower wheels, clumps the clippings into mats that smother the grass underneath, spreads fungal disease from blade to blade, and produces an uneven, torn cut that customers notice immediately. But not all rain is equal. A light shower that ends by mid morning usually allows an afternoon mow on a well drained sandy lawn. Heavy overnight rain on compacted clay soil may mean waiting a full day or more. The decision is never just whether it is raining. The real question is how wet the soil is right now and how fast it drains at each specific property, which is why local knowledge and per property notes matter so much for weather calls.

A handful of weather signals should trigger a rescheduling decision each week: rainfall totals over the past twenty four to forty eight hours, the hourly forecast for the service window rather than the daily summary, the soil type and drainage on the route, temperature (heat advisories slow crews and stress lawns, and mowing during extreme heat can do real damage), and wind, which matters for spraying and for blowing debris. The best operators make the call the evening before, not at seven in the morning with the crew already in the truck and the customers already expecting them. And they communicate the decision. A short message to affected customers saying the crew will come tomorrow builds trust. Silence followed by a no show erodes it.

Every rain day compresses the rest of the week, so the recovery plan matters more than the delay itself. The options are familiar: run longer days, push the missed route to Saturday, split the missed stops across the remaining days, or, in a low growth week in fall, simply skip and resume on the next cycle. The key is having the recovery rule written down before the season starts. Crews who know that rain on Monday means a Saturday makeup can plan their lives around it, and customers on a recurring plan should know the same rule from their agreement. The schedule survives the weather because it has a rule, not because it never rains.

Property Knowledge and Crew Handoffs

Every property has quirks. A gate code, a dog that is friendly until it is not, a sprinkler head lurking near the sidewalk, a customer who insists on bagged clippings, a slope that needs the smaller mower, a neighbor who complains about blowing before nine. In a one crew company, the owner carries all of this in their head and it mostly works. By the time there are three crews and a seasonal hire who started last week, the knowledge is scattered across text threads, sticky notes, and memory. Per property notes are the fix, but only if they are short, current, and visible at the exact moment the crew pulls up to the curb. Notes buried in an office system that the crew never opens are the same as no notes at all.

What makes a property note useful is structure and restraint. One screen, most important item first, updated by whoever noticed the change, and dated so the crew knows whether it is still relevant. A note that reads "sprinkler head by the mailbox, marked with a flag, 2026-09-07" is useful. A paragraph of history about the previous owner is not. Standardize a small set of fields that every property gets: access instructions, hazards, mowing height, edging and trimming preferences, clipping disposal, and how the customer prefers to be contacted. Then let a free text field handle everything else. Crews will actually read six labeled lines. They will not read six paragraphs.

Properties change between visits, and crews need a clear protocol for what to do when they arrive and something is different. A new fence, a freshly planted bed, a construction dumpster in the driveway, a tree that came down in last night's storm, a newly seeded patch that looks like bare dirt. The protocol should be simple: photograph it, add a note, do what is safe and obvious, skip what is unclear, and flag it for the office to confirm with the customer before the next visit. The worst outcome is a crew guessing, mowing straight over a new seeded area or a buried drip line, and the customer discovering it when the invoice arrives. A thirty second photo and a skipped section costs almost nothing. A ruined seeding job costs the account.

Pricing Recurring Mowing Plans

Pricing a recurring plan starts with knowing your true cost per stop, and surprisingly few operators do. Add up labor hours including drive time, equipment depreciation and repairs, fuel, insurance, and a fair share of overhead like the shop, the phone, and the software, then divide by the number of stops a crew actually completes in a week, not the number you hoped for. That figure is your floor. Add the margin you need to grow and you have a price. Operators who set prices by asking what the company down the street charges, without knowing their own cost per stop, are guessing, and many of them discover in August that their biweekly customers have been losing money for the entire season.

The structure of the plan matters as much as the number. Per visit pricing is simple and transparent, but revenue swings with weather and season, which makes payroll stressful in a rainy month. Flat monthly pricing smooths cash flow and customers like the predictability, but you have to set the annual visit count honestly and explain that a summer month with five visits and a fall month with two cost the same. Seasonal contracts sell a defined number of visits across the season for a fixed total, often billed in installments, and they pair well with the seasonal ramp described earlier. Whichever structure you choose, write the visit count and the rain policy into the agreement so that nobody is arguing about a skipped week in October.

Bundling and add-ons are where recurring plans become profitable rather than merely sustainable. Edging and string trimming should be part of every mowing visit, because customers judge the cut by the edges. Bagging, bed maintenance, fertilization, weed control, aeration, overseeding, and leaf cleanup should be add-ons or separate plans with their own pricing. Raise prices once a year and say so in the agreement in advance, because a planned increase is accepted and a surprise increase is churn. Charge for drive time when a property sits outside your service cluster. And track cost per stop by crew and by route, because a price that works beautifully on a dense route fails quietly on a scattered one.

Choosing Software Without Losing the Plot

Software should do three things for a recurring lawn care business, and everything else is secondary. First, it should hold the recurring schedule and generate visits automatically, including the seasonal interval changes, so nobody is recreating jobs by hand every spring. Second, it should sequence and rebalance routes on a map so the drive time analysis from earlier in this guide becomes something you can see rather than something you estimate. Third, it should put property notes in front of the crew on their phone at the moment they arrive. Invoicing, payments, a customer portal, and marketing tools are all useful, but if a tool does the three core things badly, no amount of polish on the invoice template will rescue the week.

When evaluating tools, look for a few specific capabilities rather than long feature lists. Recurring rules that support seasonal changes without deleting and rebuilding every job. Drag and drop route reordering with an actual map, not just a list. A mobile app for crews that works reliably with a weak signal, because half your route may be in a cellular dead zone. A rain delay function that shifts an entire day at once and notifies affected customers in a single action. Notes that surface automatically at the stop instead of hiding behind three taps. Be honest about company size, too. A solo operator with thirty customers may be fine with a spreadsheet and a calendar for another season. A three crew company with two hundred recurring customers is not, and pretending otherwise costs more in lost hours than any subscription.

Our honest view, since we build LawnCadence for exactly this problem: the software is only ever as good as the operating rules behind it. Decide your intervals, your rain policy, your note standards, your route review cadence, and your pricing model first. Then pick a tool that enforces those decisions consistently across every crew and every week. Operators who buy software hoping it will invent the rules for them are usually disappointed. Operators who arrive with the rules already written find that the software makes them stick, and that is where the real gains come from. The tool is a way to keep promises at scale. It cannot decide which promises to make.

More guides on this topic

Further reading from the LawnCadence blog, each answering one specific question in depth.

Recurring lawn care is a rhythm business. The grass sets the tempo, the weather interrupts it, and the operator's job is to build a schedule and a set of rules that keep the rhythm going anyway. Start with the agronomy, because it tells you how often each lawn genuinely needs a cut and how high to cut it. Turn that into a seasonal recurring schedule with real capacity behind it. Route by density and review the routes every quarter. Write down the rain rule and the recovery rule before the first storm. Put property knowledge into short, dated notes that crews actually read. Price from your real cost per stop and structure plans so cash flow is predictable. Then, and only then, choose software that makes all of it repeatable. None of these steps is complicated on its own. The operators who thrive are simply the ones who do all of them, every season, without letting any single piece slide.