Most job searches are run from memory and a browser with forty tabs open. That works for about two weeks. After that you start forgetting which version of your resume went where, missing follow-ups, and applying twice to the same company — and, more damagingly, you lose the ability to tell whether your search is working, because you have no record of what you did.
A tracked search fixes both problems. It takes about twenty minutes to set up and a few minutes a day to maintain.
What tracking gives you
- Diagnosis — where applications are dropping off, so you fix the right thing
- Follow-ups that actually happen, on time
- Interview preparation from your own notes rather than memory
- Evidence of progress on the weeks when it feels like there is none
The tracker
A spreadsheet is sufficient and generally better than a dedicated tool, because you can change it. One row per application.
| Column | Why |
|---|---|
| Company | Prevents duplicate applications |
| Role title | Shows which titles convert |
| Date applied | Drives follow-up timing |
| Source | Which channels actually produce responses |
| Resume version | So you know what they read |
| Contact name | Who to follow up with |
| Status | Applied / Screen / Interview / Final / Offer / Rejected / No response |
| Next action + date | The column that makes the whole thing work |
| Salary range | Keeps your expectations calibrated |
| Notes | Names, questions asked, what they said about the role |
Add one more thing: a link to the job description, and a copy of its text pasted into a document. Postings get taken down, and you will want the description when you are preparing for the interview three weeks later.
Stages, and the numbers to watch
Think of the search as a funnel. Each stage has a conversion rate, and knowing which one is failing tells you what to fix.
- Roles identified → how many you actually apply to
- Applications → responses of any kind
- Screens → first interviews
- First interviews → later stages
- Final stages → offers
Roughly speaking, 5–15% of well-targeted applications producing a response is normal. If you are below 3% across thirty or more genuinely matched applications, the problem is upstream — targeting or documents — and sending more applications will not fix it.
The most common error in a job search is treating every problem as a volume problem. If you are getting interviews and not progressing, more applications is precisely the wrong response — you need interview practice. Tracking is what tells you which it is.
Follow-ups, scheduled
The “next action” column is what turns a record into a system. Every row always has a next action and a date, even if the action is “close as no response.”
A reasonable default schedule:
- Day 0: apply. Next action: follow up on day 12.
- Day 12: one short follow-up if no response. Next action: close on day 21.
- Day 21: mark as no response and stop thinking about it.
- After any interview: thank-you note within 24 hours. Next action: the date they told you, plus two days’ grace.
- At the timeline they gave: one polite check-in.
One follow-up per stage. A second unanswered chase does not help and occasionally harms.
“Hello — I applied for the Operations Manager role on 4 September and wanted to check the application arrived, and whether the timeline is still as advertised. Happy to send anything further that would be useful.”
“Thank you for the conversation this morning — I enjoyed it, and the detail about the reporting pack being rebuilt by hand each month was useful context. It is close to what I dealt with at Beta, and it makes the role more interesting rather than less. Do let me know if anything else would help.”
“Hello Dele — you mentioned decisions would be made by the end of last week, so I wanted to check in. No rush if timelines have moved; I am still very interested.”
Preparing from your own notes
When an interview is booked, your tracker should already contain the job description, who you spoke to, what they said about the role, and anything unusual about the process. That turns preparation from an hour of reconstruction into fifteen minutes of review.
Add after every interview, while it is fresh:
- Who you met and their role
- Every question you were asked
- Anything you answered badly — this is the highest-value note you will take
- What they told you about the team, the problem, and the timeline
- What you promised to send
The list of questions you were asked, accumulated across a search, becomes an accurate prediction of the next interview, because the same questions recur.
Managing versions
Keep one master resume and a small number of variants — usually one per target role type. Name files so the employer can read them: Marcus-Reed-Resume-Operations.pdf, not resume_final_v3_ACTUAL.pdf.
Record which variant went where. When a recruiter calls about an application from three weeks ago, you want to know what they are looking at.
A weekly review
Twenty minutes, same time each week:
- Update every status. Close anything past 21 days.
- Count the funnel. Applications, responses, interviews this week and cumulatively.
- Find the drop-off. Which stage is losing you the most?
- Check the sources. Which channels produced responses? Do more of those.
- Set next week’s target. A specific number of applications and conversations.
- Pick one improvement. One thing to fix — a resume section, one interview answer, one company list.
This review is also what protects you psychologically. On a week with no responses, the tracker shows you did the work, and that the work is the part you control.
Handling rejection in the system
Mark it, note any reason given, and where you reached a late stage, ask for feedback. Then keep the row — rejected companies re-open roles, and a rejection at final stage often means you were close enough to be worth a second look in six months. Note the hiring manager’s name for that reason.
Common questions
Is a spreadsheet really better than a job search app?
For most people, yes — it is free, it works offline, and you can change the columns when your search changes shape. Dedicated tools add browser extensions that capture postings automatically, which is genuinely convenient. Either works; not tracking at all does not.
How many applications should I have live at once?
Five to ten. Enough that no single process determines your outcome, few enough that you can tailor each one properly and prepare properly when they convert.
Should I apply to several roles at the same company?
Two, at most, if they are genuinely different and you match both. Applying to six signals that you have not read any of them. Where a company has an internal recruiter, ask them which is the better fit rather than guessing.
What do I do about applications that go completely unanswered?
Close them at 21 days and stop thinking about them. Most applications are never answered; it is a widespread failure of employer practice and it carries no information about you.
Should I tell an employer I have another offer?
At offer stage, yes, if it is real — it is legitimate and effective information. During earlier stages, saying you are in process elsewhere can usefully accelerate a slow timeline. Do not invent one.
