Organizing a class reunion 10 or 15 years later: the method that works

Karim got the idea one evening in January, stumbling on an old class photo from his vocational college years on a dusty hard drive. Fifteen years had passed. Thirty-eight names in his head, about thirty faces still clear, and barely a dozen contacts he could still reach without effort. He typed "organize class reunion" into a search engine, read a handful of forum stories that all told the same tale with slight variations: a genuine wish to reconnect, an enthusiastic WhatsApp group, then three months of silence and a project quietly dying. This piece follows his very concrete case to show where things get stuck, and how they do not have to.

Finding thirty-eight people, not twelve

The first trap is not organizing the evening itself. It is believing that the handful of contacts still on social media represent the whole group. Karim had fourteen Facebook contacts and eight on LinkedIn, with six people overlapping. Out of thirty-eight classmates, he actually knew what had become of about fifteen, and had no idea about the other twenty-three: married and settled elsewhere, living abroad, on bad terms with the school, or simply never active anywhere online.

The method that works, as told by several former organizers on alumni forums, comes down to three steps. First, list every name you can remember, even roughly, with whatever you know: a likely city, a job, a mutual old friend. Second, split that list among three or four people from the core group, each tasked with tracking down five to ten people through their own network, since a former classmate finds someone far more easily than a stranger writing cold. Third, centralize every contact found in a single document, not scattered across ten private conversations, or half the information gets lost along the way.

It took Karim six weeks to reach twenty-nine contacts out of thirty-eight, relying on the school's Facebook groups, a former class representative who had kept a paper list, and plain word of mouth. Nine people remained untraceable, and he eventually accepted that this was not a failure but a normal outcome after fifteen years.

The date poll that kills the project before it starts

Once contacts are gathered, the number one mistake is sending a message like "let's do something, who's in, drop your availability." A story shared on an alumni discussion forum sums up the pattern well: out of thirty people contacted, twenty-two reply with an emoji within the first day, then nothing for two months. Nobody wants to be the one proposing a date, because proposing a date means risking excluding someone, or getting the format wrong.

With thirty-eight people scattered across several regions, sometimes several countries, crossing everyone's availability by hand is close to impossible. Everyone has their own constraints: parental leave falling in September, a move planned for October, a cousin's wedding in November. A simple three-date poll in a WhatsApp group creates an illusion of method, but it forces people to choose among three options that may suit nobody, and says nothing about the format or the budget each person is willing to commit.

Dinner, weekend, with or without partners: the real sticking point

The second trap, deeper than the date itself, is the format. Fifteen years after graduating, in a group of thirty-eight, life situations have diverged so much that the same word, "reunion," covers incompatible expectations.

Some live twenty minutes from the proposed venue, single or in a couple without kids, for whom a full weekend with lodging is an easy, pleasant idea. Others have two or three young children, for whom a childcare-free weekend is a logistical headache, while a Saturday dinner works fine. Others have moved to Canada or Australia, for whom the trip only makes sense paired with a real weekend, or even a longer stay in France, otherwise the travel-to-presence ratio simply does not add up.

Karim recalls that a first attempt, two years earlier by another classmate, failed exactly on this point: the person jumped straight to proposing a weekend with partners and children in a rented house in the Dordogne, and only nine people replied, five of them from the same city. The format, chosen too early and without any consultation, scared off everyone for whom it was not the right fit.

Budget follows the exact same scattering logic. A dinner at a city-center restaurant costs between 35 and 60 euros per person depending on the city, excluding lodging and travel. A group weekend in shared accommodation with communal meals can run to 150 or 200 euros per person, travel included for those coming from afar, and climb to 300 or 400 euros once partners and an extra hotel night for children are added. In a group where some are students returning to study and others are senior executives, that range can discourage a third of the group if it is never clearly stated from the start.

What Karim learned from the second failed attempt

The second attempt, the one Karim himself launched three years before the one that finally worked, collapsed for a different reason: too many communication channels running in parallel. He had a general WhatsApp group, a Facebook event created by someone else, and email exchanges with the three or four alumni he knew best. As a result, information traveled at three different speeds, some people got updates two weeks after others, and nobody knew anymore where the real conversation was happening. Two people ended up organizing their own small dinner separately, assuming the whole project had been dropped.

This story comes up constantly on alumni organization forums: scattered channels kill more projects than lack of motivation ever does. People are not reluctant to reconnect. They are simply drowning under scattered requests, unsure which one deserves a real reply.

The method that worked the third time

On the third attempt, Karim changed his approach. He first accepted that he did not need everyone: out of twenty-nine contacts found, he knew that eighteen to twenty-two would likely say yes, and that this was enough for a successful event. He then asked three structuring questions before even mentioning a date: simple dinner or full weekend, with or without partners and children, and an acceptable budget range for each person. Asking these three questions together, rather than piecemeal as the conversation went on, revealed a clear trend within days: fifteen people wanted a light format, a dinner, while seven would have preferred a weekend. He went with the majority format, while offering a brunch the next day for those who wanted to extend the reunion, an intermediate solution that satisfied nearly everyone.

That is when he used OuiCanPlan to structure the rest, after looking for a tool that would avoid exactly the pitfall of an overly simplistic poll. The idea is to generate between 10 and 15 targeted questions depending on the type of event, here adapted to a class reunion: format, budget, partners attending, date constraints, city preference. Each person answers on their own, simply providing a first name, an email and a mobile number, with no need to create an account to reply. As soon as three people have answered, the responses appear anonymized within the group, which let Karim see, without ever naming anyone, that four people were hesitant about the weekend budget and two others could absolutely not free up a Saturday because of alternating childcare arrangements.

The tool then surfaced cross-compromises based on those anonymous answers, and ranked several concrete proposals with an agreement percentage displayed for each, along with direct booking links for the restaurant and for the backup accommodation offered to people coming from far away, when relevant and after a real web search. Karim set a response deadline, with automatic email reminders seven days before, then three days before, then twenty-four hours before, which removed the chore he dreaded most: chasing each of the twenty-nine contacts individually through private messages. The results are real and ad-free.

Twenty-four people finally showed up for dinner, at a city-center brasserie chosen because it offered a group menu at 42 euros per person, drinks excluded, and a private space for thirty guests. Six of them stayed for the next day's brunch with their partners, letting those who had driven more than three hours make the trip worthwhile without imposing a heavy format on everyone else.

What remains true for any graduating class

Karim's story has nothing exceptional about it, and that is exactly what makes it useful. Reuniting a graduating class ten or fifteen years after finishing school always runs into the same obstacles: lost contacts that must be tracked down by cross-referencing rather than by miracle, a date that never decides itself in a messaging group, a format that must be chosen before the date rather than after, and a budget that needs to be stated clearly from the start so as not to unknowingly exclude part of the group. The difference between a project that succeeds and one that fades out in a chat thread rarely comes down to initial motivation, and almost always comes down to method.

In short

Organizing an alumni reunion is not a matter of goodwill, it is a matter of organization, with well-known pitfalls: underestimating the work of tracking down contacts, launching a date poll too early, imposing a format before discussing it, and never clearly stating a budget. By anticipating them, as Karim did on his third try, a class scattered across several cities and countries can gather around a table one Saturday evening, fifteen years later, without anyone having to carry the whole weight of the organizing alone.