The Best Way to Track Job Applications (and the Column Everyone Forgets)

The short answer

Track five things per application: the company and role, the date you applied, the stage it is in, the next action with a date attached, and where the lead came from. The source column is the one people leave out and the one that eventually tells you which channel is worth your time. A dated next action matters more than a tidy sheet, because undated intentions do not get done.

You applied to a role six weeks ago. A recruiter calls this morning, and you cannot place the company, cannot remember which version of your resume you sent, and the posting itself has been pulled. That moment, not some abstract urge to be organized, is why people start tracking applications.

A spreadsheet handles the first ten fine. Past that it fails in three specific ways: you stop updating it because logging each status change by hand is tedious, it has no sense of time so follow-up windows pass unnoticed, and it cannot tell you anything, so patterns in your own search stay invisible.

What belongs in each row?

• Company and role, with a link to the posting. Postings get pulled, so save the text, not just the URL.
• The date you applied. This is what makes a follow-up window visible instead of theoretical.
• Stage: applied, screening, interviewing, offer, closed. Five values are enough; more becomes admin.
• The next action and the date it is due. Not "follow up", but "email the recruiter on the 22nd".
• Source: job board, referral, recruiter outreach, direct application. This is the column everyone forgets.

The source column earns its place slowly. After thirty applications it answers a question you cannot otherwise answer: which channel actually produces replies for you. If referrals convert three times better than cold applications in your own data, that is an argument for spending your week differently, and you will never see it without the column.

Why does a dated next action work better than a to-do list?

Because intentions with a time and place attached get acted on far more often than intentions without one. This is one of the better-replicated findings in behavioural psychology: Gollwitzer and Sheeran's meta-analysis of 94 studies and over 8,000 participants found that if-then plans specifying when and where you will act had a medium-to-large effect on actually following through, compared with holding the same goal in general terms.

Applied here, that is the difference between "I should follow up with them at some point" and "Tuesday morning, email Priya about the analyst role". The second one happens. The first one is how applications quietly die.

How long should you wait before following up?

Five to seven working days after applying is a reasonable default, and one working day after an interview for a thank-you note. There is no research establishing an optimal interval, so treat these as convention rather than fact. What matters more than the exact number is that the note is short, names the specific role, and adds something rather than just asking for a status.

Most candidates never follow up at all, which is a large part of why it works. One follow-up is worth sending. A third one to a generic careers inbox is not, and it is the version people default to when they have no record of what they already sent.

How do you stop the tracker going stale?

Reduce the manual updates, because that is what kills every spreadsheet. The emails you already receive contain the status changes, so the less re-typing between inbox and tracker, the longer the system survives.

Then run a short weekly review rather than continuous maintenance. Fifteen minutes, three questions: which applications have gone quiet and need a follow-up, which follow-ups are due this week, and what the funnel looks like overall. That last one is the point. If thirty applications have produced one reply, the problem is upstream in your resume or your targeting, and knowing that in week two rather than week eight is worth more than any amount of tidiness.

Who it is not for

If you are applying to a handful of carefully chosen roles, a note in whatever you already use is fine and a tracker is overhead. If you have one process running through a recruiter, they are tracking it for you. And if you are using tracking as a substitute for the harder work of applying and talking to people, a beautifully maintained sheet is just procrastination with a nice interface.

How ours works, described plainly: in Mbason AI, each application in the job application tracker gets its own forwarding address. Forward a recruiter email to it and the status updates from the email itself, which removes most of the manual entry that makes trackers rot. There is one-click export to Apple or Google Calendar so the dated next actions sit alongside the rest of your week.

Is a spreadsheet good enough for tracking job applications?

For roughly the first ten applications, yes. Past that the failure is not the format but the upkeep: a spreadsheet only knows what you retype into it, and it has no sense of when a follow-up is due. If you keep yours current and review it weekly, it works fine.

What should you track for each job application?

Company and role, the date applied, the current stage, the next action with a date, and where the lead came from. Five fields is enough. Adding more columns feels productive and usually just increases the maintenance cost until you abandon the whole thing.

How many jobs should you have in progress at once?

Enough that one rejection does not end your search, few enough that you can tailor each application properly. There is no validated number. Watch your reply rate instead: if it is near zero, adding more applications repeats the problem rather than solving it.

Should you keep tracking after you accept an offer?

Close the loop on anything still live, since leaving processes hanging burns relationships you may need later. Keep the record itself. The next time you search, knowing which channels worked and which companies replied is genuinely useful, and you will not remember it otherwise.