What to Include in a Multi-Event Indian Wedding Invitation

An Indian wedding is rarely one event. It is a haldi in the morning, a mehendi that afternoon, a sangeet the night before, the ceremony itself, and a reception in another city a week later. The card has to carry all of it without turning into a timetable, and it has to do so for guests who are invited to different parts of it. This is the checklist we use: what every card must carry, what each function needs, and what to take off the card and put on a wedding website instead.

What every card carries, whatever the function

• The invocation. Ganesh, Om, a cross, Bismillah, Ik Onkar — the one that belongs to the ceremony, placed first. Your parents will look for it before they read anything else.
• Who is inviting. In most families the parents invite, and the grandparents are named above them. If the couple invites on their own, say so plainly and warmly. Many families now name both sets of parents on one card.
• The two names. The couple, in the order your family uses. Many regions add the parents' names after each.
• The date, the day of the week and the year. Guests travelling from abroad plan around the day; the year stops the card being mistaken for last season's.
• The venue, with the full address and a map link. A banquet hall name alone is not enough in a city with three of them.
• Who the card is for. The guest's name, written on the card, is the single line that most increases the chance of a reply. On Ayozan every guest's copy carries their own name and salutation without you writing two hundred cards.
• How to reply. A phone number works. A one-tap RSVP link that records the answer for each function works better.

What each function needs

Give every function its own block with the same four lines, in the same order, so a guest can scan: name of the function · date and time · venue · dress code or note. Then add the one detail specific to that function.

• Roka / tilak / engagement. Usually a smaller list. Say whether it is family only; guests will not ask.
• Haldi. The time matters more than usual because the ceremony is short. Tell guests to wear yellow, and that the turmeric does not come out of silk.
• Mehendi. Give the start of the mehendi application separately from the start of the function; the two are often hours apart.
• Sangeet. This is the one guests dress up for. Name the dress code (festive, Indo-western, a colour), and say whether dinner is served.
• Baraat and the wedding. Give the baraat's departure time and the muhurat separately. Guests on the bride's side arrive for the muhurat; the groom's side gathers for the baraat. A muhurat that is late at night deserves a line saying so, so elders can decide.
• Reception. Often a different city and a different, larger list. If a guest is invited only to the reception, their card should show only the reception — see the next section.

If you are still choosing the day, the 2026 wedding muhurat dates are listed by month, with the Chaturmas gap marked.

Not every guest sees every function

This is where paper fails and a per-guest invitation earns its place. Your office is invited to the reception. Your cousins are invited to all five days. Your parents' friends are invited to the ceremony and reception but not the sangeet. With a single printed card you either list everything and let guests guess, or print three versions and track who got which.

On Ayozan you mark, per guest, which functions they are invited to, and their card and their RSVP show only those. The reception-only guest never sees the haldi; the cousin sees the whole week. Nobody turns up to a function they were not invited to, and nobody feels left out by a function they were not meant to see.

Move these off the card

A card that tries to hold everything gets skimmed. These belong on a wedding website that the card links to:

• Travel and stay. Which hotel, how to reach it from the station or airport, whether a car is arranged, and who to call when the car does not come.
• The full schedule with timings. The card holds the headline time for each function; the website holds the arrival time, the ceremony time and when food is served.
• Dress codes in detail, with a colour reference if you have a theme.
• Gifts and blessings. A line saying your presence is the gift, or a UPI option for those who insist, is easier to say on a page than on a card.
• Headcounts and meals. A reply that asks how many are coming and whether anyone needs a Jain or vegan meal saves the caterer a dozen phone calls. Ayozan's RSVP collects a reply per family for each function, with those numbers.
• Changes. Venues move and timings slip. A card that is a live link updates for every guest at once; a PDF already forwarded to two hundred people does not.

The order on the page

1. Invocation
2. Who invites
3. The couple's names
4. The main ceremony: date, time, venue
5. The other functions, each in its own block, in date order
6. The guest's name and their reply link
7. Family names and the link to the website

For the words themselves — the formal and the friendly versions, in English and in Indian languages — see the Indian wedding invitation wording guide. For the ceremony's own design, start from the Hindu, Sikh, Nikah or Christian wedding collections, and send a save the date first if the wedding is more than two months away.