Booking software guide

How much time does an appointment really take?

Customers see the service time. Your team also needs time to prepare, clean up, and reach the next appointment. This guide shows you what to measure and how to test any booking system before you trust its available slots.

Build a schedule your team can actually keep

First checks

Service
The time spent delivering the appointment
Hidden work
Preparation and cleanup around the service
Between visits
Travel and setup before the next appointment

Try it yourself

Can these two appointments fit?

Enter two real appointments. Include service length, preparation, cleanup, and travel. The checker shows whether the next start is safe and, if not, exactly how many minutes are missing.

Your result

5 minutes short

The next service should start at 10:50 or later.

Time available after service: 45 min
Cleanup + travel + next preparation: 50 min
Earliest safe next start: 10:50
Missing time: 5 min

This is a planning aid. It does not make a booking, check live traffic, or guarantee that a particular product supports these rules.

Why this matters

An open slot can still create an impossible day.

A customer may see a 60-minute appointment, but your calendar needs to protect everything around it: preparation before the service, cleanup or notes afterward, and travel to the next stop.

Booking notice and the future booking window are different. They control when someone may make a booking; they do not add minutes to the appointment itself.

The simple rule

Time to protect = preparation + service + cleanup + travel to the next visit

Example: a service starts at 9:00 and lasts 60 minutes. Add 15 minutes of cleanup, 25 minutes of travel, and 10 minutes to prepare for the next customer. The next service cannot safely start before 10:50.

Keep the four kinds of time separate

Only service, preparation, cleanup, and travel consume the working day. Notice and booking-window settings control when customers may reserve.

Service duration

The customer-facing appointment

Use the same duration for the booking page, staff calendar, reminders, price rules, and anything the service reserves. Offering starts every 15 minutes does not turn a 60-minute service into a 15-minute appointment.

Preparation and cleanup

The hidden work around the appointment

Preparation happens before the service. Cleanup, notes, recovery, checkout, or handoff happen afterward. Set them separately because different services consume different amounts of hidden time.

Booking notice and window

When customers are allowed to book

Minimum notice stops last-minute bookings. The booking window limits how far ahead customers can reserve. These policies can hide a date, but they are not buffers and should not change the appointment's occupied time.

Travel between visits

The journey created by the actual route

For mobile work, calculate travel from the previous appointment to the next one. Direction, departure time, and destination matter. Keep a realistic contingency because a route estimate is not an arrival guarantee.

Choose who controls the duration

Choose the simplest model that fits the real service. Recheck price, staff time, resources, calendars, messages, policies, and neighboring appointments whenever duration changes.

Fixed per service

The business sets one length

Use this when a service normally takes the same amount of time. If staff change the length later, the system must recheck surrounding availability instead of stretching the booking silently.

Published duration choices

Customers choose from safe options

Offer clear choices such as 30, 60, or 90 minutes when each choice is a real service variant. Every option should carry its own price, buffers, resource needs, and available slots.

Customer-selected within limits

Customers choose a bounded length

Use this only when any duration inside a minimum, maximum, and step size is genuinely deliverable. The final save must recalculate price, staff time, resources, and the next appointment before confirming.

Staff-adjusted after booking

The team changes the confirmed length

Useful when an appointment grows or shrinks after assessment. The change should show every affected slot, price, resource, calendar event, reminder, and policy outcome before staff approve it.

Measure the real job before changing the software.

There is no universal best buffer. Start with the way your team already works, then turn those observations into service-specific rules.

Measure ready-to-ready time
For several normal appointments, note when preparation begins and when the employee is genuinely ready for the next customer.
Separate preparation from cleanup
A consultation may need ten minutes of notes but no setup. A treatment may need both. Avoid forcing the same gap onto every service.
Decide how combined services behave
If one customer books several services, decide which gaps belong between services and which cleanup happens once after the whole visit.
Test the exact boundary
Try the minute before, the exact allowed time, and the minute after. The slot list and final booking should always agree.

Watch for these software-demo red flags

Ask the demonstrator to create, move, extend, and override appointments while you watch the surrounding availability.

A slot appears, then fails at checkout

The public calendar and final save are probably using different rules. A customer should not be offered a time the system already knows it cannot accept.

Changing one visit breaks the next one

A longer service or a new location affects both neighbouring gaps. The system should recheck the full chain before it confirms the change.

A route error becomes zero travel

If travel cannot be calculated, the safe response is a fallback time or staff review—not pretending the journey takes no time.

Every service gets the same buffer

A single global gap is easy to configure but often wrong. Ask whether preparation and cleanup can vary by service and by combined visit.

Staff can override a conflict silently

Necessary overrides should show the warning, missing minutes, affected appointments, reason, and person who approved the exception.

Test one real day before you shortlist software.

The strongest demo is not a tour of settings. It is your own schedule, entered the same way in every product you are considering.

Measure preparation, service, cleanup, and realistic travel for each important service.
Test a normal day and one difficult day with tight gaps, a location change, and a route failure.
Repeat the test after rescheduling, changing duration or location, cancelling, and using a staff override.