How to plan an Indian wedding without losing the plot
Most Indian weddings are not one day. They are a short season: a Roka or engagement if you are having one, then Mehndi, Haldi, Sangeet, the ceremony, the reception, and the quieter hours around them. The work is not “pick a venue and a lehenga.” It is keeping a moving guest list, a stack of vendors, a family with opinions, and a budget that wants to expand, all pointing at the same weekend.
This is an order of operations, not a mood board. It is written for couples and the family members actually running the wedding — and it still holds if a planner is in the mix. A planner does not remove the need for one visible plan. They make that plan more valuable.
Start with the weekend, not the colour palette
Before you book a florist or argue about invitation paper, write down the events that are actually happening. Name them the way your family names them. A Sangeet is not a “cocktail evening.” A Haldi is not a “pre-function.” If an event is undecided, keep it on the list as undecided. A blank is more honest than a fake date.
For each event, only five facts matter on day one:
- The name of the event, in your words
- The city — and whether guests are travelling
- A date, even if it is still a window
- A rough guest count, not a final list
- Who is hosting it, because hosting decides who pays and who decides
Everything else — outfits, playlists, centrepieces — can wait until those five facts stop moving. Indian weddings go sideways when decoration decisions are made while the guest count is still a rumour.
Write the guest list before you book the bigger rooms
Catering, transport, and hall size are all guest-count problems wearing nicer clothes. Start the list earlier than it feels polite. You do not need every phone number on week one. You need households, side (bride, groom, or both), and a first-pass “invited to which events.”
A useful first list is grouped by family, not entered as 400 disconnected rows. Kapoor family, Mehta family, college friends, office, neighbours. Groups are how Indian guest lists are actually maintained, and they are how RSVP follow-ups get sent without writing 400 messages.
Expect the list to change. Uncles will add names. A cousin will marry in between. Someone will ask for a plus-one you had not planned for. The point of writing it down early is not to freeze it. It is to see the change instead of discovering it the week the caterer asks for a final number.
Put a number on the wedding before vendors do
If you do not name a budget, the first three vendor quotes will name it for you. You do not need a perfect spreadsheet. You need a ceiling, a split of who is contributing, and a first allocation across the things that actually consume the money:
- Venue and catering — usually the largest line, and the one most sensitive to guest count
- Outfits and jewellery — often paid across months, easy to lose track of
- Photography and video — easy to under-brief and overpay
- Décor and production — the line that expands to fill leftover optimism
- Travel and stay, if this is a destination weekend
- Invites, favours, and the small things that feel cheap until they are not
Write what is already promised: deposits paid, halls blocked, outfits ordered. A budget that ignores committed money is a wish. Keep vendor costs and family contributions permissioned — not every aunt who is helping with RSVPs needs to see what the photographer costs.
Book the few vendors that lock the date
Not every vendor is equal in time. The ones that hold the calendar should be first: venue, pandit or officiant, photographer, and the mehndi artist if your date sits in peak season. Catering follows guest count; décor follows venue. Outfits can run in parallel because they do not usually block the weekend for anyone else.
For each booking, keep four facts in the same place as the rest of the plan: the vendor name, the events they are covering, the amount agreed, and what is still owed. A WhatsApp chat is not a vendor record. It disappears the week you need to know whether the balance was paid.
Give every event an owner, not a group chat
A wedding WhatsApp group is a good announcement channel and a bad project manager. When a task belongs to “the family,” it belongs to no one. For each event, name one person who is allowed to say yes — on the menu, on the cue sheet, on the guest overflow. Other people can advise. One person decides.
The same rule applies to the couple. If both of you are the owner of everything, you will re-litigate the Sangeet playlist fourteen times. Split the weekend into lanes. One of you can own guests and RSVP. The other can own vendors and dues. A parent can own travel for outstation family. Write the lanes down so they survive the next argument.
Keep one place the plan actually lives
The failure mode is not a lack of tools. It is six tools. The guest list in a spreadsheet, the budget in another, vendor quotes in email, the itinerary in a PDF, RSVP notes in WhatsApp, and the “final” version in someone’s notes app. Each copy drifts. On the Thursday before the Mehndi, nobody is sure which one is true.
Pick one living plan and treat everything else as an export. The living plan has to hold, at minimum: the events, the guests, RSVP by event, the vendors, what is owed, and the next actions for this week. If a tool cannot show “what needs you now,” it is an archive, not a plan.
A calm order of operations
Timelines flex with how far away the wedding is, and with whether you are in peak season. The sequence below is more reliable than a rigid month-by-month copied from a magazine. Move faster on venues and photographers in November–February in north India; you can move slower on décor almost anywhere.
- Lock the events and cities. Undecided is allowed; unnamed is not.
- Draft the guest list by family group, with a first-pass event invite.
- Name a budget ceiling and who is contributing.
- Hold the venue and the photographer. Get the deposits on paper.
- Share a short family update: dates, cities, and what is already decided. Do this before relatives start booking their own flights against a rumour.
- Send save-the-dates to outstation guests. Do not wait for invitation design.
- Build the rest of the vendor stack against the guest count you actually have.
- Stand up RSVP, one event at a time. Follow up by group, not by heroic one-off messages.
- In the final fortnight, switch from planning to a run sheet: who arrives when, what is owed, what is still open.
What to ignore until later
A lot of wedding content is designed to make you feel behind. You are not behind if the napkin fold is undecided. You are behind if the guest count, the venue, or the photographer is still a vibe. These can wait: favours, most décor minutiae, the last outfit change, the perfect invitation reel, and any tool that wants you to “design your wedding aesthetic” before you can name the Sangeet host.
Where Phere fits
Phere is a wedding workspace for this exact mess: events, guests, RSVP, budget, vendors, and the next actions, in one place that families and planners can share on purpose. It is not a vendor marketplace, and it will not pretend a colour palette is a plan.
If you want the weekend visible — and the next step obvious — start a wedding in Phere and put the real list in, not a demo one. The writing on this site will keep being about the work of the wedding, not about collecting pages for their own sake.
Put the wedding in one place
Start free. Bring the events, the guest list, and the vendor dues onto one plan when you are ready.
Start free