Key takeaways
- Most double bookings come from a second diary: a paper pad, a phone note or a platform that does not sync. One live diary with one owner per shift removes most of them.
- When it happens anyway, the party that arrived on time is not the problem. Offer a real choice within two minutes, not a loop of apologies.
- Agree a recovery ladder before service so hosts can act without hunting for a manager.
- Never tie a free dessert or discount to a review: concealed incentivised reviews are banned content under CMA guidance[1].
Why double bookings still happen
A double booking means two parties hold the same table at the same time. Software alone rarely causes it. The usual culprit is a gap between two places where bookings live, or a manual override made in a hurry. Evenings carry the risk: restaurants, cafés and bars took 42% of time-stamped consumer spending between 6pm and 6am in an ONS sample week[2], so clashes land in the slots you can least afford to lose.
| Cause | How it shows up | Fix |
|---|---|---|
| Second diary | A phone booking written on a pad and never entered | Ban side books; phone bookings go straight into the live diary |
| Platform not syncing | A third-party booking lands on a table already sold online | Map every channel to the same table plan and check sync daily |
| Manual table move | A manager moves a four to fit a six and strands the original party | Moves only through the diary, with a note of who moved it |
| Duplicate guest record | One guest books twice under two spellings | Search by phone number before confirming |
| Wrong date typed | The diary says the 14th; the guest heard the 15th | Read the booking back and send a written confirmation |
| Walk-in on a held table | A walk-in is seated at a table due in 20 minutes | Visible hold tags on the floor plan and a turn-time check |
Prevention: one diary, one owner, one rule
Prevention costs less than recovery. The goal is simple: every booking, from every channel, lands in one diary that the host stand trusts on the night. The guide to running one diary across Google, Instagram and platforms covers syncing in depth. These are the essentials.
Name the diary owner
One person per shift owns the diary. Anyone can add bookings, but only the owner moves or overrides tables during service.
Retire the side books
Collect the paper pads, the shared notes app and the sticky notes. If the system goes down, use one printed sheet that the owner types up afterwards.
Make the read-back a habit
Every phone booking ends with the day, date, time, party size and name read back, followed by a written confirmation. Saying the day as well as the date catches most mishearings.
Check channel sync at opening
Before each service, compare the number of tonight’s bookings on each platform with the diary. A mismatch of even one booking means stop and check.
Search before you save
Look up the phone number before confirming a new booking. A second booking under the same number is often a duplicate or a change of plan.
Lock the plan close to service
From an hour before doors, table moves need the owner’s approval. That stops well-meant shuffles that strand a party.
The first two minutes at the door
When two parties arrive for one table, the host’s tone decides the evening. The guests who turned up on time have done everything right, and they know bookings are a two-way promise: 83% of diners in OpenTable’s research recognised that failing to honour a reservation can harm a restaurant[3]. They expect the venue to keep its side too. Hosts should be able to run this sequence without fetching a manager first.
- Own it plainly: “I’m sorry, we’ve made a mistake with the diary and your table isn’t ready. That’s on us, not you.”
- Separate the parties. Never let two groups debate one table at the stand; take the second party to the bar or a quiet corner.
- Give a real time. “I can seat you at a table for four in 15 minutes” beats “shortly”.
- Offer a choice rather than a decision: wait with a drink on the house, take the next available table, or rebook at a time they choose with a gesture on the return visit.
- Confirm what you agreed and who is looking after them: “I’m Sam, and I’ll come and get you myself.”
- Log it on the booking before the end of service so the next shift knows.
A recovery ladder staff can use
Set the ladder before service. Hosts should not need a manager for the first two rungs. Keep gestures in proportion to the wait and the occasion; an anniversary kept waiting half an hour needs more than a round of soft drinks.
| Situation | Offer | Who can approve |
|---|---|---|
| Wait under 10 minutes | Drinks at the bar on the house and a warm handover to the table | Host |
| Wait of 10 to 30 minutes | Drinks plus a starter or dessert for the table, with a check-in every 10 minutes | Host or supervisor |
| No table tonight | A rebooking at a time of their choice, a held table and a meaningful gesture on the return visit | Manager |
| Special occasion affected | The manager speaks to the party in person and personalises the rebooking | Manager |
| Guest leaves upset | Take a number, call the next day, offer to rebook and note it on their record | Manager |
Speed matters because a broken table rarely costs only one booking. When OpenTable asked operators about the knock-on effects of no-shows, 60% said no-shows had led them to turn away other bookings[3]. A double booking runs the same chain in reverse: the slot that looked sold twice could have gone to a third party who rang and was told you were full.
Example: a Friday clash at a 60-cover bistro
Example. A fictional 60-cover bistro takes a phone booking for four at 19.30 on a Friday. The system is slow, so the staff member writes it on a pad. Ten minutes later an online booking for table 12 at 19.30 arrives. At 19.25 both parties walk in. The host apologises, seats the online party at table 12 and takes the phone party to the bar with drinks on the house. Two neighbouring two-tops free up at 19.45; the host joins them and walks the party over personally, and a dessert for the table follows. The next morning the manager removes the pad, adds a sync check before each service and records the cause in the incident log.
What made it work: the host gave a time, offered a choice, stayed with the guests until they were seated, and the cause was fixed rather than blamed on a person.
When the clash is spotted before the guests arrive
The best double booking is the one you find at 4pm rather than at the door. A pre-service diary check catches most of them, and the fix is far easier while guests are still at home.
- Look for two bookings on one table at overlapping times, and for any table holding more covers than seats.
- Decide which party is easier to move: a two on a four-top can often go to the bar or a counter seat; a six usually cannot.
- Call the party you need to move, not text them. Explain the mistake, offer two alternative times or a different table, and say what you will add to make up for it.
- If you cannot reach them, plan the floor so they can be seated within minutes of arrival, and brief the host by name.
- Update the booking notes so whoever is on the door knows the history before the guest says a word.
Guests who are told early, by a person, with a real alternative, rarely leave unhappy. Guests who discover the mistake at the stand often do, however good the free drink.
Compensation, reviews and what not to promise
Under the Consumer Rights Act 2015, every contract to supply a service includes a term that the trader performs it with reasonable care and skill[4]. A booking you accepted and then could not honour is the venue’s mistake, so treat recovery as putting things right rather than as a favour. Keep the gesture proportionate and record it on the guest’s profile.
Avoid two traps. First, never offer a free dessert or discount in exchange for a positive review. The Competition and Markets Authority treats concealed incentivised reviews as banned content, and businesses that publish reviews must take reasonable steps to prevent fake ones[1]. Ask every guest for honest feedback; never buy a good one. Second, do not promise a table you cannot see on the floor plan. A second broken promise on the same night does more damage than a longer, honest wait.
Peak dates raise the stakes. NIQ describes Christmas and New Year as the sector’s crucial trading period[5], and those weeks bring more large parties and more phone changes. Run the sync check twice a day from late November.
After service: close the loop
- Record every double booking with the date, slot, channels involved and cause.
- Review the log weekly. Three incidents from the same cause point to a process fault, not bad luck.
- Call the affected guest the next day if they left unhappy, and note the outcome.
- Brief the team at the next pre-shift meeting on what happened and what changed.
- Check that your booking confirmation shows the day, date, time and party size clearly, so guests spot errors early.
If phone bookings cause most of your errors, look at who answers the phone during service. An AI employee such as Ava can take booking requests and log every call, so details are captured the same way each time and passed to the diary owner instead of being scribbled on a pad mid-rush.
Frequently asked questions
What should we say when we have double booked a table?
Own the mistake straight away, separate the two parties, give a real time and offer a choice: wait with a drink on the house, take the next available table, or rebook with a held table. Do not blame the system or the other guests.
Who keeps the table when two parties hold the same booking?
Usually the booking that was made first and confirmed in writing. Look after the second party with your recovery ladder rather than debating it at the door.
Can we give a discount if the guest leaves a good review?
No. CMA guidance treats concealed incentivised reviews as banned content[1]. Make recovery gestures freely and ask for honest feedback separately.
How do we stop double bookings from third-party platforms?
Map each platform to the same table plan, compare tonight’s booking counts with the diary before service, and treat any mismatch as a reason to stop and check.
References
Competition and Markets Authority (2025). Short guide for businesses: publishing consumer reviews and complying with consumer protection law (opens in a new tab) ↑
Office for National Statistics (2022). The night-time economy, UK: 2022 (opens in a new tab) ↑
Restaurant Online (2026). No-show rates fall year-on-year, report finds (OpenTable Restaurant Impact Report) (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2015). Consumer Rights Act 2015, section 49: service to be performed with reasonable care and skill (opens in a new tab) ↑
NIQ (CGA by NIQ) (2026). Hospitality loses 19 licensed premises a week ahead of crunch Christmas (Hospitality Market Monitor Q3 2026) (opens in a new tab) ↑