How to write Indian wedding invitation wording for multi-event functions
A practical way to word mehendi, sangeet, wedding, and reception lines so guests know where to be, without a second WhatsApp essay.
Write the host line before the functions
Indian wedding wording fails when it opens with a function list and never says who is inviting. Start with the hosts: parents, the couple, or both, in the order your family actually uses on paper cards. If both sides are hosting, give each side its own line rather than a slash-joined sentence that guests have to parse on a phone.
Use the names people will hear at the venue. A formal name on the invite and a nickname in the family group is how guests miss the right person at the door. If a name has an initial, a house name, or a title your elders expect, put that in the host line and keep pet names for the message underneath.
One short blessing or welcome line is enough under the names. Maṅgalya is a website, so you do not have to compress three days into a couplet. The host line should still stand alone if someone screenshots only the top of the page and forwards that image.
Design the wording in the editor before you pay. Preview is free. You pay ₹799 when you publish the live link, so you can rewrite the host line with your parents in the room and only release it when the names are settled.
Give every function its own block
A multi-event wedding is not one date with a footnote. Mehendi, sangeet, haldi, the wedding muhurtham, and the reception are different rooms, different clothes, and often different guest lists. Write each function as its own block: name of the function, day and date, start time, venue name, and area.
Put the wedding ceremony in the block guests will look for under pressure, not buried under a poem. If the muhurtham is a short window, say the time guests should be seated, not only the priest’s start time. Families lose an hour when the card says 9:14 and the baraat is still on the road.
If a function is family-only, say so in that block. “All are welcome” on the wedding and silence on the mehendi reads as an open mehendi. A single line — hosted for close family, or colleagues welcome at the reception only — saves a round of clarifying messages.
You do not need every detail on the day you first share the link. Maṅgalya keeps one URL. Edit the function block later and guests who already have the WhatsApp message see the update when they open the link again.
Mehendi, sangeet, and the wedding day
Mehendi wording can be warm and still specific. Name the host (often the bride’s side), the afternoon or evening, whether lunch is served, and whether kids are expected. If the mehendi is at home and the wedding is at a hall, do not reuse the hall address. Guests will drive to the wrong gate.
Sangeet or cocktail wording should say the tone. A seated dinner and a dance floor imply different arrival times. If there is a performance window, give the time you want people seated, and say whether the couple’s entry is at the start. Colleagues who have never been to a sangeet need that more than a line of song lyrics.
The wedding block should carry the muhurtham, the venue, and the rite in plain language: wedding ceremony, pheras, or the name your family uses. Add a line for the baraat only if guests are expected to join it. Otherwise they will wait on a pavement for an hour.
Reception wording is often the only block office friends will read. Lead with date, time, venue, and dress if you care about it. “Festive attire” is clearer than a colour theme nobody outside the family knows. If the reception is on the same day as the wedding, say that explicitly so outstation guests do not book a gap between them.
Dress, food, and gifts without a second card
Dress codes belong on the function they apply to. A pastel mehendi and a black-tie reception cannot share one line at the bottom of the page. If you have no dress code, skip the line. Invented themes create more questions than they prevent.
Mention food only when it changes the plan: a Jain meal on request, a brunch instead of dinner, or no dinner at a short ceremony. Guests use that to decide whether to eat before they leave home. Do not list the full menu. The live page is for decisions, not a catering PDF.
Gift wording is a family decision, not a template default. If you want nothing but presence, say that once. If you are sharing a bank account or a registry, put it in one place on the page and do not repeat it under every function. Maṅgalya does not require a gift block.
Kids, plus-ones, and “no phones during the ceremony” are the lines people actually screenshot. Write them as short sentences under the relevant function. A blanket rule for the whole weekend is fine if it is true for every event.
Keep one link current
Paper cards freeze wording the day they go to print. A digital invitation does not. When a venue shifts from the lawn to the hall, or a sangeet moves an hour, edit that block and save. The WhatsApp message you already sent still points at the right page.
Read the page once on a phone before you publish. Host lines that look balanced on a laptop often collide on a narrow screen. Function times should be visible without opening a map. If a sentence needs a footnote, it is too long for the block.
Publish when the names and the first confirmed functions are right, not when every aunt has approved a caption. You can add a haldi the next morning. The base fee to release the link is ₹799. RSVP, if you want replies on the page, is a separate ₹399 add-on and is covered in the RSVP guide.
When you are ready, open the Maṅgalya editor, choose a wedding design, and put each function in its own block. Share the one link. Correct it there instead of in a chain of forwarded messages.