Staying organised3 min read
Did I already apply here? Keeping track without a spreadsheet
You are looking at a posting that seems familiar. Same company, similar title, and something about the second paragraph rings a bell. You may have applied in March. You may have read it and decided against it. You genuinely cannot tell.
So you either apply again and risk looking disorganised, or skip it and risk missing a role you wanted. Neither is a good option and both cost you a few minutes of low-grade dread.
Why the spreadsheet always dies
Almost everyone starts a tracker. Company, role, date, link, status, notes. It works beautifully for about two weeks.
It dies for a structural reason, not a discipline one. The tracker asks for effort at exactly the moment you have the least of it: immediately after finishing an application, when the only thing you want is to close the tab. The reward for filling it in arrives weeks later, and only occasionally. Any system with that shape, high cost now, vague benefit later, loses to being tired.
It also dies because it goes stale asymmetrically. You log the applications. You do not log the rejections, because they arrive as email you skim and delete, and updating a row to say "no" is a small act of self-flagellation nobody volunteers for. Within a month the tracker is a list of things that might still be alive, which is worse than nothing because it looks authoritative.
What tracking is actually for
Worth being clear about why you want the record, because it changes what the record needs to be.
It stops duplicate applications. It tells you which version of your résumé went where, which matters when someone calls. It tells you whether you are applying at the rate you decided to apply at, which is the number most likely to quietly collapse without you noticing. And it gives you something to look at on the bad days that proves you have been working, which matters more than it sounds.
Notice what is not on that list: a detailed status pipeline. Most people build a tracker with six status columns and use two of them.
A version that survives
Record at the moment of sending, automatically if possible, never later from memory.
Capture the four things that are genuinely load-bearing: company, role, date, and which résumé went out. Everything else is optional and everything optional will be skipped.
Treat silence as the default outcome rather than a state to update. If you only record what went out and when, the record stays true without maintenance. A row that says nothing came back after six weeks is complete information.
Make the weekly count visible, because it is the number that tells you whether the search is still moving.
Where ApplyPipe fits
Because ApplyPipe sends the applications, it also keeps the record, which sidesteps the entire problem. Every role it applied to is logged at the moment it went out, with the date and the role attached, and nothing depends on you remembering to write it down while tired.
You can look up whether you already applied somewhere and get an actual answer. The count is there without you counting.
The short version
Your spreadsheet did not fail because you lack discipline. It failed because it demanded effort at the worst possible moment and paid out much later. Record automatically at the point of sending, keep only the fields you will actually use, and treat no reply as the normal outcome rather than a status to maintain.