How to Manage RSVPs for Nikah, Mehndi and Walima

Create an event map before sending invitations

List each celebration with its date, venue, intended audience and supplier cutoff. Include small family gatherings if they need a meal or room count. A guest may be invited to the Walima but not the Mehndi, or may attend only one of the events they were invited to.

The following fictional example shows a planning structure, not a prescribed wedding schedule. Choose your own names and arrangements. Keep arrival and start times separate where the venue needs guests to arrive early.

Keep invited and confirmed columns separate

Start with the invitation list, then record replies against it. Do not build the list solely from whoever has submitted a form. You need to know who has not replied as well as who declined.

Record named people when different members of a household have different plans. A response saying 'four of us are coming' needs clarification if two attend the Nikah and all four attend the Walima. The fictional matrix below keeps those cases visible.

• Use 'not invited' separately from 'declined'.
• Use 'pending' separately from 'not attending'.
• Record children according to the actual supplier's headcount rules.
• Keep a date beside the latest confirmed change.
• Assign one person to maintain the final list.

Choose a shared invitation or separate links deliberately

A shared page is convenient when the same people may see all the events and choose which to attend. It can hold the schedule and a clear set of attendance choices. It is less suitable when some guests must not see an event's details or should not be offered that event at all.

SaidVows supports configurable event choices in the shared RSVP form on the applicable plan. All guests who can access a shared invitation see its published details and choices. It does not automatically hide a Mehndi section or a Walima option according to a person's identity, gender or family group.

If audiences differ, create separate invitation links where appropriate or send the private arrangements directly. Premium permits two published invitations at a time; Luxury permits five. A Luxury password controls access to a whole invitation, not individual sections. A recipient can still forward a link or password, so use practical care with private information.

Set up event questions with clear answer choices

Make every event choice include a date or a recognisable label. 'Ceremony' and 'reception' can be ambiguous when there are several functions. If the RSVP field offers a single choice, include combinations such as 'Nikah and Walima' only where that fits your guest list. For more complex combinations, use separate custom questions or separate invitations.

In SaidVows, Premium and Luxury offer custom text and dropdown questions. You could ask one clear question for an offered shuttle and another for attendance at an additional celebration. The form records the choices; check the replies before treating them as per-event supplier totals.

Use the same event labels across languages and households

A translated invitation must preserve the event distinctions. Do not translate one version as 'wedding' and another as 'reception' if you mean the same Nikah ceremony. Put dates, venue names and map links beside each event so guests can recognise the right one.

SaidVows translates standard controls in supported languages on Premium and Luxury, while custom questions and descriptions stay as entered. Write bilingual custom labels when needed and ask a reader from each language group to test them. The label 'both' needs the same two events in every language.

When a relative replies by phone or WhatsApp, record the response in the same list. Read the event choices back to them, including the names of attending household members. Do not count the chat message as a separate RSVP if they later complete the form.

Reconcile three separate counts before the supplier cutoff

For each event, check people, meals and transport separately. A child may occupy a seat but have a different meal arrangement; a guest may attend without using the shuttle. Confirm the caterer's and venue's definitions before giving them a total.

Use the top-level dashboard as a starting point, then review event answers. A single attending count across the whole wedding should not become the Walima meal order unless you have checked that those people are attending the Walima. If a reply includes an additional guest, verify their event choices too.

• Filter or review confirmed attendees for the specific event.
• Check adults, children and additional guests against the invitation list.
• Resolve 'maybe' and ambiguous household replies directly.
• Confirm meal requests and access arrangements with the relevant guest.
• Count transport seats only for guests using that journey.
• Share the final necessary columns with the supplier, not private guest notes.
• Keep a short change log after the final numbers are sent.

Handle late changes through one organiser

Choose one contact for the final week so a guest does not update three relatives with different information. Record the time of the change and the events it affects. A guest cancelling the Mehndi has not necessarily cancelled the Walima.

Send a short confirmation back to the guest: 'Thank you; we have changed your Walima reply to two adults and one child.' Then tell only the suppliers whose arrangements changed. A careful manual reconciliation is more reliable than assuming every event total updates into every supplier's workflow automatically.

If the reply deadline has passed, explain how to contact you. SaidVows closes online replies at the end of the selected deadline date in UTC. Guests across time zones may need that clarification, and late changes may need an organiser update rather than a fresh form submission.