How to Batch Service Calls by Neighborhood and Cut Drive Time in Half
Your Techs Are Burning 90 Minutes a Day Just Driving Between Jobs
Batching service calls by neighborhood means grouping all of a tech's jobs for the day into the same geographic area — the same ZIP code, the same subdivision, or at least the same side of town — instead of scattering them across your entire service area. Done consistently, this one scheduling habit can cut your average drive time between jobs from 25–30 minutes down to 10–12 minutes, which translates to one or two extra jobs per tech per day without adding a single hour to anyone's shift.
Most home service companies lose this time without even noticing it. You've got a plumber starting in the northeast corner of town, driving southwest for the next job, then back up north for the afternoon. Nobody planned it that way — it just happened because jobs came in and got slotted wherever there was an open window. But scattered scheduling is quietly one of the biggest profitability leaks in the business.
What "Batching" Actually Looks Like in Practice
Route density — the concentration of jobs within a tight geographic radius — is the metric that matters here. A tech running five jobs all within a 3-mile radius is having a very different day than a tech running five jobs spread across 40 miles. The first tech might log 15 miles of driving. The second might log 80+. Same number of jobs, wildly different fuel cost, wear on the vehicle, and mental fatigue by 4pm.
Here's a concrete way to think about batching zones for a company with 5–10 techs:
- Divide your service area into geographic clusters. These don't have to be perfect — ZIP codes work well because customers recognize them and they're easy to filter in your scheduling tool. Aim for clusters that take no more than 15 minutes to drive across end to end.
- Assign each tech a "home zone" for the day. That tech fills their day with jobs inside that zone before accepting overflow from adjacent zones. A tech in Zone A takes Zone B work only when Zone A is full.
- Anchor each tech's first job near their home or the zone boundary closest to them. A 20-minute commute to the first job quietly sets the tone for the whole day.
- Protect afternoon density just as hard as morning density. Most dispatchers batch mornings okay but let afternoon slots get scattered when urgent calls come in. Hold the zone discipline even for add-ons.
The Numbers: What Denser Routes Are Actually Worth
Let's put real numbers to this. Say you have 6 techs each averaging 4 jobs a day. Drive time between jobs averages 28 minutes. That's roughly 112 minutes per tech per day in transit — about 672 minutes, or 11 hours, across your whole crew. Every day.
Cut average drive time to 12 minutes through neighborhood batching and you're down to 48 minutes per tech in transit — a savings of 80 minutes per tech. Across 6 techs, that's 480 minutes freed up. At an average job duration of 90 minutes, that's roughly 3 additional jobs your crew could run without anyone working late. At a $200 average ticket, that's $600 in recoverable daily revenue — or about $150,000 a year if you work 250 days.
That math isn't hypothetical. It's what happens when you stop letting jobs get booked wherever there's a gap and start protecting route density like the asset it is.
Where Batching Breaks Down — and How to Fix It
The most common reason batching fails is that customers book themselves into the wrong zone. A homeowner calls, someone answers, checks the calendar for the first available slot, and books them — no one asks where the job is relative to that tech's other work that day. By the time the tech looks at tomorrow's schedule, they've got a job in Riverside at 10am sandwiched between two jobs on the north side.
The fix is to take geography out of the human decision entirely. When a customer books through Cartoply, they enter their address and the platform automatically routes them to the tech whose territory covers that location. Your customers get a real booking confirmation; your techs only see jobs inside their assigned zones. No dispatcher has to manually check a map, and no one accidentally books a tech 35 minutes away from their next job.
The territory setup is flexible — you can draw zones by ZIP code, county, city, or a custom radius around a tech's home base. If you're already running Jobber, Cartoply pulls your service areas in as territories so you're not rebuilding anything from scratch.
A Simple Batching Checklist to Start This Week
- ☐ Map your service area and draw 3–6 geographic zones (ZIP codes are a fast starting point)
- ☐ Assign each tech a primary zone based on where they live or where your job density is highest
- ☐ Set a rule: techs fill their primary zone first, take overflow only when it's full
- ☐ Review tomorrow's schedule today — flag any job more than 15 minutes from a tech's other work and swap it to the right zone
- ☐ Track drive time per tech weekly for two weeks before and after — the number will motivate your whole team to hold the discipline
- ☐ If you're booking jobs online, make sure your booking flow routes by address, not just availability
Start With Tomorrow's Schedule
You don't need new software to try this today. Pull up tomorrow's schedule right now and look at each tech's jobs on a map. If any tech has a gap of more than 15 miles between consecutive jobs, see if you can swap it to a tech already working that side of town. That one swap might save 40 minutes of drive time tomorrow.
When you're ready to stop doing that swap manually for every single booking, Cartoply's territory-based scheduling handles it automatically — every customer gets routed to the right tech the moment they enter their address. You can set it up in an afternoon and have it working before your next booking comes in.