Do not follow up with everyone. Give each contact a quick score for specific shared context, mutual relevance and a credible next action. Send prompt messages when all three are strong, save promising but premature contacts for a defined later trigger, and release encounters that offer no clear reason to continue. The purpose is not to rank people; it is to replace an exhausting open-ended obligation with a small, defensible queue.
Capture enough detail to make a decision
Before sorting contacts, record what actually happened: the person’s name, where you met, the subject you discussed and any commitment either of you made. The Entrepreneur networking guide recommends making a short note after a conversation so the name and identifying details remain available later. A usable note might read: “Mina, regional design meetup, onboarding problems, recommended a research newsletter.”
A basic post-event email can simply acknowledge that it was good to meet, but continued contact is more useful when it has a reciprocal purpose. The same guide describes strong networking relationships as two-way: people may introduce or advocate for each other and notice relevant opportunities. That does not require immediate equivalence; it does suggest looking beyond “What can this person do for me?”
- For each name, write one sentence beginning, “We spoke about…” If you cannot finish it specifically, mark the context as weak.
- Record any promise, such as sending a link, making an introduction or answering a question. A promise takes priority over the scoring exercise.
Use the three-part contact score
Use this suggested triage score rather than trying to judge whether someone is generally “valuable.” Give zero, one or two points in each category. For shared context, use zero if you barely remember the exchange, one for a general topic and two for a distinct detail. For mutual relevance, use zero when no connection is apparent, one for a plausible overlap and two when both people expressed a relevant interest or need.
For credible next action, use zero when you cannot name one, one for an idea that still needs clarification and two for a specific, modest step: sending the promised article, arranging a short conversation or making an appropriate introduction. Add the three scores. This is an editorial sorting tool, not a measure of a person’s worth or a prediction about the relationship.
- Five or six points: prompt follow-up. There is enough shared context and a concrete reason to write while the conversation is still easy to identify.
- Three or four points: later reconnection. Preserve the note, but attach it to a genuine trigger rather than repeatedly reminding yourself to “keep in touch.”
- Zero to two points: release. Keep the card only if required for another purpose; otherwise, take no networking action.
- Override the total when you made a clear commitment, the person requested a reply or continued contact would cross a personal or professional boundary.
Write the smallest message that completes the job
A useful prompt follow-up has three parts: recognition, relevance and one next step. Try: “Hello [Name], I enjoyed our conversation at [event] about [specific subject]. You mentioned [detail], so I’m sending [resource] as promised. No reply needed, but I hope it is useful.” Removing the demand for a response is appropriate when delivery, not discussion, is the whole purpose.
When you want another conversation, make the request bounded: “Hello [Name], it was good to meet you at [event]. Your point about [detail] stayed with me because [brief relevance]. Would you be open to a 20-minute call in the next few weeks to compare notes on [defined topic]? If now is busy, no problem.” Adjust the duration or channel to match what you can comfortably offer.
For a later reconnection, do not send a placeholder message merely to keep a thread alive. Log a trigger instead. When that trigger occurs, write: “Hello [Name], we met at [event] and discussed [subject]. You mentioned [specific interest]. I saw [opportunity, development or resource] and thought it might be relevant. Would you like me to send the details?” For the release path, the template is intentionally blank: no message is required.
Distinguish a real trigger from indefinite postponement
“Contact someday” leaves the decision active in your head. A later-reconnection entry should name an observable reason to return: the publication of the person’s project, your completion of a related piece of work, registration opening for a relevant event, or the arrival of information they explicitly wanted. If no credible trigger exists, release may be more honest than maintaining a permanent maybe-list.
- Write the trigger as an event, not a mood: “When applications open,” rather than “When I feel more social.”
- Add a review date only when the opportunity itself is date-dependent. Otherwise, let the named event prompt the contact.
- Delete later entries that remain vague after review. A contact log should reduce mental load, not archive guilt.
Worked example: three conversations, three paths
Suppose Alex leaves a conference with three names. Priya discussed a specific reporting problem, said she was comparing tools and asked Alex to send a checklist. She receives two points in every category: six total and prompt follow-up. Alex sends the promised item with a short note and no extra request.
Jon and Alex discovered that their teams may attend the same autumn workshop, but neither has information yet. Their context is specific, mutual relevance is plausible and the next step depends on registration details: four points and later reconnection. Alex logs “when workshop registration opens” rather than sending a generic check-in.
Sam exchanged brief introductions with Alex in a crowded line. Alex remembers no shared topic, request or next action. That produces zero points and the release path. Sam may be pleasant and professionally accomplished; neither fact creates an obligation. If they meet again, they can begin from that new encounter without treating the first one as unfinished business.
Keep a log that shows only what matters next
A lightweight log can live in a notes app, spreadsheet or contact record. Use one line per person: name; event and date; shared topic; identifying detail; promise made; context score; relevance score; action score; chosen path; next action or trigger; message date; response; and one follow-on note. Leave fields blank when they do not apply.
After sending, record the outcome once. If there is no response and no unfinished commitment, close the entry instead of repeatedly drafting new approaches. If the person replies, decide on the next step from the actual reply—not from the original score. The queue has done its work once it turns an ambiguous encounter into a completed action, a defined trigger or a deliberate release.
- Process names in one short session while conversation details are still available.
- Complete promised actions before optional relationship-building messages.
- Personalize with one accurate detail rather than a long recap of the event.
- Ask for only one next step in each message.
- Close entries that have no commitment, trigger or current reason to continue.