How to Cut Tech Drive Time by Optimizing Service Territories

Drive Time Is Eating Your Margins — Here's What to Do About It

If your techs are spending more than 60–90 minutes a day behind the wheel between jobs, your service territories are probably working against you. Optimizing territories — drawing clear, logical boundaries around where each tech works — is the single most effective way to reduce drive time without hiring another person or buying another truck. Companies that get this right routinely cut per-tech daily drive time by 30–45 minutes, which adds up to two to four additional billable jobs per week across your crew.

The core idea is simple: every tech should own a geographic zone where they do the majority of their work. When jobs cluster together instead of scatter across a metro area, your techs spend less time in traffic and more time at the door. That's better for your customers, better for your techs, and a direct line to higher revenue per day.

Why Most Small Companies Have a Drive Time Problem

It usually starts the same way. You hire your first few techs and assign jobs by who's available, not who's closest. Over time, you end up with techs crossing each other's paths all day. Tech A is heading north while Tech B is driving south — to jobs that are three miles apart. This is sometimes called route spaghetti, and it's one of the most common margin killers in home services.

The underlying cause is almost always a lack of defined service territories. Without clear zones, dispatch becomes a guessing game. Customers book with whoever has an opening, not whoever is already working in their neighborhood. And without route density — a high concentration of jobs in a tight area — drive time compounds fast.

The Business Case: What Route Density Actually Means in Dollars

Here's a quick way to see the cost on paper. Assume a tech costs you $35/hour fully loaded (wages, truck, fuel, insurance). At 90 minutes of drive time per day, that's $52.50 in dead cost per tech per day. Across five techs over 250 workdays, that's $65,625 a year in drive time you're paying for but not billing.

Cut daily drive time to 45 minutes per tech and you recover roughly $32,800 annually — without changing your prices, your crew size, or your service offerings. You're just getting more jobs out of the same labor hours.

How to Build Service Territories That Actually Reduce Drive Time

There's no perfect formula, but the following approach works well for companies with 3–20 techs operating in a suburban or mixed urban/rural market.

• Start with your job history, not a map. Pull the last 6–12 months of completed jobs and plot them by ZIP code or neighborhood. You'll almost always see natural clusters — areas where demand already concentrates. Build your territories around those clusters, not around equal geographic size.
• Assign territories by ZIP code or county, not by drawing a freehand line. ZIP codes are clean, easy to explain to techs and customers, and simple to update. Radius-based zones work well in rural areas where job density is lower.
• Size territories by realistic daily job volume. A residential HVAC tech can run 4–6 service calls per day. Design each territory so there are enough potential customers to fill that schedule — typically 8,000–20,000 households per territory, depending on your service frequency.
• Give each tech a home base anchor. Where a tech lives or parks their truck at night matters. Territories that align with a tech's home ZIP code eliminate the first and last commute of the day, which is often the longest drive.
• Define overlap rules before you need them. You'll have capacity overflows. Decide in advance when it's okay to send a tech outside their territory (e.g., same-day emergencies, or when a neighboring tech is fully booked three days out).

Territory Optimization Checklist

Use this before your next dispatch planning session:

• ☐ Have you mapped your last 6 months of jobs by ZIP code?
• ☐ Does each tech have a clearly named, documented territory?
• ☐ Are territory boundaries based on ZIP codes, counties, or defined radii — not verbal agreements?
• ☐ Is your booking system routing new customer requests to the right tech automatically based on their address?
• ☐ Do you know your average drive time per tech per day right now?
• ☐ Have you reviewed territories in the last 6 months for expansion, contraction, or rebalancing?
• ☐ Are your techs' home locations factored into territory boundaries?

Where Booking Creates a Drive Time Problem You Don't See Coming

One often-overlooked source of bad route density is your own booking process. If customers can call in and get manually assigned to any available tech, you're constantly creating one-off jobs in the wrong zones. The fix is automatic tech assignment at the point of booking.

This is where Cartoply directly solves the problem. When a customer clicks your booking link and enters their address, Cartoply checks which territory that address falls in and routes the job to the correct tech automatically — no dispatcher decision required. Territories can be drawn by ZIP code, county, city, or radius, and techs only ever see the jobs inside their own zone. The result is that your route density improves passively, just by taking bookings the right way.

If you're running Jobber, the integration goes a step further: every Cartoply booking automatically creates a Jobber Request, so there's no manual data entry, and your existing service area records in Jobber can be imported directly as Cartoply territories.

Benchmarks Worth Tracking

If you don't have visibility into these numbers, start there first:

• Target drive time: 45–60 minutes per tech per day (8-hour shift)
• Route density goal: 70%+ of weekly jobs within the assigned territory
• Cross-territory jobs: Keep below 15% of total weekly job volume
• Territory review cadence: Quarterly for growing companies; twice a year once stable

Start With One Territory This Week

You don't have to remap your entire operation in a single afternoon. Pick your highest-volume tech, pull their last 30 jobs, and draw a territory boundary around where most of those jobs landed. That's your starting point. Assign them exclusively to that zone for 30 days and measure the change in their daily drive time.

If you want to skip the spreadsheet work and get territories built directly into your booking flow, set up a free Cartoply account and import your ZIP codes today. Your techs will notice the difference before the end of the first week.