Dinner RSVP Form Template
A dinner party RSVP for a table with finite chairs — seat confirmation, mains, wine pairing, and the notes your kitchen needs before service.
Eight chairs, one long table, and a menu we've been rehearsing all week. Claim your seat and tell the kitchen how to take care of you.
A dinner party is the rare event where the RSVP has a hard ceiling: the table seats eight, and the ninth yes is not a bigger party — it is a problem. This template is built around that ceiling. It reads like hospitality, but underneath it is a capacity system: seats confirmed one by one, mains counted for a kitchen that cooks to order, and a close rule that shuts the door the moment the last chair is spoken for.
Why these fields. The seat question is phrased as an offer — "shall we set you a place?" — because a dinner invitation is personal in a way a generic RSVP is not, and the copy should sound like the host. The seating-plan name matters at a dinner more than anywhere: eight people around one table is a seating puzzle, and solving it starts with knowing exactly who confirmed. The phone field replaces email deliberately; dinner-night changes happen at 5pm on the day, and a text is the only channel that arrives in time. The main selection carries three kitchen-realistic choices (the vegetarian option labeled as a dish, not an apology), the wine question includes both "surprise me" and "none for me" because a good host pours generously and assumes nothing, and the intolerance field speaks to the kitchen directly — at this scale, the cook reads every word.
What we left out. Full course-by-course menus — that is the RSVP with meal choice template, built for plated events with a caterer; a home kitchen offering three mains does not need starter and dessert ballots. Email addresses, guest counts (invitations here are individual), and anything that smells like a registration desk.
Who uses this. Hosts of dinner parties and supper clubs, chefs running ticketed tasting tables at home, and anyone whose "small dinner" has become a recurring institution with a waiting list of friends.
Make it yours. Set close-after-responses to your chair count in Settings — when seat eight confirms, the form closes itself with a message you wrote, which beats telling a friend "we're full" in person. Write that closed message warmly ("the table filled fast — you're first on the list for the next one"). Add password protection if the link travels beyond the invited circle, and keep duplicate prevention on so one enthusiastic guest cannot claim two chairs by accident. Before cooking day, the Summary view shows your mains split and the CSV is your prep sheet.
Scarcity, handled kindly. The whole design exists so the ninth person hears "next time, promise" from a well-written closed screen instead of an awkward conversation — and so the kitchen cooks exactly eight plates, each one right.
Frequently asked questions
Can the form stop at exactly eight seats?
Yes — set close-after-responses to your chair count in Settings. When the table is full, the form closes with a message you write yourself.
What do late guests see once seats run out?
Your custom closed message — most hosts write something warm like "the table filled fast; you are first on the list for the next one."
How private can I make an invite-only dinner?
Add password protection in Settings and share the password with the link. Duplicate prevention keeps one reply per device on top of that.
Why a phone number instead of an email here?
Dinner-night changes are last-minute by nature — a text lands in time, an email does not. The label says exactly how the number is used.