Waitlists in practice: a sober workflow for capacity, contact and deadlines
A practical look at which capacity signals should determine whether the waitlist is opened, how expectations are kept realistic both internally and externally, which contact order is easiest to defend afterwards, and why a fixed expiry time makes the routine predictable for both guest and staff.
Capacity signals that should actually trigger a waitlist
A waitlist should not be opened because the evening feels hectic, but because there is a clear signal that capacity has genuinely run out. Look at the number of confirmed bookings against tables actually available, not against total capacity on paper. For restaurants using the TableBookings dashboard, the floor plan gives an overview of bookings and tables, which makes this assessment easier than relying on a guess from memory.
Another signal is the pattern of cancellations in the last hour before service. How many cancellations the restaurant normally sees at this point, and whether the waitlist should wait until the pattern is confirmed for the evening, are questions each restaurant must settle for itself. Opening the waitlist too early can create an unnecessary queue, while waiting too long leaves staff less time to plan table turnover.
Expectation management that keeps staff and guest aligned
Before a guest is placed on the waitlist, staff should have an internal understanding of what can actually be promised. That means a brief check-in between host and kitchen about realistic table turnover, not a guess based on optimism. Without this internal alignment, the restaurant risks giving the guest a timeframe that does not match what is actually happening on the floor.
Externally, the expectation should be framed as a possibility, not a promise. There is a difference between telling a guest they are first in line for a table within a given window, and suggesting a specific time. The first phrasing allows for normal variation in operations, while the second creates an expectation staff must defend if the timing slips.
A contact order that is easy to explain afterwards
The simplest order to defend is time of registration, adjusted for party size. The guest who signed up first is contacted first, but only if an available table actually suits the group size. If a table for two becomes free and the next group on the list is four people, it is reasonable to move on to the next registration rather than leave the table empty.
This kind of skip should be briefly noted with a reason, such as table size or no response within the deadline. Without a noted reason, the order can look arbitrary in hindsight, even when the decision was correct at the time. A simple log makes it possible to explain the choice to a guest who asks, or to a colleague taking over later in the evening.
An expiry time that makes the waitlist predictable for both parties
An expiry time should reflect how long it takes to reach the guest, and how long the restaurant can realistically hold a table open. How many minutes this should be depends on party size, day of the week, and how full the venue is, and is a choice each restaurant must make for itself. The time should be short enough that the table doesn't sit empty for long, but long enough that the guest has a genuine chance to respond.
When the deadline expires without a response, the next person on the list should be contacted immediately, and the original guest moved to the end or removed from the list, depending on the restaurant's own practice. This should be a fixed rule applied equally to everyone, not a judgment made anew each time. A short review after service, counting up expired cases, shows whether the deadline has actually been set correctly.
Want to see how it works in practice?
Start with a free restaurant account and build your tables, opening hours and booking link at your own pace.
Start free