The Alumni Reunion Follow-Up Nobody Plans For

Article · 5 min read

Your reunion classmates feel like old friends, which is why you lose them.

Reunions skip the capture habit that conferences make normal. The familiarity discount explains why old classmates vanish after the night, and how to keep the one thread that mattered.

Two weeks after the reunion, one name is missing

Two weeks after the fifteen-year reunion, the class Facebook group is still busy. Photos from the bar. A slideshow somebody scanned from the yearbook. A thread about who flew in from where. And somewhere in that scroll is the classmate who told you, near the end of the night, that their team was hiring for exactly the role your partner has been trying to land.

You can't find them.

You remember the conversation. You remember the drink in your hand and the song that was playing. What you don't have is a name you're sure of, because you spent the night calling people by nicknames from 2011 and nodding at faces you half-recognized. Scroll the group's member list and three people could be the one. Messaging all three to ask "were you the one hiring?" feels worse than letting it go.

So the lead dies in a group chat. That's the reunion follow-up failure, and it happens at the one kind of event people never plan capture for.

The familiarity discount

Reunions fail differently from conferences. At a conference, everyone knows the encounter is transactional, so people swap cards, scan badges and jot a note on the back. The social contract makes capture normal.

A reunion runs on the opposite contract. Writing someone's details down feels like admitting you don't know them, and the whole night depends on the pretense that you do. Call it the familiarity discount: because the person feels like an old friend, you discount the need to record anything about them.

But most of the people in that room are near-strangers. You shared a hallway, a dorm floor, maybe one chemistry lab, and then ten or fifteen years of separate lives. The version of them you know is out of date in every detail a follow-up needs: where they work, what they do, where they live, what they're looking for.

Nostalgia covers the gap for one evening. It doesn't carry a relationship into Tuesday.

Nostalgia covers the gap for one evening. It doesn't carry a relationship into Tuesday.

Why "they're in the alumni group" doesn't save you

The standard reassurance goes like this: you don't need to capture anything at a reunion, because everyone's in the alumni group, the class Facebook page, the LinkedIn school filter. You can always look them up later.

Looking someone up requires knowing who to look up, though. An alumni directory is a list of names. It holds none of the context from the conversation: who mentioned the job opening, who's moving to your city in the spring, who asked whether you still do contract design work. That context is the whole asset, and it lives only in your head, where it starts fading on the drive home.

Reunion conversations also run long and wide. A conference exchange is a few minutes about one thing. A reunion catch-up can run an hour across marriages, kids, career changes and the friend who didn't make it, with one actionable line buried in the middle. More context gets generated and less of it survives, because none of it felt like business while it was happening.

Are old classmates worth reconnecting with?

Yes, and the research points the same way. Mark Granovetter's 1973 paper "The Strength of Weak Ties" argued that acquaintances outside your close circle are where new information, job leads included, tends to come from. A 2022 experiment published in Science, run with LinkedIn across more than 20 million users, found that moderately weak ties (people you share some connections with but aren't close to) were the most useful for job mobility.

A reunion room is packed with exactly those kinds of ties: shared history, real trust, almost no current overlap. The value is there. What's missing is any record of what each person told you.

One reunion, walked through

Take a ten-year reunion on a Saturday night. You talk to maybe a dozen people in any real way. Three of those conversations contain something you'd act on: a classmate who just started a firm in your industry, one whose company is hiring, and one relocating to your city next year.

At a conference, you'd leave with three cards and three quick notes. At the reunion you leave with three warm memories and zero records. By the following weekend the details have blended. Was the founder the one moving, or the one hiring? Was the move this spring or next?

The fix is small, and it has to happen in the room or in the car before you start the engine. Three fields per person are enough. What they do now. The live thread (the opening, the move, the ask). And the shared anchor you'd open a message with. The comparison below shows where reunion capture breaks from conference capture.

Conference contactReunion contact
Default social normCapture is expected (cards, badge scans)Capture feels awkward, so it's skipped
Conversation shapeShort, one topicLong, many topics, one actionable line
What you think you knowAlmost nothing, so you write it downTheir past self, which feels like enough
What the follow-up needsWho they are and what they askedWho they are now and the live thread
Best openerThe topic you discussedThe live thread first, the shared history second
Capture differences by occasion type. Observational comparison, not survey data.

Follow up on who they are now

If the familiarity discount is real, the reunion follow-up needs a different opener. The instinct is to lead with the past: "so great to see you, can't believe it's been ten years." That message is pleasant, gets a heart reaction, and ends the thread.

The stronger opener names the live thread first and lets shared history supply the warmth. "You mentioned the analyst opening on your team. My partner's been looking for exactly that role, could I introduce you? Also still laughing about the field trip story." The past earns the reply. The present gives it somewhere to go.

Because the trust already exists, you've got some slack on timing. What you can't fake is the detail. A reunion message that names the actual thing you talked about reads as attention. One that doesn't reads like a note to the whole class list.

Treat the reunion like an event, because it is one

Met was built for conference floors, and the mechanics transfer cleanly to a reunion. Turn on Event Mode when you walk in and the night's contacts stay grouped together, so two weeks later you're looking at the people from that room instead of the entire class group. Add the live thread to the contact while it's fresh (the opening, the move, the ask) and the follow-up starts from the detail you'd otherwise lose. Event Mode is a rapid-capture mode you start from an event: each scan is filed under that event automatically, a live counter tracks how many people you've met, and a post-event wrap-up lets you follow up afterward. You don't need a business card to add someone. You can enter a contact manually and attach context such as where you met, what you talked about, and tags.

Everything stays in your own iCloud. For a room of old classmates that matters: what they told you was said as a friend, and it shouldn't end up on someone else's server.

Conference memory decay has its own timing, covered in our piece on the 72-hour memory cliff. Reunions need a simpler habit. Three fields per person, captured before you leave the parking lot.

Keep the people from the reunion, and what they told you. Get Met.

Met is built for people whose work runs on remembering who they met and what was said: founders, recruiters, consultants, advisors. It keeps each event's contacts together with the context that makes a follow-up specific, stores everything in your own iCloud, and shows no ads. A reunion is one more room full of people worth keeping, and the same capture habit applies.

Get Met in your inbox

Field notes on conference networking, follow-up timing, and what we ship next. No spam, no AI hype.

No spam. Unsubscribe anytime. Replies go to support@sailquery.com.