Article · Use case

Networking events: a tagging system that survives Monday

The fundamental problem

Networking events compress what would normally be twenty separate first-meetings into a single afternoon. Every introduction is short, the room is loud, and you're under social pressure to keep moving. The result, predictably: dozens of half-formed memories, a small stack of business cards, and almost no usable record of who you met.

The fix is not about trying harder during the event. You need a small, repeatable system that captures just enough at the time, and lets you reconstruct the rest the next morning while the day is still fresh.

Before the event

Five minutes of prep saves an hour of post-event mess.

  1. Create one tag for the event. "TechCrunch Disrupt 2026" or "Sara & Mike wedding," specific enough that you'll remember it. See the tags guide.
  2. Pre-tag people you already know who'll be there. If three of your existing pals are attending, tag them with the event name now. They become anchors when you scroll the network later.
  3. Write a goal. Not a sales target. A memory anchor. "Want to follow up with two people on the AI panel" gives you a frame the next morning.

During the event

Don't try to add full profiles in the moment. Two reasons: it's awkward, and the next-in-line effect [1] will eat your capture quality the second you start composing notes mid-conversation.

Instead, capture just enough to reconstruct from:

Don't capture in front of them

The exception is asking to add them in betterpal openly. Some people love it, especially in tech-friendly contexts. But the default should be: capture out of sight, never let it interrupt the actual conversation.

The morning after

This is the highest-leverage 30 minutes of the entire process. Do this before you check email or Slack.

  1. Walk through your captures. For each quick-entry note from yesterday, open the person and add what you actually remember while it's fresh: the gist of the conversation, what they were working on, anything you said you'd send them.
  2. Add the event tag to everyone you met. Two taps each.
  3. Add cross-tags where they fit. "AI panel," "VC dinner," "Booth 12." Granular sub-tags become useful months later when you're trying to remember a specific room.
  4. Link relationships for the obvious connections: "met through Sam," "works with Priya."
  5. Set follow-up reminders for the people you actually owe something to. A note with a 5-day reminder is the difference between a real follow-up and a permanent intention.

Three months later

The tagging system either pays off here or it doesn't. If you've done the morning-after pass:

Common patterns

Conferences

Tag with conference name + year. Sub-tag by panel/booth/dinner. Tag any people you met as a group ("AI dinner Tuesday"). Useful when one of them follows up.

Weddings

Tag with the couple's names + year. Cross-tag with relationship to bride/groom ("college friends," "his side"). Note the table you sat at if relevant. Add the kids' names if you met them.

Recurring events (book clubs, run clubs, monthly meetups)

One tag for the recurring event. Inside that, you accumulate context over time. The Network view eventually becomes a useful picture of who really shows up and how the group connects.

One-on-one coffee chats

Tag with "intro coffee" or similar. Set a follow-up reminder for two weeks later when the conversation is still recent enough to seem natural and not awkwardly delayed.

What this isn't

This isn't a CRM. There are no scoring fields, lead stages, or pipeline buckets. The point is to remember people, not convert them. If you start treating networking events as a leaderboard you'll write less, not more, and the system stops being honest.

References

  1. Brenner, M. (1973). The next-in-line effect. Summarized in the Noba Project, Memory: Encoding, Storage, Retrieval.