A wedding in an Indian family is rarely one event. There might be a nichayathartham or engagement, a mehendi, a sangeet, the muhurtham itself, and a reception. They could be in three venues across two days, and half of your guests will attend only some of them. If all of that sits in one paragraph of text, people will message you to ask “wait, what time is the reception?” until the day.
The solution is structural, not decorative.
One event, one block
Each event gets the same small set of facts, in the same order:
- Name: Engagement, Muhurtham, Reception.
- Date and day: “Saturday, 14 February.”
- Start time: and an end time if people need to plan around it.
- Venue and city: the name guests will see on the signboard.
- A map link: one tap to directions.
- One note line: dress, parking, or who it is for.
Keep the format identical for every event. Once guests have read the first block, they can scan the rest in seconds.
Order by date, then time
List the events in the order they happen. Do not group by importance. If the reception is the biggest event but happens last, it still goes last.
Be specific about who is invited
This is the hardest part and the part most invitations leave vague. If the engagement is family only, say “By invitation, close family”. If the reception is for everyone, say so. It lets guests plan their leave and spares you awkward conversations.
Handle different venues honestly
If events are in different places, name them clearly and mention distances. “The reception is in the same city, about 25 minutes from the temple” is more useful than two addresses. For guests travelling in, add a line about where to stay near each venue if you have suggestions.
Dress and customs
One line per event is enough: “Traditional wear”, “Smart casual”, “Silk saree or veshti”. Do not write a paragraph. If customs matter, such as removing footwear at the temple, mention it in the event note.
Keep the family names elsewhere
The event blocks are for practical information. Put the long list of relatives, if you want one, in a separate “Family” section further down, or leave it to the printed card. Names crammed into event blocks push the useful details off the first screen.
Use the same details in your messages
When you send the link, mention the events in your message so guests know what is coming. For example: “Engagement on 12 Feb, muhurtham on 14 Feb, reception that evening.” See WhatsApp wedding invitation messages you can copy.
If a time changes
This is where a page beats a PDF. Edit the event once and every guest with the link sees the update. Send a short message so people know to check. If you built the invitation as a scrollable page, that is all there is to it.
What a good events section looks like
Here is a sketch, written as plain text:
Engagement: Thursday, 12 February, 6:00 pm. Sample Hotel, Madurai. Family and close friends. Smart casual.
Muhurtham: Saturday, 14 February, 8:30 am. Sample Kalyana Mandapam, Madurai. Everyone is welcome. Traditional wear.
Reception: Saturday, 14 February, 7:00 pm. Same city, 25 minutes from the mandapam. Everyone is welcome. Dinner follows.
These are sample details for fictional events, shown only to illustrate the format.
Want to see it?
Our wedding invitation website page shows how events appear, and our designs all handle several events with timeline and countdown. The what to include guide covers the rest of the page.
Quick questions
How many events can one invitation hold?
As many as the wedding has. Our self-serve invitations hold up to six events, each with its own map and time.
Should every guest be invited to every event?
Not necessarily. Say clearly which events are for everyone and which are family only, so guests do not have to guess.
Should I put the dress code on the invitation?
Yes, one short line per event if it matters, such as traditional wear for the muhurtham. It saves many messages.
What if the events are in different cities?
Give each its own city and map link, and mention travel time between them in the event note.