Guest Management

How to Manage a Wedding Guest List Across Multiple Functions

Wedding guest list management across Haldi, Mehendi, Sangeet and reception needs one master record with attendance tracked per function, not four separate lists.

26 September 2026 · 1 min read

Why one total guest count is not enough

In a multi-function Indian wedding, the same guest may attend one function and skip another. Planners therefore need both a master guest list and function-level attendance.

Start with one master guest record

Capture name, phone number, family/group, bride/groom side and other core information once. Avoid creating separate disconnected records for every function.

Organise guests by side and group

Bride/groom side, family groups and household relationships can help planners coordinate communication and hospitality.

Track attendance by function

Create separate attendance status for Haldi, Mehendi, Sangeet, wedding, reception and other functions as required.

Track RSVP status

Use confirmed, declined and pending statuses. Keep the status associated with the relevant function.

Manage plus-ones

Define a consistent process for additional guests. Record the number or identity where operationally required so the planner does not double-count.

Add accommodation information

For destination weddings and outstation guests, track room requirements, arrival/departure information and other hospitality details where appropriate.

Connect guest information to catering and hospitality

Guest data should support actual decisions: meals, seating, rooms, transport, welcome desks and hospitality staffing.

Keep one current version

Guest lists change continuously. A central system prevents different departments from working from different copies.

Use WhatsApp for RSVP follow-up

WhatsApp can support communication, while the guest-management system provides the structured status behind the communication. Lighter connects these workflows.

Create a final function-wise guest report

Before each function, confirm expected attendance, special requirements, accommodation and other operational details. This becomes the team's working number for execution.

Practical implementation checklist

Create one master guest record and stop duplicating guests per function.
Record side and group so lists can be produced without sorting by hand.
Track attendance and RSVP status per function, not per wedding.
Count plus-ones as part of the headcount rather than as a note.
Produce the function-wise report from the same record catering is given.

Frequently asked questions

How should wedding guests be organised?

Use one master guest database with groups, side, function attendance and RSVP status rather than separate disconnected lists.

How do you track guests attending different functions?

Maintain function-level attendance against the same guest record.

What should a wedding guest list contain?

Names, contact information, groups, side, function attendance, RSVP status and relevant operational information such as plus-ones or accommodation.

See this on your own events

Bring one real event to a 30-minute demo and we will set it up live, using your own numbers.

Book a demo Guest management