How to Word a Wedding Invitation (With Indian Examples)

Wedding invitation wording is one of those problems that looks trivial until you sit down to do it. Who is doing the inviting? Do you write “request the honour of your presence” or “request the pleasure of your company”, and is there a difference? What do you call the person whose father died last year? And how do you write all of this in a way that sounds like a real family rather than a template?

This is the practical version, written for Indian weddings in Indian English — where the host line is genuinely complicated, where “and family” does a lot of quiet work, and where a wedding routinely means five events rather than one.

The anatomy of an invitation

Almost every invitation, printed or online, is built from the same eight parts. Not all of them are compulsory, but knowing the list makes it obvious what’s missing:

• The invocation. A blessing or sacred opening, if your family uses one.
• The host line. Who is inviting. The single hardest line to get right.
• The request line. “request the honour of your presence” and its relatives.
• The couple. Names, and often parentage.
• The occasion. Named correctly: the wedding, the nikah, the Anand Karaj, the reception.
• Date, time, and place. Including the muhurtham where there is one.
• The reply line. How and by when.
• The closing. Anything from a formal request to a warm sentence in your own voice.

1. The invocation

If your family opens invitations with a blessing, it goes at the very top, above everything — including the names. Common openings include ॐ श्री गणेशाय नमः before an auspicious beginning, the Bismillah on a nikah invitation, and a line of scripture — 1 Corinthians 13 is the near-universal Christian choice.

2. The host line — who is doing the inviting

In much of India the invitation comes from the parents, not the couple, and the phrasing follows from that. The modern versions are equally correct; what matters is that the line is consistent with the names that follow.

Parents of one side hosting

The traditional form. “Mr and Mrs Suresh Nair request the honour of your presence at the wedding of their daughter Anjali to Vivek…”

Both families hosting

Increasingly the norm, and the easiest to keep balanced: “Mr and Mrs Suresh Nair, together with Mr and Mrs Ramesh Iyer, invite you…”

The couple hosting

“Anjali and Vivek, together with their families, invite you to celebrate their wedding.” The “together with their families” construction is worth knowing: it lets the couple issue the invitation without appearing to leave the elders out, which in most Indian families is the point of contention.

When a parent has died

The usual convention is to name them with “the late”: “Anjali, daughter of Mrs Latha Nair and the late Shri Suresh Nair”. Some families instead write “daughter of Mrs Latha Nair” in the host line and remember the parent in a separate line further down. Both are respectful; the deciding vote belongs to the surviving parent.

Separated or remarried parents

List them on separate lines rather than joined by “and”. Two clean lines are far less awkward than one line that implies something untrue.

Grandparents or an elder hosting

Common when a grandparent is the head of the family: name them first, then the parents on the following line. The order on the page is the order of seniority, and people notice.

3. The request line

There is a real distinction here, and it’s simple once you know it:

• “request the honour of your presence” — traditionally used for the ceremony itself, particularly one held in a place of worship. The formal register.
• “request the pleasure of your company” — traditionally the reception, the party, the meal. Slightly warmer.
• “invite you to share in their joy” / “would love you to celebrate with them” — modern and warm. Perfectly correct; just don’t mix it with the formal register in the same sentence.
• “cordially invite you and your family” — the standard Indian-English form, and the one that does the most useful work. In much of India an invitation is understood to extend to the household, and “and family” makes that explicit instead of leaving people to guess.

4. Naming the events correctly

A wedding website has room for the whole schedule, which is its advantage over a card. Use each event’s real name, and add one plain sentence for guests who won’t know it:

• Mehendi — the henna evening, usually the bride’s side, usually informal.
• Haldi — the turmeric ceremony. Warn guests not to wear anything they love.
• Sangeet — the music and dance night.
• Baraat — the groom’s procession. Give an arrival time, because it sets everything else.
• Muhurtham — the auspicious time for the ceremony itself. Sacred, and not the same as “when to arrive”.
• Nikah — the marriage contract. Often followed by a walima, the reception hosted by the groom’s family.
• Anand Karaj — the Sikh ceremony, held in the gurdwara.
• Reception — the evening celebration, frequently with a wider guest list than the ceremony.

If two events have different guest lists, say so on the page. It is far kinder than letting someone arrive at an event they weren’t invited to, and no one has ever been offended by clarity plainly given.

5. Date, time, and place

• Write dates out. “Sunday, the 15th of February 2026”. Numeric dates are ambiguous across countries and your cousin in Toronto will read 02/03 backwards.
• Separate the muhurtham from the arrival time. The muhurtham is the auspicious moment; guests need to know when to be seated. Give both: “Muhurtham at 10:42 AM · kindly be seated by 10:15”.
• Say IST if you have guests abroad. One extra word prevents a very sad phone call.
• Give the full address, not just the venue name. Plus a map link. On a website this is a tap; on a card it’s a landmark line.

6. The reply line

On a card this is “RSVP” and a phone number. On a website it’s a form, which is better — but the wording still matters:

• Give a date. “Kindly reply by the 20th of January” gets a far better response than an open invitation to reply eventually.
• Say what you need. If you need a head count including children, ask for a number, not a yes/no.
• Keep the form short. Every extra field costs you replies, and a question you won’t act on is a question not worth asking.
• Name a human. “Any questions, call Meera on…” is worth more than a generic contact block.

The full system — what to ask, when to open and close replies, how to chase people — is in how to collect wedding RSVPs online.

Worked examples

Take these as scaffolding, not as scripture. Change the register until it sounds like your family saying it out loud.

Wording a website, not a card

A card and a website are doing different jobs, and the wording should reflect that. The card is ceremonial: it carries the invocation, the elders’ names, the formal request. The website carries all of that and everything the card has no room for — and it can afford a warmer voice further down the page.

• Keep the top formal. Invocation, host line, names, date, venue. That part should read the way the card reads.
• Let the middle relax. How you met, what to wear, where to park, whether children are invited. Write these the way you’d say them to a friend.
• Use your own headings. Section wording is editable on most builders, ours included — “Our Story” can become “How this happened”, and the RSVP heading can become “Will you come?”.
• Answer the questions you keep getting. Three questions in the FAQ, drawn from your actual WhatsApp messages, will save you fifty replies.

The mistakes that cause the most trouble

• Mixing registers. “Request the honour of your presence” followed by “let’s party!” reads as a page written by two people who never spoke.
• Inconsistent honorifics. If one father is “Mr”, the other is not “Shri”. Pick one system per invitation and hold it.
• Muhurtham as arrival time. Guests arriving at the muhurtham are guests arriving late. Give both times.
• No year. Astonishingly common, and genuinely confusing for a save-the-date sent a year ahead.
• Burying the venue. Name, full address, map link. Every time.
• Saying nothing about children. If children aren’t invited, say so once, plainly and warmly, in the FAQ. The silence is what causes the awkward conversation, not the rule.
• An apologetic gifts paragraph. One line, stated plainly, or nothing at all. Hedging reads worse than either.
• Guessing at a script. Worth repeating: if you don’t read it, don’t print it unchecked.

A final pass

• Read the whole thing aloud. Wording that sounds wrong out loud is wrong.
• Check every name against a document, not from memory. Misspelling an in-law is a story that outlives the wedding.
• Have both mothers read it before it goes out. They will catch things you cannot.
• Open it on a phone. That’s where it will be read.

When the words are settled, the design is the easy half — start with choosing a template by tradition or go straight to the template catalogue. Building and previewing is free; plans are one-time, and the custom-domain guide covers putting it on your own web address.