Key takeaways
- A cancellation policy has six parts: scope, window, fee, how to cancel, exceptions and refunds.
- Diners accept a stated table hold, typically 15 minutes, as fair[1], so put the late-arrival rule in the same policy.
- Cancelling must work at any hour: an OpenTable estimate put 25% of online bookings between 10 p.m. and 10 a.m.[2].
- Show the policy before the guest commits and repeat it in every message after.
What a cancellation policy has to do
A good cancellation policy does three jobs. It tells guests how to release a table they no longer need, it gives the restaurant enough notice to give that table to someone else, and it sets out, in advance, what happens when neither of those things occurs. Most policies fail at the first job. In Cornell's survey of 1,230 frequent diners, respondents said guests should call when plans change, but often found it difficult to reach the restaurant to do so[3].
Cornell's guidance on reservation policies recommends making it easy for customers to contact the restaurant if they are running late or cannot make it[4]. Write the policy with that in mind. The cancel path comes first, the fee comes last, and everything is short enough to read on a phone.
The six parts of the policy
| Part | What to decide | Example choice |
|---|---|---|
| Scope | Which bookings the policy covers | Parties of 6 or more, plus all Friday and Saturday bookings after 6 p.m. |
| Window | The deadline for a free cancellation | Noon on the day for ordinary bookings; 48 hours for holidays |
| Fee | What happens after the window or on a no-show | A fee per guest charged to the card on file |
| How to cancel | Every route that counts as notice | Link in the confirmation, reply to the text, phone or email |
| Exceptions | When a manager waives the fee | Emergencies, severe weather, restaurant changes, first-time misses |
| Refunds and credits | How deposits are returned or converted | Refund to the original card within five business days, or a credit on request |
Decide each part on its own before writing a word. Owners who start with the fee amount usually end up with a policy that is clear about the penalty and vague about everything else, which is the opposite of what guests need and the opposite of what holds up in a dispute.
Choosing the window
The window should match how quickly you can resell a table. A restaurant with a long waitlist on Saturdays can fill a table cancelled at 4 p.m. A neighborhood spot that rarely has walk-ins after 6 p.m. may need notice the day before. Look at your own data: when do your late cancellations arrive, and how many of those tables were filled again?
- Same-day noon deadline: easy to remember, and works when you have walk-ins and a waitlist.
- 24 hours: common and widely understood, but harsher for guests who book on the day.
- 48 hours or more: reserve for holidays, tasting menus and private dining, where prep starts early.
- Do not set a window longer than the guest's booking lead time; a policy that applies before the booking was made is not a real window.
Setting the fee
Choose a fee structure guests understand at a glance. A flat amount per guest is simplest. Forfeiting a deposit works when you already took one. For fixed-price menus, a share of the menu price reflects the real loss. Whatever you choose, charge for whole-party no-shows and late cancellations rather than for one missing guest. Cornell research found that penalties for short-shows, where part of a party does not appear, were seen as the least acceptable policy, while card guarantees were among the most acceptable[5]. The legal side of fees is covered in no-show fees: legal and fair use.
Large parties and private dining
Large parties and private rooms need their own section of the policy, because the loss from a late change is bigger and the organizer is often not the person who pays. Add a headcount deadline, such as final numbers 48 hours ahead, and say what happens if fewer guests arrive than confirmed. For private dining, the contract or event agreement should carry the detail, with the booking policy pointing to it.
- Name the organizer as the contact for all changes, and send every message to them.
- Set a final-number deadline that matches when you order and prep for the group.
- Say whether a minimum spend or a set menu price applies to the confirmed number or to guests who arrive.
- Keep the fee for a whole-party cancellation separate from the rules for a smaller turnout.
A fill-in template
Cancellation policy for [restaurant name]. We set every table for the guests we expect, so please tell us if your plans change. You can cancel or change your booking for free until [deadline, for example noon on the day of your reservation] using the link in your confirmation, by replying to our text, or by calling [phone number]. For [scope, for example parties of six or more and Friday and Saturday evenings], cancellations after the deadline and bookings where no one arrives are charged [fee, for example a set amount per guest] to the card provided when you booked. We hold tables for [15] minutes after the booking time; after that, tell us you are on the way or we may release the table. If something unexpected happens, contact us and a manager will review it. Deposits are refunded to the original card within [five] business days when you cancel before the deadline, or kept as a credit if you prefer.
Fill in the brackets with your real choices, read it aloud, and cut anything a guest would not understand on first reading. Diners view a stated hold, typically 15 minutes, as fair[1], so include it here rather than in a separate rule.
Where the policy must appear
| Place | What to show |
|---|---|
| Booking widget | The full policy before the guest enters card details, with a tick box to agree |
| Phone script | The policy read word for word, followed by a clear yes from the guest |
| Confirmation message | A short version plus a link to the full policy and the cancel link |
| Reminder message | The deadline and how to cancel, in one line |
| Reservations page on your website | The full policy in plain words |
| Booking platform profile | The same text as your website |
| Receipt for any fee | Which rule was applied and how to contact you |
| Host stand cheat sheet | The policy and the waiver rules, so every host says the same thing |
Make cancelling work around the clock
Guests change plans at all hours, and they book at all hours too. OpenTable estimated that 25% of its reservations were made between 10 p.m. and 10 a.m.[2], when most restaurants are closed. A policy that only accepts cancellations by phone during opening hours punishes the guest who tried to cancel at midnight. Accept a cancel link, a text reply and email, and treat each as valid notice with its timestamp.
- Made between 10 p.m. and 10 a.m. 25%
Source: Cornell University Center for Hospitality Research (Sheryl E. Kimes), 2009[2]
Show the data
| Item | Value |
|---|---|
| Made between 10 p.m. and 10 a.m. | 25% |
The phone still matters, especially during service when guests call to say they are late or cannot come. If calls go unanswered, notice is lost and tables go empty. An SI Employee such as Ava can answer those calls, take the cancellation or change request and log it with the time, so the host sees it straight away.
Refund steps
Confirm the time of notice
Use the timestamp of the link, text, email or call log. When in doubt, the guest's earliest attempt counts.
Apply the policy
Before the deadline: full refund or credit. After it: the stated fee, unless a manager approves an exception.
Refund promptly
Refund to the original payment method within the time your policy states, and never ask the guest to chase it.
Confirm in writing
Send a message stating what was refunded or charged and why.
Log it
Record the decision, the reason and who made it, so patterns are visible and disputes can be answered.
Brief the team on the policy
Every host, server and manager who talks to guests should be able to explain the policy in one breath. Put a short version on the host stand cheat sheet, practice the phone script at pre-shift, and agree who can grant exceptions. Inconsistent answers are the fastest way to lose a dispute, and the most common source of complaints about a policy that is fair on paper.
Give staff a line for the guest who is upset about a fee: “I understand. Let me get the manager, who can look at what happened.” Staff should not argue the policy or promise a refund they cannot give. The manager reviews the case against the written exceptions and decides.
Exceptions and review
Write down the exceptions managers may grant: illness or emergency, severe weather, travel disruption, any change made by the restaurant, and a first miss by a guest with a good history. Then trust managers to use them. A policy enforced without judgment produces disputes and reviews that cost more than the fee.
Review the policy after 90 days. Count fees charged, fees waived, disputes and complaints, and compare no-shows with the period before. If most fees are waived, the window is probably wrong. If no-shows did not fall, the problem may be reminders or the cancel path rather than the policy itself.
Frequently asked questions
Is a 24-hour cancellation policy standard for restaurants?
It is common, but not required. Many restaurants use a same-day deadline, such as noon, for ordinary bookings and a longer window for holidays and special menus. Match the window to how quickly you can resell a table.
Do we need a cancellation policy if we do not charge fees?
Yes. Guests still need to know how and when to cancel, and how long you hold a table. A policy without a fee is still the best tool for getting early notice.
Can we change the policy for holidays?
Yes, as long as the holiday policy is shown before the guest books. State it clearly on holiday booking pages and confirmations, and do not apply it to bookings made under the old terms.
References
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2009). How Restaurant Customers View Online Reservations (Cornell Hospitality Report Vol. 9, No. 5) (opens in a new tab) ↑
Cornell University Center for Hospitality Research (Sheryl E. Kimes) (2008). A Consumer's View of Restaurant Reservations Policies (Cornell Hospitality Report, 2008) (opens in a new tab) ↑
Cornell University (Sheryl E. Kimes) (2011). Customer Attitudes towards Restaurant Reservations Policies (Kimes, Journal of Revenue and Pricing Management, 2011) (opens in a new tab) ↑
Cornell University (Sheryl E. Kimes) (2011). Customer Attitudes towards Restaurant Reservations Policies (Kimes, Journal of Revenue and Pricing Management, 2011) (opens in a new tab) ↑