What Questions to Ask on Your Wedding RSVP Form

The aim of a wedding RSVP form is straightforward: get a clear answer from every guest before you have to start chasing them individually. That means keeping it short enough that people actually fill it in, while collecting the information you genuinely need for catering, logistics, and seating.

The two failure modes are obvious in hindsight. Too many questions and guests abandon the form halfway through, planning to come back to it — which usually means never. Too few, and you close the RSVP with 120 confirmed guests and no idea who's vegetarian or who has a serious allergy.

The rule is simple: only ask for information that will change something you're planning.

The essentials — always include these

1. Attendance

Sounds obvious, but be precise about who the form covers. If you're inviting couples or families, the form should make clear whose attendance is being confirmed.

For individual invites:

Will you be joining us? ○ Yes, I'll be there ○ Sorry, I can't make it

For a plus-one invite:

RSVP for: Emily and guest ○ We're both coming ○ Just me ○ We can't make it

If your guest list already has names imported, skip asking for their name again — you already have it.

2. Headcount (for group invitations)

For families or guests listed with a plus-one, you need a clear number for catering and seating. Keep it specific rather than vague:

Will children be joining you? ○ Yes ○ No ○ Not sure yet

You need these numbers to confirm catering quantities and arrange seating accurately.

3. Dietary requirements and allergies

This is the most important practical information you'll collect. Caterers need it, and for guests with serious allergies — anaphylaxis, coeliac disease — it's a safety issue, not a preference.

A free-text field works better than a list of checkboxes here:

Any dietary requirements or allergies? (Leave blank if not applicable)

If your caterer needs a hard split between vegetarian and non-vegetarian numbers, add that as a separate question — but not instead of the allergy field.

---

Questions worth adding (depending on your situation)

These aren't essential for every wedding. Add them only if you know what you'll actually do with the answers.

4. Meal choice

If your caterer needs numbers in advance, ask. If everyone gets the same menu, don't bother.

Main course: ○ Roast chicken ○ Pan-roasted salmon ○ Wild mushroom risotto (v)

One choice per guest. Don't ask people to mark meal choices for a whole table — it creates confusion when you're trying to seat people later.

5. Day guests vs evening guests

Many UK weddings have separate day and evening guest lists, which changes what you need from each group. Day guests need the full form — dietary requirements, meal choice, all of it. Evening guests just need a confirmation of attendance.

It's worth building two separate short forms, or clearly labelling which section applies to whom. Sending everyone the same form and hoping they answer the right questions is a reliable route to chaos.

6. Transport / coach

If you're running a coach from a central meeting point, it's useful to know numbers in advance:

Will you need transport from [meeting point]? ○ Yes please ○ No, making my own way ○ Not sure yet

Don't include this question if you're not organising transport — it confuses guests into thinking they need to arrange something.

7. Children

If children are welcome and you want to plan for them — high chairs, a kids' menu, a children's corner — ask:

Will children be joining you? ○ Yes, ___ child/children ○ No

If the reception is adults-only, say so clearly in the invitation and on your wedding website. Don't let guests discover it through the RSVP form — that's not the right moment.

8. A note to the couple

An optional free-text field that takes seconds to add and occasionally produces something you'll keep forever.

Anything you'd like to say to us? (optional)

---

What to leave off the form

Information you already have. If guests are imported from your guest list with their name, email, and phone number, don't ask for those again. Redundant questions make the form feel disorganised.

Things you can collect elsewhere. Song requests for the DJ, preferences for the evening playlist, a choice of favour — these don't belong in the RSVP form. Collect them separately, when they're actually needed.

Questions you already know the answer to. If someone was invited solo, don't ask whether they're bringing a plus-one. If the reception is adults-only and guests know it, don't ask about children. Unnecessary questions add noise and suggest a lack of thought.

Anything that feels like a survey. "How did you hear about our venue?" or "Which decade of music is your favourite?" — guests can tell when they've accidentally wandered into a feedback form. It's a mood-killer.

---

What a well-built form looks like in practice

A form that covers everything and doesn't put guests off usually looks something like this:

Block 1 — Attendance:

• Coming or not? (yes / no)
• How many people? (for group invitations)

Block 2 — Food:

• Dietary requirements and allergies (always)
• Meal choice (only if the menu requires it)

Block 3 — Logistics:

• Transport needed? (only if you're running a coach)
• Day or evening guest? (only if you have separate guest lists)

Block 4 — Close:

• A note to the couple (optional)

That's 4–7 questions. Two to three minutes to fill in. Response rates are measurably higher than forms with 12+ fields.

---

When to send your RSVP and how long to leave it open

Send 6–8 weeks before the wedding. Earlier than that and guests put it to one side because the date feels far away. Later and you don't have enough time to chase stragglers and finalise numbers with your venue and caterer.

Set a specific deadline. "Please RSVP by 15th April" is far more effective than "as soon as possible". Guests with a deadline know they need to act. Guests without one will assume there's still time, indefinitely.

Set the deadline 3–4 weeks before the wedding. That leaves you time to follow up with non-replies, finalise catering numbers, and begin seating planning — without doing all of it in the final week.

Once the deadline passes and guests still haven't replied, don't send another broadcast message. Text or call them directly. It's the only thing that reliably works at that point.

---

FAQ

Can I combine the meal choice with the RSVP form? Yes — and it's the simplest approach for guests. One form, one link, one sitting. No need for a separate process a few weeks later.

What should I do if guests don't reply by the deadline? Send a gentle reminder around 14 days before the deadline, and another 3–4 days before it closes. After the deadline, follow up personally. A direct message or phone call works; another mass link to the form does not.

Do I need to ask about dietary requirements even if everyone gets the same menu? Yes. The allergy field should always be there. Even with a fixed menu, your caterer needs to know about serious allergies.

How long should the form take to complete? A reliable guide: it should fit on one phone screen without scrolling. If guests have to scroll more than once, you're probably asking too much.

Should I include a comment box? An optional free-text field is worth adding. Most guests leave it blank. The ones who don't often write something genuinely lovely.

---

You can set up your RSVP form in a few minutes with Celebrate's online RSVP tool. Replies feed directly into your guest list, so there's nothing to copy across manually.