Restaurant Waitlist Form Template

Tonight's table queue without the clipboard — party size, seating preference, and a phone number the host can actually read.

Free · copies into your editor in one click
Live preview — try it, nothing is saved

Put your name on tonight's list right from your phone. We seat in order, we call when your table's up, and you're free to wander until then.

press Enter ↵

The clipboard at the host stand fails in three reliable ways: names nobody can pronounce from handwriting, parties that evaporated forty minutes ago, and the Saturday-night argument about who was here first. Putting tonight's list behind a form fixes all three — every entry is timestamped on arrival, so queue order becomes a fact instead of a memory, and the host reads names from a screen instead of deciphering them off a wet page.

Why these fields. The name label says "name we'll call out" because that's the actual job — it nudges people toward whatever the host can shout across a loud room, which is not always what's on their ID. Party size is a proper number field capped at twelve, so the kitchen is never ambushed by a "we're maybe 15?" scrawl; if you take larger groups, raise the cap, and if you don't, the cap politely says so. The phone number is the one field this template treats as sacred, and it's why this is the phone-first entry in a category of email-first forms: nobody outside your restaurant is refreshing an inbox while hungry, but everyone is holding their phone. The host calls, a human answers, a table gets sat — no technology in between. Seating preference converts "any table" chaos into matchable slots; "patio, weather permitting" carries its own disclaimer so nobody relitigates the drizzle. And the prep question — high chair, wheelchair-friendly table, birthday dessert, stroller space — means the table is actually ready when the party reaches it, which is the difference guests describe as "they had it together."

What we left out. Email (wrong channel for a forty-minute horizon), dates and time slots (this is tonight's queue, not a reservation book — the moment you add a date picker you're running a different system with different promises), and deposits or card holds, which walk-in culture rightly reads as hostile.

Who uses this. No-reservation restaurants with a nightly line, brunch places drowning every Saturday, taquerias and ramen bars where the queue is part of the brand, food halls seating for multiple vendors, and pop-ups whose "system" was, until now, someone's memory.

Make it yours. Print the form link as a QR code for the host stand and the window, and add it to your Google profile so people can join from the sidewalk — the hidden entry_point field (?entry_point=door versus ?entry_point=web) tells you where the line actually forms. Keep Focus mode on: one question at a time is what one-thumb-on-a-phone wants. Turn on duplicate prevention per device so a nervous double-tap doesn't become two entries, and set the form to close at last seating with a message that says when the list reopens. Your staff works straight from the responses view, oldest at the top — call, seat, next.

The line, civilized. Same wait, zero arguments: everyone can see they're in the queue, and the host's authority moves from handwriting to timestamps.

Frequently asked questions

Do guests need to install anything or make an account?

No — the form is a link. Guests open it from a QR code or your site, answer five quick questions, and they're on the list. Accounts are only for the restaurant side.

How does the host know who's next?

Every entry is timestamped the moment it arrives, so the responses view is the queue itself — oldest at the top. Call the top party, seat them, move down. No clipboard math.

Can the list shut itself off at closing time?

Yes — set a close time in Settings and the form stops accepting entries, showing your own message, like "the kitchen's done for tonight, see you tomorrow from 5pm."

What stops pranksters loading the list with fake parties?

The built-in honeypot, timing checks, and escalating invisible challenge screen out bots, and per-device duplicate prevention stops one phone from stacking multiple entries.