A to-do list for class reunion organizers - bringing together classmates with scattered contact details
What makes organizing a class reunion hard is not the act of picking a date itself. The difficulty is that contact details are scattered across different routes depending on the person, and some people never receive the invitation at all. For a work meeting, you can send to everyone at once through the same channel, but for a reunion, the route that reaches each person is different, and the reason for no reply is more often “the invitation never arrived” than “the date does not work.” Build your process starting from that point.
Pick candidate dates by season
Reunion attendees live all over the country, so travel by classmates who live far away constrains the date. If you go looking for everyone’s free days, the candidates multiply without end, so reverse the order. First pick one season when it is easy to travel home, and offer only 2 or 3 candidates within that season.
- Center on the periods when people travel home. Obon (the mid-August holiday in Japan) and the New Year holidays make it easier for distant classmates to come, but they compete with family plans
- Skip the first and last days of long weekends. Those are travel days, so distant classmates drop out first
- Limit candidates to 3. For reunions, adding candidates does not increase answers and only makes the organizer’s tally heavier
- Have organizers settle on one plan among themselves first. If there are several organizers, finish coordinating among them before sending the invitation to everyone
Long weekends shift from year to year, so before offering candidates, check the holiday and long weekend calendar to avoid the mistake of placing a candidate on a travel day.
Take stock of the reunion’s contact routes
Before sending the invitation, sort out which route reaches each classmate. Different routes mean different delivery speeds and reply rates, so just sending the same message through every route leaves you with lopsided returns.
Two-stage distribution: spread the word without collecting contacts
If the organizer tries to collect everyone’s contact details, months disappear into the collecting, and the responsibility for managing that personal information stays with them. Spreading the word without centralizing contacts is faster. Ask the classmates the organizer is directly connected to to pass it on to a few people each.
- Send individually to the people the organizer can reach. Say clearly that you would like them to pass it on to people they are in touch with
- Write an invitation that still makes sense when forwarded. Put the graduation year and class, the purpose of the gathering, the organizer’s name, where to reply, and the deadline in a single message
- Do not have contact details sent back to the organizer. If people write their answers directly in the attendance poll, the organizer does not need to hold a list
- Record only who was reached. If you keep whether people were reached rather than their contact details, you can hand it off to the next organizer
The link in the invitation should not ask classmates who open it to sign up or register. After years without contact, a screen that says “please register first” is where answers stop. If you create an attendance poll with the PickDay creation form, you only need to put a single registration-free URL in the invitation.
Design deadlines assuming replies will not come back
Reunion answers come back in a cluster on the day you ask, and then barely move. Rather than piling up reminders to raise the reply rate, it is more practical to split the deadline into 2 stages and decide what each stage settles.
- First deadline = intent to attend. Use it to tentatively fix the headcount for the venue. Accept answers even if they stay at △
- Second deadline = paying the fee. If payment is what confirms attendance, the headcount on the day is less likely to shift
- Do not read no answer as not attending. If you count “no answer” separately from “invitation did not arrive,” the gaps in your list become visible
- Send a reminder only once, through a different route. Repeating the same route will never reach someone it did not reach the first time
Combining the idea of an attendance check (RSVP) with systems to prevent last-minute cancellations keeps the headcount on the day from swinging.
The order of booking the venue and fixing the headcount
You need to hold a venue before the date is decided, yet the headcount is not final until the deadline. This twist in the order is what burdens the organizer. First ask the venue the date when cancellation fees start, and set the attendance poll deadline by counting back from that date.
Limit the fields in the attendance poll
A reunion attendance poll mixes people whose family names changed after graduation and people others only remember by their old nicknames. Keep it to the minimum needed to tell whose answer it is, and ask for nothing more.
- Show how to write maiden names in the invitation. An example like “Yamada (née Tanaka)” keeps the entries consistent
- Ask people to add their class or club. In a year with classmates who share a family name, this alone tells them apart
- Do not have people write addresses or phone numbers. Do not leave contact details in an attendance poll anyone can open
- If you invite former teachers, the organizer contacts them separately. Mixing them into the same poll fails to convey how fees and seating are handled
What to pass to the next organizer
Reunions are held every few years, so leaving only information that can be handed over when organizers change makes the next one lighter. What you pass on is not a contact list but a record of who was reached through which route, and the result of what share of people came in the season you chose. Handing over a contact list also hands over the responsibility of managing it, but a reach record can be used as is for the next distribution plan.
If attendance grows beyond 30 people, combining this with the step-by-step narrowing in tips for scheduling large groups lets you decide without adding candidates.