Households are the unit, not individuals
Western event tools default to a row-per-guest spreadsheet. That works for a 100-person party where everyone is invited individually and travels alone. It does not work for a South Asian celebration where the Patel family of five turns up together, replies together, eats together, and sits together. The first thing Jubily does differently is treat the household as the primary unit. You add the Patel family as one entry, with five guests inside it. They get one RSVP code, one invite link, and one row on your seating chart. When Mrs Patel replies that her family is coming, she replies for everyone. When her son can't make the morning pooja but is coming to the evening party, she ticks that one box. When her daughter is vegetarian and her husband halal, both go on the same form.
Per-event RSVP — because they're not all coming to everything
A wedding can have six events; a milestone birthday might have a family pooja and a bigger party; a griha pravesh might pair a havan with a lunch. Most guests don't come to everything. Close family come to it all; friends might come to the reception or the party only; a cousin might join the Mehndi and skip the rest. Generic RSVP tools force one yes/no for the whole celebration, which is useless. Jubily's RSVP page lets each guest tick which events they're attending, individually — so the younger cousin can come to the Sangeet but skip the Vivah, or come to the party but not the morning pooja, and that's captured cleanly. You see the per-event count in real time. The catering team gets accurate per-event numbers. The seating chart pulls from the right per-event guest list. Nothing is approximated.
Dietary capture that actually means something
A South Asian caterer — whether feeding a 600-guest wedding or a fifty-person housewarming — needs to know more than "vegetarian, gluten-free, allergic to peanuts". They need to know: pure vegetarian (no onion, no garlic — Jain), Jain-compatible, halal-only, kosher, vegan, vegetarian-but-eats-eggs, and dozens of allergen and preference combinations. Jubily's dietary form is structured for this. Each guest gets a primary preference (the dominant signal) plus an "additional" multiselect (allergies, sub-categories) plus a free-text notes field. The result is a clean, exportable dietary brief that goes straight to the caterer — not a chaotic email thread of "Auntie Sushila is Jain, but she's OK with garlic on Sundays" three weeks before the day. For a children's party the same structure puts allergies front and centre, where they belong.
A guest list that becomes a seating plan and a day-of timeline
The guest list is the foundation. Once it's in place, everything else builds from it. The seating plan picks up the same households and lets you drag-drop them onto tables. The dietary brief flows automatically into a printable PDF for the caterer. The day-of timeline shows the right per-event count to your venue and vendors. The event website pulls in the guests-only schedule and the right RSVP link per household. There is no re-keying of data anywhere. This is how a planning platform should work, and how a spreadsheet never can.
Privacy, fairness, and family politics
Some guests get plus-ones; some don't. Some get full menu choice; others are at table 14 with the kids. At a wedding some are on the bride's side, some on the groom's, some shared; at a family celebration some are the host's side and some are friends. Some are VIP and need special seating; some are last-minute additions you wish you could quietly disinvite. Jubily lets you tag, side, prioritise, and reorder without the rest of your family seeing your private notes. You can also share the guest list with read-only access to specific people — your planner, your seating coordinator — without giving them edit access to everything else.
What's inside
Built to handle the full job.
Households as units
One row per family, with multiple guests inside.
Per-event RSVP
Each guest can attend any combination of your events — ceremonies, poojas, parties.
Structured dietary capture
Pure veg, Jain, halal, allergens, free-text notes — caterer-ready.
Side, plus-one, VIP tags
Host side / other side / shared, plus-one allowance, VIP flagging.
Personalised RSVP links
Each household gets a unique URL — no logins, no friction.
CSV import & export
Bring guests in from your existing spreadsheet, export anytime.
In real weddings
How couples are using it.
320 guests across six events
Mehndi (180), Sangeet (240), Anand Karaj (320), Lunch (320), Choora (60), Reception (300). Jubily tracks each event's invite list separately, sends per-household RSVP links, and gives you live attending counts per event for catering and seating.
A pure-veg-and-halal mixed wedding
The bride's family is Gujarati Hindu (mostly Jain-compatible); the groom's family is Muslim. The reception caterer needs accurate counts of pure veg, halal-only, Jain-strict, and vegan guests. Jubily's structured dietary capture exports a single, clean PDF brief the caterer can work from.
A 60th birthday with a morning pooja and evening dinner
You're hosting a Sashti Poorthi for your father — a pooja for 40 close family in the morning and a 180-guest dinner at night. Households RSVP per event, so you know exactly who's at the intimate pooja versus the big dinner, and the caterer gets separate, accurate counts for each.
Frequently asked
