RSVP Questions Every Indian Wedding Form Should Ask

The standard Indian wedding RSVP form asks three things: name, number of people attending, and maybe a food preference. That's not enough.

By the time the wedding is three weeks away, every couple discovers the information they wish they'd collected upfront: which guests are coming to which specific events, who needs accommodation, which outstation guests have actually confirmed travel, how many children are in the group, who needs a Jain meal.

Getting that information now — through a well-designed RSVP form — saves 40+ hours of phone calls later. Here's every question worth asking, why it matters, and how to frame it for the best response rate.

The baseline questions every form needs

Before the Indian-wedding-specific questions, make sure you have the obvious ones structured correctly.

Full name — Ask for both partners' names if couples are attending. "Rahul and Priya Mehta" gives you a searchable, seatable record. "The Mehtas" gives you nothing useful.

Number of people in your group — Set a maximum if you have a strict cap. "Party of 1 to 4" is friendlier than "No additional guests permitted." Consider whether you want to auto-allow plus-ones or ask them to specify names.

Mobile number — Make this required, not optional. You need a number to confirm last-minute details and send venue/logistics updates over WhatsApp. Collecting it here means you won't have to hunt it down later.

If you have guests whose first language is Hindi or Tamil, consider offering a Hindi/Tamil version of the form or at minimum translating key field labels. Response rates go up when guests aren't confused by field names.

The questions most Indian wedding RSVP forms skip

1. Per-event attendance

This is the most important category and the most commonly missing.

A single "Are you attending?" question assumes all guests attend all events. In reality, headcounts vary dramatically by event — your Haldi might have 120 guests while your Reception has 400. Collecting per-event attendance upfront gives you the numbers your caterer, venue, and decorator need for each function.

For each event you're hosting, add a yes/no question:

Will you be attending the Mehendi? ☐ Yes ☐ No
Will you be attending the Haldi? ☐ Yes ☐ No
Will you be attending the Sangeet? ☐ Yes ☐ No
Will you be attending the Wedding Ceremony? ☐ Yes ☐ No
Will you be attending the Reception? ☐ Yes ☐ No

If an event is family-only (Haldi and some Mehendi ceremonies are), either remove it from the form or add a note: "Haldi is for immediate family only — please skip this question if you're a friend."

Multi-Event RSVP for Indian Weddings: Track 500 Guests Across 5 Functions

2. Dietary preference (in detail)

"Veg or non-veg?" is the bare minimum. A well-designed form captures four categories:

Vegetarian — standard veg
Non-vegetarian
Jain (no onion, garlic, root vegetables, or underground produce)
Satvik (no onion or garlic; differs from Jain in that root vegetables are allowed)

Why this matters: Jain catering requires a completely separate preparation line at most venues. If you don't know how many Jain guests you have, the caterer will either refuse to offer it, or quote for a large contingency buffer that you pay for regardless.

Some couples also add:

Vegan (still rare in Indian weddings but growing, particularly for NRI guests)
Allergies or restrictions — an open text field for anything that doesn't fit a category

Ask dietary preference per person if possible, not per party. A group of four may have two non-veg, one vegetarian, and one Jain. If you only capture one preference per party, someone gets the wrong meal.

3. Children attending

Children are often overlooked in RSVPs because adults fill out the form and forget to mention them. You need to know:

How many children are in your group?
Ages (broadly): Under 5 / 5–10 / 10+ — this affects meal type (high chair, kids' menu, or adult portion)

Caterers charge differently for children under 10 (typically 40–60% of the adult plate rate). If you have 30 children at your wedding that nobody counted, you're paying full adult rates for some and scrambling to arrange kids' food for others.

4. Outstation or local

This single question shapes your entire logistics planning:

Are you travelling from another city for the wedding? ☐ Yes ☐ No (I'm based locally)

For outstation guests who answer yes, add:

Have you confirmed your travel arrangements? ☐ Yes, travel is booked ☐ No, still planning
Will you need accommodation? ☐ Yes, please share hotel recommendations ☐ No, I've arranged my own
Will you need airport/station pickup? ☐ Yes ☐ No
Arriving on: [date]
Departing on: [date]

The arrival/departure dates let you plan the farewell breakfast headcount separately — one of the most commonly underestimated meals at Indian weddings, because the guest count is exclusively outstation guests who haven't yet left.

The travel confirmation question is critical for your catering buffer. Outstation guests who have booked flights have a very low no-show rate (3–7%). Outstation guests who "plan to come" but haven't booked yet have a no-show rate of 20–35%. Knowing which category each outstation guest falls into helps you set a more accurate catering guarantee.

Collect all of this automatically

The Curated Knot's RSVP form captures per-event attendance, dietary preferences, and outstation details — and gives you live headcounts by event.

Try it free

5. WhatsApp number for updates

Even if you already have guests' numbers in your contact list, asking for a WhatsApp number on the RSVP form gives you:

A verified, current number for each attendee
A clear record of which guests have opted in to receive wedding updates
An easy export list for creating WhatsApp broadcast lists for event-day logistics

Frame it as: "We'll send event updates, venue details, and reminders over WhatsApp. What's the best number to reach you?"

Most guests are happy to share this when it's framed around convenience, not formality.

6. Language preference for communication

If your wedding has a bilingual guest list — common for NRI couples or mixed North/South Indian families — ask:

Would you prefer updates and communications in English or Hindi?

This is especially useful if you're sending event timelines, venue maps, or schedule PDFs. Having two versions (English and Hindi) and knowing which guests get which saves you from sending the wrong document to the wrong group.

7. Special requirements or accessibility needs

A simple open-text field: "Do you have any special requirements we should know about? (Wheelchair access, specific dietary restriction not listed above, etc.)"

This is both courteous and practically useful — knowing about a guest who needs wheelchair access before you book the venue layout, rather than on the day, can save significant stress.

Questions for specific event types

For the Sangeet / Mehendi

Are you performing / participating in the programme? ☐ Yes ☐ No
(For Mehendi) Would you like Mehendi? ☐ Yes ☐ No (this helps the Mehendi artist estimate how many hands they're doing)

For destination weddings

Do you need a hotel room? ☐ Yes — please add me to the room block ☐ No, I'll arrange separately
Room type preference: Single / Double / Triple sharing
Do you need local transportation from the hotel to venue? ☐ Yes ☐ No

For the farewell breakfast

Most couples don't create a separate RSVP for the farewell breakfast, but if you're hosting one, ask outstation guests:

Will you join us for the farewell breakfast? ☐ Yes ☐ No
What time are you checking out / departing?

How to structure the form without overwhelming guests

The goal is to collect everything you need without making guests feel like they're filling out a government form. A few structural tips:

Use conditional logic. Show the outstation questions only to guests who mark themselves as outstation. Show the travel confirmation question only to confirmed outstation guests. This keeps the form concise for local guests who don't need those fields.

Group questions by theme. "Your attendance" → "Your group" → "Logistics" → "Anything else?" is a natural flow. Mixing dietary preference questions with accommodation questions mid-form creates friction.

Mark required fields clearly. Name, mobile, and per-event attendance should be required. Dietary preference should be required. Outstation details are required only for outstation guests. Everything else is optional with a gentle prompt.

Set a clear deadline. Put the RSVP deadline at the top of the form, not buried in small text at the bottom. "Please RSVP by 12 May" is the first thing guests should see after the opening greeting.

Keep the form mobile-friendly. A large portion of your guests will fill this out on their phones, possibly in WhatsApp after clicking a link you sent. Forms that are hard to navigate on mobile get abandoned. Stick to simple yes/no toggles, dropdowns, and short text fields.

Why Indian Guests Don't RSVP — And How to Get Responses

The complete checklist

Here's every question worth including, in logical order:

Attendance basics

Full name (all attendees in the group)
Number of people in your group
Mobile number (WhatsApp)
Language preference (English / Hindi / Tamil / other)

Per-event attendance

Mehendi: attending? (Y/N)
Haldi: attending? (Y/N)
Sangeet: attending? (Y/N)
Wedding Ceremony: attending? (Y/N)
Reception: attending? (Y/N)
Farewell breakfast: attending? (Y/N) — for outstation guests

Dietary

Dietary preference per person (Veg / Non-veg / Jain / Satvik / Vegan / Other)
Any specific dietary restrictions or allergies? (open text)

Children

Number of children in group
Ages of children (range: Under 5 / 5–10 / 10+)

Outstation & logistics (show to outstation guests only)

Special requirements

Accessibility needs or anything else we should know? (open text)

You won't use every one of these for every wedding. A 150-guest intimate wedding in one city needs fewer fields than a 600-guest multi-city destination wedding. Start from this list and remove what doesn't apply to your situation.

The Curated Knot's RSVP builder lets you create forms with per-event attendance, conditional outstation fields, and dietary preference collection — and gives you real-time headcount dashboards by event. Start free →