In summary
What you need to know
A clear, adaptable policy framework for cancellations, late arrivals, deposits and exceptions.
- Write specific, visible terms
- Capture acknowledgement
- Review both protection and conversion
- Best for
- Hospitality operators reviewing no-shows & deposits
- Reading time
- 4 min read
- Last reviewed
- 2 August 2026
Share this guide
A no-show policy should set expectations without sounding hostile. Use this framework as a drafting aid, adapt it to local law and your service model, and have legal counsel review it where needed.
01
What the policy should cover
State the cancellation deadline, how guests cancel, what counts as a no-show, the late-arrival grace period, any charge or forfeiture and how exceptions are handled. Use exact times rather than vague phrases.
02
Plain-language template
“Please cancel or change your reservation by [deadline] using the link in your confirmation. For bookings covered by a deposit or card guarantee, cancellations after this time and non-arrivals may result in [charge]. We hold tables for [minutes] after the reserved time. Contact us if circumstances outside your control affect your booking.”
Policy drafting table
Replace vague terms with exact guest actions
Complete every field, show the applicable version during booking and keep a record of acceptance.
| Policy element | Weak wording | Operational wording |
|---|---|---|
| Cancellation deadline | Cancel in advance | Cancel by 18:00 two days before |
| Late arrival | Tables may be released | Table held for 15 minutes |
| Charge | A fee may apply | €25 per guest after the deadline |
| How to act | Contact the restaurant | Use the link in your confirmation |
03
Where to display it
Show the relevant terms beside the booking action, at payment, in the confirmation and in reminders. Ask guests to actively acknowledge chargeable terms. Keep a timestamped record of the version accepted.
04
Review performance
Monitor booking conversion, cancellations, no-shows, disputes and guest feedback after introducing the policy. Adjust deadlines and amounts by service rather than changing everything at once.
Venue-specific application
A realistic operator example
A policy for a weekend group booking can say: cancel by 18:00 two days before arrival using the link in the confirmation; later cancellations and non-arrivals may forfeit the stated deposit; the table is held for 15 minutes unless the guest contacts the venue. The booking flow shows these terms immediately before confirmation and records the accepted version. This example is a drafting framework, not legal advice, and should be adapted to local consumer and contract law.
- Use an exact cancellation deadline
- Define no-show and late-arrival treatment
- Explain the charge or forfeiture plainly
- Provide a simple cancellation method
- State how exceptional circumstances are reviewed
- Keep the accepted policy version with the booking
What to measure
Signals that belong in this review
Next operational step
Use the relevant UpSalt workflows
- Write specific, visible terms
- Capture acknowledgement
- Review both protection and conversion