Guide 06 · Multi-Function Planning

Multi-Function Weddings: Sangeet, Mehndi and Reception Without Losing Your Mind

The Short Answer

Most multi-day weddings run four core functions — mehndi, sangeet, the wedding day and the reception. A sensible budget split is roughly 20% mehndi, 25% sangeet, 40% wedding day, 15% reception — concentrating spend where it matters instead of spreading it evenly. The real risk isn't the number of functions; it's identical décor, a repeated menu, and guests who are visibly tired by function three.

What Counts as "A Function"

Four events form the backbone of most modern multi-day weddings: mehndi (henna, typically an intimate daytime gathering), sangeet (music and dance, usually the biggest party-energy night), the wedding day itself (haldi, baraat, the ceremony), and the reception (the widest guest list, most formal). Many families add haldi as its own separate function rather than folding it into wedding-day morning. Not every family runs every event, and the order shifts by region and preference — this is the common baseline, not a rulebook.

How Many Days, and In What Order

A common structure spans three to four days: mehndi and sangeet combined into day one, haldi the following morning, the wedding ceremony that same day or the next, and the reception following the wedding day or the evening after. Larger or more traditional families sometimes extend to five or seven days with additional rituals. The order is genuinely flexible — some families merge mehndi and sangeet into a single evening entirely, and Sikh ceremonies often shift the morning schedule.

Splitting the Budget Across Functions

The instinct to split a budget evenly across four functions is understandable and usually wrong. A more sensible allocation concentrates spend on the events that carry the most weight — namely the wedding day itself and the sangeet, where production and guest experience matter most:

Budget split across wedding functions Mehndi 20%, sangeet 25%, wedding day 40%, reception 15%. Mehndi 20% Sangeet 25% Wedding Day 40% Reception 15%

A concentrated split, not an even one — the wedding day carries the largest share by design

This is a starting allocation, not a formula — a family that treats sangeet as the true centerpiece will reasonably shift more toward it. What matters is deciding the weighting deliberately, before booking anything, rather than discovering it by accident once the mehndi has quietly eaten a third of the total.

The Guest List Isn't One List

Concentrated spending on fewer, bigger functions is only affordable if the guest list is differentiated too. Mehndi is typically intimate — close family and friends, sometimes as few as 50 — while the reception is usually the widest list, often 300–400. Inviting your full reception list to every single function multiplies your catering and seating costs across all four events instead of one, which is the single fastest way to blow a carefully split budget.

Avoiding Function Fatigue

The real failure mode in a multi-function wedding isn't running out of budget — it's running out of distinctiveness. Three warning signs to watch for:

  • Repeated décor. The same floral palette and backdrop across mehndi, sangeet and reception reads as one long event rather than three, even to guests attending all of them.
  • Repeated menus. Catering fatigue is real for a vendor team running multiple functions in close succession — confirm menu variation explicitly rather than assuming it.
  • No rest window. Back-to-back functions with zero gap exhaust guests and hosts alike. Even a half-day buffer measurably changes how present people feel at the next event.

Vendor Logistics Across Back-to-Back Functions

If mehndi and sangeet run on the same day, or the wedding day flows straight into the reception, décor teardown-and-rebuild time between them needs to be scoped explicitly with the vendor — not assumed. Ask directly how many hours a full turnover takes, and whether that window actually fits your schedule. This is the same category of question covered in more depth in Guide 04 and the venue-questions checklist.

A Sample Three-Day Structure

DayFunctionTypical Guest Count
Day 1, eveningMehndi + Sangeet~50–150
Day 2, morningHaldi~50–100
Day 2, evening / Day 3Wedding Ceremony~300–400
Day 3, eveningReception~300–400

Figures in this guide are compiled from published Indian wedding-planning and multi-day event budgeting guides, rounded for clarity. Family and regional traditions vary meaningfully — treat this as a starting structure to adapt, not a fixed template.

FAQs

Quick Answers

How many functions does a typical Indian wedding have?
Most modern multi-day weddings run four core functions — mehndi, sangeet, the wedding ceremony and the reception — often with haldi as a fifth. Larger or more traditional families sometimes extend to five or seven days with additional rituals, but four is the common baseline.
How should I split my budget across functions?
A commonly used split allocates roughly 20% to mehndi, 25% to sangeet, 40% to the wedding day itself, and 15% to the reception — concentrating spend on the day that matters most rather than dividing it evenly across every function.
Should every function have the same guest list?
No, and treating it as one list is a common budgeting mistake. Mehndi is typically intimate — close family and friends, sometimes as few as 50 — while the reception is usually the widest guest list, often 300–400. Differentiating the list by function is what makes concentrated spending on fewer, bigger events actually affordable.
What's the biggest risk with a multi-function wedding?
Not the number of functions itself, but functions that blur into each other — identical décor, a repeated catering menu, and guests who are visibly tired by the third event. Deliberate variation in look, food and pacing is what keeps a multi-day wedding feeling like several distinct celebrations rather than one long one.
How much time should there be between functions?
Mehndi and sangeet are often combined into a single evening; haldi typically sits one to two days before the wedding, in the morning; the reception usually follows the wedding day or sits the evening after. Back-to-back functions with no gap raise both vendor turnaround risk and guest fatigue — a built-in rest window, even half a day, measurably helps both.
Does each function need its own vendor team?
Not necessarily, but décor turnover time between back-to-back functions at the same venue needs to be scoped explicitly — a full teardown and rebuild between an afternoon mehndi and an evening sangeet is a tight window that should be confirmed with the vendor in advance, not assumed.

Planning Several Functions at Once?

Let's Map Out Every Function Together.

No pressure — a straight read on how your functions fit your budget and timeline.