Indian wedding catering is generosity in motion — thalis, live counters, late-night chai — and it is also logistics. Jain guests, vegetarian households, allergies, kids’ plates, and fasting days all collide in one headcount. Collecting guest meal preferences for an Indian wedding early enough (and clearly enough) protects both hospitality and sanity.
This guide covers what to ask, when to ask, how to ask without turning RSVP into an interrogation, and how to hand clean numbers to your caterer.
Why meal preferences need a structured ask
“Veg or non-veg?” in a WhatsApp group produces incomplete answers, duplicate replies, and silent guests who assume you already know they are Jain. Caterers need counts by category, sometimes by function, and sometimes by special constraint (no onion/garlic, gluten-free, dairy-free, diabetic-friendly desserts).
A structured preference collect — on the RSVP form, wedding website, or a short follow-up — turns guesswork into a sheet you can share with the kitchen lead.
What to collect (keep the form short)
Ask only what will change plating or purchasing:
Core fields
- Household name / guest names attending
- Function(s) they will eat at (if menus differ by event)
- Meal preference category per guest or per household
Useful categories for many Indian weddings
- Vegetarian
- Non-vegetarian
- Jain / no onion–garlic
- Eggetarian (if your menu truly treats egg separately)
- Child meal / simpler plate
- Other constraint (free-text, short)
Allergy / medical note (optional one-liner)
- Nuts, shellfish, gluten, lactose — whatever your kitchen can realistically honour
Do not ask for favourite cuisines, spice-level personality quizzes, or six dessert votes. Preference collection is operations, not a food blog survey.
When to collect meal preferences
Tie meal questions to RSVP timing:
- With the RSVP for guests who reply online — one flow, fewer chases
- After a first RSVP wave if printed cards go first — send a short digital follow-up to confirmed households
- Cut-off 714 days before catering freeze (confirm exact freeze with your caterer)
Outstation guests should see meal questions early enough that you are not calling them the night before the sangeet. Local guests still need a reply-by date; “we’ll tell you on the day is not a preference system.
How to word the question kindly
Tone matters. You are hosting, not auditing.
Clear and warm examples:
- To plan the menu with care, please share a meal preference for each guest attending: Vegetarian / Non-vegetarian / Jain (no onion-garlic) / Child meal / Other (please specify).
- “Any allergies we should tell the kitchen about? (Optional)”
- “If preferences differ within your household, list names with each choice.
Avoid:
- “Confirm diet or we cannot serve you”
- Public group messages calling out individuals
- Assuming community = diet (not all guests from a region share one preference)
Per-function menus vs one weekend preference
Some weddings serve similar food throughout; others run a light mehndi spread, a grand sangeet dinner, and a ceremonial lunch.
If menus and guest lists differ by function:
- Collect preference per function only when the attendee list differs, or
- Collect one preference and apply it to all functions that guest attends
The second approach is simpler and usually enough. Use per-function meal RSVPs when reception-only guests far outnumber ceremony guests, or when one event is strictly sattvik.
Channels that work in Indian guest mixes
Wedding website / digital RSVP: best default for friends, colleagues, and many relatives comfortable with links. Preferences sit next to attendance so you do not maintain two lists.
Printed card + digital follow-up: elders receive the card; a family member submits the household preference online, or you collect via a polite phone call logged into the same sheet.
WhatsApp: fine for reminders and clarifications, poor as the only database. If someone replies “2 veg 1 Jain” in chat, copy it into the master sheet the same day.
Platforms such as LoveSolutions that combine invitation details with guest RSVP fields make it natural to capture meal preferences beside each household’s reply — without launching a separate survey people ignore.
Building a caterer-ready sheet
Your master sheet should include:
| Guest / Household | Function | Veg | Non-veg | Jain | Child | Allergy notes | Source | Updated |
|---|
Rules of thumb:
- One owner for the sheet (not five cousins editing freely)
- Freeze date agreed with caterer
- Buffer only for known late locals if the venue allows — not an infinite “maybe” column
- Special meals called out in a separate short list for the kitchen captain
Give the caterer category totals plus the short exception list. They do not need your full family politics.
Special cases to plan for
Fasting or festival overlaps
If a wedding day coincides with a fast some guests observe, note a simple fasting-friendly option with the caterer rather than collecting theology essays from every uncle.
Live counters
Live pasta or chaat stations still need base preference counts for planning protein vs vegetarian throughput. Preferences remain useful even when service is buffet-style.
Kids
“Child meal” prevents waste and meltdowns. Ask ages only if the kitchen needs them; otherwise a child-meal tick is enough.
Helpers and drivers
Plan separate staff meals. Do not mix them into guest preference totals without labelling — it distorts per-plate costing and seating.
Last-minute adds
Keep a small contingency percentage only if your caterer recommends it. Preference data should still cover named guests; contingency is for surprise plates, not a substitute for RSVP discipline.
Sample RSVP meal block (copy and adapt)
Meal preferences Please choose one per attending guest:
- Vegetarian
- Non-vegetarian
- Jain / no onion-garlic
- Child meal
- Other:
Allergy or kitchen note (optional):
Reply by: [date]
Mistakes that create kitchen-day stress
- Asking for preferences without a freeze date
- Letting three different aunts keep three different tallies
- Changing the category list after half the guests have replied
- Ignoring Jain / allergy notes until the menu tasting is over
- Assuming “family is veg” without asking married-in relatives
- Collecting exquisite detail you never send to the caterer
FAQ
Should every guest answer individually?
Ideal for allergies and mixed households. For uniform vegetarian families, one household answer can be acceptable if names and counts are still clear.
What if someone skips the meal question but RSVPs yes?
Follow up once with a short direct message and a default rule you have pre-agreed with the caterer (for example, count unspecified adults as vegetarian if that matches your menu majority — only if the caterer supports that default). Document the default; do not invent silently on the day.
Do we need meal preferences for cocktail-only receptions?
If substantial food is served, yes at a lighter level (veg / non-veg / allergy). For drinks-and-canapés with mixed platters, a simpler veg–non-veg split may suffice.
Can we collect preferences only from outstation guests?
You can prioritise them first, but local guests still eat. Partial collection creates false confidence in totals.
Closing thought
Collecting guest meal preferences for an Indian wedding is an act of care disguised as admin. Ask a short, respectful set of questions with the RSVP, keep one master sheet, freeze on time, and hand your caterer totals they can cook against. Guests feel seen — Jain, non-veg uncle, child with a simple plate — and you spend the wedding week celebrating instead of auditing dinner guesses.