What to do when the route is full

It's Tuesday morning. You've got 6 new quote requests from the weekend, a route of 38 weekly accounts, and a truck that pulls out of the driveway at 6:45. You can't take all of them. You might not be able to take any of them.

Welcome to mid-May.

This is the part of the season nobody talks about. The first six weeks are a sprint. You take everything. You quote everything. You squeeze the new ones in because the route still has gaps. Then around the second week of May the gaps close, and the requests keep coming, and the question changes from "how do I get more customers" to "what do I do with the ones I can't take."

Most operators handle this badly. They quote anyway, hoping the customer says no on price. Or they ghost the request. Or they take the job and pay for it three weeks later when Saturday turns into a 12-hour day to keep up. None of those are the move.

This is about the move.

First, know what full actually means

Full is not a feeling. It's a number.

The number is your sustainable weekly stop count, at your real average drive time and average job duration, with a buffer for rain days and equipment hiccups. For most solo operators on residential routes, that often lands somewhere between 28 and 45 weekly mows depending on lot size and density. Tight-density suburban routes push higher. Rural or large-lot routes push lower.

If you don't know your number, find it in two passes. Pull last week's invoices. Count the stops. Subtract the ones you regretted (the 50-minute property in a 20-minute neighborhood, the one you finished after sunset). That's a closer-to-honest version of full than the one your calendar shows.

For most weeks in peak season, full sits about 2 stops below your maximum. The 2-stop buffer is what lets you handle a flat tire, a customer who needs an extra service, or a 90-degree Wednesday without working past dark every day for the rest of the week.

When you've crossed full and you're still saying yes, you're not running a business. You're running a backlog.

Three buckets for incoming requests

Every new request in May falls into one of three buckets. Sort it before you reply.

Bucket 1: doesn't fit the route. Wrong neighborhood, wrong scope, wrong day. A 25-minute drive each way for a $40 mow is a charity, not a job. Decline cleanly. Don't quote. Don't follow up. Tell them you're not taking work in that area this season and wish them well.

Bucket 2: fits the route but you're at capacity. Right neighborhood, right size, right scope. The customer looks like the rest of your route. You just don't have a slot. This is the bucket most operators botch. Do not decline. Waitlist them. (More on this in a minute.)

Bucket 3: fits the route and is worth swapping for. Higher-rate property, tighter to your existing stops, or a recurring contract that would let you drop two one-off jobs you've been carrying. This is the only bucket you actually quote. Maybe one in ten requests in May. Treat it like a real opportunity.

The mistake is treating all three buckets the same. The first two get a short, kind reply in under 30 seconds. The third gets a real quote.

The two-line decline that doesn't burn the lead

For Bucket 1 and Bucket 2, the reply is short. It does three things: thanks them, tells them the truth, and leaves a door open.

A version that works:

"Thanks for reaching out. I'm full on my weekly route through the season and not adding new mows right now. If you want, I can put you on the list for next spring — happy to send a quote in February when I'm building the route."

That's it. Two sentences. No apology. No long explanation. No "but maybe I can squeeze you in."

What the line does:

• Tells them the answer. "I'm full" is a complete sentence. You don't owe them a workaround.
• Names the timeline. February is when you'll send the quote. The customer knows when to expect to hear from you.
• Captures the lead without committing. A waitlist signup costs you nothing. A meaningful share will follow up in February. Some of those become customers next year.

Send the same line every time. Don't customize it per request. The 90 seconds you save per decline turns into time you use to handle the Bucket 3 quotes well.

Build a real waitlist (it takes 10 minutes)

A waitlist is not a screenshot of a text thread you'll forget about. It's a list with names, addresses, scope, and the date they asked.

The simplest version is a single customer record in your invoicing tool with a note. Add the customer with their name, address, phone, and email. In the notes field, write the date and the scope they asked about: "5/13 — weekly mow + edge, .25 acre, asked via Facebook." No quote sent. No services attached. Just a record.

In February, you sort your customer list by note date, send them a quick "hey, you reached out last spring — building the route for the season, here's the rate" message, and a fresh quote at this year's price.

You will not chase every one of them. You don't need to. The ones who replied to your decline politely, the ones who said "no rush," the ones who confirmed an address — those are the ones to start with.

This is the single best habit a full-route operator can build. Most of next February's growth comes from this list, not from new ads.

“

Sort the request. Send the line. Add the name to the list.

Bucket 3: how to quote the swap-worthy job

The job that's actually worth taking in mid-May meets three tests: it's denser to your route, the rate is at or above your current average, and the scope is recurring or large enough to matter.

For these, you still need to move fast. The customer asked because their guy didn't show up or because they're three weeks into shopping. They are not going to wait a week for your quote. Send it the same day they ask, at your actual current rate, with no "thanks for your patience" caveat.

A few things to check before you quote

• Drive time. If the property adds more than 8 minutes to your route, the per-hour rate has to compensate. Most don't.
• Real scope. "Just a mow" sometimes means a quarter-acre with a slope and a fenced backyard. Look at the property on satellite before you quote.
• Day of week. A property that wants Saturdays only is a property you're going to fight with. Quote your real day or pass.

If you're going to take a swap-worthy job by displacing an existing customer, that's a separate conversation. Don't drop a long-tenured customer for a 3% better rate. Drop them for a 20% better rate, plus density, plus a customer who's actually pleasant to work with.

Lock in the route you already have

The thing most operators miss in May: a full route is only full if everyone stays. Somewhere between 10 and 20% of weekly accounts churn per season for reasons that have nothing to do with you. Houses sell. Customers move. Helpers cancel. Budgets tighten.

If your route isn't on recurring jobs, every one of those gaps is a slot you'll scramble to refill mid-summer. If your route is on recurring jobs, the gaps are visible the moment they happen, and your waitlist fills them in days.

Set up the recurring jobs for every weekly and bi-weekly customer you have. The draft invoice appears each cycle, you send it from the truck, the customer's clock starts. When someone cancels, the cycle stops. The empty slot is obvious on your list, not buried in a paper schedule.

If your saved services haven't been updated since last year, this is also the week to fix them. Update your services and rates so every new quote in May goes out at this year's number, not last year's. Five minutes of cleanup pays back across every Bucket 3 quote for the rest of the season.

What full feels like when you're running it right

A full route, handled well, looks like this. Monday morning you open the phone, see 4 new requests from the weekend, send 3 declines in under 5 minutes, and quote 1 swap-worthy job at this year's rate. Your existing customers are on recurring. Friday's invoices go out from the truck. The waitlist grows by 3 names a week, none of whom are mad at you. The route holds.

A full route handled badly looks like a 14-hour Wednesday, a quote you sent at last year's rate because it was 9 p.m., and a Bucket 1 customer who's been texting you since April about whether you've decided yet.

The difference is not how hard you work. It's how fast you sort.

Sort the request. Send the line. Add the name to the list. Get back to the route.