Why Your Techs Are Driving Past Each Other's Jobs (And How to Fix It)

The Problem You Can See on a Map (But Probably Aren't Tracking)

If your techs are driving past each other's jobs, the root cause is almost always the same: you don't have defined service territories, so every new booking gets assigned by gut feel, availability, or whoever picks up the phone first. One tech ends up on the north side of town at 8am, then drives 40 minutes south for a noon job — while another tech starts the day two streets away from that noon job and drives right past it. It happens every week, and it's costing you real money.

The fix isn't hiring a better dispatcher. It's building a system where the right job automatically goes to the right tech based on where they work — before the schedule ever gets made. Here's why overlapping routes happen, what they actually cost, and how to stop it.

Why Overlapping Routes Happen in the First Place

Most home service companies start small. The owner dispatches by memory — they know which tech lives on which side of town, they know who's fast and who's slow, and they make it work. That system breaks down fast once you hit 5 or more techs.

Here's what goes wrong:

• No defined service areas. If nothing is written down (or drawn on a map), every dispatcher makes their own call. Consistency disappears the moment you hire a second person to answer the phone or handle bookings.
• Online booking that ignores location. A customer in the south ZIP code books through your website and gets whoever has the next open slot — not the tech who already has three jobs five minutes away.
• Last-minute job swaps. A tech calls out sick, jobs get shuffled around without checking geography, and suddenly two guys are running opposite diagonals across your market.
• No visibility into where jobs actually are. When your schedule lives in a shared Google Calendar or a whiteboard, it's nearly impossible to see clustering problems before the day starts.

What Overlapping Routes Actually Cost You

This isn't just an inconvenience — it's a measurable drain. Let's put some numbers on it.

• The average field tech drives 60–80 miles per day on a well-routed schedule. Poorly assigned jobs can push that to 100–130 miles.
• At current fuel and vehicle costs, that extra 40–50 miles per tech per day runs roughly $25–$40 in direct costs — before you factor in the billable hour of drive time you just gave away for free.
• A tech spending 90 minutes more per day in the truck instead of on a job site is a tech completing 1–2 fewer jobs per week. At an average ticket of $250, that's $250–$500 in lost revenue per tech, per week.
• For a 6-tech crew, that adds up to $1,500–$3,000 in lost capacity every single week — just from bad route density.

Run that math for a year. It's not a scheduling inconvenience. It's a staffing-level expense hiding inside your operations.

How to Fix It: A Step-by-Step Approach

You don't need to overhaul everything at once. Start here:

1. Draw your territories first. Pull up a map and divide your service area by ZIP code, neighborhood, or city boundary. Assign each tech a primary zone. It doesn't have to be perfect — it has to exist. In Cartoply, you can draw territories by ZIP code, county, radius, or city and save them as permanent assignments.
2. Connect your booking flow to those territories. When a customer enters their address to book online, the system should route them to the tech who owns that area — not just whoever has a free slot. This is the single biggest lever. Cartoply does this automatically: a customer books, enters their address, and gets matched to the right tech based on your territory map.
3. Give each tech a single calendar view of their own jobs. When techs can see their own schedule — and only their own schedule — they stop calling the office to ask what they have tomorrow. One shared company booking link, filtered per tech. No more forwarded spreadsheets.
4. Audit your route density weekly, not daily. Once a week, look at where jobs landed and whether they clustered the way you intended. Are there ZIPs that keep getting assigned to the wrong tech? Adjust the territory boundary, not the individual jobs.
5. Build a coverage rule for callouts. Decide in advance: if Tech A calls out, which tech takes their zone, and in what priority order? Write it down. The worst routing decisions happen at 6:45am when someone calls in sick and the dispatcher improvises.

A Quick Checklist: Signs Your Routing Is Broken

• ☐ Techs regularly drive more than 30 minutes between jobs mid-day
• ☐ Your dispatcher manually assigns every single booking
• ☐ Customers in the same ZIP code get different techs every time
• ☐ You've had two techs on the same street on the same day — on different jobs
• ☐ Online bookings don't account for where the customer is located
• ☐ You have no written rule for what happens when a tech calls out

If you checked three or more of those, your routing problem is structural — and it won't get better by asking techs to update their calendars more carefully.

The Fastest Way to Get This Under Control

The companies that solve this fastest aren't necessarily the most organized — they're the ones that stop relying on people to make geography decisions in real time. When territories are defined and booking is tied to location, the right tech gets the right job before anyone has to think about it.

If you're already using Jobber to manage your field operations, Cartoply pulls your existing service areas in as territories and syncs new bookings directly as Jobber Requests — so nothing falls through the cracks and you're not running two systems manually side by side.

Your Next Step

Open a map right now — Google Maps works fine — and draw a rough line through your service area. How would you split it if each tech had their own zone? That's your starting point. Once you have a territory sketch, set up a free Cartoply account and build those territories in under 15 minutes. Connect your booking link, assign your techs, and by tomorrow morning your dispatcher won't have to make a single geography decision manually.

Your techs shouldn't be driving past each other's jobs. With the right system in place, they won't be.