Field Service Routing Software: How Territory Routing Cuts Drive Time

Territory routing software assigns each booking to the tech whose zone covers the customer's address, cutting daily drive time by 60–90 minutes per tech without manual dispatch.

Why field service teams lose so much time to windshield hours

Picture a 10-tech pest control company. Tech A starts her day in the north end of town. Her second job is downtown. Her third is back north. Meanwhile, Tech B is running the same zigzag in reverse. They drive past each other's jobs twice before lunch.

This is not a discipline problem. It is a booking problem. When customers book online — or when a dispatcher takes calls and assigns jobs by gut feel — there is no geographic logic enforcing who gets which address. The result is route density that looks like a plate of spaghetti and fuel bills to match.

A 2023 study by Geotab found that unnecessary route detours add an average of 25–30% to field team drive time. For a team of 10 techs each working 8-hour days, that is roughly 20–30 hours of paid labor burned on windshield time every single day. At $25/hour fully loaded, that is $500–$750 a day — $130,000–$195,000 a year — in labor that produces zero billable work.

How territory routing actually works

Territory routing is a deceptively simple idea: define which geographic area each tech owns, then make sure every new booking is automatically assigned to the tech whose territory contains the job address.

In practice, that means:

• Territory definition: You draw service areas on a map using ZIP codes, counties, city limits, or a freehand radius. Each territory is assigned to one tech or crew.
• Address matching at booking: When a customer books online and enters their address, the software checks which territory it falls in and routes the job to that tech automatically.
• Calendar confirmation: The tech sees the job on their calendar. No dispatcher has to touch it.

This is different from route optimization — which sequences jobs already on the schedule into the most efficient drive order. Territory routing happens before a job is even booked. It prevents the scatter in the first place. For a deeper look at when you need both approaches, see territory routing vs route optimization: when field teams need both.

How to set up territory routing in 6 steps

Set up territory routing for your field service team

1. List every active tech and their realistic daily job capacity.
2. Map your existing bookings by ZIP code to find natural density clusters.
3. Draw territory boundaries that balance job volume, not just geography.
4. Assign each territory to one tech in your routing software.
5. Set your company booking link live so address matching runs automatically.
6. Review cross-territory job counts weekly and redraw boundaries as needed.

The drive-time numbers territory routing actually moves

The benchmark to hold yourself to: a tech doing 4–6 jobs a day in a well-drawn territory should spend no more than 15–20 minutes driving between consecutive jobs. If your inter-job drive time is averaging 35–45 minutes, your territories are either too large, not enforced at booking, or overlapping.

For an HVAC team running service calls across a mid-sized metro, tightening territories from county-level to ZIP-code-level typically drops average inter-job drive time by 30–40%. The math compounds quickly: shave 20 minutes off each of 5 daily drives and a tech gains 100 minutes of capacity — enough to add one more billable job per day.

Mobile businesses feel this even more acutely. A mobile grooming van or mobile detailing operator whose whole revenue model runs through a 6–8 slot day cannot absorb 40-minute gaps between stops. Every unpaid mile is a direct hit to margin. That is why keeping a mobile van's day inside one neighborhood is not just a nice-to-have — it is how the unit economics work.

Recurring service companies — house cleaning crews, window cleaners, pressure washers — face the same pressure with a twist: crews are staffed and paid before a single job starts. Route scatter on a recurring route is paid labor with no revenue to offset it. Tight zones protect the margin built into the recurring model.

Territory routing vs manual dispatch: a realistic comparison

Factor	Manual dispatch	Territory routing software
Job assignment time	2–5 min per booking (human touch)	Instant (automatic on address entry)
Cross-territory jobs	Common — dispatcher judgment varies	Blocked by zone rules at booking
Average inter-job drive time	30–45 min in metro areas	15–20 min with well-drawn zones
Scales with team growth	Requires hiring another dispatcher	Add a zone, assign a tech — done
After-hours booking	Queues until dispatcher is in	Routed and confirmed automatically
Customer experience	Callback to confirm who's coming	Immediate confirmation with assigned tech

If your team is at the stage where dispatch is a bottleneck — especially for same-day and after-hours requests — why your dispatch system is slower than online booking is worth a read before you make any tooling decisions.

What good territory boundaries actually look like

The most common mistake is drawing territories by city or county because those boundaries are easy to see on a map. The problem: a county can take 45 minutes to cross at rush hour. A city limit may cut through a neighborhood your tech already owns half of.

ZIP codes are the better default for most field service businesses. They are granular enough to create real drive-time separation, they match how customers describe their location, and they are easy to add or remove as your team grows. The county vs ZIP code territory comparison for plumbing companies breaks down the tradeoffs in detail — the logic applies equally to HVAC, electrical, and any trade with similar job density.

For teams with highly variable job durations — solar installations, roofing assessments, multi-day jobs — territory size needs to account for time-on-site as well as drive time. A tech doing two 4-hour installs per day needs a tighter geographic zone than one doing six 45-minute service calls.

Cartoply's HVAC scheduling software lets you draw territories as a custom shape, radius, or ZIP code list — whichever maps cleanest to your actual coverage footprint — and the right booking routes there automatically at the moment a customer enters their address.

One booking link, every tech covered

A common objection: "Won't customers be confused if there's one booking link but multiple techs?" No — and that is exactly the point. You share one company booking link. The customer enters their address. The software matches the address to a territory, checks that tech's availability, and confirms the booking — all without the customer knowing or caring which tech is assigned. The tech only sees their own jobs. No cross-visibility, no scheduling conflicts, no dispatcher in the middle.

For teams already using Jobber for job management, the Cartoply–Jobber integration creates a Jobber Request automatically when a booking comes in — client, property, and assigned tech all pre-populated — so your field management workflow picks up exactly where booking left off.

Frequently asked questions

What is field service routing software?

Field service routing software automatically assigns new jobs to the correct technician or crew based on the customer's address and predefined service territories. It replaces manual dispatch decisions with geographic rules, ensuring each booking goes to the tech closest to — or responsible for — that location. Most platforms also sync confirmed jobs to techs' calendars in real time.

How much drive time can territory routing actually save?

A team with poorly enforced territories typically averages 30–45 minutes of inter-job drive time in a metro area. Well-drawn ZIP-code-level territories bring that to 15–20 minutes per move — a 30–40% reduction. For a tech running 5 jobs a day, that is 75–125 minutes of daily capacity recovered, enough to add one extra billable job without extending hours.

Does territory routing work for small teams or solo operators?

Yes. Even a two-tech team wastes time when customers can book either person for any address. A single-tech operator benefits by enforcing a service radius at booking — preventing jobs that are too far to be profitable before they ever land on the calendar. In Cartoply, a solo operator sets up an organisation (one member, one seat) to access territory and payment features.

What's the difference between territory routing and route optimization?

Territory routing determines which tech gets a job based on service zone — it happens at the moment of booking. Route optimization determines in what order a tech drives to jobs already on their schedule. The two solve different problems: territory routing prevents scatter at the source; route optimization sequences whatever jobs remain. Most small field service teams see bigger gains from fixing territory routing first.