Almost every venue that has double-booked a room tells the story the same way. Someone took a call on a Saturday, wrote the date on a notepad, meant to put it in the calendar on Monday, and didn't. Two weeks later a second enquiry came in for the same date and the room got sold twice.
It gets treated as a mistake by one person. It almost never is. If three people can take an enquiry and the record of what's held lives in someone's head, a notepad and an inbox, double bookings are not a risk — they're a matter of time. The fix is structural, and none of it requires new software to start.
Why a shared calendar and a spreadsheet still isn't enough
Most venues have already tried the obvious thing: a shared Google Calendar, or a spreadsheet on the office drive. It reduces the problem without solving it, for three reasons.
- Nothing stops a conflicting entry. A calendar will happily accept two events in the same room at the same time and show them side by side. Nothing warns you. You only find out when someone looks closely.
- A tentative hold looks identical to a confirmed booking. Once a pencilled date and a paid-deposit function are the same grey block, staff either release things they shouldn't or hold dates forever out of caution.
- The enquiry and the record live in different places. The conversation is in an inbox, the date is in a calendar, and the money is in a spreadsheet. Keeping three systems in step is manual work that gets skipped on a busy Saturday.
Five fixes, in the order they pay off
1. Name one calendar of record
Not the most calendars — one. Whatever tool you choose, the rule has to be that if a date is not in that calendar, it is not held. No notepads, no "I'll add it later", no dates living only in an email thread. This is a rule about behaviour, not software, and it is the single change that removes most double bookings.
The practical test: if someone rings on a Sunday and the manager is away, can whoever answers see the true state of every room in under thirty seconds? If not, you don't have a calendar of record yet.
2. Make holds expire
A tentative hold with no expiry is just a permanently blocked date. Every venue has a handful of them — someone enquired in March, never came back, and the Saturday has been quietly unsellable ever since.
Give every hold a date it dies on. Seven or fourteen days is typical, and it should be stated to the customer when you place it: "I can hold that for you until the 15th, and it releases after that unless we have your deposit." That sentence does two useful things at once — it protects the date and it creates a deadline that moves the booking forward.
3. Agree on a shared status vocabulary
Most confusion comes from words meaning different things to different staff. "Booked" means deposit-paid to one person and pencilled-in to another. Pick three or four statuses, write them on the wall, and use only those:
- Enquiry — a conversation. Nothing is held. The date is still sellable to someone else.
- Tentative — the date is held, with an expiry. Not sellable until it lapses.
- Confirmed — deposit received. The date is gone.
- Cancelled — released, kept on record so you can see the pattern later.
The point is not the exact words. It is that everyone uses the same four, so a glance at the calendar answers the question "can I sell this?" without a phone call.
4. Decide who can confirm
Taking an enquiry and confirming a booking are different jobs and should have different permissions. Anyone can take an enquiry and place a tentative hold. Moving something to confirmed — the irreversible step — should sit with a named set of people who know the deposit has landed.
In a small team this may be one person plus a backup. Write down who the backup is. Most of the bad weekends happen when the usual person is away and nobody was clear who was covering.
5. Reconcile once a day, not once a month
Five minutes each morning: open the calendar of record, look at the next fourteen days, and check that every tentative hold is either progressing or expiring. It is a small habit that catches the two things that actually cost money — dates being held by customers who have gone quiet, and confirmed functions with no deposit against them.
Where software actually helps
You can do all five of the above with a whiteboard and discipline. What software changes is that it stops depending on the discipline.
A booking system holds availability per room and per site, so two people looking at the same Saturday see the same answer. Holds carry an expiry and release themselves. Statuses are the same words for everyone because they're built into the record, not a convention people remember. And the enquiry, the hold, the deposit and the invoice sit on one booking instead of three systems that have to be kept in step by hand.
That's the part worth paying for: not the calendar, but the fact that nobody has to remember to update it. The same logic applies to the guest count — see getting an accurate headcount. You can see how ezybooked handles holds, statuses and per-branch availability on the features page, and pricing starts free for a single venue.
The short version
If you only change one thing
Name one calendar of record and give every tentative hold an expiry date. Those two changes remove most double bookings on their own, and neither costs anything.