Territory Size vs Drive Time for Landscaping Techs: The Right Balance

A landscaping tech's territory should be sized so total daily drive time stays under 90–120 minutes — about 20% of an 8-hour shift — using a drive-time radius from their home base rather than ZIP codes.

Why territory size and drive time are the same problem

Most landscaping companies set territories once — usually by ZIP code or by drawing a rough circle on a map — and never revisit them. That's how you end up with a tech in the northwest corner of the city servicing three accounts on the south side because "they were already on that road last Tuesday."

Windshield time is a silent margin killer. A crew of two that spends two extra hours driving per day burns through roughly $60–$80 in labor alone, before you count fuel. Do that five days a week across a six-tech operation and you've lost $1,800–$2,400 per week in capacity that isn't generating a single invoice.

The fix isn't just about routing — it's about territory design. Routing optimizes the order of jobs inside a territory. Territory design determines which jobs belong to which tech in the first place. Get the second one wrong and no amount of routing software recovers the lost time. See the full breakdown in territory routing vs route optimization — they're complementary, not interchangeable.

The benchmarks that actually matter

Here's a concrete target set to work from for landscaping operations:

• Jobs per day per tech: 4–8 (depending on service type — a mow takes 30 minutes; a full landscape install takes a full day)
• Maximum daily drive time: 90–120 minutes total (not per leg)
• Average drive between consecutive jobs: 8–15 minutes
• Territory radius from home base: 10–15 miles for dense suburban markets; 18–25 miles for rural or semi-rural markets
• Overlap buffer at territory edges: 1–2 miles maximum before a job should be reassigned to the adjacent tech

If your techs regularly report 3+ hours of daily drive time, the territory is too large, too irregular, or too full of outlier accounts that should be dropped or reassigned.

For a deeper look at how job count and territory size interact, the right territory size for a tech doing 4–6 jobs a day walks through the math by service type.

How to size a landscaping territory correctly

Follow these six steps to build territories that hold up through the season:

1. Set each tech's home base or depot — their real starting point each morning.
2. Draw a drive-time radius (not a mile radius) of 15 minutes around that point.
3. Plot all current accounts on the map and identify which fall inside each radius.
4. Flag any account more than 20 minutes from the nearest tech's base as an outlier.
5. Reassign outlier accounts to the closest tech, or batch them into a dedicated "far route" day once per week.
6. Lock each tech's booking territory so inbound jobs auto-route to the right crew — no manual dispatch.

The step most companies skip is step two. Mile-based radiuses look clean on a map but they lie. A 10-mile radius in a grid-street suburb might be a 14-minute drive. That same radius across a lake, a highway interchange, or a gated community can be 35 minutes. Drive-time radiuses based on real road data are the only kind that translate to an actual schedule.

Cartoply's landscaping scheduling software lets you draw territories as a custom shape, by radius, or by ZIP code — and once a territory is live, every inbound booking from that address automatically routes to the assigned tech. No dispatcher needed. Customers use one booking link; the right crew gets the job.

Warning signs your territory is out of balance

Watch for these signals. Any one of them is worth a territory audit:

• Techs driving past each other's jobs. If two crews cross paths on the same street on the same day, your zones overlap or your dispatch logic isn't geography-aware.
• One tech is always behind, another is always idle. Uneven job density — not personality or skill — is almost always the cause. The busy tech has a territory that's geographically tight but account-heavy; the idle one has a territory that's spread thin.
• Recurring jobs keep shifting crews. When a weekly lawn client gets a different tech each visit, you lose the trust that drives referrals and upsells. Stable territories produce stable recurring assignments.
• Drive time spikes on Mondays. Monday is often catch-up day after weekend cancellations. If outlier accounts land on Monday by default, that day's route becomes the worst of the week. Build territory buffers that absorb rescheduling without blowing up the route.

The piece on cutting tech drive time by optimizing service territories covers the audit process in more detail, including how to spot which accounts are silently dragging down your route density.

Seasonal adjustments landscaping companies have to plan for

Landscaping isn't a flat-demand business. Spring cleanup and fall aeration seasons can double inbound volume in six weeks. If your territories are sized for peak without a plan for shoulder season, your techs are either overloaded in April or idle in November.

A practical approach: define a "core territory" each tech owns year-round, then define an "overflow zone" at the edge of their territory that activates only when their core calendar is full. Cartoply handles this with territory boundaries that stay fixed — the booking system won't offer a tech's slots to accounts outside their zone until their availability opens up.

For companies that add seasonal crew, territory reassignment during crew transitions is its own project. Territory management for landscaping companies with seasonal crew changes has a practical framework for handing zones off without losing account continuity.

Route density is the metric that ties it all together

Territory size and drive time come together in a single operational metric: route density. Route density is the number of billable jobs completed per hour of field time (drive + service combined). A well-designed landscaping territory runs at 0.6–0.8 jobs per field hour for standard recurring maintenance. If you're below 0.5, drive time is eating your margin.

Track route density by tech, not just by day. A tech with low density probably has a territory problem, not a performance problem. Fix the zone before you have the performance conversation.

Frequently asked questions

How large should a landscaping technician's territory be?

For a tech doing recurring maintenance (mowing, trimming, edging), a territory covering a 10–15 mile drive-time radius from their home base works well in suburban markets. That typically yields 30–60 accounts within a manageable daily route. Rural markets may require 18–25 miles to reach sufficient account density, but daily drive time should still stay under 120 minutes total.

How do I stop landscaping techs from driving past each other's jobs?

The root cause is almost always territory overlap — either no formal zones exist, or they're defined by ZIP code boundaries that don't reflect real drive patterns. Draw zones based on drive-time radiuses from each tech's starting point, then enforce them in your booking system so inbound jobs auto-assign to the correct crew. When booking enforces geography, dispatch conflicts disappear without manual intervention.

Should I use ZIP codes or drive-time radius for landscaping service areas?

Drive-time radius is more accurate for scheduling purposes, but ZIP codes are easier for customers to understand and for marketing geo-targeting. A practical middle ground: use drive-time radiuses to define internal tech territories in your scheduling system, and use ZIP codes for marketing boundaries on your website. Cartoply lets you define territories either way — or combine both approaches for different purposes.

What is a good drive time between landscaping jobs?

Target 8–15 minutes of drive time between consecutive jobs on a well-designed route. Anything consistently over 20 minutes per leg signals that those accounts belong in a different tech's territory, or that job batching by neighborhood isn't happening. Total daily drive time should stay under 90–120 minutes for a standard 8-hour shift to maintain profitable route density.