Wedding RSVP questions: what to ask your guests, and what not to.

Every wedding RSVP form on the internet asks the same nine questions, and about four of them are actively working against you. This is what we've watched happen inside real wedding sites: which questions guests actually finish, which ones make them close the tab, and which ones save you from a caterer email at 11 p.m. the week before the wedding.

If you've been staring at a template builder's default form wondering whether you really need "favorite drink" and "home address" and "will you be attending the after-party at TBD," this page is for you. We build bespoke wedding sites, in as many languages as your family speaks, hidden from Google by default. The RSVP is where all of that pays off: a form that respects your guests gets answered.

The question set your caterer will thank you for

Ask these questions, in this order, and stop. Every extra field is a chance for a guest to bail out mid-form.

• Which events are you attending? Ceremony, reception, and any next-day brunch, each as its own checkbox. Guests reply honestly when they can accept the parts they can travel for without feeling like they're refusing the whole invitation.
• How many are coming, and what are their names? One row per person, first and last name. Names, not headcount. This one field alone kills three follow-up messages: the seating chart uses it, the escort cards use it, and the caterer's dietary tags need it.
• Meal preference, as a single choice: vegetarian, vegan, gluten-free, strictly kosher, no restriction, or "other" as a short free-text field. Kosher and vegan belong in the main list, not tucked behind "other." First-class options for the guests who need them, and your caterer sees the counts cleanly.
• Allergies and intolerances, as a short free-text field. Different from a dietary preference; you want to know about the peanut allergy even if the guest ticked "no restriction" for meals.
• Kids' meal count. If children are invited, ask how many kids' meals to prepare and note ages if the caterer needs them. If children are not invited, do not add a field asking about children; the address on the invitation has already handled that.
• Plus-one confirmation, only for guests you're actually offering one to. This is not a question you ask everybody. More on this below.
• Shuttle or transport, if you're running one. "Will you use the 4 p.m. shuttle from the hotel?" The bus company needs a real number, not a shrug.
• Song request, one line, optional. Teenagers love this. Uncles love this. Your DJ will filter it, but the guest who requested the song will remember all night that you asked.
• Dance floor promise: "Will you be on it after midnight?" The teens tick yes competitively. It's a small thing that turns the form from paperwork into a conversation, and it doubles as a soft prediction of your late-night crowd.

That's nine fields. Some are yes/no, some are one-tap, one is optional. The whole form fits on a phone screen without scrolling twice. A guest opens it at a bus stop, finishes it before their coffee arrives, and closes it feeling like a person.

The questions to SKIP

These are the fields we quietly delete from every draft that arrives from a template builder. Each one costs you completions, and none of them pays you back.

• Home address. You don't need it. If you needed it for the paper invitation, you already have it. Guests are wary of typing their address into a form on a website they don't recognize, and rightly so. The one occasion you'd want it is for a thank-you note; a shared spreadsheet from the two of you covers that better than a form.
• Phone number, if you already have it. If the guest is on your invite spreadsheet, their number is already there. Asking them to retype it feels like a database, not a wedding.
• Favorite drink. Surveys are for tech companies raising a Series B. Your bartender needs three signature cocktails and a wine list; they do not need 140 individual answers to "what's your favorite drink?" The information is unusable, and asking for it flips the tone of the form from "come celebrate with us" to "please complete this intake."
• Are you bringing a gift. Never. Not phrased any way. Not even softened. A registry link belongs on a separate page, mentioned once, in a warm sentence. It does not belong on the RSVP.
• Hotel booking status. A helpful "let us know if you need accommodation suggestions" is fine as a note near your travel section; a required field on the RSVP form is not. Guests who need help finding a hotel will email you. Guests who don't don't want to answer.
• Guest of honor moments. Whether they'd like to give a speech, propose a toast, be asked to sign the ketubah: figure that out privately, in a phone call. A form is not the way to invite someone to be moved.

Rule of thumb: if a question won't change what your caterer, seating chart, shuttle driver, or DJ does on the day, it doesn't belong on the RSVP. It belongs in a text to that friend.

How to phrase plus-ones without offense

The golden rule is short: decide plus-ones before the invitation goes out, not through the RSVP form. Do this and the whole plus-one drama evaporates.

Here's how the address on the invitation carries the decision, so the RSVP doesn't have to:

Because the address has already declared who's invited, the RSVP form only needs to say: "Hi Sarah, we saved 2 seats for you. Please let us know who's joining." The plus-one field appears prefilled with "guest" and Sarah types the name. It appears only on Sarah's form, because your website matches the guest to their invitation record.

Never, under any circumstances, add a global question that reads "Would you like to bring a plus-one?" That question hands the decision back to the guest for a call you've already made. Guests who weren't offered one now feel demoted; guests who were will assume you're second-guessing yourself. Bad math on both sides.

When your guest list is mixed, some couples, some solo, the form still copes: the invited pair sees two rows, the solo friend sees one, nobody sees a field they didn't need. Custom design pays off here, because the shape of the form changes per guest without a single awkward toggle.

The reminder cadence

Guests reply on time when the deadline feels real and the reminders feel like a kindness. Two automated nudges, in decreasing volume, get you almost all the way there:

The trick isn't the number of reminders. It's the wording. A reminder that sounds like it came from a marketing platform gets ignored; one that sounds like it came from you gets answered. Both automated emails go out with your names in the signature, your voice in the sentence, and the guest's first name at the top. Never "Hi there."

Set the RSVP deadline itself six weeks before the wedding. Closer than that and your caterer starts pricing extras nervously; further out and guests forget between the reply and the day. Six weeks is the sweet spot every planner we've worked with converges on, and once you've picked it, put the date on the RSVP page in a size you can read from across the room.

Chasing politely, template messages

The last stragglers are almost always friends, and friends respond to friend-language, not form-language. Two templates our couples reuse, one gentle, one direct:

Two rules for chasing: never in a group thread, and never through the person's partner. Both feel like being called on in class. A personal message to the individual, from you, gets a reply within the day.

From RSVP list to seating chart and caterer sheet

The point of collecting the answers is being able to use them. A wedding RSVP form that spits raw data at a spreadsheet is fine; a wedding RSVP form that shows you real numbers, on the page, filtered by event, is transformative.

Here's how a well-built site turns replies into decisions:

• Live totals, filtered by event. How many are coming to the ceremony, the reception, the brunch, right now, at a glance. You will refresh this page more than any other in the last month before the wedding. It should feel calm, not like a dashboard.
• Meal counts by category, broken out: 62 no restriction, 14 vegetarian, 8 vegan, 4 gluten-free, 3 strictly kosher, 2 other (with the free text shown). This is the exact shape your caterer needs. Export it as a PDF or CSV, send it, done.
• Allergy list, isolated. A separate view for allergies only, printed and handed to the kitchen the day before the wedding. Nobody has time to hunt for the peanut allergy in a spreadsheet at 6 p.m.
• Names, grouped by household. Feeds the escort cards, feeds the seating chart, feeds the welcome bags.
• Kids' meals, isolated. The kitchen prints one sheet with kid names and ages. Small kindness that makes the day feel considered.
• Song requests, deduplicated, ready to hand to the DJ. Ten minutes of your time on the Wednesday before the wedding, and the playlist has ten more moments people will scream at when they hear them.

Every one of those views is a filter, not a re-entry. You are not copy-pasting from one sheet into another the week of your wedding. That's the one thing template wedding-site builders don't manage to keep, because they were built for averages, not for your day.

Questions couples ask us

Written by the Digithad studio

We design wedding websites for couples across the English-speaking world, and for the mixed-language families who make weddings such wonderful, complicated events. Every site is custom, private by default, and built to answer your guests' questions without you having to. Updated July 2026.