The RSVP is the single most stressful part of wedding planning that nobody warns you about. You send the invitation. People reply on WhatsApp, on email, on Instagram DMs, in person at coffee. Some confirm and forget to mention they are vegetarian. Others say "of course we are coming" and disappear for two months. By the time the venue asks for a final headcount, you have a spreadsheet with three different versions of the same answer for half your guests.
This is exactly the problem an RSVP wedding website is built to solve. Here is what one should actually include in 2026, and what you can safely skip.
The five fields that matter
An RSVP form does not need to be complicated. The fields that make a real difference for the wedding planning are exactly five.
Name — Guests type their full name, exactly how they want it on the seating chart. Do not assume you remember the spelling of every cousin.
Attending: yes / no / maybe — A simple three-option choice. "Maybe" exists because some guests need to check flights or kids' schedules and want to confirm later — better to have a tracked maybe than no answer at all.
Plus one (if you allow it) — A toggle plus a name field if active. The plus one rule should be set by you, not negotiated case by case in the form.
Dietary preference — A dropdown with the menu options you are offering. Three to five categories is the sweet spot: meat, fish, vegetarian, vegan, kids menu. Add a free-text field for allergies.
Optional message — A small text box where guests can write a personal note. You will be surprised how many take the time to use it. Some couples print the messages and bind them as a wedding day keepsake.
Anything beyond these five fields tends to make guests close the form. We have seen couples ask for hotel preferences, transport options, song requests and ice-breaker questions — and the response rate dropped by 30% compared to the simpler version.
What guests hate about RSVP forms
We have run informal user testing on a few dozen real wedding RSVP flows. The complaints are surprisingly consistent.
Forms that ask to create an account. Nobody wants to sign up for a service to confirm a wedding. Every minute you add to the RSVP is a guest who closes the tab. The form should work on the first tap, no login required.
Forms with mandatory phone number. Same problem. The bride already has the number, asking for it inside the form looks like a mailing list trap.
Forms that do not confirm the submission. A guest taps submit, the page reloads, and nothing happens. Did it work? Should they try again? A confirmation message ("Thank you, we have your reply") is the difference between a peaceful evening and an inbox full of "did my reply go through?".
Forms that look broken on a phone. 90% of RSVPs happen on a phone, on the toilet, in the gap between two work meetings. If the form requires zooming or horizontal scrolling, the guest gives up.
What happens after they hit submit
The guest sees a thank-you message. You receive a notification in your private dashboard. The new RSVP shows up in the guest list with the date, the choices and the message. You can filter by attending / not attending, sort by submission date, export to CSV if your venue needs the headcount in a spreadsheet.
This is what makes online RSVP genuinely useful: not the form itself, but what happens with the data afterwards. A spreadsheet with 100 guests is unmanageable. A live dashboard with the same 100 guests, sorted and filtered, is the difference between sleeping at night and refreshing your email.
The deadline question
Set the RSVP deadline three weeks before the wedding. Not two — three. Here is why: at three weeks before the wedding, you still need to give the venue the final headcount, finalise the seating chart, print the place cards, and chase the late replies. Two weeks is too tight. Three weeks gives you a buffer.
The wedding website should show the countdown to the deadline, not just the date. "Reply before March 15" is less powerful than "Reply in 12 days". A live countdown reminds guests they are running out of time without you having to send a reminder.
What about late replies?
You will have late replies. Every wedding does. The smart move is to set the form to keep accepting submissions even after the deadline, and just remove the countdown from the page. That way, the guests who realise on day -10 that they forgot can still confirm without having to text you in panic.
The dashboard shows you who replied after the deadline so you can flag them in your seating planning. Some couples chase them with a friendly "we noticed you replied late, can we still count on you?" message. Most just absorb them into the headcount and move on.
Building it without writing any code
You do not need to build any of this from scratch. Wedding30s includes the RSVP form, the dashboard, the menu choices, the dietary tracking and the export to CSV by default. You fill in your details, you publish the wedding website, the form is live. 49€ one time, no subscription.
The setup takes five minutes. The peace of mind it gives you in the last month before the wedding is hard to put a price on, but if we had to: it is the difference between sleeping eight hours a night and refreshing your email at 2am.