Job application tracking works fine for the first fifteen or twenty applications, whatever fits in memory. Past that point, three things fail at once: you cannot remember which CV version you sent where, statuses go stale because updating a spreadsheet is nobody's favourite task, and follow-ups get missed because nothing prompts you to send one. This is a tooling problem, not a discipline problem, and it has a specific, fixable shape.
This guide covers the minimum fields a tracking system needs, a spreadsheet setup that works, where spreadsheets structurally break, the four-stage pipeline that matches how hiring actually happens rather than the ten-stage fantasy pipeline most templates suggest, and a follow-up cadence that reads as organised rather than pushy.
Key takeaways
- Tracking collapses around application 15 to 20, not from laziness but because memory-based tracking runs out of capacity exactly there.
- Six fields are the minimum viable tracker: company, role, date applied, status, CV version sent, and next action. Anything less and you lose information that matters.
- A spreadsheet works fine up to a point. The failure mode is not the tool, it is the missing link between the CV file you sent and the row that represents it.
- Four pipeline stages match reality: applied, interview, offer, closed. Templates with ten stages add ceremony without information.
- A polite, effective follow-up cadence is mechanical, not personality-dependent. The right interval and message template remove the awkwardness that makes people skip following up entirely.
Why tracking collapses after about 20 applications
At five applications, you remember everything. You know which company you applied to on Tuesday, which CV file you attached, and that you are waiting to hear back from the recruiter who said "next week" ten days ago. Tracking is not a separate task, it is just memory.
Past roughly fifteen to twenty applications, three things break at once, which is why the collapse feels sudden rather than gradual.
Versions. If you tailor your CV per application, and you should, you now have fifteen to twenty CV files. Without a system, they end up named CV_v2_final.docx, CV_v2_final_FINAL.docx, CV_company_maybe.docx, and by application twelve you cannot tell which file went to which employer.
Statuses. "Applied" is not static. It becomes "no response," then "interview requested," then "waiting on round two," then "rejected" or "offer." Multiply that by twenty applications moving at different speeds, and keeping each one's state in your head is no longer possible.
Follow-ups. A follow-up sent at the right interval, roughly a week to ten days after applying if you have heard nothing, is a normal, expected part of a job search. One that never gets sent because you forgot which applications were due is a missed opportunity a system would have surfaced.
None of this is really about discipline. It is about a system whose capacity has been exceeded, and the fix is a better system, not more willpower.
The minimum viable fields
Six fields cover the information you actually need to act on an active job search. Fewer than this and you lose something that matters; more than this and the tracker becomes its own chore.
| Field | Why it matters |
|---|---|
| Company | Worth its own column rather than folded into a notes field, so you can sort and search by it. |
| Role | Job title as posted. Useful when you have applied to the same company for two different roles, which happens more often than expected. |
| Date applied | The anchor for your follow-up cadence. Without it, "should I follow up yet" is a guess instead of a calculation. |
| Status | Applied, interview, offer, or closed, kept current. The field that goes stale first if updating it is not made easy. |
| CV version sent | A filename or link to the exact CV file submitted. Almost every spreadsheet omits this, and its absence is the single most common reason a candidate cannot answer a screening call's first question well, walk me through your resume. |
| Next action | What happens next and when: follow up on the 14th, prep for an interview on the 20th, send a thank-you note today. Without this field, a tracker is a log, not a tool that moves applications forward. |
Optional but useful: a link to the original job posting (postings get taken down), the recruiter's name if you have it, and a notes field for anything you will want to recall before a follow-up call.
A spreadsheet setup that works
A spreadsheet handles this well for most job searches, and setting it up properly takes about fifteen minutes.
Start with one row per application and the six columns above, left to right, so the fields you scan most often, company, role, status, sit where your eye lands first. Add a dropdown list, data validation in Google Sheets or Excel, restricted to the four pipeline stages below, for the status column. This prevents small inconsistencies, "Applied" versus "applied" versus "APPLIED," that make filtering unreliable later.
Add conditional formatting on the date-applied column: highlight any row where status is still "Applied" and the date is more than ten days old, in a colour impossible to miss. This single rule replaces the mental effort of remembering which applications are due for a follow-up.
For the CV version field, do not just write a filename. Store tailored CVs in a folder structure that mirrors the sheet, one folder per application, or paste a cloud storage link directly into the cell so the file is one click away. A filename with no working link is only marginally better than no record at all.
Use a second tab for anything closed, rejected, or withdrawn, so the main view only shows applications that still need attention. A sheet with sixty rows, most of them dead, is harder to act on than one with the eight live applications that need a decision this week.
Where spreadsheets break
Even a well-built spreadsheet has three structural limits no amount of careful setup fully solves.
No real link between the CV version and the application. A pasted file link is better than a filename, but it is still a manual step for every row, and one more place drift creeps in: you tailor a CV further after applying, forget to update the link, and the sheet points at a stale version. There is no enforced connection, only a convention you maintain by hand.
No reminders. Conditional formatting only works when you open the sheet. It cannot notify you on day ten; it can only display something differently next time you look. If your job search is not the only thing occupying your attention that week, a passive visual cue is easy to miss past the point a follow-up would still have felt timely.
Manual status hygiene. Every status update is a task you have to remember, separate from the actual event, an interview invite lands and updating the sheet is a second, unprompted action. Skip it a few times and the sheet stops reflecting reality, so people stop trusting it and stop updating it, which is how trackers die.
None of these are reasons to avoid a spreadsheet. For a search under roughly fifteen to twenty applications, it is genuinely the right tool: simple, flexible, no new software to learn. They are reasons to know where the ceiling is, so you can move to something more structured before it costs you something that mattered.
Pipeline stages that map to reality
A lot of job-tracker templates ship with pipelines like researching, applied, phone screen, technical interview 1, technical interview 2, onsite, reference check, offer, negotiating, closed, ten stages that look thorough and are mostly ceremony. Real hiring processes vary too much between companies for a fixed ten-stage template to match any of them consistently, and forcing your tracker to distinguish round two from round three adds bookkeeping without adding a decision you can act on.
Four stages cover what you need to know at a glance: applied (in the queue, no response yet), interview (any stage of active conversation, from a phone screen to a final-round panel), offer (a decision pending, on your side or theirs), and closed (no longer active, whether that is a rejection, a withdrawal, or a role you turned down). For more granularity on a specific application, a notes field handles it, third round, waiting on team fit interview, without forcing every other row to carry detail it does not need.
This is also the model RecastCV's Track board uses: four columns, not ten, because four is the number of states that actually change what you need to do next.
A follow-up cadence that is polite and effective
Following up feels awkward mostly because people improvise it without a plan, so each instance feels like a judgment call about whether they are being too pushy. A fixed cadence removes the judgment call.
Send a first follow-up seven to ten days after applying, if you have heard nothing. Keep it short: restate the role, one sentence of specific interest, and ask whether there is any update. Three sentences is enough; a long follow-up reads as anxious rather than organised.
If a recruiter gives a specific timeline, we'll be in touch by the 15th, follow up two to three business days after that date, not before. Following up early against a timeline the company gave you reads as not listening; a few days late reads as patient.
After an interview, send a thank-you note within 24 hours, then treat the promised follow-up window the same way, wait it out, then check in two to three business days past it. Two follow-ups with no response is a reasonable number before you move the application to closed. A tracker with a working next-action field is what makes this cadence actually happen, because the sheet tells you which applications are due today.
How RecastCV ties every application to the exact CV that was sent
The gap that breaks spreadsheets, no enforced link between the CV version and the application row, is the specific problem RecastCV's Track board is built to close. Every application on the board is generated from a tailoring pass against your master CV and project library, and the tailored CV produced is stored against that application automatically, not pasted in as a link you have to remember to update. Open any application months later and the exact file submitted is still attached, with its ATS score against that job description, so "what did I actually send this company" is never a question you reconstruct from memory.
The board uses the four-stage pipeline above, applied, interview, offer, closed, because that maps to an actual decision rather than ceremony. For a search under roughly fifteen applications, a spreadsheet with the six fields in this guide serves you well and costs nothing to set up. Past that point, a system that keeps the CV and the application as one record saves more time than the spreadsheet ever cost to build. Pricing is credit-based with three free credits at signup, enough to test the workflow first.
Frequently asked questions
What is the minimum information I need to track a job search?
Six fields cover it: company, role, date applied, current status, which CV version you sent, and your next action with a date. Anything less and you lose information you will need later, most commonly which CV file actually went to which employer, a real problem the moment you get a call back and cannot recall what you claimed on that document.
At what point should I stop using a spreadsheet?
Somewhere between fifteen and twenty active applications, or the moment statuses start going stale because updating them is not part of any automatic step in your process. A spreadsheet is not wrong past that point, it just requires more manual discipline than most people sustain during an already demanding job search.
How many pipeline stages should my tracker have?
Four: applied, interview, offer, closed. Templates with eight or ten stages add detail that looks organised but rarely changes what you do next. If a specific application needs more nuance, a notes field handles it without complicating every other row.
How soon should I follow up after applying if I hear nothing?
Seven to ten days is a reasonable default if no timeline was given. Keep the message to two or three sentences: the role, one sentence of specific interest, and a direct question about status. If a recruiter gave you a date to expect an update, wait two to three business days past it rather than following up early.
Does a job application tracker need to be linked to my actual CV files?
It should be, even if the link is manual. The most common gap in a spreadsheet tracker is a status column with no connection to the document actually submitted, which means the moment a recruiter calls, you are reconstructing from memory what you said rather than reviewing the real file. A tracker that stores the exact tailored CV against each application removes that gap entirely.