Restaurant Reservation Templates: Sheets, Emails, Policies and Scripts

A reservation system, at minimum, is five artifacts: a sheet that holds tonight's bookings, a phone script that captures the right details, a policy that protects the tables, messages that confirm and remind, and a waitlist for the door. We publish all of them free, no email wall, in casual and formal versions. This guide is the map: what each template does, when it is enough, and when it stops being enough.

The reservation sheet (paper or spreadsheet)

Seven columns run a service: time, guest name, party size, phone, table, notes, status. One page per service, sorted by time, pencil at the stand. The same seven columns become a Google Sheet or Excel table in about two minutes with a frozen header, a time-formatted first column and a status dropdown; the template page has the exact click-path for both. The phone column is the non-negotiable one: it is the difference between a no-show and a rescued table.

The phone script

Hosts do not need lines, they need a checklist: five details every call (name, phone, party, time, notes), a read-back before hanging up, exactly two alternatives when the slot is gone, and one-breath answers to the policy questions. Print it, tape it inside the stand, and train by role-playing the full-night call, because that is the one that loses revenue when improvised.

The policy set

Four policies cover a dining room: no-show, cancellation, deposit, and large party. Each is three decisions dressed in wording: the fee (operators report $10-25 a head casual, $50+ fine dining), the window (2-4 hours casual, 24-48 for hard-to-resell formats), and the mechanism (hold vs deposit). All four templates ship in casual and formal registers with bracketed numbers to fill in, or the generator composes the whole thing from your inputs.

The message pack (email and SMS)

Five emails and six texts cover the guest lifecycle: confirmation (details plus manage link plus one-sentence policy), day-before reminder (the money message: it catches plan-changers while the table can be re-sold), cancellation notice, waitlist updates and the deposit request. Texts stay under 160 characters with the restaurant name first. All are written to be sent from any system, or any phone.

When templates stop being enough

Paper and spreadsheets have one hard limit: they cannot stop two bookings landing on the same table, because they do not know your tables. The day reservations arrive from two channels at once (the phone plus your website, say), you need one shared book with live availability. That is the honest upgrade point, and the templates above remain useful after it: the policies, script and messages plug into whatever system you run. TableHelm's free plan is one option (unlimited reservations, one location, booking page, floor plan, waitlist, guest book, email confirmations); Eat App and resOS have free tiers with monthly caps (100 covers and 25 bookings respectively). Pick any of them over double-booking a Saturday.

Common questions

What templates does a restaurant need to take reservations?

Five: a reservation sheet (paper or spreadsheet), a phone script, a policy (no-show and cancellation wording), a confirmation and reminder message pack, and a waitlist sheet for the door. All are free in our template library.

Is there a free reservation template for Google Sheets?

Yes: our reservation sheet page includes the exact two-minute Google Sheets build (frozen header, time column, status dropdown, filter) and the equivalent Excel setup, plus a printable version for the host stand.

When should a restaurant move from spreadsheets to software?

When bookings arrive from more than one channel at once, when two people edit the book simultaneously, or when you want card holds for no-shows. Those are the three things a spreadsheet structurally cannot do.