Households, not RSVPs
Households, not RSVPs, means the real unit of a large cultural wedding is the family group that arrives, sits, eats, and moves together, not a single person clicking yes or no. Once a wedding has several hundred guests and more than one event, planning by household is more accurate than planning by isolated replies.
- Unit
- The household or family branch.
- Seat truth
- Dinner seats, program-only places, and waitlist by event.
- Why it matters
- Families arrive together and expect to sit together.
- Best for
- Large, multi-day, family-led weddings.
What does households, not RSVPs mean?
It means you invite a household once and manage the seats that household needs across every event. Auntie, uncle, their children, and a grandparent are not four unrelated replies. They are one family unit with a shared welcome, shared table needs, and often a shared language.
The model still needs names. It simply starts from the group before it assigns each person a seat, door key, and event access.
Why does the Western RSVP model break at 500 guests?
A one-person reply model breaks because big family weddings do not grow one person at a time. They grow by branches: a cousin adds children, an elder brings a helper, an uncle expects his household to sit together, and different events have different guest scopes.
The operational truth is not just who said yes. It is who needs a dinner seat for henna, who is program-only for the ceremony, who is waitlisted for the main hall, and which household owns that change.
What should you track instead?
Track people inside households, then assign each person a seat state per event block. The useful states are dinner seat, program-only, waitlist, and not invited to that block.
That lets the couple protect capacity without breaking dignity. A person can be welcomed to the ceremony but waitlisted for dinner, or seated at the family night but not the smaller contract ceremony.
How does a household model help at the door?
At the door, the greeter needs to welcome people, not litigate a spreadsheet. A household model lets the scanner find a guest by QR or name, show their household, seat, and event access, and handle walk-ins without losing context.
If a family arrives together, the team can see the whole group instead of checking five disconnected rows.
How does Martida use households?
Martida invites the household, holds seats across event blocks, gives each guest one pass, and keeps dinner seats, program-only access, waitlists, door check-in, language, and the photo album connected to the same wedding record.
The point is not to remove hospitality. It is to remove the manual chasing that makes hospitality hard to deliver at scale.
Common questions
Do you still need individual guest names?+
Yes. Households are the organizing layer, but each guest still needs a name, seat state, and pass.
Is this only for cultural weddings?+
No, but it matters most when families are large, events are multi-day, and guest lists are co-owned by relatives.
Can a guest attend one event but not another?+
Yes. That is the point of event blocks: each person can have a different seat state per event.
Is waitlist a rejection?+
No. It is a capacity state. The guest can still be welcomed honestly where there is room.