Quick answer
Per-function RSVP means each guest answers separately for every function they are invited to (for example yes to the Sangeet and wedding, no to the Haldi), along with how many people are coming to each. It gives a real headcount per function, which is what caterers, venues and decorators actually quote against. A single yes/no RSVP gives one number that is wrong for every function.
Key takeaways
- Caterers quote per plate per function, so you need a headcount per function.
- Invite people only to the functions they are really invited to: event-wise invitation links do this.
- Remind only the people who haven't replied, and only about what they haven't answered.
- Reconcile RSVP numbers with day-of check-ins to calibrate your next wedding.
Why a single RSVP fails at Indian weddings
Western RSVP tools assume one event: are you coming, yes or no? An Indian wedding is often four to six events across two or three days, and attendance varies a lot between them. Close family comes to everything. Colleagues come to the reception. Friends of the couple come to the Sangeet and the wedding. Out-of-town relatives may arrive after the Haldi.
Ask all of them one yes/no question and you get one number. Use it for the Haldi and you over-order; use it for the reception and you under-order. Either mistake costs real money, and the second one is visible to every guest.
What per-function RSVP looks like
Each guest opens their invitation and sees a short list of the functions they are invited to. For each one they choose yes, no or maybe, and how many people from their party are coming. Optionally, they add a meal preference or a message for the couple. You then see, for every function: attending, maybe, declined and not yet replied, plus the total headcount.
| Function | Attending | Maybe | Not replied | Headcount |
|---|---|---|---|---|
| Haldi | 48 | 6 | 12 | 71 |
| Mehendi | 96 | 14 | 30 | 164 |
| Sangeet | 180 | 22 | 41 | 312 |
| Wedding | 240 | 18 | 35 | 436 |
| Reception | 210 | 30 | 60 | 395 |
Step 1: Define the functions properly
Before a single invitation goes out, list every function with its date, time, venue and dress code. Decide which functions need a reply at all. A small family puja may not; the Sangeet and reception almost certainly do. Only ask about the functions where the number changes what you order.
Step 2: Decide who is invited to what
This is where most of the errors come from. If the office group is invited only to the reception, they should never be asked about the Haldi. The clean way to do this is event-wise invitations: a separate invitation link per group, each showing only that group's functions. Office colleagues get a link with the reception; close family get a link with everything.
Step 3: Collect party size, not just a yes
"Yes" from Mr Sharma might mean one person or six. Always ask how many are coming to each function, and set a sensible maximum per invitation so a single reply cannot add twenty people. Headcount, not reply count, is the number that goes to the caterer.
Step 4: Chase only the silent guests
Most of the work in RSVP is chasing people who have not answered. Send reminders only to guests who have not replied, and only about the functions they have not answered. Reminding someone who already said yes is the fastest way to get your messages ignored. A reasonable rhythm is the invitation about six weeks out, a reminder around four weeks out, and a final reminder two weeks before the first function, adjusted for how fast replies come in.
On WhatsApp, use approved message templates and track delivery and reads, so you know whether a guest ignored you or never received the message. More on this in WhatsApp for wedding planners.
Step 5: Split by side and group
Families will ask "how many from our side are coming to the Sangeet?" Record each guest's side (bride's or groom's) and group (family, friends, office) as separate fields. Then every headcount can be broken down by side, which matters for seating, hospitality and, often, how costs are split between families.
Step 6: Turn RSVPs into orders
- At your final-numbers deadline, take the attending headcount per function.
- Decide how to treat "maybe" replies. Many planners count a portion of them; agree the rule with the couple in advance.
- Agree a guarantee number and a buffer with each caterer, in writing.
- Send each vendor the number for their function only, not the whole spreadsheet.
Step 7: Reconcile on the day
Check guests in at the welcome desk (a QR code on their invitation makes this fast) and compare arrivals with RSVPs for each function. Over a few weddings you will learn how your clients' guests actually behave, and your buffers will get tighter and cheaper.
How Baton handles it
Every wedding run on Baton includes Wedence Signature: per-function RSVP with party sizes, event-wise invitation links per group, WhatsApp invitations and automatic reminders to guests who have not replied, guest intelligence by side and group, and a QR arrival desk on the day. You see each wedding's response rate from the Baton portfolio, and the full per-function breakdown inside the wedding.
Baton brings your enquiries, client weddings, vendors, payments and team together, with per-function RSVP and WhatsApp invites for every couple. Free for 2 months.
Try Baton freeFrequently asked questions
Per-function RSVP lets each guest reply separately for every function of a wedding, such as the Haldi, Mehendi, Sangeet, wedding and reception, including how many people are coming to each. It produces an accurate headcount for every function instead of one total.