Double bookings: six causes and six fixes

Few moments at the door are worse than two parties arriving for the same table at the same time, each holding a confirmation. One of them will wait, be squeezed in somewhere worse or be sent away, and both will remember it. Double bookings are among the most damaging reservation mistakes a venue can make, because they fall on guests who did everything right.

They are also among the most preventable. Double bookings come from a small number of causes, nearly all of them about how bookings enter the venue and how the diary is kept. Fix those, and double bookings become rare enough to be a genuine surprise.

This guide sets out the six causes of double bookings, a fix for each, and the single change that removes most of them at once: one diary behind every channel. Every figure in it is an example.

A double booking is two bookings that cannot both be honoured as made. The obvious kind is two parties given the same table at the same time. Others are less obvious: two bookings that overlap because the first was given too short a time, a booking accepted when the room was already at capacity, or the same guest booked twice under different names, holding two tables when they need one.

All of them end the same way: at some point in the evening, the venue has promised more than it has.

The most common cause is taking bookings in two places that do not share availability. A booking platform and the venue's own booking page. An online system and a phone diary. A website form that emails the venue, and a separate diary the host fills in. Each channel can sell the same table, because neither knows what the other has sold.

The fix: one diary behind every channel. Every booking, from every source, goes into the same system, so a table sold in one place disappears from all the others at once. Where a channel cannot connect to your diary, give it its own allocation of tables or times that no other channel can sell. Our guide to booking platforms covers how platforms fit around your own booking page.

Many venues keep a paper reservation book "just in case" alongside an online system, or switch between them depending on who is on. Every booking written in the book and not entered in the system is invisible to online booking, and the system will happily sell the same table.

The fix: one record. If the system is the diary, the book is retired, or kept only as a back-up for the rare moment the system is unavailable, with every entry transferred the moment it is back. The paper reservation book has real strengths, but running two records at once combines the weaknesses of both.

A host takes a booking by phone during service, writes it on a pad and means to enter it later. By the time it is entered, the same slot has been booked online. Or it is never entered at all.

The fix: enter every phone booking during the call, from the screen, and read it back to the guest. Our guide to taking bookings by phone when the room is full sets out the routine. A booking that exists only on paper is a double booking waiting to happen.

Two bookings on the same table at seven and eight-thirty look fine in a diary. If the seven o'clock party realistically stays two hours, they overlap by thirty minutes, and the eight-thirty party waits. Double bookings in time, rather than in table, come from booking durations that do not match how long guests actually stay.

The fix: set durations from your own data, by party size and service where you can, and review them every few months. Our guide to turn times covers how to find the right figure.

Guests sometimes book twice: once online and once by phone, to be sure; two members of the same party each booking a table; a guest booking two venues and planning to choose later. The venue holds two tables for one party, and turns away someone else.

The fix: look for duplicates when reviewing tomorrow's bookings, especially bookings with the same name, phone number or email on the same evening. Contact the guest to check. Making it easy to change or cancel a booking reduces the urge to book twice "to be safe".

A guest calls to move their booking from seven to eight; the host moves it in their head, or in the book, but not in the system. A cancellation is taken at the door and never removed. A large party shrinks from ten to six, but the merged tables are never released. The diary drifts away from reality.

The fix: record every change at the moment it is made, in the same system, by whoever takes it. A change that is not recorded leaves the table either blocked when it is free or free when it is taken.

Look back at the six causes and four of them have the same root: bookings recorded in more than one place, or not recorded at the moment they happen. The single most effective change a venue can make is to have one diary, kept in one system, that every booking, change and cancellation goes into immediately, whoever takes it and however it arrives.

With one diary, online booking, phone bookings, walk-ins and the waitlist all draw from the same availability. Tables sold in one place vanish from the others. Changes and cancellations free up tables for everyone at once. Most double bookings simply stop being possible.

Online booking has its own small risk: two guests choosing the same table at the same moment. Good booking systems hold the chosen table for a few minutes while the guest finishes booking, so the second guest cannot book it at the same time, and release it if the first guest gives up.

If your system works this way, set the hold long enough for a guest on a phone to finish, but not so long that tables are held by guests who have walked away. Our guide to booking abandonment covers the balance.

Some venues deliberately accept more bookings than they have tables, expecting some no-shows, as airlines and hotels do. The practice is described in Wikipedia's article on overbooking. In a restaurant, it is risky: when everyone turns up, the venue has created its own double booking, and the guests who wait or are turned away did nothing wrong.

If you overbook, do it knowingly and modestly, based on your own no-show rate for that night, with a plan for the evenings when everyone arrives. For most venues, reducing no-shows through reminders and an easy cancellation link is a safer way to fill the room than overbooking.

Some double bookings are really capacity mistakes: the diary accepts more covers in a half hour than the kitchen and floor can serve, so tables are technically free but the service collapses. Our guide to booking capacity covers how many covers to sell in each period, and our guide to pacing covers so the kitchen never drowns covers spreading arrivals.

Even with one diary, a short daily check catches what slips through. Each afternoon, look at tomorrow's bookings and tonight's:

Five minutes a day prevents most of the double bookings that would otherwise reach the door.

Despite everything, it occasionally happens. Handle it with speed and generosity. Seat the party that arrived first if you can, and look after the other immediately: a drink at the bar while a table is found, a different table, an apology that takes responsibility. If no table can be found, help them find one elsewhere and offer them a reason to come back.

Then find the cause. Every double booking is a clue to which of the six causes is still open.

Large parties are often seated by joining tables, and every join takes tables out of the diary. If a party of ten is booked on two fours and a two that are joined for the evening, all three tables must be blocked for the whole booking. If only one is blocked, the system will happily sell the other two to someone else.

The opposite mistake happens when a large party shrinks or cancels and the joined tables are never released, so tables sit empty while the diary says they are taken. Record joins and splits in the same diary as the bookings, and check them whenever numbers change. Our guide to designing a restaurant floor plan that sells covers layouts that make joining and splitting easier.

Walk-ins cause double bookings when they are seated at a table that is booked later in the evening, for longer than the gap allows. A couple seated at seven at a table booked for eight are lovely guests until they order dessert at a quarter to eight.

Before seating a walk-in, check when the table is next booked, and tell the guests how long the table is theirs: "This table's yours until eight, is that all right?" Most guests are happy to know. Record walk-ins in the same diary as bookings, so the table shows as taken and the next arrival is visible to whoever is on the door.

Private hire, events and closures are bookings too, and they need to be in the diary. A room hired for a party, a terrace closed for weather, a section taken by a large event: each removes tables, and if the diary does not know, online booking will keep selling them.

Block the tables, or the whole venue, as soon as an event is confirmed, not on the day. If the event is provisional, decide whether to hold the space, and put a date on that decision, so a provisional enquiry does not quietly stop the venue selling a whole evening.

Many double bookings happen at the join between shifts: the morning team takes a phone booking and means to enter it, and the evening team arrives and starts selling the same table. A short handover, five minutes at the change of shift, closes most of that gap.

The person handing over checks that everything taken during their shift is in the diary, mentions any changes or cancellations and flags anything uncertain. The person taking over reads tonight's diary before service. Our guide to booking notes the whole team will actually read covers how notes travel through the handover.

Double bookings often come from one person who does things differently: the owner who takes bookings on a personal phone, the manager who writes them on the back of a menu, the bartender who promises a table to a friend. One rule, the same for everyone, is the fix: every booking goes into the diary, at once, by whoever takes it, with no exceptions.

Explain the rule and the reason, and make it easy to follow: a screen at the host stand, a phone that can open the diary, and a short training session for anyone who might take a booking. A rule the owner follows is a rule the team follows too.

Where a booking platform cannot share your diary, the safest arrangement is a fixed allocation: a set of tables, or a set of times, that only the platform can sell. Your own booking page and the phone sell the rest. Review the allocation each week. If the platform's tables are often empty, move some back; if they always sell out first, ask whether the platform is bringing you new guests or simply taking bookings that would have come to you directly.

Each booking from the platform still needs entering in your own diary, so the host sees one complete list on the night. Whoever checks the platform's bookings should do so at set times each day, and before every service.

Some guests book by email, by a message on social media or through the contact form on your website. These are bookings too, and they are easy to lose: the message is read in the morning, answered with "lovely, see you then", and never entered in the diary. The table is then sold online to someone else.

Treat every message that asks for a table as a booking, not a conversation. Check the diary before replying, enter the booking before confirming it, and reply with the same details a confirmation email would carry. Where you can, point guests who message to your booking page, so their booking goes straight into the diary.

When a venue moves to a new booking system, or changes its settings, double bookings sometimes appear because the system does not behave as the team expects. Before relying on it on a busy night, try a few test bookings: two bookings for the same table and time, a booking that overlaps the end of another, a large party that needs joined tables. See what the system allows and what it blocks, then remove the test bookings.

An invented restaurant takes bookings on its own booking page, through a booking platform and by phone, with a paper book at the host stand for phone bookings. It has a double booking most weekends.

It makes three changes. Phone bookings go straight into the main system during the call, and the paper book is retired. The platform gets its own allocation of four tables on Friday and Saturday, which the restaurant's own page cannot sell. And booking durations for parties of five or more are lengthened to match how long they actually stay. Double bookings drop to a rare event, and the host stops dreading the eight o'clock rush.

servearound keeps one diary behind every way a booking arrives. Bookings from your booking page, the widget on your website, the phone, staff and walk-ins all go into the same reservations, so a table taken in one place is gone from the others, and the waitlist draws on the same availability. While a guest finishes an online booking, their table is held for the time you set, and released if they give up. See the reservations module.

Booking rules set the booking duration, the booking times for each shift and the maximum party size online, and staff can assign and seat tables on the floor plan. servearound does not connect to other booking platforms, so bookings taken on a platform need entering by hand, or a separate allocation of tables, to avoid double bookings.

Bookings taken in two places that do not share availability: a platform and your own page, or a paper book and a system.

Keep one diary that every booking, change and cancellation goes into immediately, whoever takes it and however it arrives.

Only as a back-up for when the system is unavailable, with every entry transferred the moment it is back. Running both at once causes double bookings.

Yes. If a booking is given less time than guests actually stay, the next booking on that table overlaps it.

Check tomorrow's bookings for the same name, phone or email on the same evening and contact the guest to confirm which booking they want.

It is risky in restaurants. If you do it, base it on your own no-show rate and have a plan for nights when everyone arrives.

Quickly and generously: seat the first party if possible, look after the second with a drink and a table, apologise, and find the cause afterwards.

They can, if they sell the same tables as your own page without sharing availability. Give them their own allocation or connect them to your diary.

Every afternoon, for tonight and tomorrow, looking for overlaps, duplicates, changed numbers and bookings not yet entered.

They can, when a walk-in is seated at a table booked later without enough time. Check when the table is next needed and tell the guests how long it is theirs.

Yes. Private hire, events and closures remove tables, and online booking will keep selling them unless they are blocked as soon as the event is confirmed.

Yes, if they are answered without being entered. Enter every booking in the diary before confirming it, however it arrived.

Double bookings come from six places: channels that do not share availability, a paper book alongside a system, phone bookings entered later, booking durations shorter than guests stay, guests who book twice, and changes that are never recorded. Each has a fix, and most share one: a single diary that every booking, change and cancellation goes into at once.

Hold tables while guests finish booking online, set durations from your own data, give unconnected channels their own allocation, avoid overbooking unless you know your no-show rate, and check tonight's and tomorrow's diary every afternoon. When a double booking still happens, put it right generously and then close the gap that caused it.