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

The Problem Nobody Talks About in the Morning Meeting

Open up a map of yesterday's jobs and trace where each of your techs actually drove. Odds are, you'll see lines crossing each other like a bowl of spaghetti. One tech drove 40 minutes north while another spent the morning 10 minutes south of him — and they passed within two blocks of each other's job sites. This is the hidden profit leak that kills small home service companies: techs driving past each other's jobs every single day. It's not a people problem. It's a scheduling structure problem, and it has a clear fix.

The root cause is almost always the same: you have no defined service areas per tech. Jobs come in, someone assigns them manually based on who's available or who picked up the phone first, and over the course of a week you've burned $300–$600 in unnecessary fuel and handed away 10–15 hours of billable drive time. Here's how to diagnose it and shut it down.

Why Route Overlap Happens (Even When You're Trying to Stay Organized)

Most dispatchers and owners aren't ignoring geography — they're just working with the wrong tools. Booking software shows you availability. It doesn't show you where a tech physically is or which ZIP codes they should own. So when a customer in ZIP 78745 calls in, the dispatcher checks who has an opening at 2pm, not who's already working in 78745 that day.

Three patterns cause most of the overlap:

• No defined territories. Every tech is technically available everywhere, so jobs get scattered based on time slot, not geography.
• Customers self-selecting the wrong tech. If you have an online booking link that shows all available times company-wide, a customer in the north part of town might book a tech who lives and works the south side.
• Last-minute fill-ins. When a cancellation opens up, you grab whoever's free — not whoever's already in that area — and suddenly two techs are leapfrogging each other all afternoon.

What Route Overlap Actually Costs You

Let's put numbers on this. The average service van costs $0.67–$0.85 per mile to operate when you factor in fuel, maintenance, and depreciation. A tech who drives 20 unnecessary miles per day because of poor territory management costs you roughly $13–$17 per day, per tech. Across 8 techs over 250 working days, that's $26,000–$34,000 a year in pure waste — before you account for the extra jobs that tech could have completed instead of sitting in a van.

Beyond the math, route overlap demoralizes your best techs. Nobody wants to spend two hours a day in a van when they could be on a job. High windshield time is one of the top reasons experienced techs start looking elsewhere.

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

You don't need to overhaul everything at once. Work through these steps in order:

1. Map your current job density. Pull the last 90 days of completed jobs and plot them by ZIP code or neighborhood. You'll immediately see where your natural clusters are. Those clusters should become the foundation of your tech territories.
2. Assign each tech a primary zone. Give each tech 2–5 ZIP codes or a defined radius as their home territory. This doesn't mean they never leave it — it means that's where their jobs get routed first, and another tech is the fallback only when that zone is full.
3. Build territories around where your techs live. A tech who lives in the northwest quadrant of your service area will always have shorter drive times if his territory is in the northwest. This is low-hanging fruit most owners miss.
4. Fix your booking flow so customers can't pick the wrong tech. If customers book online, the system should use their address to route them to the right tech automatically — not show them a full company calendar. With Cartoply, a customer enters their address and gets shown only the availability for the tech assigned to their territory. One booking link for your whole company, and every job lands with the right person.
5. Review route density weekly, not just daily. Daily dispatch fixes individual days. Weekly review catches drift — situations where a territory is slowly creeping outside its boundaries because of repeat customers or word-of-mouth referrals in adjacent zones.

Benchmarks: What Good Route Density Looks Like

If you're not sure whether your current setup is tight or loose, here are benchmarks worth tracking:

• Average drive time between jobs: Should be under 20 minutes for a well-zoned tech in a suburban or urban market. If you're regularly seeing 35–45 minutes between stops, your territories are too large or too undefined.
• Jobs per day per tech: In most home service categories, a tightly zoned tech should be able to complete 5–8 jobs per day. Poor routing often holds that number to 3–4.
• Fuel cost as % of revenue: Target is under 5%. If you're consistently over 8%, overlapping routes are likely a significant contributor.
• Windshield time ratio: Techs should spend no more than 20–25% of their working day driving. Track this for one week — most owners are surprised how far above this number they actually are.

One More Leak to Close: Jobs Without Deposits

While you're fixing your routing, fix this too: a tech who drives 25 minutes to a job only to have the customer not be home — or dispute the invoice afterward — is a double loss. Requiring a deposit at booking eliminates a huge chunk of no-shows and payment chases. Cartoply lets you collect a deposit or full payment before a booking is confirmed, so your techs only drive to jobs that are locked in.

Start With One Week of Data

You don't need a perfect system on day one. Start by pulling one week of completed jobs, plotting them on a map, and identifying which techs are consistently working in overlapping areas. That single exercise will show you exactly where to draw the territory lines. Once you have defined zones, automating the routing — so customers self-assign to the right tech at booking — is the step that locks the fix in permanently and removes the dispatcher from the equation entirely.

If you want to see how territory-based scheduling would look for your specific service area, map out your zones in Cartoply free — draw them by ZIP code, city, or radius, and see how your current jobs would have been distributed.