In this guide 6 sections
Double bookings come from four gaps. Channels keep separate calendars, slots are not held during payment, rooms and staff are booked as unrelated items, and reception edits skip the availability check. One shared calendar, a timed hold at checkout and linked resources close all four gaps, provided every channel writes to the same place.
Separate calendars are the first cause
The paper diary, the portal’s own calendar and a staff member’s phone are three sources of truth, and each is correct about itself and wrong about the others. That is the flaw.
A walk-in is written in pencil at ten o’clock, and the portal sells the same slot at ten past, because it never saw the pencil. Nobody was careless. The diary and the portal never spoke.
The control is simple to say and hard to do: every channel must read and write one calendar in real time, even when the front desk is busy.
- Portal bookings write straight to the master calendar
- Phone and walk-in entries use the same screen as the portal
- Staff phones show the same calendar, not a copy
- Paper diaries are retired or entered within minutes
The slot nobody is holding
A customer picks 4 pm and opens the payment page, and for three minutes the slot looks free to everyone else who is browsing the same afternoon. A second customer pays faster and wins. The first payment then succeeds or fails against a slot already gone, and someone at the desk must phone the customer to apologise and offer a different time.
A timed hold fixes this. Simple, but strict. The slot locks when the customer starts checkout and releases after a few minutes if payment does not arrive, so a stalled card never blocks the diary.
Test the failure path too. A payment that completes after the hold expired must either re-check the slot or be refunded automatically, and the customer should hear which happened within a minute.
Rooms and staff booked independently
A treatment needs a therapist and a room, and a class needs an instructor, a studio and sometimes a reformer bed, so one booking holds several resources. Separate calendars hide the clash.
Model the booking as a bundle. The slot is only offered when every required resource is free for the whole duration, including cleaning or setup time before and after.
Buffer time is often the hidden culprit. Cleaning counts too. A forty-five minute service in a sixty minute slot looks fine until another customer is booked at the forty-five minute mark while the room is still being reset.
- Service defines the resources it needs
- Duration plus buffer blocks every resource
- Staff leave and room maintenance block slots automatically
Edits made at reception
Rescheduling is where most clashes enter. A receptionist drags a booking to a new time, an override lets it land on top of another, and the portal then shows both customers in one slot.
Allow overrides, but make them deliberate. No silent drags. Ask for a reason, show the clash in red, and record who made the change and which channel the original booking came from.
Check cancellations too. A cancelled booking should free every resource it held, the room, the equipment and the staff member, otherwise the diary shows a phantom clash that blocks a sale.
Find your clashes before changing anything
Export last month’s bookings and sort by resource and start time; overlaps show up as consecutive rows where one ends after the next begins.
Tag each overlap with its channel and cause. A pattern usually appears within an hour of tagging, and it tells you which of the four controls to build first, which is cheaper than guessing.
Take that list to your next software vendor meeting, because it is a sharper brief than a general complaint about clashes, and it names the channel at fault. Bring dates, not impressions.
Double booking audit sheet
A single log with columns for date, resource, the two clashing bookings, the channel each came from, who edited last, probable cause from four options and the fix owner. A summary box counts clashes by cause.
Open a blank worksheet to printQuestions owners ask
How long should a slot be held during payment?
Long enough for a normal checkout, commonly several minutes, with a visible countdown so customers know exactly when the slot will release back to everyone else.
Can one calendar cope with walk-ins?
Yes, on the same screen. Treat a walk-in as a booking that starts now, with a named resource and a duration, so the pencil entry becomes a record the portal sees at once.
Should overbooking ever be allowed?
Some venues choose it on purpose, for example to cover no-shows, but it should be a setting with a hard limit per slot and not an accident.
What if two staff book the same moment?
The system must lock the resource at save time so the second save fails with a clear message, and the screen should then display the nearest alternative slots.