Indian Wedding RSVP Deadlines: A Guide for Every Function

Most RSVP deadline advice on the internet tells you the same thing: "set your deadline 3–4 weeks before the wedding."

That's advice written for a one-event, 100-guest wedding in Connecticut. It's wrong for your 5-event, 400-guest shaadi — and following it will leave you chasing RSVPs the week of your Sangeet while you should be doing your trials.

Indian weddings have multiple functions, each with different guest lists and different lead time requirements. Your Haldi deadline isn't the same as your Reception deadline. Your outstation family needs more notice than your local friends. And one "RSVP by" date for everything — a single reminder, a single follow-up cycle — doesn't match how Indian families actually make attendance decisions.

Here's a timeline that actually works.

Why one RSVP deadline doesn't work

Think about the decision-making chain your outstation relatives go through to attend your Mehendi:

They need to check their work calendar. Their spouse needs to check theirs. They need to book flights or trains. If they have children, school schedules are involved. Chacha might need to ask Chachi. Chachi might need to ask her parents if they're coming too.

That process takes 3–5 weeks for outstation guests — minimum. If you set your Mehendi RSVP deadline 3 weeks before the Mehendi, you've given them no time at all.

Then there's the second reality: Indian guests do not respond to the first reminder. Not because they're being difficult, but because the RSVP decision isn't fully theirs to make. They need to discuss, confirm with the group, and then respond. One reminder cycle is not enough. You need to build in a second chase.

A realistic first-attempt response rate for digital RSVPs in India is 40–60%. The remaining guests typically respond after a personal follow-up — phone call, WhatsApp message, or a nudge from a mutual family member. Build this into your timeline rather than treating it as failure.

The RSVP timeline: function by function

Assume your wedding day is Day 0 — the day of the main ceremony. Work backwards from there.

Haldi — Day -1 or Day -2

Invite issued: 6 weeks before Haldi RSVP deadline: 3 weeks before Haldi Second chase: 2 weeks before Haldi (for non-responders) Final count submitted to venue: 10 days before Haldi

Haldi is typically the smallest, most intimate event — immediate family only, usually 30–60 people. Because the guest list is small and mostly local, the turnaround can be tighter. But you still need 10 days to give a final count to whoever is managing food and space.

Mehendi — usually Day -2 or Day -3

Invite issued: 8 weeks before Mehendi RSVP deadline: 5 weeks before Mehendi Second chase: 3 weeks before Mehendi Final count to mehndi artist and caterer: 2 weeks before

Mehendi often has outstation guests — especially female relatives flying in specifically for pre-wedding functions. Eight weeks gives them time to book travel. Five weeks is your first deadline. You'll need to chase; expect 30–40% of responses to come in the second window.

Sangeet — usually Day -1

Invite issued: 8 weeks before Sangeet RSVP deadline: 4 weeks before Sangeet Second chase: 2 weeks before Final count to venue: 10 days before

Sangeet typically has the widest guest list of the pre-wedding functions — it's where extended family, college friends, and family friends all mix. Wider list means more decisions to coordinate, which means slower initial response rates. Give yourself 4 weeks of lead time after the deadline to chase and finalise.

Baraat — Day 0 (procession)

RSVP deadline: 3 weeks before Final confirmation: 1 week before

Baraat RSVPs aren't about logistics on your end as much as they are about confirming who's walking. The venue knows to expect the whole wedding group. But the procession itself — number of vehicles, dhol bookings, dancing coordination — depends on an accurate count. Get confirmation a week out.

Pheras / Ceremony — Day 0

RSVP deadline: 6 weeks before Second chase: 3 weeks before Seating arrangement submitted: 2 weeks before

The ceremony is where seating matters most. Mandap seating, family seating, and the overall ceremony layout depends on knowing your count. Six weeks is not too early — it lets you produce accurate seating charts and give the venue a confirmed number before the pre-wedding functions even begin.

Reception — Day 0 or Day +1

Invite issued: 10 weeks before RSVP deadline: 6 weeks before Second chase: 3 weeks before Final headcount to caterer: 2 weeks before

Reception is the largest event and often has the most expensive per-head catering cost. A late RSVP here has direct financial consequences. Caterers typically need final numbers 2 weeks out. That means your second chase cycle needs to be complete by 3 weeks out — which means your first deadline needs to be 6 weeks out.

Set RSVP deadlines per function — automatically

The Curated Knot lets you create separate RSVP forms for each Indian wedding function with individual deadlines, WhatsApp reminders for non-responders, and dietary and travel modules built in. Free to start.

Try it free

The second chase: what to do with non-responders

At your first deadline, you'll have responses from roughly half your guest list. Here's what to do with the other half.

Segment before you chase. Not all non-responders are the same:

Outstation guests who book travel late — they may just need more time. A gentle reminder is enough.
Elderly relatives — they likely received the digital RSVP but weren't sure how to complete it. Call them. Don't send another form.
"Family group" responses — one household that's coming as 6 people may have had one person respond but not the others. Clarify rather than chase individually.
The genuinely unsure — some guests won't know until closer to the date. Set a hard final deadline and stick to it.

Message for the second chase (WhatsApp):

"Hi [Name]! We're finalising numbers for [function] with the venue this week. We'd love to have you — can you let us know by [date]? Here's the link if it's easier: [link]"

For older relatives, a phone call is more effective than any digital reminder. Have someone in the family make those calls — not you, two weeks before your wedding.

When you give caterers a final headcount, add 8–10% to your confirmed RSVP count. Indian wedding attendees who never formally RSVPed will show up anyway — usually as "+2" to someone who did confirm. Build that buffer into your numbers.

A practical summary table

Function	Issue invites	First RSVP deadline	Second chase	Final count
Haldi	6 weeks before	3 weeks before	2 weeks before	10 days before
Mehendi	8 weeks before	5 weeks before	3 weeks before	2 weeks before
Sangeet	8 weeks before	4 weeks before	2 weeks before	10 days before
Ceremony	8 weeks before	6 weeks before	3 weeks before	2 weeks before
Reception	10 weeks before	6 weeks before	3 weeks before	2 weeks before

If all your functions are within a 4-day window, work from the earliest function and give every deadline some extra buffer. It's better to have accurate numbers 4 weeks out than to be chasing on Day -5.

When your functions are compressed into one weekend

Not every wedding has functions spread across two or three weeks. If your Mehendi, Haldi, Sangeet, and ceremony all happen within a 3–4 day window, the timeline above won't work function-by-function — you need to consolidate.

In this case, treat the earliest function as your planning anchor. Issue all invitations at once, 8–10 weeks before the first event. Set one RSVP deadline — 5 weeks out — that covers all functions simultaneously. Your second chase (3 weeks out) is then the only follow-up cycle before you finalise counts.

The catch: you need to capture per-function attendance in a single RSVP form. This means your form must ask "Which events will you be attending?" with checkboxes for each function, rather than sending separate forms for each. The tradeoff is slightly more complex form design in exchange for a single, consolidated RSVP process.

For compressed schedules, don't forget that NRI guests booking international travel need 8–10 weeks minimum. If you send invitations 8 weeks out and set your RSVP deadline at 5 weeks, NRI guests have only 3 weeks from invitation to response — very tight if they're waiting for flights to be affordable or leave approval to come through. Consider sending a "save the date" to NRI family 3–4 months out so they can book travel before the formal invitation arrives.

NRI-specific deadline adjustments

NRI guests planning travel to India for a wedding operate on a different timeline than local guests. They need to clear annual leave, book international flights (ideally 8–12 weeks out for decent prices), and coordinate family travel schedules. Your RSVP deadline needs to account for this.

Adjusted timeline for NRI guests:

Save the date: 4–5 months before the wedding
Formal invitation: 10–12 weeks before the main ceremony
First RSVP deadline: 8 weeks before (so they can book travel immediately on confirming)
Second chase: 6 weeks before
Final count for catering: 3 weeks before

Send NRI guests their invitations 2–3 weeks before the general invitation batch. This gives them lead time without making local guests feel they received theirs late.

One thing worth automating

Manually tracking which guests have responded to which function, then sending function-specific reminders to non-responders, is several hours of spreadsheet work per function. For a 400-guest wedding with 5 functions, you're looking at 20+ hours of admin over 3 months.

The Curated Knot's RSVP feature handles this — separate RSVP forms per function, individual deadline settings, and automated WhatsApp reminders to guests who haven't responded. You set the deadline and message once; it runs the follow-up cycle without you managing a spreadsheet.

Tracking per-function deadlines and chasing non-responders is the part of wedding planning that eats the most time. The Curated Knot automates the follow-up cycle — set your deadline and message once per function, and the system handles the rest. Try it free →

Frequently Asked Questions

How early should I send wedding RSVP invitations in India?

For the reception and main ceremony, send invitations 10 weeks before and set your first RSVP deadline 6 weeks before. For pre-wedding functions (Mehendi, Haldi, Sangeet), 8 weeks for the invite and 4–5 weeks for the first deadline works well. NRI guests should receive a save-the-date 4–5 months before and a formal invitation 10–12 weeks before.

What is a reasonable RSVP deadline for an Indian wedding?

The "3–4 weeks before the wedding" advice common in Western wedding planning doesn't work for multi-event Indian weddings. You need 6 weeks before the reception for caterer headcounts, and even more for outstation and NRI guests who need to book travel. Set per-function deadlines, not a single deadline for everything.

What percentage of Indian guests respond to the first digital RSVP?

Expect 40–60% response rate on your first RSVP request. The remaining guests typically respond after a personal follow-up — phone call, WhatsApp message, or a nudge from a mutual family member. This is normal and expected. Build a second chase cycle into your timeline rather than treating low first-round response as failure.

Should I set different RSVP deadlines for Mehendi vs Reception?

Yes. Your Mehendi guest list is typically smaller and more intimate; your reception is the largest event with the most expensive catering. The reception caterer needs your final headcount 2 weeks before — which means your second chase needs to be complete 3 weeks before, and your first deadline 6 weeks before. Mehendi can work with a tighter 3-week first deadline if it's a local, smaller event.

How do I handle guests who didn't RSVP by the deadline?

Segment before you chase: elderly relatives who may have had trouble with the form need a phone call, not another link. Outstation guests who are sorting travel need a personal message acknowledging the complexity. Friends who are procrastinating need a casual WhatsApp with a mild deadline. Do not send a generic broadcast reminder to all non-responders — it's less effective and more likely to annoy guests who are already planning to come.

How much buffer should I add to the caterer's headcount?

Add 8–10% to your confirmed RSVP count for the caterer. Indian wedding guests who never formally RSVPed will show up — usually as "+1" or "+2" to someone who did confirm. Some guests will also RSVP yes and not attend. These two groups roughly cancel out, but to be safe, give the caterer a number that's 8–10% above your confirmed digital RSVPs.