RSVP Form Template
The classic yes-or-no headcount form. Attendance, party size, and dietary notes on the way in, plus a warm two-question exit for guests who cannot make it.
You're invited, and this takes less than a minute. Tell us if you can make it, how many you're bringing, and anything the kitchen should know.
Every event, from a backyard barbecue to a company summit, reduces to the same question: how many chairs? An RSVP form answers it early and with precision, which group chats, reply-all threads, and mental notes never manage. Replies scatter across channels, "maybes" evaporate, and someone ends up re-asking half the guest list the week before. This template turns the question into a running tally you can plan against.
How the branch works. The attendance question comes first, and everything else hangs off it through conditional logic. Guests who accept see two more planning questions: party size, asked as a select rather than a free number because "just me / 2 / 3 / 4 or more" is faster to tap and impossible to typo, and a dietary field that catches the vegetarian cousin and the nut allergy before the menu is final. Guests who decline skip all of that, since the form routes them straight to a warm goodbye ending, two questions after they started. The name is required because a headcount without names cannot chase stragglers. The email is optional and labeled with its one job, announcing a venue change, and the note field stays visible on both paths, because decliners often have the sweetest things to say.
What this form skips. Meal course selection, since a caterer who needs entree counts is served by the RSVP with meal choice template and its full three-course flow. Mailing addresses belong in an address-collection form before invitations go out. Account creation has no place here: guests tap the link, answer, and are done, which is most of why they answer at all.
Who sends it. Hosts of engagement parties, housewarmings, retirement sendoffs, community meetups, club socials, and every gathering in between, anywhere the guest list is real enough to need a number but informal enough that a wedding-grade form would feel stiff. It stays generic on purpose, ready to rename for anything by changing three lines of copy.
Making it yours. Set an RSVP deadline in Settings with the close-by-date rule, or cap responses at your venue capacity and let the form shut itself. Turn on duplicate prevention if the same household keeps double-tapping the link, and email notifications if you want each reply the moment it lands. When planning time comes, the Summary view already counts acceptances per option, and the CSV export turns the guest list into a spreadsheet your co-host can work from.
The branch is the whole trick. One link serves both answers: accepters get the planning questions, decliners get grace and brevity. That is why this form gets replies from the people who never touch the group chat. It respects the thirty seconds they are willing to give it, and it never asks a question their answer made irrelevant.
Frequently asked questions
Can guests change their reply after submitting?
They open the same link and submit again. Every reply is timestamped in your responses view, so the newest answer is easy to treat as current.
How do I stop taking RSVPs after a deadline?
Set a close date in Settings and the form shuts itself with a message you write. You can also cap total responses at your venue capacity.
Do guests who decline see all the questions?
A logic rule keeps party size and dietary questions hidden unless they accept, and routes decliners to their own goodbye ending. Edit it in the Logic panel.
How do I get the final headcount out?
The Summary view counts each attendance option live, and the CSV export gives you names, party sizes, and dietary notes in one spreadsheet.