For the relative who said 'I'll organise it'
Pick the date together, decide the place centrally, then hand one link to the family chat for answers, travel notes, and headcounts. A plan built for a reunion where nobody lives in the same town.
The pattern repeats in every scattered family. Someone proposes a reunion in the group chat, the enthusiasm is immediate, the logistics are a wreck within a week. The date argument has nine opinions and no vote; the branch abroad missed three messages; by the time someone asks who is cooking for how many, two families have quietly decided not to come.
The cause is that the plan lives in a conversation. Chats are terrible at storing decisions, terrible at counting households, and hostile to a final number. A reunion needs one central place for answers, and it should be the link you send — not the chat where the link lives.
So the re-plan is simple in principle: settle date and place through the mechanisms below, then move everything else onto one page that every branch holds and can reply to.
The date is the reunion's one real negotiation. Run it as a process and it takes ten days, not a year.
The organising household offers two or three candidate weekends in a set window — never 'when works for everyone?', which invites an endless list. Three options collapse the negotiation into a choice.
Each family branch sends one answer, not five. Whoever holds the chat or the page collects them by a stated day and announces the result with the other two dates struck through.
The eldest members and the travelling branch are the fixed points. Check school terms and unavoidable dates before publishing, because a date announced twice is worse than a date announced late.
A reunion works with enough structure to give the day a shape and enough slack for the cousins who only came for the food.
The page carries the detail; these are the words that get it opened. Adapt the names.
The 2026 reunion has a page now: weekend of 15 August at the Lindqvist farm, the whole plan in one place. Vote on the date there by Friday, and once it's set everything else lives on the same link.
We kept the reunion in the same week the cousins are already visiting. Everything is on the page — the address, the two hotels we found that have rooms, and a place to tell us how many are coming so Aunt Marta can plan the cooking honestly.
Reminder from the page: please confirm your household by Sunday. Marta needs the number for the food, and the head table can't seat ghosts.
When the reunion lives on a My Joyfullday page, the scattered problem stops being a problem. Every branch holds the same link, so the date nobody can find is the one that changed and you edited once. Households reply against their own names — plus-ones inside your limits, meal notes for whoever cooks — and the guest list reads itself instead of being reconstructed from chat history every time someone asks.
The features a reunion genuinely needs are the quiet ones: reminders sent to the non-responders without you typing another message, a directions block so cousins who finally came after eleven years reach the right gate, a wishes page for the branch that reads everything and attends none of it, and a photo gallery where the day lands in colour.
How it works
Two or three candidate weekends, one vote per household, a booked gathering place with a rain plan. These are decisions, not configuration.
Build it on the web or message Jitabi: 'family reunion, Lindqvist farm, weekend of 15 August, about forty people across four countries.' Edit the draft into the family's voice.
RSVP per household with a deadline stated as a date, directions and accommodation notes, a wish list for what to bring, and a gallery code for the day.
The link goes into the chat once, pinned. From then on the outstanding column answers 'who's still coming?', reminders handle the silent branches, and updates never need a second announcement.
Questions
Replies scale with your plan rather than a fixed cap. Start from your rough headcount, and upgrade as the guest list grows if the branches keep multiplying.
They are the reason the reply deadline matters. The list shows which households have confirmed and which are silent, and reminders go to the quiet ones through WhatsApp or email — in their own timezone's inbox, where they actually read them.
Potluck below about thirty guests; anything larger needs one person — or one kitchen — owning the food. If you potluck, the page should say what each household brings rather than leaving it to the loudest chat member.
One named organiser, on a shared list co-hosts can also read at their own access level. It should not live on a private phone, because the questions arrive from everywhere.
Yes, and it is one of the nicest uses of the page. Wishes and photographs left before the day give older relatives a place in it now, and they arrive already part of the story.
Get Started
A date by process, a plan on one link, answers gathered from every branch in the same list. That is how scattered families actually end up in the same photograph.
