Operations 8 min read

The reservation book and no-shows: how to stop an empty table at peak

AuthorTudor RaduAPPY Team

A no-show at 8pm on a Saturday is not a free table, it is a table you turned someone else away from. The difference between a notebook and a digital record is not convenience, it is what you can do with the information: on paper, a broken booking vanishes without trace; digitally, it becomes a pattern you can correct. This article covers what the record needs to hold, what actually reduces no-shows, and what is lost when bookings live in three different places.

Why the notebook costs more than it looks

A notebook works for one shift, with one person reading it. Trouble starts when the evening host is not the one who wrote it down, when someone calls to change the time, or when two bookings land on the same table because one came by phone and the other through Instagram.

The second loss is invisible: you cannot count. You do not know how many bookings went unhonoured last month, at what hour, on which days, or whether the same people do it repeatedly. With no numbers, the only available answer is to stop taking bookings — which costs more than the problem.

The third shows on the return visit. A guest who ate well three months ago appears nowhere when they call again. You treat them as a stranger, though they are exactly the guest you want to keep.

What it has to hold, at minimum

Date, time and expected duration — without duration you cannot turn a table twice in an evening. Party size and the table or area assigned. A name and a contact channel that works: a phone that receives SMS beats an email address.

The booking's source: phone, website, Google, social. Without it you will never know which channel brings guests who actually show up.

The notes that change the service: allergies, a high chair, a birthday, a preferred area. These turn a booking into a welcome.

And per-guest history: how many times they came, how many times they did not. It is the only basis on which you can treat a regular differently from someone who has left a table empty three times.

What actually reduces no-shows

A confirmation the day before, on the channel the person actually reads, with one-click cancellation. Most no-shows are not bad faith, they are changed plans plus the awkwardness of phoning. Give people an easy way out and they free your table in time.

A reminder on the day itself, a few hours ahead, for evening bookings. Short, with the time and the venue name.

One-tap cancellation. If backing out requires a phone call in the middle of a working day, people would rather just not turn up.

For large parties and busy nights, a card guarantee. Not a measure for everywhere, but for a table of ten on a Saturday it changes the equation entirely.

Overbooking is a tool, not a solution

The temptation is to take more bookings than you have tables, betting on a no-show rate. It works until the evening everyone turns up, and then you pay in angry guests at the door and reviews you will read for months.

If you do it, do it on your own data, not on instinct: your real no-show rate, by day of week and by time slot. And the margin has to be smaller than the rate, not equal to it.

The healthier alternative is a waiting list. When a booking cancels, the slot goes automatically to the next name — you win the table back without gambling on anyone.

Bookings have to see the floor

A record that does not know what is happening in the room is just a calendar. If table 7 is still occupied at 8:15pm, the 8pm booking for table 7 is a problem that surfaces only once the guest is already at the door.

When bookings and the table map live in the same system, the host sees what is clearing and when, can move a booking with a drag, and can say "ten minutes" and mean it instead of guessing.

The link matters in reverse too: a table marked as reserved should not be handed to a walk-in from the bar without anyone knowing.

What to measure after the first month

No-show rate, split by day and by time slot. You will almost certainly find the problem is concentrated, not uniform.

Confirmation rate: how many reply to the message beforehand. If it is low, the message or the channel is wrong, not the guests.

Table turns: how many services you get out of a table in an evening. It is the number that tells you whether your duration estimates are realistic.

The source of bookings that actually show. Not the source that brings the most bookings — the source that brings the most people to the table.

Frequently asked questions

Is a card guarantee worth asking for?

Selectively. For large parties and high-demand evenings it cuts no-shows significantly. Applied to every booking it also deters guests acting in good faith, particularly a table of two on an ordinary night.

How early should the confirmation go out?

The day before works best, plus a short reminder on the day for evening bookings. What matters is that cancelling takes one click rather than a phone call.

Can I overbook to cover no-shows?

Only on your own data, by day and time slot, and with a margin smaller than your real no-show rate. A waiting list that automatically picks up cancelled slots achieves the same thing without the risk of turning guests away.

What is the minimum a reservation record should hold?

Date, time, expected duration, party size, table or area, name, a contact that receives SMS, the booking source, the notes that change service, and the guest's history of showing up or not.

This website uses cookies to ensure you get the best experience on our website.