Late guests: time windows, clear routines and the right tone create predictability
A look at how restaurants can divide delays into time windows suited to their own operations, give staff a shared system for signalling table status to one another, and choose a tone that is friendly and specific - without any of this guaranteeing a particular outcome for the evening.
Delays happen regardless - the question is how they are handled
Late-arriving guests are a situation most restaurants are familiar with, though how often it happens and how large the delay becomes varies from place to place. Traffic, parking and prams that need unpacking are factors the restaurant cannot control. What can be controlled, however, is how staff respond when it happens, and whether that response is random or built on a routine everyone knows.
Without a shared routine, handling can vary from person to person. One server holds the table for a long time, another gives it away quickly, and the guest may experience different practice from visit to visit. How long a table should be held is a question the restaurant should settle internally, rather than leaving it to be decided randomly in the moment. This kind of variation also makes it harder to explain why a decision was made.
Divide delays into windows that make sense for operations
A fixed time window does not necessarily suit every situation. How long a lunch booking for a small party should wait during a quiet period may be a different question from how long a large dinner booking should wait when the schedule is tight. By considering short, medium and long windows based on group size and time of day, the restaurant can make the decision more predictable before the delay actually occurs.
A practical starting point can be to ask how long a table for a small party should be held on a quiet weekday, compared with a large group on a busy weekend evening with a tight schedule. The point is not to find the one correct number, but to give staff a shared starting point to work from, instead of deciding everything from scratch each time a guest is late.
Internal communication that makes table status visible to everyone
A time window helps little if only one person knows the clock has started ticking. The restaurant should have a simple way to mark that a table is waiting for a delayed guest, so that everyone who passes the table sees the same status without having to ask. In TableBooking, the dashboard shows bookings, guests and the table map together, which can make this kind of status easier to keep updated throughout the evening.
Once a table has been given a reference marker in the system, it also becomes easier for staff to find the right spot quickly when the delayed guest arrives, particularly in venues with many similar tables or several rooms. Combined with a clear verbal note at shift changes or when tables are being allocated, the risk of a waiting table being given away by mistake can be reduced.
The words used with the guest determine how the delay is experienced
When a guest calls to say they are running late, the response should be friendly and specific, without promising anything the restaurant cannot deliver. A phrase such as "we'll hold the table until 7:15, and let you know if anything changes" is clearer than "it should be fine," which creates an expectation no one can guarantee when the pressure in the room is high.
The same applies when the guest arrives later than the agreed time window allowed. A sentence such as "we've had to release the table, but we'll find a solution as quickly as we can" is honest about the situation while still showing a willingness to help. This kind of language makes the deviation easier for the guest to understand, even when the outcome is not the one originally planned.
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