How much travel buffer should you leave between appointments?

What should a travel buffer include?

Count every task between finishing work for one customer and being ready for the next. That can include cleaning, notes, equipment pack-down, driving, parking, walking, building access and setup. If a task prevents you from travelling or starting, it occupies the transition whether or not it appears on a map.

Keep the buffer separate from inaccurate service duration. When hands-on work repeatedly finishes late, extend the service. When a city-centre appointment creates a parking search, adjust the relevant access allowance. One oversized generic buffer hides the cause and makes future improvement harder.

• Pack-down after the first service
• Expected door-to-door journey
• Parking, walking and access
• Setup before the next service
• A proportionate uncertainty margin

How do you choose a starting number?

Measure a representative week. Record actual service end, departure, arrival and ready-to-start time for different postcode pairs and times of day. Exclude neither normal slow journeys nor ordinary setup work. Label exceptional disruptions separately so one severe incident does not dictate every future appointment.

Find the range that covers normal transitions for each useful group: nearby, cross-area, peak period or difficult-access locations. Start conservatively enough to keep commitments, then refine after more evidence. A number copied from another business is unreliable because service equipment, geography and arrival requirements differ.

Should you use an average or a range?

An average can hide important variation. If half your complete transitions take twenty minutes and half take fifty, thirty-five minutes is not dependable for the long group and wastes time for the short group. A range or location-based rule preserves the difference instead of pretending every journey is typical.

For a fixed buffer, choose a value that safely covers normal journeys inside a deliberately compact area. Handle exceptional outer locations on selected days or manually. For varied geography, calculate by postcode or road context and add the non-driving operational time consistently.

When should distance change the buffer?

Distance should change the answer whenever regular customer pairs create materially different transition times. A five-minute local drive and a thirty-five-minute cross-area drive should not both inherit a forty-five-minute blanket gap unless simplicity is worth the lost nearby capacity to your business.

Time of day and access can matter as much as distance. School traffic, bridges, city parking or building entry can make one route variable. Road and expected-traffic checks add context, but they do not include every incident or on-site task. Retain a margin based on your observed uncertainty.

What does a worked buffer example look like?

A mobile service finishes at 14:00. Packing takes ten minutes, the expected drive is twenty, parking takes five and setup takes ten. The operational transition is forty-five minutes, making 14:45 the earliest next start before any separate uncertainty margin. Each term should come from the way the business actually works.

If completed data shows that this route varies by up to ten minutes under ordinary conditions, the business might protect a 14:55 start. If another customer pair has only a five-minute drive, the equivalent total is thirty minutes plus its margin. Variable scheduling can avoid imposing 14:55 on both.

How do you protect the onward appointment?

For an in-between booking, calculate the transition into it and the transition out. Add the proposed service duration between those journeys. The complete chain must fit before the next confirmed start. Otherwise a reachable new customer can still make the following appointment impossible.

Apply boundary rules at the beginning and end of the day. If travel from base matters before the first visit, include it. If the final return does not constrain a customer commitment, it may be handled differently. Document the choice so staff and software tests use the same assumptions.

How often should the buffer be reviewed?

Review after the first week of a new rule, then monthly and after changes to services, coverage, season or working hours. Compare planned with actual ready-to-start time. Record the cause of differences so travel settings are not blamed for longer services or customer delays.

Change one element at a time and keep a safety threshold. Track excessive waiting as well as late arrival, because both reveal poor fit. Do not remove margin merely because a few days ran smoothly. A stable buffer should tolerate ordinary variation while leaving severe exceptions for customer communication and manual recovery. Note seasonal roadworks, school terms and recurring local events in the review so a temporary quiet period does not become the permanent baseline.

• Separate service overrun from journey delay.
• Review edge postcodes and peak travel periods.
• Measure ready-to-start time, not arrival alone.
• Keep an exception process for major disruption.
• Use repeated evidence before tightening the rule.