Indian Wedding Operations

How to Manage Haldi, Mehendi, Sangeet & Wedding as One Project

This is how to manage multi-function Indian wedding work as one project: a single wedding record, with each function carrying its own venue, vendors, guests and tasks.

26 September 2026 · 1 min read

Why multi-function weddings need a different workflow

An Indian wedding may involve several functions, venues, guest groups and production requirements over multiple days. The planner needs both a master view and function-level detail.

One wedding project, multiple functions

Create one master project for the couple/client, overall dates and commercial scope. Under it, create functions such as Haldi, Mehendi, Sangeet, wedding and reception.

Give each function its own operational identity

Each function should have its own date, venue, timings, checklist, vendors, production requirements and guest attendance while remaining connected to the parent wedding.

Create reusable function checklists

A Sangeet checklist should not be identical to a Haldi checklist. Build reusable templates for common functions and customise them for each wedding.

Assign vendors by function

A decorator may handle several functions, while an entertainment vendor may be needed only for Sangeet. Record assignment, scope, timing and cost for each function.

Manage multiple venues

Some weddings move between hotels, banquet halls, homes, farms or outdoor venues. Keep venue-specific access timings, restrictions, contacts and logistics connected to the correct function.

Manage guests by function

A guest may attend the wedding but not the Mehendi. Function-wise RSVP is therefore essential for accurate catering and hospitality planning.

Accommodation and transport

Destination and outstation weddings add rooming, arrival/departure and transportation requirements. These should remain connected to the guest and wedding record.

Track production dependencies

Shared production inventory, transport, staff and setup crews can create cross-function dependencies. A master timeline should show these dependencies.

Track expenses at project and function level

The client may have one commercial agreement while expenses are incurred across many functions. Consistent categorisation allows management to see both the whole wedding and individual function economics.

Run a master wedding review

Regular reviews should cover client approvals, vendor confirmations, venue readiness, guest RSVP, production, transport, accommodation and finances.

How Lighter supports multi-function weddings

Lighter lets event businesses manage the wider wedding project while organising function-level tasks, vendors, venues, guests, RSVP and expenses within connected workflows.

Practical implementation checklist

Create one wedding project and add each function to it.
Give every function its own date, venue, timing and owner.
Build a reusable checklist per function type.
Assign vendors to the function, not to the wedding as a whole.
Track expenses at both project and function level from day one.

Frequently asked questions

Should each wedding function be a separate event?

Usually it is more useful to treat the wedding as one project with individual functions so shared client, guest and commercial information stays connected.

How do planners manage vendors across multiple functions?

Assign vendors to the relevant functions and record their timing, responsibility and cost for each assignment.

How should guest counts be calculated?

Use the master guest database plus function-level attendance so each function has its own operational number.

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 Wedding planner software