Plan every event of your wedding — not just the wedding

Anvaya treats every ceremony as a first-class object with its own date, time, venue, capacity, host side, and budget — not a row buried under a single wedding date. Drop in the mehndi at the courtyard pavilion on Thursday night, the sangeet at the ballroom on Friday, the haldi at the bride's family home Saturday morning, the baraat at the golf-club entrance Saturday afternoon, the pheras under the mandap right after, and the reception on Sunday evening. Each event has its own page, its own guest set, its own task list, its own vendor roster, and its own seating canvas.

The dashboard shows all six side by side with dates, venues, guest counts, and booking status. A glance tells you the reception is awaiting a venue deposit and the baraat needs a horse confirmation by Tuesday. Click into any ceremony and the workspace narrows to just that event — the guest list, task list, and vendor list all filter to it. No more mental filtering of one huge spreadsheet.

The data model knows the canonical South Asian ceremonies — mehndi, sangeet, haldi, baraat, pheras, reception, garba, walima, Anand Karaj — and lets you add custom ones for regional rituals. Tamil, Bengali, Pakistani, Sikh, Gujarati, and Marathi weddings can keep their own vocabulary without forcing one tradition's structure on another.

Every desi wedding runs the same hundred-plus tasks, and yet every couple ends up rebuilding the list from scratch on a fresh Notion page at midnight. Anvaya ships with 23 starter task templates, each tagged by ceremony — more on the way. Book the mehndi artist, order the dholki, confirm the haldi turmeric paste with the family priest, arrange the baraat horse, finalise the pheras muhurat with panditji, print the reception menu cards, schedule the mandap floral install. Each template carries the ceremony it belongs to, a default lead time, and a suggested owner (couple, parent, decorator, planner).

Filter the workspace to a single ceremony and the task list collapses to just that event. Filter to a single owner and the list shows you what your mom is responsible for. Filter to a single status and you see what is blocked. The same tasks surface on the readiness dashboard so a glance at the wedding week tells you whether the haldi is on track and the reception still needs work.

You can override any pre-loaded task, add custom ones, and duplicate tasks across ceremonies. Tasks support dependencies (confirm the venue before sending save-the-dates), due-date math (six weeks before the ceremony), and family-side scoping so the bride-side tasks roll up to her mom's dashboard and the groom-side tasks roll up to his. The list knows it is planning six weddings, not one.

Most desi weddings hire ten to fifteen vendors, and each one covers a different slice of the weekend. Your photographer is at every ceremony. Your mehndi artist works the mehndi only. Panditji handles the haldi and the pheras. Your videographer skips the haldi and shoots the rest. The DJ runs the sangeet and the reception. The caterer for the mehndi and sangeet is different from the reception caterer. A flat vendor list has no answer for which vendor is on which event — Anvaya stores per-vendor coverage as a matrix and surfaces it as a dashboard you can read at a glance.

Each vendor card carries the ceremonies they serve, the contracted price for each, the payment schedule, and the contact who handles them on the day. Filter the workspace to one ceremony and you see only the vendors on it — the mehndi event page shows the mehndi artist, the photographer, the dholki, the caterer, and the decorator that covers the courtyard, but not the reception caterer or the pheras pandit. The day-of coordinator opens the ceremony page on a tablet and runs the event from a single screen.

Vendor email extraction reads the quotes that come back and pre-fills the right ceremony coverage. Forward the quote from your mehndi artist to your wedding-specific email address and Anvaya extracts the name, contact, price, and the fact that the artist is on the mehndi only. Compare two photographers side by side with their per-ceremony coverage — the dialog reads the matrix and shows which one covers the haldi and which wants extra.

A 400-guest desi wedding is not a homogenous group. Half the family is vegetarian. A cousin keeps halal. Your future mother-in-law is Jain — no onion, no garlic, no root vegetables. Your husband's grandfather has a peanut allergy that ends in an epi-pen. Your bride's aunt is in a wheelchair. The deaf cousin needs an ASL interpreter for the pheras. The relatives flying in from London prefer Hindi for the welcome speech. None of this is exotic — it is the standard composition of a multi-generational, multi-region South Asian guest list, and the tool that asks for a single "dietary restriction" per guest is not ready for it.

Anvaya stores dietary, allergen, accessibility, and language preferences per guest per ceremony. The same guest can hold a Jain tag at the mehndi, a halal tag at the reception, a wheelchair tag for the ceremony, and a Hindi-preferred tag for the welcome dinner. Allergens get a separate field with severity (mild, moderate, severe, anaphylaxis) and severe allergens are flagged at the top of the caterer's export. Accessibility needs are surfaced to the day-of coordinator so the wheelchair ramp is staged at the right entrance.

The aggregated per-ceremony counts drive the actual decisions. The mehndi caterer gets forty Jain, twenty-five vegetarian, fifteen vegan. The reception caterer gets a hundred and twenty halal mains, ninety vegetarian, sixty Jain, and three severe-allergen alerts at the top of the sheet. The seating canvas places Jain guests near the vegetarian station and wheelchair-using guests near the step-free entrance. Every vendor gets the slice they need.