A single Indian wedding is rarely a single event. Most families plan four to six distinct gatherings — mehndi, sangeet, haldi, the ceremony itself, a reception, and sometimes a post-reception lunch — and each of those events has its own guest list, its own venue, its own dress code, and its own running order. The math compounds fast. By the time you have five events and three hundred guests, you are managing roughly fifteen hundred guest-event combinations, and a spreadsheet stops being kind.

Over the last two years we have watched several hundred families plan multi- event weddings on Tanvrit. The same patterns show up over and over. Here are five lessons that, if applied early, would have saved every one of them at least a week of avoidable stress.

1. Pick the events before you pick the venues

It sounds obvious. It is not. The most expensive planning mistake we see is families who book a beautiful banquet hall for the reception in January and then, in March, decide they also want a mehndi at the same venue — only to discover the venue is double-booked on that date. The fix is unglamorous: write down every event you want to host, in order, with a target date and a rough guest count, before you talk to a single vendor.

We recommend the simplest possible artefact for this — a table with five columns: event name, target date, expected start time, expected duration, and guest-count tier (intimate, mid, full). That table fits on an index card. It also fits, more usefully, into the events page of any planning tool. Once it exists, every later decision (venue, catering, decor, photography) has something to align to.

2. Treat the guest list as one list, not five

Every multi-event wedding we have studied started with five separate spreadsheets — one per event — and ended with five spreadsheets full of inconsistent names, duplicate phone numbers, and conflicting RSVP states. The mehndi tab says Aunt Sunita is coming. The reception tab says she cancelled. The sangeet tab does not list her at all. Nobody knows which is current.

The way out is to model your guest list as one list of people, each tagged with the events they are invited to. When somebody RSVPs no to the haldi, that update lives next to their other event statuses. When somebody changes their phone number, you change it in one place. This single decision saves dozens of phone calls in the final week.

3. Build the budget around payments, not estimates

The other planning artefact families bring us is the budget spreadsheet, and it almost always has the same flaw: it lists what they expect to spend, not what they have actually paid. By the time the wedding arrives, the "estimated" number and the "actual" number are wildly different and there is no audit trail.

The version that works is a payments ledger: every advance, every milestone, every final settlement, with a date and a payee. The budget category is a derived view on top — sum the payments by category, compare against the cap, flag anything over. The numbers are always current because the source of truth is the payment record, not a memory or an intent.

4. RSVP cut-offs are a kindness, not a rudeness

Indian wedding culture treats the RSVP date as soft. Guests are accustomed to deciding the morning of, sometimes literally on the way to the venue. This is a kindness to guests and a cruelty to caterers, decorators, and seating planners. The compromise we have seen work best: publish a firm RSVP date seven days before the event, with a clearly stated reason ("our caterer needs the final headcount by..."). Two days before the event, send a soft "still coming?" nudge to anyone who has not replied — automatically, in the background, by message rather than phone call.

Families that do this consistently report a 70 to 80 percent final RSVP accuracy by the day of the event. Families that do not report 40 to 50 percent — which is to say, half of their seating chart is fiction.

5. Print the seating chart on paper at the last possible moment

The seating chart is the artefact most likely to change in the final 24 hours. Plus-ones arrive unannounced; an uncle catches an earlier flight; a family group reshuffles after a quiet argument. Print it too early and you will be hand-scribbling corrections at the venue while the bride is doing her hair.

The principle we now teach is: keep the seating chart digital until the morning of the event, then print exactly two copies — one for the registration desk and one for the head waiter. Anything more elaborate (engraved name cards, calligraphed table signs) belongs to the day-after-tomorrow version of the wedding industry, not the planning reality of today.

What we got wrong

None of these lessons are clever. They are obvious in hindsight. We list them because every single family we have worked with has independently rediscovered them, the hard way, in the final ten days before the wedding. A planning tool cannot save you from making wedding decisions, but it can save you from making the same five operational mistakes that everyone else has already made.

If you take only one thing from this post: the guest list is one list, the budget is a ledger of payments, and the RSVP cut-off is a feature, not a fence. Everything else is decoration.