"Wedding RSVP Questions: What to Actually Ask Your Guests"

An RSVP card asked one question because it had to fit on a card. An online RSVP has no such excuse, which is how couples end up with a twenty-field form that guests abandon halfway through. The goal isn't to ask more — it's to ask each person only what actually applies to them, and to have every answer land somewhere you'll use it.

Here's the rule the rest of this guide follows: if an answer won't change a decision you make or a service you provide, don't ask it. Curiosity is not a reason to add a field.

The questions every RSVP needs

Are you coming? One question, two options. "Joyfully accepts / regretfully declines" if your wording is formal, "Yes, I'll be there / Sorry, I can't make it" if it isn't. Don't offer "maybe" — it converts a decision you need into one you'll have to chase later.

Which of you is coming? This is the one most forms get wrong. An invitation goes to a household; an RSVP comes from people. If the Morgans are four names on one invitation, you need four answers, because Taylor might come and Jamie might not. Ask per person, not per envelope.

Who is your plus-one? Only if you offered one, and only if you need the name — which you do, the moment you're printing place cards or building a seating chart.

Meal questions

If guests choose an entrée in advance, put the options in the RSVP with the real dish names, not "Option A":

• Beef tenderloin
• Herb-roasted chicken
• Wild mushroom risotto
• Children's meal

The critical detail is again per person. A household of four can want four different mains, and a form that asks once per party quietly loses three of those answers. (Shared Beginning lets you set each custom question to ask per guest or per party for exactly this reason — meal choice is per guest, "which hotel are you staying at" is per party.)

Dietary requirements and allergies

Ask this as an open question, not a checklist:

Do you have any dietary restrictions or allergies we should know about?

A tick-box list forces someone with a serious allergy into the same bucket as someone who'd simply rather not have fish, and your caterer needs to tell those apart. Free text costs you nothing and gets you the sentence that actually matters: "coeliac, not a preference — cross-contamination is a problem."

Keep the answer attached to the guest, not in a separate document. The chain you want at the end is guest → attending → meal → dietary note → table, unbroken. The moment dietary needs live on their own sheet, someone has to reconcile it by hand at the worst possible time.

Multiple events

If your wedding is a weekend, one yes/no doesn't describe it. Somebody may come Friday and Saturday but fly home before brunch. Ask per event:

• Will you join us for the welcome party on Friday evening?
• Will you be at the farewell brunch on Sunday?

And ask only the people who are invited to that event. A guest who isn't on the rehearsal dinner list shouldn't see a rehearsal dinner question — it reads as an invitation, and you'll spend a week explaining that it wasn't. (In Shared Beginning you assign guests to events, and each guest's RSVP shows only their own events.)

Travel and accommodation

Useful for destination weddings and weekends with a shuttle, and mostly noise otherwise:

• Where are you staying?
• What day do you arrive?
• Will you use the shuttle from the hotel?
• Do you need a lift from the airport?

Ask the shuttle question only if there's a shuttle. Every field you add that leads nowhere makes the ones that matter easier to skip.

Accessibility

One open question does more than a list of conditions:

Is there anything that would make the day more comfortable for you?

Answers come back about step-free routes, seats away from the speakers, a chair rather than a pew, dimmable lighting, a quiet room, a service dog. You don't need anyone's medical history — you need to know what would help, which is a different question and a much easier one to answer honestly.

Children

If children are invited, ask what you'll actually act on: how many are coming, whether they need a children's meal, and whether they'll use childcare if you're providing it. Make your policy clear on the invitation and the website before the RSVP, though. A question about children's meals is not the place a family should first discover their kids are welcome — or aren't.

The fun ones

One or two, at the end, is plenty:

• What song will get you on the dance floor?
• What's your best marriage advice?
• What drink should we have waiting for you?
• Where should we go for our first anniversary?
• What's your favourite memory of us?

The song question earns its place — hand the list straight to your DJ. The rest are charming and optional. Put them last so nobody wades through them looking for the meal choice.

More examples, by category

If you want to browse rather than follow a structure, here's the fuller set:

• Attendance: will you attend, which members of your party, who is your guest, what name should we use on your place card
• Meals: entrée choice, children's meal, second-course choice, will you attend the seated dinner
• Dietary: allergies, restrictions, severity, will your dietary needs change by event
• Events: welcome party, rehearsal dinner, ceremony, reception, after-party, brunch, excursion
• Travel: arrival date, departure date, hotel, shuttle, airport transfer, parking, are you driving
• Accessibility: mobility needs, seating preferences, hearing or sight needs, quiet space, service animal
• Children: how many, ages, children's meals, childcare, high chair
• Contact: email, mobile number, postal address for thank-you cards
• Fun: song request, marriage advice, drink of choice, favourite memory, message for the couple

Take what applies. Leave the rest.

How many is too many?

There's no number — there's a shape. A guest who declines should answer exactly one question. A guest attending a one-day wedding with a plated dinner should answer three or four. A guest attending a four-event destination weekend might reasonably answer a dozen, because every one of those answers is doing a job.

What makes a long RSVP feel short is that nobody sees the parts that don't apply to them. Declining hides the meal choice. Not being invited to the rehearsal hides the rehearsal question. That's the whole trick.

Setting the deadline

Work backwards. Ask your venue and caterer when they need final numbers, then set your RSVP deadline two to three weeks before that — one week for the stragglers, one for you to chase them, and a few days to build the seating chart without panic.

Assume you will chase. There is always a handful, and a short list of names to text is much less work than a spreadsheet you have to re-derive.