How do you plan a multi-day wedding?

The unit of planning is the function, not the day

Almost every planning tool, template and checklist is built around one question: what happens on the wedding day. That question has no single answer here. A wedding that runs across a mehndi, a sangeet, a ceremony and a reception is four events with four sets of guests, four budgets, four sets of clothes and four schedules, some of them hosted by different people.

Once you plan per function rather than per wedding, most of the confusion resolves itself. The list below is what actually differs between functions, in the order it tends to cause trouble.

1. A different guest list for each function

This is the defining feature and the one that carries the most emotional weight. The gaps are not small. One bride described her own wedding in these terms:

“a majority of my family’s guests (I’m the bride) aren’t invited to my reception, but mostly all of my fiancés guests are. For us, only the brides close family are invited to the reception, unless it’s a massive event. Our wedding guest list is around 500-550 and the reception around 350-400.”

cursedauror — r/DesiWeddings, invited to the ceremony but not to the reception

That thread exists because a guest was hurt. The person who started it had been invited to the sangeet and the ceremony but not the reception, wrote that their family was upset because the couple “used to be a close family friend”, and was weighing up not going at all.

Couples on the other side of it get consistent advice, and it is not reassurance. On a thread from a couple planning exactly this split, one reply is blunt — “just understand that there will be blowback, and while you may not have an issue, it will fall on your parents” — and the most useful one names the fix:

“I recommend being transparent so you manage everyone’s expectations and no one is surprised to learn that they weren’t invited.”

octopusbride — r/DesiWeddings

The damage is done by the discovery, not by the decision. Splitting the list is normal. Letting someone find out sideways is what causes the injury.

2. Whoever pays for a function tends to decide who comes to it

The guest-list split is usually not arbitrary. It follows the money, and in a two-family wedding the money is often split by function rather than by percentage. The clearest statement of the mechanism came from a commenter on that same thread:

“I have heard traditionally the girls side pays for the wedding (boy and girl have individual sangeets) and the reception is from the guys side. Nowadays its usually 50 50 but in some cases where its not, I would assume the family paying dictates invite list.”

IsLifeCake — r/DesiWeddings

Writing in Stylist, a British Gujarati bride set out her own version and her discomfort with it: her parents were “paying for the entire cost of the wedding day (that’s the religious ceremony and a buffet dinner for 300 guests)”, insisting on it as “part of the well-known and longstanding tradition that the bride’s father pays for the wedding”. She quotes a friend who split her wedding bill equally between both sets of parents: “The girl’s side paying for the ceremony is something I can’t comprehend, regardless of the traditions.”

This is the same law our research into how weddings go wrong found everywhere: once someone pays for something, they want a say in it. In a multi-day wedding that plays out one function at a time, which at least makes it legible. Write down who is hosting each function before you write the lists.

3. Guests will not come to all of it

Plan attendance per function, because your guests already are. Commenters advising one couple on a five-day schedule were unanimous that the later events would thin out:

“No one is coming to your monday ceremony, except local people that are really close to your family. Sticking it on the back end like that makes it seems unimportant.”

Conscious_Mind_1235 — r/ABCDesis, thoughts on my wedding schedule

Another in the same thread doubted that friends would attend both the church wedding and the Indian ceremony, and described their own plan as arriving Friday night and leaving after the mehndi, for the ordinary reason that they had almost no annual leave left.

Guests also run out of stamina, and they feel bad about it. On a general thread about how many consecutive days are too many, the most-agreed answer describes tapping out on day three: “For us, the third day was too much. It was fine but we were exhausted. Yet we felt obligated to be there because my husband was a groomsman.” That particular thread is explicitly about weddings with no cultural component, so read it as evidence about multi-day weddings in general rather than about mehndi and sangeet specifically. The practical response is the one an Indian bride gave on the same thread: invite family and the wedding party to the first two days, everybody to the last, and treat declining individual events as fine.

4. The budget multiplies rather than stretches

The costs that repeat are the ones people miss, because a single-day budget has one line for each of them. The clearest statement we found came from someone talking a couple out of a five-day plan:

“You also have to pay per-day prices for photography and makeup too (if you want those). Per day DJ if you want that. If you just cut 2 meals (maybe just 1 meal, depending on pricing), you more than make up for the price difference.”

oddblueberries — r/ABCDesis

Note the lever in that last sentence. On a multi-day wedding the number of catered meals is the strongest single control you have, and it is easier to move than the guest list, because dropping a meal removes a cost without removing a person.

5. An outfit for every function

For the couple this is a set of purchases, not one. The British bride writing in Stylist counted hers plainly: four weeks out, she and her husband-to-be had “stocked up on clothes (seven brilliantly embellished Indian outfits each)”. Her phrase for the wedding itself, in the same sentence, is “the big day(s)”.

It reaches the guests too. A first-time guest asking what to budget for a three-day wedding was told that outfits add up quickly across the days, and given a tier that rises with closeness to the couple and with each successive event. Those figures were quoted in dollars by North American posters, so we have not reproduced them here as pounds, but the structure is the point: guests dress up progressively, and the main ceremony is treated as the most formal.

6. Why the templates do not fit

The generic wedding spreadsheet is built for one day, and people notice the moment they try to use one:

“There are some excellent spreadsheets available that are tailored to Western style weddings… But i do wish i could customize it more to fit the role of having 3-4 events, different guest lists for each event.”

r/DesiWeddings, a spreadsheet catered to desi weddings

A reply in the same thread describes the workaround people land on: not one sheet but a folder of them, “a whole plethora of sheets in a Google drive so we could give different people access to them as needed”.

One honest correction to a claim you will see elsewhere: it is not true that no software handles this. Several established wedding websites do manage multi-event invitations and RSVPs properly, and couples say so in the same threads. The problem is narrower and more specific — the free templates, printable checklists and month-by-month timelines that most people start with assume a single ceremony and a single reception, and there is no obvious point at which to add a fourth function.

What to do

The first four are drawn from the evidence above. The fifth is our own recommendation rather than a finding, and we would rather label it that way.

1. Write the functions down first, before any list. Name each one, and beside it name who is hosting it and who is paying for it. That single table settles most of the guest-list arguments before they start.
2. Build one guest list per function, not one list with columns. A person invited to the mehndi and the ceremony but not the reception is a different record in each place, and you need to be able to see each function’s list on its own.
3. Tell people what they are invited to, in writing, early. The hurt in every thread we read came from discovery, not from the decision itself.
4. Cost each function separately, and count the meals. Photography, makeup, music and catering repeat per day. Cutting one catered meal is usually the least painful saving available.
5. Give every function its own runsheet. One page per event: start and end time, who is setting up, who is the point of contact, which suppliers are on site, what has to be moved to the next venue. A single master timeline across four days becomes unreadable at exactly the moment somebody needs it.

That last one exists because the handover between days is where multi-day weddings actually fail. One couple posted the night before their events began that their planner and photographer still had the wrong information: “Now they are messing up dates and times with our vendors.” A runsheet per function will not fix a bad supplier, but it makes it obvious, in advance, which day is missing an answer.