Invitations and RSVPs are the first ten percent. This is the other ninety — every detail in one place, visible to the whole committee, so the work spreads out instead of landing on one person.
Every family has that one person who ends up holding the whole reunion in their head: the hotel block, the deposit deadline, who’s driving from the airport, whose kid can’t have peanuts, who still owes for their plate. It doesn’t have to work that way.
Start with the headcount, then handle what comes after it. Adults and children counted separately, and payments tracked by who covered whom.
Build the itinerary once, and everyone works from it. Activities, times, locations, and who's leading each one.
The hall, the hotel block, the park pavilion. Contacts, deadlines, and signed contracts kept with the reunion instead of in one person's email.
The part that always happens over scattered texts. Who lands when, who's picking them up, and how everyone gets between venues.
Meals for a crowd, with the details that matter to the people eating them.
Assign the room in minutes, then walk in with everything already on paper.
Orders by person and size, totalled for you. Judith needs a black XL, and the order sheet says so.
The part nobody enjoys and everybody asks about.
Email for the plan, text for the moment. Reach the whole family, or just the people affected.
The pictures stop living on forty different phones.
Cards, boards, and screens for a room with three generations in it — and someone besides you to run them.
Give each part to the person who’ll do it best, and give them access to that part only. The cousin running games doesn’t see the budget. The person booking the hotel doesn’t need the t-shirt orders.
Want to see it in action?
Request a demo