One page the whole family can forward.

Reunions are a logistics problem disguised as a party

A reunion is planned a year ahead, spans several days, and involves households that arrive and leave on different days. The organiser usually ends up as a human database: who is coming Friday, who needs a bed, who is bringing the smoker, who cannot eat shellfish. Every one of those is a question a form can ask once and total for you.

Plan for who will actually turn up

Long-lead family events have the widest gap between yes and attended, because a year is long enough for anything to change. Budget from confirmed counts, revisit them a month out, and read how many guests actually show up before you order for every yes.

Questions people ask

What is the easiest way to organise a family reunion RSVP?

Publish one page with the dates, the address and the questions you need, then send the link to whoever forwards things to their side of the family. Replies land in one list even though the link travelled through five group chats.

How do I count people across households?

Each household replies once with adults and children counted separately. That produces a person count for food and beds rather than a count of families, which is where most reunion budgets go wrong.

Can I ask which days each family is attending?

Yes. Add a question for arrival day, departure day, or which of the weekend's events they will join. Saturday lunch and Sunday brunch usually have very different numbers.

Can relatives update their answer later?

Yes. Allow edits and each household gets a private link to its own reply. Reunion plans change over months, and this avoids a second round of phone calls.

Can older relatives use it without help?

There is no account, no app and no password. The page is one screen with large tap targets. When someone would rather phone you, add their reply yourself from the responses page and it counts the same.