Most Indian couples treat RSVP as a courtesy — a way to know roughly who's coming. The real reason to take it seriously has nothing to do with etiquette. It's money.
Catering is the single largest line item in an Indian wedding budget, accounting for 30–45% of total spend. At a national average of ₹39.5 lakhs per wedding (WedMeGood, 2025–2026), that's ₹12–18 lakhs spent on food alone. And caterers quote on headcount. Every 50 guests you overestimate across five events is money you never get back.
This post does the math nobody else does: how RSVP accuracy — or the lack of it — translates directly to lakhs saved or wasted.
Why Indian weddings make this harder than a single-event wedding
A Western wedding has one reception. You overestimate by 30 people, you waste one meal service.
An Indian wedding has five to seven events: Mehendi, Haldi, Sangeet, Wedding Ceremony, Reception, and sometimes a farewell breakfast or post-wedding brunch. Each event has a different guest list.
Here's what that looks like in practice:
| Event | Typical attendance (% of full guest list) |
|---|---|
| Haldi | 25–35% (close family only) |
| Mehendi | 50–65% (family + close friends) |
| Sangeet | 70–85% (most guests) |
| Wedding Ceremony | 90–100% (everyone) |
| Reception | 85–95% (most, some local guests skip ceremony) |
| Farewell breakfast | 30–50% (outstation guests only) |
If you have 400 confirmed guests and apply these percentages, your per-event headcounts look like this:
| Event | Headcount |
|---|---|
| Haldi | 120 |
| Mehendi | 220 |
| Sangeet | 300 |
| Ceremony | 380 |
| Reception | 360 |
| Farewell breakfast | 160 |
Total: 1,540 meals across the wedding. Not 2,400 (400 × 6 events). That 860-meal difference, at ₹1,500 per plate, is ₹12.9 lakhs. Caterers who don't ask about per-event counts — or couples who don't provide them — often quote on the worst-case total. The per-event headcount is where your RSVP data does its most important work.
Track per-event RSVPs automatically
The Curated Knot lets guests RSVP separately for each function — Mehendi, Sangeet, Haldi, Ceremony, Reception. Your headcounts update in real time.
The per-plate cost reality in 2026
Before calculating savings, you need to know what you're paying per plate. Here are current 2026 ranges by city and event type, based on vendor quotes and industry data:
| City | Budget catering (₹/plate) | Mid-range (₹/plate) | Premium (₹/plate) |
|---|---|---|---|
| Delhi-NCR | ₹900–1,400 | ₹1,500–2,200 | ₹2,500–4,000+ |
| Mumbai | ₹1,000–1,500 | ₹1,800–2,500 | ₹3,000–5,000+ |
| Bangalore | ₹800–1,200 | ₹1,400–2,000 | ₹2,500–4,000+ |
| Jaipur | ₹700–1,000 | ₹1,200–1,800 | ₹2,200–3,500+ |
| Tier-2 cities | ₹500–800 | ₹900–1,400 | ₹1,800–2,800+ |
Note: Most caterers provide a package rate with a minimum guarantee, then charge per additional plate above the guarantee. If you underestimate and exceed the guarantee, you pay a premium rate for extras (typically 20–30% higher than the package rate). If you overestimate and don't use the guaranteed plates, you pay for air.
The minimum guarantee is usually set 3–4 weeks before the event — which is exactly when your confirmed RSVP count needs to be reliable.
The actual cost of overestimating
Let's run a worked example. A 400-guest wedding in Delhi-NCR at mid-range catering (₹1,800/plate).
Scenario A: No proper RSVP tracking (conservative overestimate of 15%)
You tell the caterer 400 for the ceremony and reception, and use flat estimates for all other events. You're unsure about Sangeet, so you round up. You end up paying for:
| Event | Plates guaranteed | Actual attendance | Wasted plates |
|---|---|---|---|
| Haldi | 160 | 130 | 30 |
| Mehendi | 260 | 220 | 40 |
| Sangeet | 360 | 310 | 50 |
| Ceremony | 420 | 390 | 30 |
| Reception | 420 | 370 | 50 |
| Farewell | 200 | 150 | 50 |
| Total | 1,820 | 1,570 | 250 |
250 wasted plates × ₹1,800 = ₹4.5 lakhs paid for food nobody ate.
Scenario B: Accurate per-event RSVP data
With confirmed per-event RSVPs, you set guarantees at actual count + 7% buffer:
| Event | Confirmed RSVP | Guarantee set | Buffer plates |
|---|---|---|---|
| Haldi | 130 | 139 | 9 |
| Mehendi | 220 | 235 | 15 |
| Sangeet | 310 | 331 | 21 |
| Ceremony | 390 | 417 | 27 |
| Reception | 370 | 396 | 26 |
| Farewell | 150 | 160 | 10 |
| Total | 1,570 | 1,678 | 108 |
You now pay for 1,678 plates instead of 1,820. The difference: 142 plates × ₹1,800 = ₹2.56 lakhs saved. In premium-catering territory (₹3,500/plate), the same accuracy improvement saves ₹4.97 lakhs.
Dietary splits: the hidden cost most couples miss
The per-plate number is only part of the story. Indian catering increasingly involves separate food lines for dietary preferences — vegetarian, non-vegetarian, Jain (no onion/garlic/root vegetables), and satvik (pure veg, no onion/garlic). Each line has different per-plate costs.
If your RSVP form doesn't capture dietary preference, you're forced to assume a split — and caterers always quote on the worst case.
A typical Indian wedding dietary split:
- Vegetarian: 55–60% of guests
- Non-vegetarian: 30–35%
- Jain: 5–8%
- Satvik: 3–5%
Non-veg catering costs 25–40% more than veg (due to paneer vs. chicken/mutton pricing differentials). Jain catering involves separate preparation and is typically priced at a small premium (5–10%) for the labour. If you have 400 guests and don't collect dietary preferences, a caterer may quote based on 70% non-veg to protect their costs. On a 400-person wedding at ₹1,800/plate, moving from assumed 70% non-veg to confirmed 35% non-veg saves approximately ₹60,000–90,000 on food ingredient costs alone.
The Indian no-show rate: how to set your buffer
Unlike Western weddings where 95%+ of confirmed guests attend, Indian weddings have a well-documented "confirmers-who-don't-show" problem. How much buffer you need depends on guest type:
| Guest type | Typical no-show rate |
|---|---|
| Core family (first-degree relatives) | 2–5% |
| Extended family (cousins, relatives) | 8–12% |
| Close friends | 5–10% |
| Colleagues and acquaintances | 15–25% |
| Outstation guests (confirmed travel) | 3–7% |
| Outstation guests (not confirmed travel yet) | 20–35% |
The highest-risk segment is outstation acquaintances who said yes — they confirmed socially but haven't booked travel. These are the ones who call two days before with "so sorry, something came up."
A well-designed RSVP form asks outstation guests whether they've confirmed their travel arrangements. If they haven't, apply a higher buffer to that segment — or follow up specifically to confirm.
When caterers finalise headcount — and why it matters
Most caterers set three milestone points for headcount:
- Booking (3–4 months out): Estimated total for venue and staffing planning
- Final guarantee (3–4 weeks out): The number they commit to, and you pay for
- Emergency additions (48 hours out): Available at premium rate (+20–30%)
Your RSVP data needs to be reliable by milestone 2 — the final guarantee. This means you need your RSVP collection to close at least 4 weeks before the wedding, with follow-ups completed at least 5 weeks out.
If you're still chasing RSVPs 2 weeks before the wedding (which is very common with Indian weddings), you have two bad options: overestimate at the guarantee and waste food, or underestimate and pay emergency premium rates. Neither is good.
The solution is setting a firm RSVP deadline and closing it — with a separate smaller deadline specifically for outstation guests who need to confirm travel.
Related read
Indian Wedding RSVP Deadlines: A Guide for Every Function
When to close RSVPs for Mehendi, Haldi, Sangeet, and Reception — with a follow-up timeline that works for Indian families.
A practical RSVP-to-catering workflow
Here's how to connect your RSVP data to your catering quote:
8 weeks before wedding:
- Open RSVPs for all events
- Ask for: per-event attendance, dietary preference, outstation/local, travel confirmation for outstation guests
6 weeks before:
- First follow-up for non-respondents
- Calculate preliminary headcount per event (for venue and rough catering discussion)
5 weeks before:
- Second follow-up; start chasing outstation guests specifically about travel confirmation
- Close RSVPs formally (make this date clear on your invitation and RSVP form)
4.5 weeks before:
- Compile final headcounts: confirmed per event, with dietary splits
- Identify outstation confirmers without travel confirmation — apply higher buffer to this segment
- Provide caterer with per-event headcounts and set guarantee
3 weeks before:
- Final check for late RSVPs; incorporate into guarantee if still within caterer's change window
2 weeks before:
- Freeze headcounts; communicate final guarantee
- Provide caterer with dietary breakdown per event
This workflow assumes your RSVP system can give you per-event headcounts and dietary splits by individual guest. A spreadsheet can do this with enough discipline. A dedicated system does it automatically.
Related read
Multi-Event RSVP for Indian Weddings: Track 500 Guests Across 5 Functions
Managing RSVPs for mehendi, sangeet, pheras and reception separately — why WhatsApp fails and what multi-event RSVP actually needs to look like.
The bottom line
| Wedding size | Catering budget (est.) | Savings from accurate RSVP |
|---|---|---|
| 150-guest intimate | ₹5–8 lakhs | ₹60,000–1.2 lakhs |
| 300-guest standard | ₹10–18 lakhs | ₹1.5–3 lakhs |
| 500-guest large | ₹18–30 lakhs | ₹2.5–5 lakhs |
| 800+ guest grand | ₹30–55 lakhs | ₹4–8 lakhs |
These are conservative estimates assuming a 15% overestimation correction. In practice, couples who switch from no RSVP tracking to accurate per-event RSVP tracking report savings at the higher end of these ranges — because the starting point is often a 20–25% overestimate, not 15%.
RSVP is not a formality. It is a cost-control instrument. Treat it like one.
The Curated Knot's RSVP feature lets guests confirm attendance for each event separately — Mehendi, Haldi, Sangeet, Wedding Ceremony, and Reception — and captures dietary preferences per guest. Your headcounts by event and dietary split are available as a live dashboard, ready to hand to your caterer. Try it free →