How to make an RSVP form (including a wedding RSVP that guests actually fill out)
An RSVP form needs four things: the guest's name, a clear yes/no attendance question, a headcount, and any per-guest details like meal choice. Use conditional logic so people who decline skip straight to a warm thank-you instead of meal questions, and schedule the form to close on your RSVP deadline. For a wedding, add meal selection, dietary restrictions, and an optional song request or message field.
Paper RSVP cards get lost; reply-all email threads get messy. An online RSVP form gives you a clean list of who's coming, how many, and what they're eating — and it can close itself on the deadline. Here's how to build one for any event, with a complete wedding version at the end.
What fields does an RSVP form need?
| Field | Field type | Required? |
|---|---|---|
| Guest name | Short text | Yes |
| Email address | Yes (for confirmations and updates) | |
| Will you attend? | Multiple choice: 'Joyfully accept' / 'Regretfully decline' | Yes |
| Number of guests in your party | Number or dropdown | Yes, if attending |
| Names of additional guests | Long text | Only if attending with guests |
| Meal choice | Dropdown or multiple choice | Only if attending and you're serving a plated meal |
| Dietary restrictions or allergies | Long text | No |
| Message to the hosts | Long text | No |
How do you build an RSVP form, step by step?
- 1Create the form and name it with the event and date: 'RSVP — Sam & Riley's Wedding, September 12'.
- 2Add a welcome screen with the key details guests will double-check: date, time, venue, dress code, and the RSVP deadline.
- 3Add the attendance question first. Make it warm: 'Will you be joining us?' with options 'Joyfully accept' and 'Regretfully decline'.
- 4Add conditional logic: if the answer is 'Regretfully decline', jump straight to the ending screen. Decliners shouldn't wade through meal questions.
- 5Add headcount and per-guest fields for accepters: party size, additional guest names, meal choices, dietary notes.
- 6Write two endings if your builder supports answer-based endings: 'Can't wait to see you on September 12!' for yes, and 'We'll miss you — thanks for letting us know' for no.
- 7Schedule the form to close on your RSVP deadline so late responses go through you, not the form.
- 8Test both paths (accept and decline) on a phone, then share the link — or print a QR code on your invitations.
Put the RSVP deadline in three places: the invitation, the form's welcome screen, and the form's title ('RSVP by August 1'). Then schedule the form to actually close that day — a deadline the form enforces is a deadline guests believe.
Wedding RSVP form: a complete example
Here's a full wedding RSVP you can copy. It uses one branch of logic and takes guests under a minute.
- Welcome screen: 'Sam & Riley — September 12, 2026, Maplewood Barn, Asheville. Please RSVP by August 1. This takes about a minute.'
- 1. 'Your full name' (short text, required) — ask for the name as it appears on the invitation so you can match it to your guest list.
- 2. 'Your email' (email, required).
- 3. 'Will you be joining us?' (multiple choice: Joyfully accept / Regretfully decline, required). Logic: decline → jump to ending.
- 4. 'How many people are in your party, including you?' (dropdown: 1 / 2 / 3 / 4, required).
- 5. 'Names of everyone in your party' (long text).
- 6. 'Choose your entrée' (multiple choice: Herb-roasted chicken / Grilled salmon / Wild mushroom risotto (v), required). For parties of 2+, ask guests to list a choice per person in the next field or duplicate this question per guest.
- 7. 'Any allergies or dietary restrictions?' (long text, optional).
- 8. 'What song will get you on the dance floor?' (short text, optional).
- 9. 'A message for the couple' (long text, optional).
- Ending (accept): 'You're on the list! We can't wait to celebrate with you. Details and directions at our wedding site.'
What are common RSVP form mistakes?
- Forcing decliners through meal and song questions because there's no skip logic — it's awkward and they'll often just close the tab without answering at all.
- No headcount question, so '1 yes' might mean one person or a family of five.
- Free-text meal choices instead of fixed options — caterers need counts per entrée, not paragraphs.
- No deadline enforcement. If the form stays open, stragglers will RSVP the week of the event.
- Asking for a mailing address you already have from the invitation list.
- Skipping the test run. Always submit one fake 'accept' and one fake 'decline' before sending invitations, then delete the test responses.
What tool should you use for an RSVP form?
Any form builder with conditional logic, scheduling, and a clean mobile experience will do. Formkii covers all three free — including answer-based ending screens, a QR code for printed invitations, and CSV export so you can hand the caterer a meal-count spreadsheet. If your event sells tickets rather than collecting RSVPs, use a ticketing platform instead, since RSVP forms don't process payments.
Frequently asked questions
What should an RSVP form ask?
At minimum: the guest's name, a yes/no attendance question, and a headcount. Add meal choice and dietary restrictions for seated dinners, plus an optional message field. Keep it under ten questions — an RSVP should take less than a minute.
How do I handle guests who decline?
Use conditional logic to jump decliners straight from the attendance question to a thank-you screen. They skip meal and headcount questions entirely, which keeps the experience gracious and your data clean.
When should a wedding RSVP deadline be?
Most couples set the RSVP deadline three to five weeks before the wedding, because caterers typically need final counts one to two weeks out. Schedule the online form to close on the deadline so late replies come to you directly.
Can I make an RSVP form for free?
Yes. Free builders like Formkii let you create an RSVP form with skip logic, a close date, unlimited responses, and a QR code for printed invitations at no cost.