Save the Dates and RSVPs for an Indian Wedding: Getting a Real Headcount

Why Indian weddings have a genuine RSVP problem

Ask any planner in Hyderabad, Udaipur or Delhi what keeps them awake three weeks before a wedding and the answer is almost never the decor. It is the number. The hotel wants a rooming list, the caterer wants a guaranteed cover count, the transport contractor wants to know how many cars meet how many flights, and the family knows none of it with confidence because barely half the invited households have said whether they are coming.

This is not laziness or rudeness. It is a cultural mismatch. Across most of India an invitation is an expression of relationship, not a booking. You invite your father’s colleague from 1994, your mother’s cousin in Vijayawada and the whole of your building because not inviting them would be an insult. The invited household reads it the same way: they are being honoured, and honouring back means showing up if they can, sending a gift if they cannot, and in neither case treating the card as a form to be returned. The concept of a reply card is imported. The obligation behind it never travelled with it.

That was survivable when weddings happened in the bride’s town, in a function hall with elastic capacity, with a cook who could stretch the sambar. It is not survivable when the wedding is at a resort in Goa or a palace hotel in Rajasthan, where every guest is a physical room, a coach seat, an airport pickup and a per plate contract with a minimum. The moment your wedding has a rooming list, an open invitation becomes an operational liability.

So the job is not to import Western RSVP etiquette wholesale and be disappointed when it fails. The job is to design a communication sequence that collects the data you actually need, using channels Indian families already use, while leaving the ceremonial part of the invitation untouched. Your grandmother does not need to learn to tick a box. Someone in the family needs to phone her and write down what she says.

The cost of guessing, in both directions

Before designing the process, understand what a bad number costs, because both errors are expensive and only one of them is embarrassing.

Over-catering. The usual family instinct is to add a cushion of 15 to 20 percent on top of the invited count, on the logic that running out of food is unthinkable. On a 500 guest function that cushion is 75 to 100 plates that nobody eats. At the sort of per plate rates a five star hotel or a premium outdoor caterer quotes in 2026, that is a meaningful sum wasted on every single function, and a wedding weekend has four to six of them. Multiply the waste across sangeet, mehendi, wedding lunch and reception and the cushion alone can run into several lakh. For what a plate actually costs at different service levels, see our breakdown of wedding cost per plate in India and the full wedding catering cost guide.

Under-catering. The other direction is worse socially and, at a good hotel, not actually cheaper. Running short of a live counter at 10 pm at a sangeet is the thing families remember for a decade. And emergency covers added on the day are billed at a premium, if the kitchen can produce them at all. A banquet kitchen provisioned for 400 cannot become a kitchen for 550 because 150 people arrived unannounced.

Rooms. Room blocks are the sharpest edge. Hotels release unclaimed rooms back to inventory at a cutoff date, usually 21 to 30 days out, and after that you are buying at rack rate in a wedding season city, if anything is left at all. Hold too many rooms and you may be liable for attrition on the unsold ones. Both errors are contractual, not just awkward. We cover the mechanics in wedding hotel room blocks in India.

The headcount is therefore not an administrative chore. It is the single input that drives catering, rooms, transport, seating, welcome hampers and staffing. Get it wrong by 15 percent and every downstream number is wrong by 15 percent. If you want to see how sharply spend scales with the number, our wedding cost by guest count guide sets the maths out plainly.

Three stages, three different jobs

The mistake almost every family makes is trying to do everything with one beautiful card. The card cannot do it. Split the sequence into three documents that each do one job.

Stage one: the save the date

This is a travel planning signal, not an invitation, and it asks for no reply. Its entire purpose is to get a date and a city into the heads of people who will need to book leave, flights or school holidays. It goes to the inner circle and to anyone travelling: family, close friends, all outstation and overseas guests. It does not go to the full 800 person list, because for the local uncle who lives 4 km away a save the date is meaningless noise.

Format is unimportant. A well designed digital card sent on WhatsApp does the job as well as anything printed, and printing save the dates for 200 households is money better spent on the actual invitation.

Stage two: the formal invitation

This is the social document. It is the object that carries respect, that gets touched, that gets kept, that goes to the family deity and to the elders first. It carries names, gotra or family lineage where relevant, the function schedule and the venue. It is not, and should never be, your data capture instrument. For wording conventions across Hindu, Muslim, Christian and South Indian formats, see Indian wedding invitation wording, and for what printing and delivery actually costs, wedding invitation cost in India.

Stage three: the RSVP or logistics form

This is the operational document, and it is the one people forget to design. It is plain, digital, short, and it asks the boring questions: who is coming, to which functions, arriving when, needing what. It rides alongside the invitation as a link or a QR code, and it exists purely to feed spreadsheets.

The insight worth taking away from this whole article is that stage two and stage three must be separate artefacts. A beautiful physical card is a terrible data collection instrument. Nobody fills in a form on embossed board and posts it back in India. Put the ceremony in the card and the data in the link, and stop asking either one to do the other one’s work.

How far out each stage goes

Timing changes with how much travel you are asking guests to do. Three profiles cover almost every wedding.

Local wedding, guests in the same city. Save the dates are optional beyond the immediate family. Invitations go out 4 to 6 weeks ahead, hand delivered to elders where custom requires it. RSVP chase starts at 3 weeks and finishes at 10 days.

Destination wedding within India. Save the dates go 6 to 8 months out, because guests are booking flights into Udaipur, Jaipur or Goa in peak season and prices move fast. Invitations follow 8 to 10 weeks out. The RSVP hard close needs to land before the hotel room block cutoff, which is the real deadline, not a date you chose.

NRI wedding with guests flying from abroad. Save the dates go 9 to 12 months out. Overseas guests are managing annual leave, school terms, long haul fares and in some cases visas for accompanying relatives. Invitations go 10 to 12 weeks out and the RSVP close sits at 8 weeks so that visa support letters and room allocations can be issued in time. Our NRI wedding planning timeline maps the full sequence, and wedding booking lead time in India explains why venue and vendor dates lock long before any of this.

One rule cuts across all three: never send a save the date before the venue contract is signed and the date is astrologically and practically fixed. A retracted date costs you far more credibility than a late save the date ever will.

The communication sequence at a glance

Treat the dates in that table as indicative. Your hotel and caterer contracts will each name their own cutoffs, and those contractual dates override anything a planner or a blog suggests. Read them before you design your RSVP calendar, not after.

A WhatsApp-first RSVP that actually works in India

Any RSVP system that requires a guest to create an account, download an app or reply to an email will fail. Design for the lowest friction channel in the country, which is WhatsApp, and treat everything else as a fallback.

The pattern that works: a family member sends the digital invitation on WhatsApp with one line of instruction and one link. The link opens a short form that works on a phone browser, takes under 90 seconds, and does not ask for a login. If you have built a wedding microsite, the form lives there alongside the schedule, the venue map and the dress notes. If you have not, a plain form is completely adequate and costs nothing.

Two operational details matter more than the tool you choose. First, the message must come from a person the guest recognises, not from an unknown number set up for the wedding. A form link from an unfamiliar number reads as spam and gets ignored. Second, one form per household, not per person, with a field for the number in the party. Indian guests travel as families and will not fill six separate forms.

The fields worth collecting

• Attending yes or no, at household level.
• Which functions, listed by name and date with checkboxes. Plenty of guests come for the wedding and skip the sangeet, or the reverse.
• Number in the party, split adults and children, because children affect catering, seating and room type.
• Arrival and departure dates, which is what actually drives room nights.
• Travel mode and, if flying or on a train, the flight or train number and time. This one field is the difference between an organised airport desk and chaos.
• Room needed yes or no, and whether they are happy to share.
• Dietary needs: vegetarian, Jain, no onion or garlic, allergies. Ask this explicitly rather than assuming a default.
• Elderly or accessibility needs: ground floor room, wheelchair, a short walk from parking to the mandap, medical conditions worth the hospitality desk knowing about.
• Name as it should appear on the welcome card and place card, which quietly saves a lot of spelling grief later.

Resist adding more. Every extra field costs you completion rate. Song requests and shoe size can wait. The master sheet that all of this feeds is the same one described in our Indian wedding guest list guide, and it should be the single source of truth for every vendor.

The chase: assume most people will not reply first time

Set expectations honestly. For an Indian wedding, a first pass response rate of 40 to 60 percent within two weeks of the form going out is a normal outcome. Close family and younger guests respond quickly. Older relatives, family friends of the parents and professional contacts largely do not, and no amount of reminder design changes that.

So the chase is not a failure of the system. The chase is the system. Budget for it and staff it.

The rule that makes the chase work is simple: assign each non-responder to the person who invited them. The bride’s mother chases her side. The groom’s father chases his colleagues. A cousin chases the friend group. A guest who ignores a reminder from an unknown wedding coordinator will answer a phone call from the person whose relationship the invitation represents, because in that call the question is not administrative, it is personal. Do not centralise the chase in the planner’s team. Centralise the recording of it.

Practically, split the guest list into ownership blocks of 30 to 50 households, name an owner for each block, and give every owner a shared sheet with three columns to fill: coming yes or no, how many, arriving when. Set a single deadline for all owners, then hold one 30 minute call where every owner reads out their block. That call, usually four to five weeks before the wedding, is where the real number appears. It is unglamorous and it is the most valuable meeting in the entire planning cycle.

A few chase tactics that earn their keep: give a reason for the deadline rather than the deadline alone, because we have to release hotel rooms on the 12th gets a reply and please RSVP by the 12th does not. Offer to fill the form on the guest’s behalf during the call. And never chase an elder by text message twice; phone them once instead.

Turning RSVPs into numbers a caterer can use

A yes on a form is not a person in a chair. Convert intent into expected attendance by applying a haircut based on guest type, then give the caterer two numbers rather than one.

Indicative attendance rates, based on how these lists typically behave and offered as a planning starting point rather than a promise:

• Immediate family and wedding party: effectively 100 percent. Plan them at full count.
• Confirmed outstation guests who have booked flights or trains: 90 to 95 percent. Sunk travel cost makes people turn up.
• Overseas guests who have confirmed: 85 to 95 percent, with the risk sitting in visas and long haul disruption rather than in changes of mind.
• Local guests who said yes: 75 to 85 percent for the main wedding, and noticeably lower for a weekday morning muhurtham or a mehendi.
• Local guests who never replied: 30 to 50 percent will still come. This is the group that ruins headcounts, and it is why you cannot simply treat silence as a no.
• Professional and community invitees: 20 to 40 percent, heavily dependent on how close the relationship really is.

Attendance also varies sharply by function. Expect the reception and the sangeet to draw the largest crowds, the wedding ceremony itself to draw fewer than the reception in many North Indian families, and daytime functions such as haldi and mehendi to be family plus close friends only. Never apply a single blanket number across a four function weekend.

The guaranteed number versus the prepared-for number

Catering contracts in India generally bill on a guaranteed minimum: you name a number, and you pay for at least that many covers whether they eat or not. Set the guaranteed number at your realistic expected attendance, not at your optimistic one. Then agree separately with the caterer on a prepared-for number, typically 8 to 12 percent above the guarantee, that the kitchen provisions for but that you only pay for if consumed.

Get that arrangement in writing, including the rate at which additional covers are billed and how late they can be added. A caterer who will not put an overage clause in the contract is telling you something about how the day will go. The same logic applies to seating, where a floor plan built to the guaranteed number with a defined overflow zone beats one built to the optimistic number. Our wedding day timeline guide covers how these counts land against each function hour by hour.

Save the date content and etiquette, kept short

A save the date needs five things and nothing more: both names, the date or date range, the city, a line saying a formal invitation follows, and if the wedding is a multi day destination event, the arrival and departure days so guests book the right flights. That last item is the one families omit and the one guests most need.

Three etiquette rules are worth holding to. Anyone who receives a save the date must receive an invitation, with no exceptions, so send them only to people you are certain about. Do not name the venue if the contract is not signed, because save the dates get forwarded and a changed venue looks careless. And send them in one batch on one day, because a guest who hears about the wedding from a cousin before hearing from you has been told something about their place in the family.

On wording, tone and the question of whether to send a printed card at all, hand off to wedding invitation wording. For print, courier and hand delivery costs, see wedding invitation cost. Neither belongs in the RSVP conversation, and keeping them separate is exactly the discipline this article is arguing for.

The awkward cases every Indian wedding produces

The non-committal guest

The reply is we will try, which in Indian usage means anything from a firm yes to a polite no. Do not argue with it and do not push for certainty. Instead, ask a logistics question that has a factual answer: will you need a room on the Friday night. A guest who does not know if they are coming still knows whether they want a room held. If the answer is yes, treat them as a soft yes and hold the room to the block cutoff. If they will not answer that either, count them at 40 percent for catering and hold no room.

The last minute plus-one

Common, and usually a visiting relative or a son in law who was not on the list. Decide the family policy early and apply it consistently: either plus-ones are accommodated as a matter of course, in which case build 5 percent headroom into every function, or they are not, in which case somebody senior must be willing to say so. What breaks weddings is an unstated policy applied inconsistently, where one cousin’s guest is accommodated and another’s is turned away at the desk.

The guest who arrives having never replied

They will happen, and the correct response is to have a plan rather than a grievance. Keep a small buffer of two to four unallocated rooms until 48 hours out on a destination wedding, keep an overflow seating zone that can be set in ten minutes, and brief the hospitality desk to greet an unlisted guest warmly and take their details rather than looking for their name on a sheet and failing to find it. The one thing you must never do is make a guest feel like an accounting error at your own wedding.

The guest who confirms and does not come

Almost always illness, work or a family emergency, and almost always not worth pursuing. Note it, absorb it into the haircut, and move on. If you are running a destination wedding, this is one more reason to keep the guaranteed catering number honest rather than aspirational.

For guests travelling in for a multi day event, most of these questions are answered in advance by a well written guest information note. See the destination wedding guest guide for what that note should contain.

What good looks like, in one paragraph

A wedding with a working headcount looks like this. Nine months out, 180 households got a save the date on WhatsApp and knew the city and the dates. Five months out, six family members made phone calls and produced a rough number that sized the room block before it was contracted. Ten weeks out, the printed invitation went out with a QR code on the accompanying digital card, and a two minute form collected functions, party size, flight numbers and dietary needs. Four weeks out, one call with six list owners resolved every non-responder into a yes, a no or a 40 percent. Three weeks out, the hotel got a rooming list and the unused rooms went back without penalty. Five days out, the caterer got a guaranteed number and a prepared-for number, both defensible. On the day, the airport desk had flight numbers, the hospitality team had names, and nobody was counted twice. None of that required expensive software. It required separating the ceremony from the data, and accepting from the start that in India the phone call is the RSVP.

Frequently Asked Questions

How far in advance should we send save the dates for an Indian wedding?

Six to eight months for a destination wedding within India, nine to twelve months if a meaningful number of guests are flying from abroad, and three to four months for a local wedding where only a handful of people travel. Never send one before the venue contract is signed and the date is fixed, because a retracted date does more damage than a late notice.

What response rate should we realistically expect from an RSVP form in India?

Plan for 40 to 60 percent of households replying within two weeks without being chased. Close family and younger guests reply fast; parents’ friends and professional contacts largely do not. The remaining 40 to 60 percent are converted by phone calls made by the person who invited them, not by additional reminder messages.

Should the RSVP go on the printed invitation card?

No. Keep the card ceremonial and put the data collection in a separate digital form linked from the accompanying WhatsApp message or a QR code. Reply cards posted back are effectively a dead convention in India, and a beautiful card is a poor instrument for collecting flight numbers, dietary needs and room requirements.

How many guests who never replied will still turn up?

For local guests, typically 30 to 50 percent of silent invitees still attend the main functions, which is why silence cannot be treated as a no. Outstation and overseas guests behave differently: if they have not replied and not booked travel, they are usually genuinely not coming. Apply the haircut by guest type, not across the whole list.

What number do we actually give the caterer?

Two numbers. A guaranteed count that you will pay for regardless, set at realistic expected attendance after haircuts, and a prepared-for count roughly 8 to 12 percent higher that the kitchen provisions for and you pay for only if consumed. Get the overage rate and the latest add-on time written into the contract.

How do we handle elderly relatives who will never use an online form?

Do not try to convert them. Assign each one to the family member who invited them, have that person phone and ask the questions directly, and enter the answers into the master sheet on their behalf. The data matters; the channel does not. A form is a convenience for guests who like forms, and the phone call is the fallback that always works.

Sources and further reading

• RSVP, Wikipedia
• Wedding invitation, Wikipedia
• Weddings in India, Wikipedia
• India Post, official website