A Job Search Tracker You Will Actually Keep Using

Why the spreadsheet gets abandoned

Almost everyone starts a job search with a tracker and most of them stop updating it inside a fortnight.

The reason is consistent. The first version has twenty columns, because building the tracker feels productive in a way that applying does not. Then every application carries fifteen minutes of data entry on top of the application itself, the entry gets deferred, three days of backlog accumulate, and the whole thing is written off.

A tracker earns its place only if maintaining it costs less than the mistakes it prevents. Those mistakes are real: applying twice to the same company, walking into an interview without remembering which version of your resume they have, letting a promising conversation go cold for three weeks, and losing the thread on which recruiter said what.

So the design goal is not completeness. It is the smallest thing that prevents those four failures.

The columns worth keeping

Nine fields cover it. Anything beyond these is optional and most of it will not survive contact with a busy week.

• Company and role. One column each, so you can sort by company and catch duplicates.
• Date applied. The anchor for every follow-up decision.
• Source. Where the role came from: a board, a referral, direct outreach, the company site. This is the field people skip and later wish they had.
• Stage. A short list, not free text. Applied, screening, interview, final, offer, rejected, no response.
• Contact. Name of the recruiter or manager, and where the conversation lives.
• Resume version. Which file you sent, so you can reread it before the interview.
• Next action. One short phrase for what you owe them or they owe you.
• Next action date. The most valuable column in the sheet.

That last pair is what separates a tracker from a list. A list of applications is a record of the past. A next-action date turns the same rows into a queue of work for this week, which is the only form of the document you will open voluntarily.

Copy the job posting text into a notes column too, or save the page. Postings are taken down the moment a role is filled, and being unable to reread the description before an interview is a genuinely annoying way to lose ground.

The weekly review

Twenty minutes, once a week, at a fixed time. This is the entire maintenance burden and it replaces daily updating, which nobody sustains.

Work through it in four passes. Sort by next-action date and do everything overdue, which is usually two or three follow-ups. Then move anything with no response after two weeks to a dormant stage rather than leaving it live, because a list full of dead rows stops feeling worth opening. Then look at your active count. Then decide what to add.

The active count is the number that matters most and it is the one people avoid. Applications in flight, meaning submitted and not yet rejected, minus the ones that have gone quiet for a fortnight. Under about ten and the search is stalling regardless of how busy the week felt.

One clear takeaway: a next-action date turns a record of the past into a queue for this week.

What the numbers tell you after a month

Four weeks of honest tracking answers a question that guessing never will: where the search is actually breaking.

Count applications, screening calls, interviews and offers. The ratios between the stages point at different problems and different fixes.

Few screening calls relative to applications. The resume or the targeting is the problem. Either the document is not clearing the first read, or you are applying to roles that are a stretch. Our tailoring guide covers the fastest version of the fix.

Screening calls but no interviews. Something in the call is not landing. Usually it is the salary conversation, the reason for leaving, or an answer about a gap that sounds evasive.

Interviews but no offers. The competition is closer than it feels and preparation is the lever. This is a better problem than the other two, because it means the resume and the targeting are working.

Low numbers across the board. Volume, not quality. Fifteen applications a month is not a search, and no amount of tuning fixes a sample that small.

The source column pays for itself here. Most people find that the channel producing the most applications produces the fewest interviews, usually a large aggregator, while referrals and direct outreach produce a handful of applications and most of the conversations. That comparison should change how you spend the next month.

The rules that keep it alive

Three habits do most of the work of keeping a tracker current.

Log at the moment of applying, never later. Sixty seconds while the tab is still open, or it does not happen. A row logged three days later is usually missing the source and the posting text, which are the two fields with the most value.

Never log a role you have not applied to. A list of interesting jobs to consider is a different document and mixing them destroys the tracker's meaning. Bookmark those elsewhere.

Do not add a column mid-search. Every new field applies retroactively to rows you will not go back and fill, which leaves gaps that make the sheet feel broken. Start narrow and stay there.

One more thing worth doing at the start: keep a folder of resume versions named by company. Two minutes of naming discipline saves the specific panic of walking into an interview unsure which of four versions they read.

Where to keep it

A spreadsheet is fine and it is what most people should use.

Purpose-built tools exist and they are worth considering only if they cut effort rather than add features. The common failure mode is a tool with pipeline stages, reminders, browser extensions and analytics, where configuring it becomes another way of feeling productive without applying to anything.

Whatever you choose has to work on a phone, because a meaningful share of follow-up decisions get made away from a desk. If updating a row requires opening a laptop, the rows will not get updated.

The search side is separate from the tracking side. Our job search builder handles finding roles across boards, and the tracker starts once you decide to apply to one.

Winding it down

When an offer lands, the tracker has one last job before you close it.

Message anyone still in progress and tell them you are withdrawing. It takes ten minutes across three or four companies, and it is the difference between being remembered well and being remembered as the candidate who vanished. Those same people hire again, often within a year.

Then keep the file rather than deleting it. The next search will start faster with a record of which sources worked, which companies moved quickly, and which contacts replied. Most people search again within three years and start from nothing every time.

Tracking conversations, not just applications

Applications are the easy half. The half that gets lost is the set of people you have spoken to who are not attached to a live role.

A former colleague who said to get in touch when you start looking. A manager who interviewed you for a job that went to someone else and told you to stay in contact. A recruiter who called about a role that was wrong but asked what you would say yes to. Each of those is worth more than a fresh application and each has an expiry date measured in weeks.

Give them their own tab with four columns: person, what was discussed, what you agreed to do, and when to come back. The last one is what makes it work, because these conversations die of silence rather than rejection.

Set the return dates generously. Three or four weeks is normal for a warm contact, and coming back with something small, a question, an update, a piece of news about their industry, keeps the thread alive without asking for anything.

The same tab is where referrals get managed. If someone offers to pass your resume to a manager, log the date and check back after a week, because internal referrals get forgotten by well-meaning people constantly and a single polite reminder recovers most of them.

Search records like this compound. The contacts tab from one search is the fastest starting point for the next one, and it is the part people most regret not keeping.

Questions people ask

What should a job search tracker include?

Company, role, date applied, source, stage, contact, resume version, next action and next action date. Nine fields, and everything beyond them tends to go unfilled.

How often should I update it?

Log each application the moment you send it, then run one twenty-minute review a week. Daily updating is unnecessary and almost nobody keeps it up.

How many applications should be active at once?

Around ten to fifteen live at any time. Below that, ordinary rejection rates mean the search stalls whatever else you do well.

Should I use a spreadsheet or an app?

A spreadsheet, unless a tool genuinely reduces the work. Configuring a feature-rich tracker is a common way to feel productive without applying.

What do the numbers tell me?

Applications with few screening calls point at the resume or the targeting. Interviews without offers point at preparation. Low totals everywhere point at volume.

Related reading

• Self Review Examples That Do Not Undersell You
• How to Get Promoted: Building the Case Before You Ask