I had two jobs booked back to back on a Wednesday. First one was a sedan at 9am, supposed to take 90 minutes. The second was an SUV at 10:30, 20 minutes across town.
The sedan took 2 hours and 10 minutes. The owner hadn't mentioned the dog hair. By the time I got to the SUV job I was 40 minutes late, sweating through my shirt, and apologizing before I even got out of the van. The customer was annoyed. I rushed. The work wasn't my best. She didn't leave a review.
That Wednesday taught me more about scheduling than any book could have.
The math that seems right but isn't
When you book back to back, the whole day is built on one assumption: every job takes exactly as long as it's supposed to. A sedan is 90 minutes. An SUV is 2 hours. Clean, predictable, tight.
But jobs don't work like that. The car is dirtier than described. The customer comes out and wants to chat. You hit traffic on the way over. There's no margin anywhere in the schedule for any of it. The first overrun breaks the whole day.
A fully-packed calendar looks productive. What it actually is, is one domino away from a bad day.
Being late costs more than you think
The obvious cost is the apology. You show up 30 minutes late and have to open with an explanation. That's uncomfortable. But the real cost is quieter.
The rushed job. The customer who felt like an afterthought. The review that says "nice work but he was late." The person who didn't rebook because the experience felt chaotic. One late job has a long tail. You feel it for months in reviews and rebooking rates, not just in that day's tip.
Buffer time isn't wasted time
Most detailers treat a gap in the schedule as dead time. Money left on the table. I used to think the same way. I wanted every slot filled.
But a 30-minute buffer between jobs changes the whole experience of your day. You arrive calm. You set up without rushing. You do the job at full quality instead of half-speed with one eye on the clock. The buffer absorbs the overrun on the previous job so it doesn't cascade into everything after it.
The buffer isn't lost revenue. It's what makes the revenue you do have worth something.
Drive time is not free
Two jobs on opposite ends of town back to back with no drive time accounted for means you're already behind before the second job starts. You built a schedule that only works if you can teleport.
Drive time is part of the job. It needs to be in the schedule just like setup and rinse time. If you don't put it there, your calendar is lying to you. And a calendar that lies to you is worse than no calendar at all.
How I fixed it
I stopped filling every slot and started designing days instead. I set a minimum gap between bookings — 30 minutes plus realistic drive time for where the jobs actually were. I stopped accepting jobs that required a cross-town sprint to make work.
On paper, I was doing fewer jobs some days. In reality, I was finishing on time, doing better work, and losing almost none of the revenue I thought I was protecting by packing the schedule tight.
Doing this manually was tedious. I was constantly checking maps, estimating drive times, mentally blocking buffers. Eventually that's part of why I built DayHold. It factors in job duration and drive time between stops before showing customers available slots. So the schedule customers see when they book actually reflects how the day works — not a best-case grid that falls apart by 11am.
A tight schedule feels like you're maximizing your day. Usually it means by 2pm you're already behind, you're stressed, and your last customer is getting a worse version of you than your first one did.