How to track job applications without the spreadsheet dying by week three

Everyone's job-search tracking system starts the same way: a spreadsheet, created with great optimism, with columns for company, role, date and status. And almost everyone's spreadsheet dies the same death, somewhere around week three, when the search gets busy enough that updating the tracker starts competing with the activities it was supposed to organise. The record decays exactly when it would start being useful.

This isn't a discipline failure. It's a design failure, and it's worth being precise about why — because the fix follows from the diagnosis.

Why the spreadsheet dies

Every update is manual, and updates are where the value lives. A tracker is only as good as its worst week. The week you have two interviews, a take-home and a recruiter chasing you is the week you stop logging — and it's also the week the record mattered most.

Status isn't one column. "Applied" hides a dozen real states: applied and acknowledged, applied into silence, screening booked, take-home pending, awaiting feedback, ghosted-but-maybe-not. A single status cell forces you to flatten states that need different actions, so the tracker stops telling you what to do next — at which point it's an archive, not a tool.

The correspondence lives somewhere else. The actual substance of your search — who said what, when, and what you promised — is in your inbox and your LinkedIn messages. A spreadsheet holds a pointer to a conversation, not the conversation. When a recruiter calls about "the role you applied for", the spreadsheet tells you a company name and a date; it can't reconstruct what was sent, which version of your CV they have, or what you last told them.

Nothing chases you. The highest-value act in application tracking is the follow-up — the polite nudge at the right moment, the check-in after an interview. A spreadsheet knows the date of your last touch and will never once remind you.

What a working system has to record

Whatever tool you use — and a spreadsheet can work for a small, slow search — the record needs to hold, per application:

• The exact artefacts sent: which CV version, which cover letter. If you tailor per role (you should), "my CV" is not one document, and interviews go noticeably worse when you can't remember which framing they read.
• The full correspondence thread, attached to the application rather than scattered across inboxes.
• A real status, granular enough to imply the next action.
• The next action and its date — yours ("follow up Friday") or theirs ("they said end of week").
• The posting itself, saved at apply time. Listings get taken down, and walking into an interview without the job description is avoidable.

Notice how much of this is clerical capture of things that already happened in other systems. That's the tell that it's automatable.

The pipeline-board shape

The kanban framing — columns for applied, screening, interviewing, offer — beats the spreadsheet for one structural reason: it makes state transitions visible instead of cell edits. You see where every application sits, where things are piling up, and where the pipeline is leaking. Applied-and-silent for two weeks is visually distinct from actively-interviewing, and different columns imply different actions.

Quarrion uses this shape, with the mechanical parts wired in: applications land on the board automatically when they're submitted (the agent submitted them, so there's nothing to transcribe), the recruiter correspondence sits on the application record in a unified inbox rather than in a parallel universe, and follow-ups are drafted and tied to the thread they belong to. The tracking is a by-product of the pipeline running, which is the only reliable way tracking ever happens — a record that maintains itself doesn't decay in week three, because nobody is maintaining it.

When tracking starts paying for itself

Whatever the system, the payoff compounds with volume. At five live applications, memory works. At fifteen, cross-talk starts: you re-apply to a company that rejected you last month, or blank on a recruiter's question about a role you can't place. Past twenty, an untracked search isn't merely disorganised — it produces actively worse outcomes, because follow-ups don't happen, and follow-ups are among the cheapest actions in the entire search.

There's also a quieter benefit: an accurate pipeline is the only honest measure of how the search is going. Applications-sent is a vanity number. What a real record shows is where things stall — plenty of applications but no screens says one thing; screens that never convert to interviews says another. You can't fix a leak you can't see, and seeing it is the whole point of writing things down.