Wedding RSVP Websites: How to Collect and Manage Responses

Collecting RSVPs on your wedding website saves you stamps, chasing and a spreadsheet full of guesses. It works best when the form is short, the deadline is realistic, and you have a plan for the replies that don't fit neatly. This guide covers all three, from the first question to the final numbers you give your caterer.

How online RSVPs work

There are two common approaches.

Personal links. Each guest or household gets their own link or code. The platform knows exactly who is replying, but you have to send and manage many different links, and printed invitations can't carry them easily.

One link for everyone. Every guest uses the same address or QR code and types their name. It is simple to print and share, but the replies have to be matched to your guest list, and the form must not reveal who else is invited.

Both work. If you print invitations, one shared link and QR code is usually far simpler. If you choose that, check how your platform handles a name it doesn't recognise, two guests with the same name, and a guest who replies twice.

Set the reply-by date

Work backwards from the date your caterer or venue needs final numbers, not forwards from the invitation. You want enough time between your reply-by date and that cut-off to follow up with guests who haven't replied. Etiquette guidance varies: the Emily Post Institute suggests a reply-by date usually two to three weeks before the wedding, and many planners prefer around a month when guests travel or hotel rooms have booking deadlines.

Put the reply-by date on the invitation and at the top of the RSVP form. If you send a reminder, send it about a week before the deadline, and only to people who haven't replied.

Decide what to ask

Every extra question is one more thing for guests to fill in on a phone. Ask only what you will actually use.

Always ask:

• each person's full name, the way they are written on your guest list
• whether each person is attending

Ask if it applies:

• the name of a plus-one, if you invited one
• dietary requirements, if you are serving a meal
• food allergies (see below)
• a contact email, if you plan to send updates, and only with the guest's agreement
• transport or accommodation needs, if you are arranging them

Optional: a message to the couple. Guests like it, and it costs you nothing.

Example wording

• Name: "Your full name, as on the invitation"
• Attendance: "Joyfully accepts" / "Regretfully declines"
• Dietary requirements: "Any dietary requirements? For example vegetarian, vegan or halal."
• Allergies: "Any food allergies we should share with the caterer?"
• Deadline line: "Please reply by Saturday 22 May 2027."

Handle allergies and dietary details with care

Allergy information is about someone's health. In the EU and UK, data concerning health is a special category under Article 9 of the GDPR, which sets stricter conditions for using it, such as the person's explicit consent. In practice:

• Ask only what the caterer needs, and say who will see it ("the couple and the caterer").
• Ask guests to agree explicitly before they share allergy details.
• Keep dietary preferences and allergies as separate questions, because they are handled differently in the kitchen.
• Delete the details when the wedding is over.

This isn't legal advice, and the rules depend on where you and your platform are. When choosing a platform, check how it stores and deletes this information.

Test the RSVP form before you share it

1. Open the form on a phone from the printed QR proof, not from a bookmark.
2. Reply as a single guest, as a couple, and as a guest who declines.
3. Try a name with an accent, and the same name typed without it.
4. Check that each test reply appears where you expect, with the right details.
5. Remove the test replies, or use a preview mode if your platform has one, so they don't count in your totals.
6. Ask one real guest you trust to reply first and tell you anything that confused them.

The same goes for the rest of the site: our guide to making a wedding website has a full pre-launch checklist.

Manage the responses

Track three groups: attending, not attending and no reply yet. The third group is the one that needs your attention after the deadline.

Follow up kindly. A short personal message works best: "Hi Anna, we're finalising numbers for the caterer this week. Could you let us know by Friday whether you can come? Reply here or at our website."

Handle changes of mind. Keep the latest answer, but note that it changed, especially if it affects numbers or seating.

Watch for duplicates. Guests sometimes reply twice, or reply for each other. Check before you count.

Turn replies into numbers. When the deadline has passed and you've followed up, export or copy the final list: total guests attending, the count for each meal or dietary need, and allergies listed separately for the caterer.

How Loverisse handles RSVPs

Loverisse is launching soon. Its RSVP is designed around one link for everyone:

• Every guest uses the same web address and QR code. There are no personal links to send.
• One reply can include several people, each with their own name and their own answer.
• When a name clearly matches one guest on your list, that guest is updated automatically. A name that matches nobody, or more than one person, waits in a review queue for you, and the system never adds guests to your list on its own.
• Every guest sees the same thank-you page, so the form can't be used to find out who is invited.
• Guests can add dietary requirements, a message and an email for updates. Allergy details are only saved when the guest agrees that the couple and the caterer may see them.
• You can set a reply-by date and an optional code that guests enter to reply.

The questions on the form are fixed for now; custom questions are not available yet.

For the rest of your site, see what to include on your wedding website.