An Indian wedding checklist runs function by function rather than as one list. The usual sequence is roka, engagement, haldi, mehndi, sangeet, the wedding ceremony and the reception, each with its own date, venue, guest circle, dress code and catering count. Bookings follow roughly: venue and priest 10 to 12 months out, caterer and decorator 8 to 10 months, photographer and mehndi artist 6 to 8 months, invitations sent 6 to 8 weeks before the first function, and final counts to the caterer 5 to 7 days before each event. The part most couples underestimate is that each function needs its own RSVP: a cousin invited to everything and a colleague invited only to the reception are answering different questions, and one combined list cannot tell you how many plates the haldi needs.
Most wedding checklists assume one afternoon, one venue and one guest list. An Indian wedding is none of those things. It is a schedule of separate events spread over several days, each with its own guests, its own dress code, its own catering count and its own set of relatives who will ask you what time it starts. The planning problem is not really the tasks, which are the same tasks every family has worked through for generations. The problem is that the information lives in six different places: a spreadsheet for the guest list, a WhatsApp group for the schedule, a notebook for the caterer, and three people who each believe they have the current version. This checklist is organised the way the wedding actually runs, function by function, with the booking timeline attached to each one.
Fix the date and the two bookings everything else depends on
Nothing on this list can be scheduled until the muhurat is set and the main venue is held. Those two decisions fix every other date, and both are booked further ahead than couples expect: 10 to 12 months for a popular venue in season, and the priest as soon as the muhurat is chosen.
Once the ceremony date exists, work backwards. The sangeet usually sits the night before, the mehndi the day before that, and the haldi on the morning of the mehndi or the ceremony depending on family custom. Write the order down before you book anything else, because caterers and decorators will quote per function and you need to know how many functions there are.
If the two families are in different cities, agree at this point who hosts which function. It sounds obvious and it is the single most common source of a re-planned schedule three months later.
- Muhurat confirmed with the priest
- Main ceremony venue booked and deposit paid
- Order and rough dates of all functions written down in one place
- Which family hosts which function, agreed in writing
- Budget split agreed between families before any further deposits
The functions, and what each one actually needs
Every function is a small wedding with its own requirements. The table below is the working version: guest circle, what it needs booked, and the thing couples most often forget about it.
The booking timeline, month by month
This assumes a twelve month runway. If you have six, the order stays the same and the gaps compress, but the caterer and the venue still come first.
The guest list is the part that goes wrong
Several hundred names, two families building their halves separately, half the list travelling, and a spreadsheet that goes stale the day it is made. Every couple planning an Indian wedding meets this, and it is rarely solved by a better spreadsheet.
The fix is structural: keep one list, invite in circles rather than individually, and collect a separate yes or no per function. Then the counts you hand to each caterer are a consequence of the list rather than a second piece of work you do by hand at midnight.
Dietary counts need the same treatment. Vegetarian, Jain and halal are not a footnote on an Indian guest list, they are the catering brief, and they have to be countable per event rather than for the wedding as a whole.
- One guest list, not one per family
- Guest circles: who is invited to which functions
- A separate RSVP for each function, not one answer for the wedding
- Meal preference collected with the RSVP, countable per event
- Allergies collected with the meal, not chased later
- A record of who has not replied, so chasing is a list and not a memory
Where an Indian wedding website replaces six WhatsApp groups
The information problem and the guest list problem are the same problem. Guests call to ask the muhurat timing, the venue, the dress code for the haldi and whether their children are invited, because the answers are spread across a card, a forwarded image and three chats.
An Indian wedding website holds all of it behind one link: every function with its time, venue and map, the dress code per event, travel and accommodation for the guests flying in, and the RSVP that answers back into your list. When the plans change, the link stays the same and everyone sees the new version, which a forwarded video invitation can never do.
The Private Wedding App was built for exactly this shape of wedding: up to seven days of functions, guest circles who each see only their own events, per-function RSVP with meal choice and allergies, a seating plan per event, a budget with instalments, and a day sheet your caterer can actually use. Both families can have their own logins with control over what each person sees.
Everything you need, in one place
Planning your own wedding without a planner is entirely achievable.
See it for yourself.
Explore the whole platform: cinematic invitation, RSVP with meals and allergies, guest list, seating chart, budget, vendors, checklist, moodboard, photo sharing and the AI planner. No account needed.
Try the full planner →What is the correct order of Indian wedding functions?
The usual order is roka, engagement, haldi, mehndi, sangeet, the wedding ceremony and the reception. Families vary: the haldi sometimes falls on the morning of the ceremony rather than before the mehndi, and the sangeet and mehndi are often combined into one evening. Fix your own order before booking anything, because caterers and decorators quote per function.
How far in advance should we start planning an Indian wedding?
Ten to twelve months for a venue in season, because the venue and the priest fix every other date. Six months is workable if the venue is available, with the same order of bookings compressed. Below four months the constraint is usually the outfits and the mehndi artist rather than the venue.
How do we handle different guest lists for each function?
Invite in circles rather than individually. Decide which groups are invited to which functions, then let each guest answer separately for each event they are invited to. That way the haldi count, the sangeet count and the reception count are each correct, instead of one number that fits none of them.
When do caterers need the final count?
Five to seven days before each function, and they need it per function rather than for the wedding as a whole. Send the dietary breakdown at the same time: vegetarian, Jain, halal and any allergies, counted for that specific event.
Do we need an Indian wedding website as well as a card?
The card is the invitation, the website is where the answers live. Guests need the timings, venues, dress code per function, travel details and a way to reply. A printed or video card cannot update when plans change and cannot take an RSVP, which is why most couples end up fielding the same questions by phone for weeks.