Buffer Time Between Service Appointments: How Much Do Techs Really Need?

The right buffer time between service appointments is 15–30 minutes for most home service trades — but that number moves significantly based on job type, drive time, and how tightly you batch jobs by neighborhood. Set it too low and one slow job cascades into a ruined day for every customer after it. Set it too high and you're burning a billable slot on empty road time.

This post gives you trade-specific benchmarks, a five-step process for dialing in your own number, and a checklist for figuring out whether your current buffers are too tight, too loose, or just right.

Why Buffer Time Is a Scheduling Problem, Not a Tech Problem

When jobs run late, the instinct is to blame the tech. But chronic lateness almost always traces back to the schedule itself. A buffer that doesn't account for real drive time, job variability, or customer delays sets your team up to fail before the day starts.

Three things eat buffer faster than owners expect:

• Drive time miscalculation. Fifteen minutes looks fine on paper. At 4:45 PM on a Friday across town, it's not. Buffer needs to absorb realistic drive time, not Google Maps at 2 AM.
• Job scope creep. A "quick filter swap" turns into a full system diagnostic. HVAC, plumbing, and electrical techs deal with this constantly. If your buffer assumes every job finishes on time, it fails the moment one doesn't.
• Customer delays. Gates locked, dogs in the yard, "I'll be there in two minutes" that becomes ten. These minutes come out of your buffer, not the customer's clock.

The result: by mid-afternoon, your tech is 45 minutes behind, the last customer of the day is furious, and your call center is doing damage control instead of booking new jobs. Read more about the downstream effects in the field technician efficiency metrics that actually matter.

Buffer Time Benchmarks by Trade

These ranges come from scheduling patterns across high-frequency home service trades. Use them as a starting point, then adjust based on your own job completion data.

Trade	Typical Job Duration	Recommended Buffer	Primary Buffer Driver
HVAC (tune-up / maintenance)	45–75 min	20–30 min	System diagnostics overrun
HVAC (repair / install estimate)	60–120 min	30–45 min	Parts, quoting, homeowner questions
Plumbing (service call)	45–90 min	20–30 min	Hidden access, scope change
Electrical (service / panel check)	60–90 min	25–35 min	Code compliance, permit checks
Pest control (standard treatment)	30–45 min	15–20 min	Drive time (high job volume per day)
Pool service (weekly route)	20–35 min	10–15 min	Route density; drive time is key variable
Roofing (inspection / estimate)	45–75 min	30–45 min	Roof access, measurement, homeowner time
Landscaping (maintenance visit)	45–90 min	15–20 min	Property size variance
Painting (estimate visit)	30–60 min	20–25 min	Scope discussion, room count

Rule of thumb: buffer should equal roughly 25–35% of your average job duration. If your average job is 60 minutes, 15–20 minutes of buffer is the floor — not the target.

How to Set Your Buffer in 5 Steps

1. Pull your last 30 days of completed jobs and note actual end time vs scheduled end time.
2. Calculate average overrun per job type — treat repairs and maintenance separately.
3. Add your average drive time between jobs (use real road time, not straight-line distance).
4. Set buffer = average overrun + average drive time + 5-minute customer access cushion.
5. Review after 30 days: if techs are consistently arriving early, tighten by 5 minutes. If they're still running late, add 5.

This is also the right moment to audit your territory setup. If your techs are regularly driving 25+ minutes between jobs, your service areas may be drawn too large. Cutting tech drive time by optimizing service territories often does more for your schedule than any buffer adjustment.

The Batching Shortcut

The single fastest way to shrink required buffer is to reduce drive time by batching jobs geographically. When a tech's first four jobs are all within a two-mile radius, the drive leg between stops drops from 20 minutes to five — and suddenly your 25-minute buffer has 15 minutes of genuine slack built in.

Batching by neighborhood also means that when job three runs long, the tech doesn't blow past an entire transit window to get to job four. The math changes completely. This is why territory-based scheduling and buffer time are inseparable — you can't set one correctly without addressing the other. Cartoply's route optimization for field teams builds daily proposals using real road drive-times, so buffer needs are baked into the schedule before the day starts rather than discovered when a tech calls in at 2 PM.

Buffer Time Checklist: Is Your Current Setup Right?

Run through this before your next scheduling cycle:

• ☐ Do your techs arrive on time for the first job of the day but late for the third and fourth? (Buffer is probably fine for the first slot; drive time is the real problem downstream.)
• ☐ Are jobs in the same neighborhood still scheduled 30+ minutes apart? (You're over-buffering — tighten and batch.)
• ☐ Does your scheduling tool use straight-line distance or real road time to calculate gaps? (Straight-line underestimates, especially in suburban or rural areas.)
• ☐ Are repair jobs and maintenance jobs using the same buffer? (They shouldn't — repairs overrun far more often.)
• ☐ Do your techs have a "travel home" buffer at the end of the day, or does the last job butt up against close-of-day? (Missing this one burns your team out fast.)
• ☐ Are no-shows eating your buffer and making the next customer wait? (Requiring a deposit at booking cuts no-shows and protects the slots around them.)

What Happens When You Get It Right

A well-buffered schedule does something counterintuitive: it actually increases the number of jobs a tech can complete in a day. When techs aren't rushing, they close the job cleanly — no callbacks, no "I forgot to check that." They also have two minutes to leave a review request, update job notes, and start the drive to the next stop without stress.

Owners who tighten their buffers based on real drive-time data — rather than optimistic estimates — typically find they can add one additional job per tech per day without extending hours. For a five-tech team, that's five more billable jobs daily. The math on that over a year is significant.

See how this fits into the bigger picture in the right territory size for a tech doing 4–6 jobs a day.

Frequently Asked Questions

How much buffer time should I add between HVAC appointments?

For HVAC maintenance and tune-up visits, 20–30 minutes is a solid starting point. Repair and diagnostic appointments should use 30–45 minutes because scope overruns are common — a "quick fix" often reveals a larger issue. If your techs regularly cross town between jobs, add actual drive time on top of those figures rather than relying on an optimistic default.

Does buffer time count as billable time for technicians?

No — buffer time is non-billable drive and transition time. That's why minimizing the drive component matters so much. When you batch jobs geographically, your buffer shrinks because drive time shrinks, not because you're cutting the slack the tech actually needs. Less buffer burned on driving means more buffer available to absorb legitimate job overruns without cascading delays.

What's the difference between buffer time and travel time in scheduling software?

Travel time is the estimated drive from job A to job B. Buffer time is the extra cushion added on top to absorb overruns, customer delays, and transitions. Good scheduling tools handle these separately. If your software only lets you set a single "gap" number, you're likely either over-buffering short nearby jobs or under-buffering long cross-town ones.

How do I know if my buffer times are set too short?

The clearest signal is a tech who's on time for jobs one and two but consistently 20–40 minutes late by job four. That's a compounding buffer problem. Other signs: frequent customer complaint calls about late arrivals in the afternoon, techs skipping lunch to catch up, and last-slot jobs regularly getting shortened or rescheduled. Pull two weeks of job completion times — the data usually makes the problem obvious.