Drive Time vs City Limits: How to Build Smarter Service Areas

City and county lines are drawn for tax purposes — not for your dispatch board. A tech assigned to "the north side of town" might still cross 40 minutes of suburbs to reach a job on the far edge of that zone. Service areas built around drive time, not administrative boundaries, keep your techs inside a tight geographic bubble, pack more jobs into a day, and stop customers on the border from being routed to whoever picked up the phone first.

The core principle: a drive-time service area is a radius of reachable addresses within a target travel window — typically 20–35 minutes from a tech's start location. When a customer books, the system checks their address against that window, not against a city name. The result is denser routes, fewer windshield hours, and less overlap between techs.

Why City Boundaries Fail Field Service Teams

Most service businesses inherit their territory definitions from wherever a sales manager drew lines on a map in year one. Those lines follow intuitive landmarks — cities, zip codes, highways — but they have no relationship to how long it actually takes a tech to get from point A to point B.

Here's what that costs you in practice:

• Uneven job density. A "city" territory in a dense urban core might hold 200 potential customers per square mile. The same label applied to a suburban fringe might hold 40. Techs in the sparse zone run two or three jobs a day; techs in the dense zone are overwhelmed.
• Border bleed. Customers near the edge of a city boundary get assigned to the wrong tech — sometimes the one who has to drive 45 minutes past two other techs to reach them. You're paying for that dead mileage every day.
• Phantom coverage gaps. Two techs share a city, but neither owns the neighborhoods in between. Leads fall through. Callbacks are slow. A competitor who does own that pocket wins the job.

If your techs are driving past each other's jobs, a city-based territory map is almost always the root cause.

How to Build a Drive-Time Service Area: 5 Steps

1. Set your target drive-time window. For most home service companies with 4–6 jobs per day, 20–30 minutes is the right ceiling. More than 35 minutes and you're burning a job slot on windshield time.
2. Anchor each territory to a tech's start point. Use their home address or depot. This is the center of their reachable zone — not the center of a city.
3. Map the zone, not the boundary. Use ZIP codes, counties, or radius circles to approximate the drive-time bubble in your scheduling tool. Aim for 80–90% coverage of addresses within your target window; don't agonize over the edges.
4. Check for overlap and gaps. Lay all territories on the same map. Any address that falls in two zones needs an assignment rule (typically: nearest tech wins, or lowest current workload). Any address in no zone needs a catch-all tech or a manual review queue.
5. Validate against a real week of jobs. Pull last month's completed jobs. Map them. If a tech drove more than 30 minutes between consecutive jobs more than twice in a week, the territory needs to shrink or shift.

The Numbers That Should Guide Your Territory Size

Drive-time territories aren't one-size-fits-all. The right size depends on job duration and daily job count. Use these benchmarks as a starting point:

• Short jobs (30–60 min), 5–7 per day: Target a 15–20 minute max drive time. Dense ZIP-code clusters or a tight radius (8–12 miles in suburban areas).
• Medium jobs (1–2 hrs), 4–5 per day: 20–30 minute max. A 3–5 ZIP cluster or 12–18 mile radius depending on road density.
• Long jobs (half-day+), 2–3 per day: Drive time matters less; territory size can expand to 30–40 minutes because you're not making as many trips.

For a deeper look at matching territory size to job volume, see the right territory size for a tech doing 4–6 jobs a day — it covers the math in detail.

The goal is that a tech can complete their first job of the day, drive to the next, and never feel like they're leaving their neighborhood. If a tech says "I was all over the place today," the territory is wrong.

Routing New Bookings Into Drive-Time Zones Automatically

Drawing the zones is only half the work. The other half is making sure every new booking lands in the right zone without a dispatcher manually checking addresses.

When a customer books online, the system should check their address against your defined territories and assign them to the matching tech instantly. No manual lookup. No dispatch call. The customer picks a time, the tech sees the job, the dispatcher sees a clean board.

This is exactly what Cartoply's territory-aware scheduling features are built to do: you define each tech's service area by ZIP code, radius, county, or city inside Cartoply, and every incoming booking is automatically routed to the right person. One booking link for the whole company — each tech only sees jobs inside their own zone.

If you're also running jobs through Jobber, Cartoply's integration creates a Jobber Request automatically when a booking is confirmed — client, property, and assigned tech all pre-filled, so nothing gets re-entered. See how that connection works in our guide to connecting Jobber with an online booking system.

Common Mistakes When Switching From City-Based Territories

• Making zones too large to avoid customer complaints. A tech who covers "the whole metro" to avoid turning anyone away will burn out and run slow routes. Set the boundary, communicate it clearly, and stick to it.
• Forgetting to account for traffic patterns. A 15-mile radius looks small on a map. At 7:30 AM on a Monday it might be a 40-minute drive. Build your zones around peak-hour travel time, not off-peak.
• Assigning territories by city when your tech base is spread out. If your techs are distributed across a metro, anchor each territory to the tech, not to a named place. Two techs can cover the same city if their drive-time bubbles carve it cleanly in half.
• Skipping the validation step. Draw the zones, then check them against real job data before going live. A zone that looks balanced on a map can still be unworkable if the road network funnels traffic in one direction.

For multi-tech companies still sorting out who owns what pocket, batching service calls by neighborhood is a useful interim tactic while you finalize your drive-time zones.

Frequently Asked Questions

How do I set up service areas based on drive time instead of zip codes?

Start by anchoring each territory to your tech's start location, then define a maximum drive-time window — typically 20–30 minutes for most home service jobs. Use ZIP codes or a radius to approximate that bubble in your scheduling software. Validate against real job history: if your tech regularly drives more than 30 minutes between back-to-back jobs, shrink or reposition the zone until the routes cluster tightly.

What's the difference between drive-time zones and zip code territories?

ZIP code territories are administrative — they follow postal boundaries that have no relationship to road networks or travel time. Drive-time zones are built around how long it actually takes a tech to move between addresses. A single ZIP code can span 5 minutes of drive time in a dense city or 45 minutes in a sprawling suburb, so ZIP codes alone don't guarantee efficient routing.

How large should a service territory be for a field technician?

For a tech running 4–6 jobs per day on 1–2 hour jobs, aim for a territory where no consecutive job requires more than 25–30 minutes of drive time. In practice, that's often a cluster of 3–6 dense ZIP codes or a 12–18 mile radius in a suburban market. Adjust for peak-hour traffic — the boundary that works at noon may not work at 8 AM.

Can I use drive-time territories with online booking software?

Yes — but only if your scheduling tool supports geographic territory assignment. Generic tools like Calendly or Acuity route based on availability, not location. A platform like Cartoply lets you define each tech's territory by ZIP code, radius, county, or city, then automatically assigns every incoming booking to the right tech based on the customer's address — no manual dispatch required.