A four-top that books, confirms, and never walks in costs you the food you prepped, the staff you scheduled, and the party you turned away for that slot. Here is how to write a no-show policy guests will accept, when deposits and card holds make sense, and what to do in the first ten minutes after a table fails to show.
September 5, 2026
Restaurant no-shows are the quietest way to lose a Saturday. Nobody complains, nothing breaks — a party of six simply never arrives, and the table you defended against three other requests sits empty through the exact window you could have sold it twice. How to reduce restaurant no-shows is really two questions: how do you make guests more likely to show up or cancel in time, and what do you do in the minutes after they do not. Most advice stops at “charge a fee.” Fees are one tool, and a blunt one — used badly they cost you regulars and one-star reviews that outlast the empty table. This guide covers the policy side and the operational side: what to write, what to charge, when to hold a card, and how to resell the table fast.
The visible loss is the unsold covers, and even that is bigger than it looks: a prime-time slot is not one table, it is that table plus every party you declined because it was booked. The less visible losses stack on top. You prepped and scheduled for a forecast that included those covers, so the food and labor were already spent. Your prep lists and par levels were built on covers that never came. And chronic no-shows corrupt your planning data — if 1 in 10 bookings evaporates, your kitchen is systematically over-prepped and your floor over-staffed on nights that look strong on paper. Industry studies in several markets have put the no-show rate around 1 in 20 bookings, with weekend large parties running meaningfully worse; your own reservation history will tell you where you sit.
It is rarely malice. The most common pattern is the double-booker: a group cannot decide, so someone reserves two or three places and picks one at 6 p.m. Second is the forgotten booking made a week out, especially bookings made through a third-party app the guest never opened again. Third is the plan that fell apart — someone got sick, the sitter cancelled — where the guest genuinely means to cancel and never gets to it because cancelling feels awkward or takes effort. Each cause has a different fix: double-booking responds to card holds, forgetting responds to reminders, and the fallen-through plan responds to making cancellation trivially easy. A policy that only punishes will miss two of the three.
A no-show policy is a contract you are asking a guest to accept at the exact moment they are excited to eat with you, so it has to read as fair, not defensive. The test for every line: would a reasonable guest nod at this? Most operators land on a tiered policy — walk-ins and small parties face no friction at all, standard bookings get reminders and an easy cancel link, and large parties or peak slots carry a deposit or card hold. Put the policy where it is agreed to at booking, repeat it in the confirmation, and mention it in the reminder. A fee a guest first learns about on their card statement is a chargeback waiting to happen — and chargebacks cost you more than the fee.
The three tools do different jobs. A deposit collects money up front and applies it to the bill, so it filters intent hardest — and creates the most booking friction. A card hold (card required to book, charged only on no-show) filters the double-booker with almost no friction for honest guests, which is why it has become the default for prime-time books. A plain no-show fee without a card on file is mostly a statement of principle — you have no way to collect it. Match the tool to the risk, not to your annoyance level.
| Approach | How it works | Best fit |
|---|---|---|
| Reminder + easy cancel | Confirmation at booking, reminder 24–48h out, one-tap cancel | Every booking, every restaurant — this alone removes the forgetful cohort |
| Card hold | Card required to book; stated per-person charge only if the party never shows | Peak slots, parties of 6+, tasting menus, busy urban books |
| Deposit | Fixed amount per person paid at booking, applied to the final bill | Events, holidays, large parties, prix fixe and ticketed dinners |
| Guest-history flag | Repeat no-shows lose booking privileges or must call to book | Regular-driven rooms where charging feels wrong but repeat offenders exist |
Have a written grace-period play, because 7:15 on a Saturday is not when you want to improvise. A common pattern: at 10 minutes, text the guest — “running late? We will hold your table 10 more minutes.” At 15–20 minutes, release the table to the waitlist or the door, and note the outcome on the guest profile. The release decision belongs to whoever runs the floor, and it should key off your table management view — if the book shows a second seating behind that table, the grace period shortens. The point of the whole policy stack is to compress the time between “they are not coming” and “someone else is sitting there.”
If you operate in Canada, check your province before writing fees into the policy. Quebec is the clearest case: provincial consumer-protection rules explicitly permit a modest, capped per-person no-show charge, but only when conditions around disclosure and confirmation are met — and they cap it low, so a Quebec no-show charge is a deterrent, not compensation. Other provinces leave it to general contract and card-network rules, where clear advance disclosure and proof of agreement are what make a charge stick when the guest disputes it. This reflects publicly available information as of 2026 — verify current rules for your province before charging anything. For the broader Canadian picture — payments, taxes, bilingual receipts — see our guide to restaurant POS in Canada.
Most restaurants that charge land on a stated per-person amount sized to sting, not to compensate — commonly in the tens of dollars per guest, higher for tasting menus and ticketed events where the loss is certain. The amount matters less than the disclosure: a small fee agreed to clearly at booking holds up; a large fee buried in fine print turns into chargebacks and public complaints.
Requiring a card to book is the part that works — it filters double-bookers and casual bookers before the no-show ever happens, and operators who add card holds to peak slots typically see no-shows drop sharply. The fee itself is rarely collected if the deterrent works. Reminders with an easy cancel link do most of the remaining work.
It adds friction, so apply it surgically: peak windows, large parties, and special events, not the Tuesday 5:30 two-top. Guests have been trained by hotels, salons, and ticketed dining to expect a card for high-demand bookings. If your book is soft, fix demand first — friction on a slow night costs more than the no-shows do.
Deliberate overbooking works at airline scale, but a 60-seat room has no volunteer-bump mechanism — when everyone shows, you are comping drinks for a party staring at a full dining room. A live waitlist plus a firm release time gets you most of the same table utilization without the blast radius. If you do pad the book, pad off-peak, never prime time.