When guests arrive late: clear time windows, shared information and calm language
A look at how a restaurant can divide delays into time windows it defines itself, ensure that floor and kitchen staff have the same information at the same time, and use language that is clear and friendly without promising a specific outcome for the evening.
Time windows the restaurant defines itself
Many restaurants rely in practice on a single vague term - "late" - which can mean very different things depending on the situation. One alternative is to divide delays into a few time windows, such as a short, a medium and a long delay. Where the boundaries between these windows should be set is something each restaurant should decide for itself, based on its own table turnover and how tightly bookings are spaced that particular evening.
The point of the windows is not to promise the guest anything, but to give staff a shared understanding of what should happen next. A short delay rarely requires any action. A medium delay should trigger a quick assessment of the table. A long delay should trigger a decision made internally before the guest reaches out or shows up.
Internal communication that keeps everyone updated
Delays rarely cause problems on their own - it's the lack of shared information that leaves a table sitting empty, or leads two staff members to perceive the same table as available at different times. A consolidated overview of bookings, guests and the floor plan makes it easier for the host and server to see which tables are in play, without having to clarify it verbally in the middle of a busy rush.
TableBooking displays bookings, guests and the floor plan in a unified dashboard, and tables can have a reference photo that makes it quicker to confirm which table a booking refers to when several staff members are involved in resolving a delay. The tool does not, however, replace a clear routine for who updates the status, and who has the final say when a table needs to be reassessed.
Language that is specific without making promises
When a guest reports that they're running late, it's tempting to respond with something reassuring but vague, like "it'll probably be fine." A more useful response is specific without becoming a promise: stating how long the table will be held, and asking the guest to give an update if anything changes. The wording is friendly, but it describes a limit rather than a guarantee, and it gives the guest a clear task.
It's worth avoiding phrases that imply a guarantee the restaurant can't keep, such as "the table is yours no matter what" or "no problem, take all the time you need." Such responses can create an expectation that later collides with the next booking or with the kitchen's pace later in the evening, and they make it harder to explain any subsequent change in a clean, orderly way.
How the three elements work together
The time window determines when something should happen. Internal communication determines whether everyone involved actually knows that it's happening. The language determines how the guest experiences the situation while it's unfolding. None of these elements resolves a delay on its own, but together they can provide a routine that stays consistent from table to table, regardless of who is running the floor that evening.
The value of such a setup lies in its repeatability, not in any guarantee of a specific outcome. Some evenings a table will still have to be released, and some guests will still feel that the wait dragged on. What the setup contributes is more predictable handling internally - so that decisions are made by the same logic every time, rather than depending on the mood in the moment.
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