Key takeaways
- Pick a grace period by booking type, often 15 minutes for standard tables, and show it at booking.
- Call at a set point, such as ten minutes late, before deciding anything. Most late guests are on their way.
- Record late arrivals and no-shows separately: a no-show only counts when staff record it[1].
- Guests know a lost booking costs a venue: 83% recognise it can harm a restaurant[2]. Clear rules are accepted when they are fair and stated in advance.
Why late arrivals matter more than they seem
A table that is 20 minutes late is not just one late table. It pushes back the kitchen, squeezes the next booking on that table and can land the party in the busiest slot of the night. On a full Saturday, a late four can delay a 21.00 booking, which in turn makes another guest wait at the bar. Without a policy, hosts make the call on the spot, and every evening is different.
Guests usually understand this. In OpenTable’s research, 83% of customers recognised that failing to honour a reservation can harm a restaurant’s business[2]. What they object to is a rule they were never told, applied without warning. A grace period that is written down, shown at booking and applied kindly removes most of the friction.
Choosing a grace period
| Booking type | Suggested grace period | Why |
|---|---|---|
| Standard table, quiet night | 20 minutes | Plenty of tables; flexibility costs little |
| Standard table, busy night | 15 minutes | The table is needed for a later booking |
| Counter or bar seat | 10 minutes | Short seat times and walk-ins waiting |
| Large group | 15 minutes for the first arrivals | Seat the group as people arrive |
| Set start time or tasting menu | None for the start; join where the menu has reached | The menu runs to a fixed pace |
| Pre-theatre | 10 minutes | The guest’s own deadline is fixed |
Fifteen minutes is the most common choice for standard tables because it absorbs a missed train or a parking hunt without wrecking the evening. Whatever you pick, use the same figure on the website, in the widget, in the confirmation and at the host stand.
Let the evening shape how strictly you apply it. On a quiet Tuesday with empty tables, there is no reason to release a table at 15 minutes; holding it costs nothing and wins goodwill. On a full Saturday with a waitlist, the grace period protects the guests who are already at the bar waiting. Give hosts that discretion explicitly, so the policy is a floor for fairness rather than a trap.
Parties that arrive in pieces
Groups often arrive one or two at a time. Seat the first arrivals as soon as most of the table is ready, or at the bar if the table is not, and take drinks orders straight away. Ask the organiser, when they book, whether they want to be seated before everyone arrives; most do. Hold the full table for the whole group, but tell the kitchen to wait for the last guests before firing mains, unless the organiser asks otherwise. If half the party is very late, offer to start the guests who are there on starters so the evening keeps moving.
The late-arrival timeline
At the booking time
Check the table is ready and the host knows who is due. Nothing else yet.
Five minutes late
If your system can, send a short text: “We’re looking forward to seeing you. Running late? Just let us know.” It prompts guests who are delayed to reply.
Ten minutes late
Call the guest. Ask whether they are still coming and how long they will be. Most late guests are on their way and are grateful for the call.
At the end of the grace period
If you have reached them and they are close, hold the table if you can. If you have not reached them, decide whether to release it, based on the evening.
Release
If you release the table, note the time and the attempts to contact the guest on the booking, and offer the table to walk-ins or the waitlist.
Record the outcome
Mark the booking as late, released or no-show, so your data reflects what happened.
What to say
Tone carries more weight than the policy. Hosts and servers need a few lines they can use under pressure.
- Calling at ten minutes: “Hi, it’s Sam from The Larder. Just checking you’re still OK for your 7.30 table? No rush, we just want to keep it ready for you.”
- Guest says they are 15 minutes away: “That’s fine, we’ll hold it. Your table’s ours until 8.00 for the next guests, so we’ll do our best to get you everything in time.”
- Guest arrives within the grace period: “Welcome, great to see you. Your table’s ready.” No comment on the time.
- Guest arrives after the table was released: “I’m sorry, we tried to reach you at 7.40 and had to give the table to guests waiting. Let me see what I can do. I can seat you at the bar now, or find you a table at 8.30.”
- Guest is upset: listen, apologise for the disappointment without blaming them, and offer the best option you have tonight or a booking for another day.
Never argue about the clock at the door. The call log on the booking shows what happened; the conversation is about what you can offer now.
Seating late guests fairly
A late party that is seated may have less time than they expected, especially if the table has a later booking. Say so kindly when you seat them, not at the end. Offer to bring drinks and starters quickly, suggest dishes that come out fast, or offer a move to another table with more time if one is free. If a table time is part of your terms, a shortened evening is fair as long as the guest knew about the table time at booking.
Booking terms must be fair to be binding. An unfair term in a consumer contract is not binding on the guest, and fairness depends on all the circumstances when the term was agreed[3]. A grace period and table time shown at booking, applied consistently and with some flexibility, are likely to be seen as reasonable. Charging a no-show fee to a guest who called ahead and arrived 20 minutes late is much harder to defend.
Late, released or no-show: record it properly
Your no-show figures are only as good as what staff record. The Resos No-Show Index counts a no-show only when staff or an integration record it, not through an automatic timeout[1]. A venue that marks every late table as a no-show inflates its rate; one that never records no-shows hides a real problem. Use three outcomes: arrived late (seated), released after contact attempts, and no-show (no contact, never arrived).
Review them monthly. If late arrivals cluster at one time, such as 19.00 on Fridays, the cause may be outside your control, such as traffic or a nearby office. If they cluster on one channel, the confirmation or reminder for that channel may be missing the time or the grace period.
Telling guests before the day
The best moment to explain the grace period is at booking, in the confirmation and in the reminder. One plain line does it: “We hold tables for 15 minutes. If you’re running late, give us a call and we’ll do our best.” Guests respond well to being told what matters to the venue. In OpenTable’s research, 48% of diners said understanding the financial cost of a broken booking would make them more likely to honour it or cancel properly, and 44% said a small deposit or card hold would encourage them to do so[2].
Source: Restaurant Online, 2026[2]
Show the data
| Item | Value |
|---|---|
| Understanding the cost to the restaurant | 48% |
| A small deposit or card hold | 44% |
Staff time is part of that cost. A table held for 20 minutes is 20 minutes of a server and a host waiting on one booking; median hourly pay for waiting staff was £12.81 in April 2026[4].
Example: Friday at a city brasserie
Example. A fictional city brasserie holds tables for 15 minutes. A table for four booked at 19.30 has not arrived by 19.40. The host calls, and the guest says they are stuck on a delayed train and will be there at 20.00. The 19.30 table has a 21.30 booking after it, so the host holds it and tells the guest they will have about 90 minutes. At 20.02 they arrive, are seated at once, and the server suggests the quicker dishes. The booking is marked “arrived late, seated”. On the same night, a table for two booked at 20.00 does not answer two calls; at 20.15 the host releases the table to a couple on the waitlist and marks the booking “no-show, two calls made”.
Frequently asked questions
How long should a restaurant hold a table for late guests?
Fifteen minutes is common for standard tables, with longer on quiet nights and shorter for counter seats and pre-theatre bookings. Show the figure at booking and in the confirmation.
Should we call guests who are running late?
Yes, at a set point such as ten minutes late. Most late guests are on their way, and a call lets you plan the table instead of guessing.
Can we charge a no-show fee to a guest who arrives late?
Only if your terms say so, were shown at booking and are fair. Charging a guest who called ahead and arrived within a reasonable time is hard to justify[3].
What is the difference between a late arrival and a no-show?
A late arrival is seated after the booking time. A no-show never arrives and does not make contact. Record them separately so your data is accurate[1].
References
Resos (2026). Restaurant no-show rate: the Resos No-Show Index (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 62: requirement for contract terms and notices to be fair (opens in a new tab) ↑
Office for National Statistics (2026). ASHE 2026 provisional, Table 14.6a: hourly pay excluding overtime by occupation (SOC 2020), all employees (opens in a new tab) ↑