Route Density: How to Cut Drive Time and Fit More Jobs Into the Same Dayv

There is one line item that never shows up on an invoice and never shows up in your P&L as its own number, and it is probably the most expensive thing your business does all week.

Driving.

You pay your tech for it. You pay for the fuel. You pay for the wear on the truck. The customer pays for none of it. Every minute a van is on the road between jobs is a minute of payroll you spend and cannot bill.

Most owners try to fix a capacity problem by hiring. Before you do that, look at your routes. There is usually a truck's worth of hours already sitting inside your current schedule.

What route density actually means

Route density is how much billable work you get out of a given amount of driving. A tech who does five jobs inside a four mile radius has high density. A tech who does five jobs spread across three towns has low density, even though it is the same five jobs and the same paycheck.

The goal is not to drive less for its own sake. The goal is to move the ratio: more wrench time, less windshield time.

Do the math on your own trucks

Run this for one truck, for one week. You do not need software to do it. Pull last week's schedule and a map.

Say your tech runs five stops a day. That is four drives between jobs, plus the drive out in the morning and home at night. If the average leg between stops is 35 minutes, that is 140 minutes a day just moving between customers. Call it two hours and twenty minutes.

Now say you tighten the route and get the average leg down to 20 minutes. Four legs is 80 minutes. You just gave that truck an hour back, every single day.

An hour a day is five hours a week. Five hours a week is roughly 250 hours a year, per truck. At a typical service ticket, that is not a rounding error. That is a real number that either shows up as more jobs, or shows up as your crew getting home on time instead of eating dinner at nine.

Do the same math with fuel. A truck that runs 90 miles a day instead of 130 is saving you 40 miles a day in fuel and maintenance, and you do not have to sell anything extra to get it.

Why schedules leak time

Almost nobody sits down and designs a bad route. It happens by default, for four common reasons.

You book in the order the phone rings. A customer calls Tuesday, you have a Thursday morning slot open, you take it. The next customer calls Wednesday, you have Thursday afternoon open, you take that. Nobody looked at where those two houses are. The schedule got built by chronology instead of geography.

Your service area has no shape. You will drive anywhere within an hour because turning down work feels wrong. That works when you have three customers. At forty customers, an unbounded service area means every day is a scramble.

Emergencies blow up the plan. One same-day call gets wedged into a tight route and the whole afternoon becomes a chase. This one is unavoidable in some trades. It is manageable, though, and we will get to it.

Techs pick their own order. Left to their own judgment, most techs run the day in the order that makes sense to them, which is often the order of easiest to hardest, not nearest to farthest.

Five things that actually tighten a route

1. Zone your service area by day of the week

Draw your service area on a map and cut it into four or five zones. Assign each zone a day. North side is Monday and Thursday, south side is Tuesday and Friday, and so on.

When a customer calls for a non-urgent job, you are not asking "when are you free?" You are saying "we are in your area Tuesday, does morning or afternoon work?" Most customers say yes to that, because most non-emergency work is not actually urgent to them either. They just want a day and a window.

This one change does more than every other item on this list combined. It turns your calendar from a list into a map.

2. Book by proximity, not by next open slot

For the jobs that will not fit a zone day, the question when booking is not "what is my next opening" but "what is my next opening near where I already have to be."

That requires whoever books the job to be able to see the day's existing stops while they are on the phone. If your schedule lives in one person's head or on a whiteboard in the shop, this is impossible. If it lives somewhere everyone can see, it takes ten seconds.

Better still is seeing the actual drive time between those stops, not just the addresses. Two jobs can look close on a map and be twenty five minutes apart in real traffic, and two that look far can be a straight shot down one road. This is exactly what scheduling in Procured does. When you build the day, it maps the real drive time between each job, so you can see before you commit whether that new stop adds ten minutes to the route or forty. You are scheduling against the road, not against a guess.

Drive view on the Procured schedule board. Each row is a tech, each block is a job, and the gap between them shows the actual drive time. Here, four techs are each losing 1 hour and 24 minutes getting from the morning job to the afternoon job. That is nearly six hours of paid time across the crew, in one day, before anyone picks up a tool.

That is the whole point of seeing it on the board. Nobody sets out to build a day like the one above. It happens when the morning job and the afternoon job get booked a week apart by two different people, and nothing on the screen connects them. Once the drive shows up as a block on the schedule the same way a job does, it stops being invisible, and you can fix it while you are still booking.

3. Protect one slot a day for the fires

If you run emergency work, stop pretending you do not. Leave a hole in the middle of the afternoon on purpose, every day. When the same-day call comes in, it drops into a slot that was built for it instead of shoving four other jobs sideways.

If the hole goes unused, your tech gets ahead or goes home early. That is a good problem. It is a much better problem than a five car pileup of late arrivals and one angry customer at the end of it.

4. Batch the small stuff

Fifteen minute jobs are murder on a route. A filter swap, a quick warranty look, a callback to check on something. Each one is a full drive out and back for almost no billable time.

Stack them. Keep a running list of small jobs and attach them to a day when you are already in that zone. Customers rarely mind waiting a few days for something minor if you tell them up front when you are coming.

5. Give the tech the whole day in one place

The route only stays tight if the person driving it can see it. Address, contact, gate code, what was done last visit, what parts to bring, and what order to run it in, all on the phone in their hand before they pull out of the driveway.

Half of lost route time is not driving between jobs. It is calling the office to ask which house, driving back to the shop for a part, or arriving without knowing what happened on the last visit and having to figure it out from scratch. Density is not just about distance. It is about not repeating a trip you already made.

Track three numbers

You cannot improve what you never look at. Pick three and check them monthly.

Jobs per truck per day. The simplest measure of whether density is improving. If it goes from 4.2 to 5.1 without anyone working longer, you found capacity for free.

Billable hours divided by paid hours. This is the honest one. If your tech is paid for nine hours and bills five, the other four went somewhere, and drive time is usually the biggest slice.

Average miles per job. Total odometer miles for the month divided by jobs completed. This one is easy to pull and hard to argue with.

You do not need all three to be perfect. You need them to be moving in the right direction quarter over quarter.

The part nobody tells you

Tightening routes is not a software problem first. It is a booking discipline problem. Zones and buffers and batching are decisions you make on the phone, weeks before the truck ever moves.

What software does is make the discipline possible to hold. When the schedule is visible to whoever answers the phone, when the tech can see the full day and the full customer history from the field, and when dispatch changes show up on the truck instantly instead of through a phone call, the good habits stick. Without that, you will design a beautiful zone map on a Sunday and abandon it by Wednesday.

That is the whole idea behind how we built scheduling and dispatch inside Procured. You schedule jobs out and see the mapped drive time between each stop as you build the day, so route density stops being something you find out about after the fact and becomes something you decide on while booking. Your customers, quotes, jobs, schedule, and invoices sit in one place, so the person answering the phone can see the day they are booking into, and the tech in the truck can see everything they need without calling the office.

Before you hire another tech to handle the load, spend a week looking at where your trucks actually go. There is a good chance the capacity you need is already on the schedule, buried in drive time.