Two trucks. Both averaging 90 minutes a day behind the wheel between jobs. That’s three hours of paid time producing zero revenue, every working day.
At a fully-loaded labor cost of $42/hour, three hours a day is $126 in wages you can’t bill. Over 250 working days, $31,500. And that’s just the wage side — it ignores the fuel, the wear, and the fact that those hours could have been billable at $95.
You will never get drive time to zero. Nobody does. But most small shops are carrying twice the windshield time they need to, because jobs get scheduled in the order the phone rang instead of the order the map suggests.
Here’s the fix, in three parts: zones, batched estimates, and a Sunday-night board.
First, measure what you’re actually losing
Before you redesign anything, get one week of real numbers. Don’t estimate this. Estimates on drive time are always low.
For five working days, have each tech log four things:
| Field | Example |
|---|---|
| Left shop / left previous job | 7:40 am |
| Arrived at job | 8:25 am |
| Job address zip | 48045 |
| Wrench time on site | 2.75 hrs |
Most job management software will do this for you automatically if you have techs clock in and out by job. If you’re on paper, a note on the back of the work order is fine for one week.
At the end of the week, total it:
| Truck 1 | Truck 2 | |
|---|---|---|
| Drive hours (week) | 8.5 | 7.0 |
| Billable hours (week) | 26 | 29 |
| Drive as % of paid time | 25% | 19% |
A two-truck shop at 25% drive time is burning about one full tech’s worth of productivity every two weeks. That’s the number that makes this worth a Sunday evening.
Part 1: Draw your zones
Open a map of your service area. Draw three to five zones. Not perfect circles — follow the real barriers: the river, the highway, the one bridge that backs up at 4 pm.
A typical setup for a shop with a 30-mile radius:
- Zone A — the city core, 15 minutes from shop, dense, small tickets
- Zone B — north suburbs, 25 minutes, bigger homes, bigger tickets
- Zone C — south and east, 30–40 minutes, spread out, you need a full day to justify going
- Zone D — the far edge. Rural. You only go when you have two jobs or a big one.
Now assign days. The simplest version that works:
| Day | Zones served |
|---|---|
| Monday | A, B |
| Tuesday | C (full day commitment) |
| Wednesday | A, B |
| Thursday | C, D |
| Friday | A, B + overflow |
When someone in Zone C calls on Monday, you don’t say “I can’t come until Thursday.” You say: “I have a crew in your area Tuesday morning — I can get you an 8 am or a 10:30.” That’s a better-sounding answer than a vague Wednesday, and it’s true.
What about emergencies
Emergency calls break zones. That’s the job. The point isn’t rigidity — it’s that your default is clustered, and you break the pattern deliberately for work that pays for the break.
Set a rule: an out-of-zone emergency has to clear a minimum ticket. If your average Zone C job is $650 and the drive is 40 minutes each way, a $180 out-of-zone service call on the wrong day is a loss. Either charge a trip premium for it or offer the next zone day. Half of callers take the zone day.
Zone discipline also gives you a clean reason to decline work you shouldn’t take anyway — which is a separate skill worth reading up on in when to say no to a job.
Part 2: Batch your estimates into one afternoon
Here’s where the hours really hide. Running an estimate across town at 2 pm doesn’t just cost you the 40 minutes of drive — it costs you the half-finished job you walked away from and the 20 minutes of restart time when you come back.
Pick one block a week. Thursday afternoon is common: late enough in the week that you can quote for next week’s schedule, early enough that the customer gets the proposal before the weekend.
Rules that make batching work:
- Every estimate request gets scheduled into the block, not “sometime this week.”
- Schedule them in geographic order, closest to shop first or last depending on traffic.
- Cap the block at five or six stops. More than that and you’re rushing, and rushed estimates lose money.
- Write the proposal on site or in the truck before you drive to the next one. Not that night. Not Saturday.
A solo operator who does four estimates a week spread across four days might burn 4.5 hours in drive and context-switching. The same four estimates batched into one afternoon: about 2.5 hours. Two hours recovered from the same work.
Some jobs don’t need a site visit at all. If you’ve built a flat-rate price book, a whole category of calls — panel swap, water heater replacement, standard fixture install — gets quoted over the phone in five minutes with a photo. Every job you quote without driving is pure recovered time.
Part 3: The Sunday-night schedule board
The zones and the estimate block don’t do anything without 30 minutes on Sunday to lay next week out.
Whatever you use — a whiteboard in the shop, a shared calendar, the schedule view in your job software — the output is the same: every truck, every day, every slot, visible in one view before Monday starts.
The 30-minute routine:
- Pull every confirmed job and drop it on the right zone day.
- Sequence each day by address, not by appointment preference, where the customer gave you flexibility.
- Check materials. Any job needing a supply house run gets scheduled so the run happens on the way, not as a separate trip. This is where supplier net-30 accounts help — will-call orders staged at the counter mean a five-minute stop instead of a 30-minute shop.
- Leave one open slot per truck per day. You will need it. A fully booked week with zero slack turns every emergency into a rescheduled customer and an angry phone call.
- Text confirmations Sunday night or Monday 7 am. Arrival windows, not exact times.
That last one matters more than it looks. A no-show customer at 8 am doesn’t just cost you a job — it blows the whole day’s sequence, because the next stop isn’t ready for you yet.
What the board looks like
| Truck 1 (Zone A/B) | Truck 2 (Zone A/B) | |
|---|---|---|
| 8:00 | Hartley – 412 Oak (A) | Nowak – 88 Birch (B) |
| 10:30 | Diaz – 9 Maple (A) | Open |
| 1:00 | Kim – 217 Oak (A) | Flores – 140 Birch (B) |
| 3:00 | Open | Reed – 155 Birch (B) |
Notice Truck 1’s day: two stops on the same street, a third four blocks away. Nine minutes of total drive after the morning commute. That’s a day where you can take a 3:00 add-on and still be home at 5.
The arithmetic on seven hours a week
Take the two-truck example above: 15.5 combined drive hours, plus roughly 4 hours of estimate-related driving and restart time. About 19.5 hours a week of non-productive movement.
Zone discipline typically cuts inter-job drive by a third once it’s running. Batching estimates recovers about two hours. Rough it out:
| Source | Hours recovered/week |
|---|---|
| Zone clustering (one-third of 15.5) | 5.2 |
| Estimate batching | 2.0 |
| Total | ~7.2 |
At $95/hour billed, that’s $684 a week in capacity you already pay for but don’t sell. Whether you actually convert it to revenue depends on whether you have the demand to fill it — which is a different problem, and a better one to have.
If you don’t have the demand yet, the same seven hours come back as a shorter week or an earlier Friday. Both are real wins.
These numbers are illustrative. Your drive percentage, your zone geography, and your ticket size will all be different. Run your own week of tracking before you believe any of it, and feed the results into your job costing sheet so you can see whether the clustered days actually came in at better margin than the scattered ones. They usually do, and not just because of drive — clustered days have fewer restarts, fewer forgotten parts, and fewer 4 pm phone calls about running late.
Where this breaks down
Be honest about the limits:
- Small service areas. If your whole territory is 12 minutes across, zones won’t buy you much. Focus on estimate batching and supply runs instead.
- Single-truck shops with long jobs. If you’re on one remodel for three weeks, there’s no routing problem to solve. The Sunday board still helps with materials and estimates.
- Trades with hard scheduling constraints. Inspection windows, utility shutoffs, and other trades on a GC’s site override your map every time.
- The first three weeks. Converting an existing booked calendar to zones takes a cycle. Don’t reschedule committed customers to make a map look pretty. Apply zones to new bookings only and let the old schedule run out.
Your next move
Track one week. Four columns, five days, both trucks: departure time, arrival time, job zip, on-site hours.
Don’t change anything yet. Just get the number. If your drive time comes in under 12% of paid hours, you’re already tight and this isn’t your bottleneck. If it’s north of 20%, draw your zones next Sunday and start assigning days to new bookings only.