Territory Routing vs Route Optimization: When Field Teams Need Both

Territory routing answers "which tech should own this job?" Route optimization answers "in what order should that tech drive to their jobs today?" They solve adjacent problems — but confusing one for the other leaves money (and miles) on the table. Most field teams with 5 or more techs eventually need both working in sequence: territory routing first, so the right person is assigned, then route optimization to make their day efficient.

If your techs are being assigned correctly but still racking up unnecessary windshield time, you need optimization. If they're being routed to jobs outside their area — or two techs keep showing up in the same neighborhood — you need territory routing. Keep reading to understand the difference precisely, and where the two tools hand off to each other.

What Territory Routing Actually Does

Territory routing is a booking-time decision. The moment a prospect submits their address, the system checks which tech's zone that address falls inside and assigns them automatically. No dispatcher involved. No "let me check the map."

The zones themselves can be drawn several ways: by radius from a tech's home base, by ZIP code lists, by county, by city, or as a freehand shape on the map. What matters is that every address in your service area resolves to exactly one tech — no overlap, no gaps.

Territory routing solves four specific problems:

• Overlap: Two techs accepting jobs in the same neighborhood, then crossing paths all day.
• Wrong-person bookings: A prospect in the north end books the tech who covers the south end because the booking link wasn't address-aware.
• Dispatch bottlenecks: An office person manually checking a spreadsheet to figure out who covers which zip — adding 10–20 minutes of lag to every new booking.
• New rep onboarding chaos: When you add a tech or rep, their zone gets defined once, and the routing rules just work from that point forward.

Territory routing is entirely about who gets the job. It has nothing to say about when during the day that job happens, or in what order it's visited relative to the tech's other stops.

If you've been dealing with techs driving past each other's jobs, the deep-dive on why your techs are driving past each other's jobs is worth reading before you set up zones — it explains the root causes that territory design alone won't fix.

What Route Optimization Actually Does

Route optimization is a dispatch-time decision. It runs after the jobs are assigned and answers: given this tech's list of stops today, what sequence minimizes total drive time using real road distances — not straight-line estimates?

A solid optimizer accounts for:

• Each tech's starting point (home base or depot)
• Job time windows or customer-requested arrival slots
• Actual road drive times, not as-the-crow-flies distances
• Recurring jobs that need to be sequenced alongside one-time calls

Route optimization doesn't know or care about territories. It just takes a tech's assigned job list and finds the most efficient sequence. That's why it's useless without good territory routing upstream — if a tech has been assigned three jobs in one part of town and two jobs across the city because the assignment logic was wrong, optimization can't undo that. It can only minimize the damage.

Cartoply's route optimization for field teams uses real road drive-times to build daily proposals the admin reviews on a map before committing anything to the techs' calendars. Nothing gets auto-dispatched — you see the proposed sequence, adjust if needed, then confirm. Techs track work in two steps (Confirm → Complete) from their jobs page, which gives you a clean audit trail of who completed what and when.

The Handoff: How Territory Routing and Route Optimization Work Together

Think of it as a two-stage pipeline:

1. Stage 1 — Assignment (territory routing): Prospect books → address checked against zones → correct tech assigned automatically → job lands on their calendar.
2. Stage 2 — Sequencing (route optimization): Admin reviews the day's job list for each tech → optimizer proposes a drive-time-minimized sequence → admin reviews on map → commits to calendars.

Stage 1 without Stage 2 means your techs have the right jobs but are still making inefficient drives because nobody sequenced the stops. Stage 2 without Stage 1 means the optimizer is doing its best with a job list that may already contain wrong-territory assignments — it can produce an efficient route through the wrong set of jobs.

A useful benchmark: if your techs are spending more than 20% of their working day in the truck, you have a sequencing problem (Stage 2). If two techs regularly end up on the same street or you're constantly moving bookings after the fact, you have an assignment problem (Stage 1). Many teams with 6+ techs have both.

For a closer look at what good scheduling metrics actually look like before and after fixing this pipeline, see the field technician efficiency numbers that actually matter.

Which Teams Need Territory Routing Only

Not every team needs full route optimization. If your jobs are spread across a day with natural gaps — a solar company running two or three long assessments, a pest control company with quarterly visits that are easy to cluster manually — territory routing alone might be enough. The key indicator: your techs have 3 or fewer jobs per day, and each job is long enough that drive time between stops is a small percentage of the day.

Territory routing is also the right first step if you're just starting to scale. Get assignment right before you optimize sequence. A team of 3–4 techs where you've never formally defined zones will see an immediate drop in wasted miles and dispatcher workload just from adding address-based routing — before any optimization logic is needed.

Which Teams Need Route Optimization on Top

Route optimization earns its cost when techs run 4–6 or more jobs per day and each stop is short enough that drive time between stops is a significant chunk of the day (HVAC tune-ups, pool service, pest control, landscaping maintenance). In those models, the sequence of stops can vary drive time by 30–50% depending on how well the stops are batched.

It also matters more as you add recurring jobs. When a tech has a mix of weekly recurring clients and new one-time jobs booked that morning, manually finding the optimal sequence before 8am is genuinely hard. An optimizer handles that in seconds and surfaces a proposal the admin can verify before anyone leaves the yard.

For teams running high job volumes daily, the scheduling patterns described in a day in the life of a high-volume home services tech show exactly where sequencing decisions make or break the day.

Quick Diagnostic: Which Problem Do You Have?

Run through this checklist. Be honest.

• ☐ Two or more techs have accepted jobs within a mile of each other on the same day → territory routing problem
• ☐ You or your dispatcher manually reassign bookings after the fact because the wrong tech got them → territory routing problem
• ☐ Techs are covering the right areas but still doing 90+ minutes of driving for a full day of jobs → route optimization problem
• ☐ Jobs are batched correctly by neighborhood but in the wrong order (e.g., zigzagging instead of looping) → route optimization problem
• ☐ You added a new tech and had to re-explain coverage boundaries to the whole team → territory routing problem (zones aren't formalized)
• ☐ Your techs have 5+ jobs per day and you're still sequencing them manually the morning of → route optimization problem

If you checked items in both columns, you need both tools in sequence.

Frequently Asked Questions

What is the difference between territory routing and route optimization?

Territory routing determines which technician or rep is assigned to a job based on where the customer is located — it's an assignment decision made at booking time. Route optimization determines the best order to visit a set of already-assigned jobs to minimize drive time — it's a sequencing decision made at dispatch time. They solve different stages of the same problem and work best when used together.

Do I need route optimization if I already have service territories set up?

Not necessarily. If your techs run 3 or fewer jobs per day and jobs are long enough that drive time is a small fraction of their day, good territory design may be sufficient. Route optimization pays for itself when techs run 4–6+ short jobs per day, where the sequence of stops meaningfully affects total mileage and how many jobs they can realistically complete.

Can route optimization fix bad territory assignments?

No. Route optimization only sequences the jobs a tech has already been assigned. If assignment was wrong — two techs sent to the same neighborhood, or one tech covering a geography that's too spread out — optimization makes the best of a bad situation but can't correct the underlying problem. Fix territory routing first, then layer in optimization.

How do I set up service territories for automatic booking assignment?

In Cartoply, you draw each tech's territory directly on a map — by radius from their home base, by ZIP code list, by county, or as a freehand polygon. Once zones are saved, every new booking automatically routes to the tech whose territory contains the customer's address. No dispatcher action required. You can see the full setup process in the service territories setup guide for home services businesses.