To keep track of people you meet, you need three things: one record per person that accumulates rather than duplicates, context captured within the hour of meeting them, and a date attached saying when you'll next make contact. Storage alone isn't tracking. Most contact logs have the first part and neither of the others.
TL;DR
- Tracking is three parts: one record per person, context captured fast, and a next date. Miss any one and the system quietly stops working.
- A contact log that only stores people is an address book with extra steps.
- Capture within the hour. By the next morning you're transcribing a business card, not recording a conversation.
- The failure is never on day one. It's at month four, when updating has become optional and nothing has broken.
- The minimum honest version is a spreadsheet with a date column and a weekly review. If you'll actually run it, use that.
How do I keep track of people I meet?
Three parts, and the order matters less than having all three.
One record per person. Not one row per meeting, not a new note each time. When you meet someone again, that encounter has to join the existing record, or you end up with fragments that individually mean nothing. This is where most phone-based approaches break immediately — a contacts app treats a second meeting as a duplicate or an overwrite.
Context captured close to the event. Where you met, what they do in your words, what they were after, what you promised. None of it is on the business card and all of it decays fast.
A date for the next contact. This is the part almost everyone skips, and it's the part that turns a list into a system. Without it you have a well-organised archive that you'll never open, because opening it requires already remembering the person.
What has to be true for a tracking system to survive?
Something has to break when you stop feeding it.
That sounds abstract until you look at why personal systems actually die. Not difficulty — my own contact spreadsheet was easy to update, and I updated it plenty of times. What killed it was that nothing depended on it. No process failed when it went stale. No colleague asked. So updating became something I did when I felt like it, which degraded from reliable to patchy to nothing across about four months. Read the full version in personal CRM vs spreadsheet vs Notion template.
A work CRM survives because a manager runs a forecast off it on Friday. A personal one has no such enforcement, so you have to build the enforcement in — either an appointment that exists whether you feel like it or not, or a system that surfaces the work rather than waiting for you to go looking for it.
Everything else is preference. This part isn't.
What should I capture, and when?
The window matters more than the fields.
- During the conversation
- What you can still capture: Everything, but you're not listening properly while you type
- What's already gone: —
- Within the hour
- What you can still capture: What they were looking for, how they came across, what you promised
- What's already gone: Nothing important
- Same night
- What you can still capture: The gist of the conversation, roughly
- What's already gone: The specific phrasing, the small asides
- Next morning
- What you can still capture: Name, company, event
- What's already gone: What they actually said
- A week later
- What you can still capture: Whatever's printed on the card
- What's already gone: The person
The row that surprises people is "next morning." It feels responsible to deal with your cards over coffee the following day, and by then you're transcribing a business card rather than recording a conversation. That's why so many people diligently enter every contact and still can't place anyone six months on — they captured accurately, on the wrong side of the decay.
Four fields are enough: where you met, what they do in your own words, what they were looking for, and anything you said you'd do. The last one matters more than its size suggests, because a forgotten casual promise damages a new relationship faster than silence does. More on the capture side in how to remember people you meet.
What does my own system ask of me?
I'll describe it in measurements rather than adjectives, because that's the only honest way to talk about a routine.
There are two ways in. If I have the card, I photograph it: seven taps on a clean card, roughly 15 to 20 seconds start to finish, with about two to three seconds of that being the model reading the card. That returns five fields — name, title, company, phone, email — which is everything a card physically contains.
If I don't have a card, or the conversation was worth more than the card, I describe the person in a sentence or two instead. That takes 30 to 45 seconds, because composing is the work; the parse afterwards costs the same two to three seconds. It returns twelve fields rather than five, including how we met, what they're looking for, and what they offered.
So the sentence path is slower and more valuable, which is the trade at the centre of this whole problem. Speed of capture is a solved problem. What a card can't hold is the part you'll be missing.
Then the third part, which is the one that makes it tracking rather than filing. When I save someone, I set a follow-up date myself — right then, while I still remember why it would be worth contacting them. When that date comes due, opening the dashboard puts the person in front of me along with the notes I wrote at the time. My own words, not an explanation the system invented about why they matter.
Two things it deliberately doesn't do. It doesn't decide for me who's become relevant, and it doesn't run in the background — nothing gets raised that I didn't schedule, and I still have to open it. That's a smaller claim than this category usually makes and I'd rather make the smaller one.
Habitus Mind is invite-only and admin-approved. There's no public signup. Request access.
Where do most contact logs fail?
Three places, in rough order of frequency.
No date field. The log stores who, never when. It's complete, accurate and inert. This is the most common failure by a distance and the easiest to fix.
One row per meeting. Meet someone three times and you have three rows, none of which tells the whole story, and no obvious way to merge them without a manual tidy-up you'll never do.
Captured too late. The entries are all technically correct and contain nothing you couldn't read off the card, because they were written the following week.
Notice that none of these are storage problems. The log itself is usually fine. What's missing is the structure that would make you open it again.
What's the minimum viable version?
A spreadsheet with five columns and a weekly review. If you'll actually run it, stop reading and go build that.
Columns: name, where we met, what they're looking for, what I owe them, next contact date. Sort by the last column. Open it on a fixed day — the same day every week, in a calendar slot that exists whether you feel like it or not — and work down the rows that have come due.
That's genuinely most of what any tool in this category does. It's free, you own the file, and it stores more per person than a phone contacts app ever will.
Its single weakness is that it depends entirely on you continuing to open it, which is also exactly how mine died. If you've kept a personal system running past six months before, that's not a real risk for you. If you've already abandoned two, the tool was never the variable, and a third one you have to maintain by hand will end the same way.
FAQ
How do I keep track of people I meet?
Keep one record per person that accumulates over time, capture context within the hour of meeting them, and attach a date for the next contact. Storage without a date is an archive — complete, accurate, and never opened, because opening it requires already remembering the person.
What should a contact log include?
Where you met, what they do in your own words, what they were looking for, and anything you promised. Plus a next-contact date. The printed details from the business card matter least, because those are the parts you can always recover later.
How soon after meeting someone should I write it down?
Within the hour. Same night still works for the gist. By the next morning you're transcribing a business card rather than recording a conversation, which is why so many carefully maintained contact lists are full of people the owner can't place.
Why do contact logs stop being updated?
Because nothing breaks when you stop. A work system survives because someone downstream notices errors; a personal one has no such pressure, so updating stays optional every day and typically degrades to nothing around month four.
Is a spreadsheet good enough for tracking contacts?
Yes, if you add a next-contact date column and run a fixed weekly review. It stores more per person than a phone contacts app and costs nothing. The weakness is that it depends entirely on you continuing to open it.