The Right Territory Size for a Tech Doing 4–6 Jobs a Day

For a tech running 4–6 jobs per day, the right territory size is typically 8–15 ZIP codes in a suburban market, or a radius of 12–18 miles from a central anchor point. Any larger and drive time eats into job capacity. Any smaller and you'll run out of demand before the day fills.

The exact number depends on three variables: average job duration, how dense the housing or commercial stock is in those ZIPs, and how much windshield time you're willing to accept. The benchmarks below give you a starting point — then a 5-step method to dial it in for your market.

Why Territory Size Directly Controls How Many Jobs a Tech Can Run

A tech doing 4 jobs a day at 90 minutes each has roughly 6 hours of productive time in an 8-hour shift. That leaves about 2 hours for drive time — split across 4 trips between jobs. That's 30 minutes of drive time per job segment before the day breaks down.

When a territory is oversized, a tech in the suburbs might spend 40–50 minutes between stops. By job three, they're already behind. By job five, they're skipping the estimate or rushing the invoice. Revenue per day drops; callbacks climb.

When a territory is undersized — say, 3 ZIP codes in a low-density rural area — you'll hit the demand ceiling fast. The tech either sits idle or gets pulled into someone else's territory, which creates the overlap problems covered in how to fix territory overlap between techs.

Territory Size Benchmarks by Market Density

Use these as starting targets before you run your own numbers:

Market type	Recommended ZIP count	Approximate radius	Max drive time per job segment
Dense urban (NYC, Chicago, LA)	3–6 ZIPs	4–7 miles	15–20 min
Suburban metro	8–15 ZIPs	12–18 miles	20–30 min
Mid-size city + surrounding towns	12–20 ZIPs	18–25 miles	25–35 min
Rural / low-density	15–30 ZIPs	30–45 miles	35–45 min

Key rule of thumb: if average drive time between jobs exceeds 35 minutes, the territory is too large for a 4–6 job day. Pull ZIP codes from the edges until drive time comes back under 30 minutes.

How to Size a Territory in 5 Steps

1. Set your job-capacity target. Decide how many jobs per day the tech should run (4, 5, or 6) and your average job duration in minutes.
2. Calculate available drive time. Subtract total job time from your shift length. What's left is your drive budget — divide by number of job segments (jobs minus 1, plus travel home).
3. Map a test radius from the tech's home base. Use Google Maps to check how many of your existing customer addresses fall inside a 15-mile radius. That's a live demand sample.
4. Count the ZIP codes that generate 80% of your calls. Pull 90 days of job history. List every ZIP code. The top ZIPs that account for 80% of volume are the core territory — start there.
5. Draw the boundary and assign it. Add ZIPs outward until the territory has roughly 20–25% more demand than one tech can handle solo. That buffer lets you fill gaps without overflow.

If you're building territories from scratch, the full process is covered in how to set up service territories for your home services business.

The Hidden Cost of Oversized Territories: Drive Time Math

Here's a number most owners don't track: every extra 10 minutes of drive time per job costs roughly one job per week across a 5-day schedule.

Example: a tech running 5 jobs a day with 4 drive segments. If average drive time is 20 minutes, that's 80 minutes of driving. Push that to 30 minutes and it becomes 120 minutes — 40 extra minutes daily, 200 minutes weekly. At a 90-minute average job, that's more than two jobs lost per week to windshield time. Multiply that by a 4-tech crew and you've lost 8+ billable jobs per week without anyone calling in sick.

Tighter territories don't just improve margins — they reduce tech fatigue, which cuts no-shows and turnover. The ROI compounds fast.

For a tactical look at reducing drive time once territories are drawn, see how to batch service calls by neighborhood and cut drive time.

How Cartoply Enforces Territory Boundaries at the Booking Stage

Most territory problems don't start in dispatch — they start when the wrong tech gets assigned to a booking. A prospect enters their address, someone manually checks a spreadsheet, and the wrong tech ends up 25 miles out of their zone.

Cartoply handles this automatically. You draw each tech's territory by ZIP code, county, or radius. When a prospect books through your link or embedded calendar, their address routes them to the correct tech — no manual check required. Each tech only sees jobs in their own territory.

If you're running round robin across techs in overlapping zones, Cartoply handles that too — rotating assignments within each territory rather than across the whole company.

FAQ

How many ZIP codes should one field technician cover?

In a suburban market, 8–15 ZIP codes is a solid starting range for a tech running 4–6 jobs per day. Dense urban markets may need as few as 3–6 ZIPs to stay within a 20-minute drive-time budget. Rural techs may need 15–30 ZIPs to hit full job capacity. The right number is whatever keeps average drive time between jobs under 30 minutes.

What is the maximum drive time between service jobs before productivity drops?

Most experienced dispatchers use 30 minutes as the hard ceiling for drive time between jobs on a 4–6 job day. Beyond 30 minutes, you start losing one or more billable jobs per day to windshield time. If you're consistently seeing 35–40 minute gaps, the territory needs to be redrawn smaller — or job-start times need to be shifted to cluster calls geographically.

How do I know if my service territories are too big?

Four signals: techs are regularly running fewer jobs than their daily target, callbacks and rushed jobs are increasing, average drive time between stops exceeds 30 minutes, or techs are crossing into each other's areas to fill their schedule. Any one of these is a sign your territory boundaries need to shrink or your anchor points need to shift.

Can I use ZIP codes to define field technician territories?

Yes — ZIP codes are the most practical unit for home services territory mapping because customers naturally describe their location that way ("I'm in the 78704 area"). The key is assigning each ZIP to exactly one tech and enforcing that boundary at the booking stage, not just in dispatch. Tools like Cartoply let you assign ZIPs directly to a tech so routing happens automatically when a customer books.