Writing · Guides

Collecting RSVPs for each wedding function separately

Ask for one answer per function rather than one answer for the wedding. A guest invited to the Sangeet, the ceremony and the reception may attend two of them, and a single yes hides that. Per-function responses give each caterer and each venue a number they can use.

A single yes or no covers a wedding with one ceremony. It falls apart the moment there are four functions across three days, because attendance is not all or nothing. A colleague comes to the reception. An aunt arrives Thursday and stays for everything. A university friend flies in on Saturday morning and misses the two events before it.

If your site asks one question, you learn that ninety people are coming to the wedding, and you still do not know how many chairs the Mehendi needs.

Ask once per function

Give every function its own question. The guest sees the functions they were invited to, and answers each one. What comes back is a number per function rather than a number for the week.

That is the figure a caterer needs. It is the figure the venue needs when it asks how many for Friday lunch. It is also the figure that tells you the Haldi is smaller than you planned and the reception is over capacity, while there is still time to move something.

Show each guest only their own functions

The guest list differs per function, so the RSVP form has to differ too. Someone invited to the reception alone should not be asked whether they are attending a Haldi. It reads as an invitation, and if they answer yes, you now have an awkward conversation ahead of you.

Tie the invitation to the guest rather than to the link. Each person opens the site, sees the functions that belong to them, and answers for those. Nobody has to work out which parts apply to them, and nobody discovers an event they were not asked to.

Let one person answer for a family

Most RSVPs arrive from households, not individuals. A father answers for four people, and two of them are only coming to the reception. Ask for the count per function alongside the yes or no, and you avoid the follow-up round of messages entirely.

Also ask for dietary needs and arrival dates at the same time. Every question you leave out becomes a phone call later, usually during the week you have the least time.

Expect answers to change

People change plans. Flights move, a child falls ill, a distant relative decides at the last minute to come after all.

Guests should be able to reopen their response and change it without asking you. If the only way to update an answer is to message the couple, you become the database, and the real numbers live in a chat thread nobody can total up.

Watch the numbers as they come in

Waiting until the deadline to count is what forces the frantic week. Watch responses per function as they arrive, and the gap between invited and answered tells you who to chase, function by function.

Chase the small list of non-responders for the function that needs a final number first. That is usually the one with the earliest catering deadline, not the one with the most guests.