How to organize contacts after a conference — in one evening

You’re home. The lanyard is on the desk, fourteen business cards are in your jacket pocket, nine LinkedIn requests are pending, and somewhere in your phone are photos of two badges and a flip-chart. This is the moment that decides whether the conference was worth attending — and it takes one evening, not a new productivity system.

Why this has to happen tonight (or tomorrow morning)

The names on the cards are safe — cardboard doesn’t forget. What’s evaporating is everything that makes those names worth keeping: which conversation belonged to which face, who mentioned the stalled migration, whom you promised the report. Memory researchers have measured this decay for over a century, starting with Ebbinghaus (1885), and the unhappy headline is that the steepest losses happen within the first day or two. We unpack the science — and what it means for the wording of your first message — in how to follow up after a networking event.

For the organizing evening itself, the implication is simple: speed beats polish. A scrappy list written tonight, with real context next to each name, is worth more than a beautiful database built next weekend from guesses. Budget about 90 minutes for a typical 30-contact conference and protect that slot the way you’d protect the conference ticket price — it’s the part of the investment that actually compounds.

One mindset note before the workflow: you are not building an archive, you’re building a follow-up queue. The output of the evening is not “all my contacts are filed”. It’s “I know exactly who gets a message, when, and about what.”

For multi-day conferences, add a nightly micro-version: ten minutes in the hotel room to annotate the day’s cards and dump names with a line of context while they’re hours old, then run the full triage once you’re home. By day three you will not remember day one — the micro-pass is what keeps a 300-person event from arriving home as mush.

The one-evening workflow

1. Gather every capture channel into one pile

   Cards from the jacket and the laptop bag. Photos of badges and cards in your camera roll. Pending LinkedIn requests, sent and received. The badge-scan export from the conference app — download the CSV now, while the link still works. Voice memos, notes-app fragments, the napkin. The point of this pass is purely mechanical: one list, one screen, nothing left in a pocket to surface in three weeks as a mystery.

2. Deduplicate while you can still tell people apart

   The same person arrives as a scan, a card, and a LinkedIn request — often with two job titles and three spellings. Merge each human into one record now; tonight it takes seconds per person, in six months it’s forensic work. If your address book is already carrying years of this debris, a contact-dedup pass is worth running while you’re at it.

3. Attach context to every name — 90 seconds each

   For each person, write four things: where you met, what you discussed, what’s open in either direction, and one personal detail. This is the pass that cannot be postponed, because it runs entirely on your memory. Don’t polish sentences — telegram style is fine. If a name produces nothing after 90 seconds, that’s information too: note where you met and move on.

4. Triage into three tiers

   Tier A — an open loop exists: something promised, a concrete next step discussed, a real click. Tier B — genuine mutual interest, nothing concrete yet. Tier C — pleasant and complete. Be ruthless about C; it usually holds 60–70 % of the pile, and admitting that is what makes A and B manageable. Tier C people get a LinkedIn connection or a one-line archive note, and that is a perfectly respectful outcome.

5. Put dates on A and B, then send three messages

   Tier A follows up within 48 hours; tier B within two weeks, ideally with something of value attached. Load the queue into a conference follow-up tracker — one row per person, context, tier, next action, date. Then, before you close the laptop: send the three most important tier-A messages tonight. Nothing fights procrastination like having already started.

What to send instead of the blast: the three-part message — a hook from the conversation, something delivered, one small ask — takes about four minutes per person once the context note is in front of you. That per-message cost is exactly what the evening’s capture work buys down.

Prioritizing honestly: open loops beat job titles

Most triage goes wrong in one predictable way: it sorts by impressiveness. The VP of a company you admire lands in tier A on title alone, while the freelance consultant you spent forty real minutes with — and promised a tool recommendation — sinks to B. That’s backwards. Follow-up converts where a thread already exists, and a thread is an open loop: something promised, a problem both of you touched, a conversation that visibly wanted to continue.

The honest tiering question is not “how useful could this person be?” but “what is actually open between us?” If the answer is nothing, no amount of seniority makes a follow-up land — there’s nothing to follow up on. You can absolutely keep ambitious contacts in tier B and build a loop deliberately, with a value-first message. But that’s a plan you make consciously, not a tier you assign out of awe. If the whole topic of building relationships before you need them is on your mind, how to network authentically takes the long view.

A second honesty check: energy. Some conversations were mutual; some were polite. You know the difference, and so does the other person. Tiering a one-sided conversation as A doesn’t make it mutual — it just schedules a disappointment.

Concretely, a typical 30-contact haul shakes out something like this: four or five tier-A people (two promised intros, a sales conversation that wants a demo, the engineer you genuinely clicked with), seven or eight tier B, seventeen-plus tier C. That converts to five messages tonight and roughly one every other day for two weeks — a workload that fits inside a normal life, which is the point. The unsorted version of the same pile reads as ‘thirty follow-ups, someday’, and someday is how an entire conference quietly becomes a rubber-banded stack in a drawer. Triage doesn’t just prioritize; it shrinks the job until it stops being avoidable.

After the evening: from list to system

The evening produces a queue; the weeks after produce the relationships. Three things keep the queue from rotting.

First, the interaction log keeps growing. When a tier-A person replies, note what was said and set the next date. A contact whose record ends at the conference is a contact you’ll re-meet as a stranger next year.

Second, dates need an enforcement mechanism. A spreadsheet column named next action is a wish; something has to make it ring. Calendar reminders work at small scale. Past a few dozen active contacts, this is the specific job a personal CRM exists for — Endearist, ours, fires the reminder and shows you the context note next to it, so the follow-up writes itself. Whether that category fits you at all is a question we answer honestly — including “probably not” — in when you actually need a personal CRM.

Third, the physical cards still on your desk: capture, verify, recycle. If throwing them away feels wrong, what to do with business cards makes the case — the card was never the asset. The note you wrote tonight is.