How Long Do You Hold a Booked Table? The Grace Period and the Reconfirmation Script That Works

It’s 8:40 p.m. The booking was for 8:30. The four-top by the window is still empty, and outside there’s a couple asking whether “anything’s opened up.” How much longer do you hold it? Five minutes? Fifteen? Half an hour?

It’s one of the most frequent and most uncomfortable calls in service. Hold the table and you risk leaving it empty all night. Release it and you risk the party arriving two minutes later to find their seat taken. The good news is there’s a standard — and, more importantly, there’s a way to handle the whole thing that drastically cuts the number of times you end up in this spot at all.

The grace period: how long to actually wait

The “grace period” is the window during which you hold a table for a late guest before treating it as free. The industry standards are fairly settled:

• Casual restaurant: 15 minutes.
• Upscale venue: 20–30 minutes, but usually paired with a phone call to the guest to find out whether they’re on the way.
• Very high-demand nights: 5–10 minutes, or none, because every table is worth gold and the waitlist is pressing.

The exact figure matters less than the principle: there has to be a threshold, it has to be communicated up front, and it has to have one big exception — the call.

If the guest calls to say “we’re stuck in traffic, we’ll be there at 8:50,” the window almost always extends. An announced delay isn’t a no-show: it’s a guest giving you the information to manage the floor. Reward it, don’t punish it.

The golden rule: communicate the threshold first

Releasing a table after 15 minutes is only fair if the guest knew it could happen. That’s why the grace period isn’t something you decide alone in the kitchen: it’s something you communicate at booking, exactly like the table time limit.

The formula is simple and gentle: “We’ll hold the table until 8:45; if you’re running late, just send a message and we’ll keep it for you.” Put that way, the threshold isn’t a threat: it’s a reasonable request for cooperation. And it hands the guest the tool to keep their table — a quick message.

Then, when it’s 8:45, the table is still empty, and nobody has written, you’re free to reassign it without guilt. The guest knew the rules. It’s the same transparency principle that runs through all of table-time management: people respect the rules they know in advance.

What to say on the phone when you call the late guest

At mid-to-upscale venues, it’s worth calling before you release a table. It’s a gesture of care and it gives you the information you need. Tone does everything.

Avoid: “Hi, you had a booking for 8:30, it’s already 8:45, we’re waiting for you.” That sounds like a telling-off.

Better: “Good evening, I’m calling from the restaurant — just wanted to make sure everything’s set for your booking tonight. We’re looking forward to seeing you.” It opens, it doesn’t accuse. The guest in good faith replies “we’ll be there in ten minutes,” and you know what to do. The guest who forgot apologizes and confirms. And in the rare case of someone who neither answers nor shows up, you’ve got a clear conscience to release the table.

A practical note: if you log the call and its outcome, over time you build a reliability history for each guest. Someone who’s been late or absent more than once is a natural candidate for a deposit on future bookings.

The real fix: the reconfirmation that reduces lateness

Handling lateness well matters, but the smartest move is to reduce the number of late arrivals and no-shows upstream. And here the tool is the reconfirmation — done the right way.

Most restaurants get the framing wrong. They ask: “Do you want to confirm your booking?” It’s a question that demands effort (replying yes) and that plenty of people ignore. The framing that works is the opposite — opt-out:

“Hi Marco, your booking for Saturday at 8:30 is confirmed. If for any reason you can’t make it, reply NO and we’ll free the table. Thanks!”

The difference is psychological and powerful. Here the default action is “all good, you don’t have to do anything.” The guest only has to act if they can’t come. It’s less intrusive, it doesn’t pester the people who’ll show up, and it gets you more early cancellations from the people who won’t — cancellations that free the table in time to reassign it. On the right channel (WhatsApp opens above 90% of messages) and the right cadence, we’ve got a dedicated piece: reminders via WhatsApp and SMS without spamming.

The numbers back the practice: well-built reminders cut no-shows by up to 32%. And one avoided no-show is worth a lot — we ran the math in what a no-show costs.

When lateness becomes a no-show: the difference

It’s worth separating two situations that often get blurred.

The announced delay is manageable: the guest tells you, you adapt. It costs little, sometimes nothing.

The no-show — the table that stays empty because nobody shows and nobody warned you — is the dead loss. All the work on the grace period is there to turn as many of the second into the first: to make warning you easy and natural, so a “we can’t make it” arrives in time to fill the table from the waitlist or with a walk-in.

That’s why the two go together: a clear threshold communicated at booking, and a dead-easy channel to warn you. The simpler it is to cancel, the fewer tables you’re left holding empty.

Mistakes to avoid

Having no threshold. “We’ll see case by case” means deciding under pressure, every time, with the risk of being unfair. Set a grace period and communicate it.

Releasing the table without having communicated anything first. If the guest didn’t know about the grace period, reassigning their table after 15 minutes is a sure way to lose them for good. The threshold belongs at booking.

A punitive tone in the reconfirmation. “If you don’t show, we’ll charge a penalty” inside a friendly reminder ruins it. The policy can exist, but the reconfirmation message has to be warm. Deposits get their own moment, with the right framing.

Forgetting to log it. A late arrival or no-show that goes unrecorded is information lost. The guest’s history is what lets you calibrate future requests.

In short

How long do you hold a table? Fifteen minutes as a standard, longer if the guest warns you, shorter on full nights — but always with a threshold communicated up front. And above all: the best way to handle lateness is to reduce it, with an opt-out reconfirmation that makes warning you easy and frees, in time, the tables that would otherwise sit empty.

The ready-to-use scripts — the line for communicating the grace period, the phone-call script, the reconfirmation template — are in the Restaurant Floor Scripts Kit below.

Coperti sends automatic confirmations and reminders with opt-out reconfirmation, records the reliability history of every guest, and frees tables for the waitlist in real time. Explore the features or tell us about your restaurant for a demo.