Why flat buffers fail
A single 30-minute gap after every job overpays on tight urban legs and underpays on cross-town runs. Over a week that means both idle time and late arrivals in the same schedule.
The alternative is to compute the gap from the actual origin and destination of each consecutive pair, then add a fixed on-site buffer for parking, walking the property and writing the job up.
Cluster before you optimize
- Assign territories or ZIP groups to days so bookings self-cluster at intake.
- Offer the customer the day their area is already being served first.
- Keep one flexible crew for out-of-cluster emergencies instead of breaking the pattern.
- Book long-distance jobs at the start or end of the day, never in the middle.
- Track drive minutes per billable hour as a standing route-health metric.
Setting arrival windows customers accept
A two-hour window with an on-the-way text beats a one-hour window that is missed twice a week. Precision that the route cannot support destroys more trust than a wider promise honestly kept.
Narrow windows are earned by route density. Tighten them in areas where you already run several jobs a day, not everywhere at once.
Traffic, weather and the reality factor
- Morning and evening peak drives can run 50-80% longer than off-peak estimates.
- Weather affects both drive time and on-site duration in most outdoor trades.
- Supply house stops are a stop — schedule them, do not pretend they are free.
- Compare estimated vs actual drive time monthly and adjust buffers per territory.