If you're running an active job search, you're almost certainly tracking applications in a spreadsheet. Or a notes app. Or your head - which is where most people start before things fall apart.
The spreadsheet works until it doesn't. At around 20-30 active applications, a flat list starts to fail: you lose track of which stage each role is at, you miss follow-up windows, and you end up applying to the same role twice or chasing a company that already rejected you.
This guide covers what a job search tracking system needs to do, how to build one that holds up over a 3-6 month search, and where the most common approaches break down.
Why tracking matters more than volume
When a search stalls, the instinct is to apply to more roles. The data doesn't support this.
Research on job search outcomes consistently shows that candidates who actively track their pipeline - meaning they know the current status of every application and follow up at the right time - convert at a meaningfully higher rate than those running a high-volume spray-and-pray approach.
The pattern that fails: applying at high volume, losing track of where each role stands, and never following up. The pattern that works: tracking every application, knowing exactly where each one is at, and showing up at the right moment with the right message.
The tool doesn't determine the outcome. The discipline of knowing where you stand does.
What breaks down in a spreadsheet
The spreadsheet fails in a predictable order.
First, you add more columns than you can usefully scan. Status, date applied, contact name, recruiter email, job title, company, URL, notes, interview date, follow-up date - each column makes sense in isolation. Together they become a surface you skim rather than read.
Then you stop updating it. Not because you are disorganised, but because keeping a spreadsheet accurate is a second job on top of the actual search. After a long day of applications and interviews, opening a spreadsheet to record a status change is the last thing you do.
Finally, the view doesn't match how a job search actually works. A spreadsheet is a list. A job search is a pipeline - roles move through stages, some stall, some accelerate, some disappear. A list doesn't tell you at a glance where everything stands. You have to read down every row, remember context, and mentally reconstruct a picture that should be immediately visible.
None of this means spreadsheets are wrong. For the first 10-15 applications, they are fine. The problem is that most people hit 30+ active applications before they think to change their system.
The three things any tracking system needs to do
Before getting into tools and methods, here is the minimum a useful job search tracker needs to handle:
1. Status at a glance
You should be able to open your tracker and immediately see where each role stands - not by reading a list, but by looking at a structure that organises applications by stage. Queued, Applied, Interviewing, Offer, and Rejected cover almost every job search scenario. Everything else is a note.
2. Time visibility
When did you apply? When did you last hear from them? When is your next follow-up due? A system without timestamps means you are relying on memory to know when to act. Memory fails. Dates don't.
3. A signal when things go stale
A tracker that tells you what needs attention - an application that's been in "Applied" for 10 days with no follow-up, an interview that happened 8 days ago with no response - turns your pipeline from a record into an action list. This is what spreadsheets don't do: they capture what happened, but they don't tell you what to do next.
What to actually track - the minimal useful set
Here are the fields that matter, and the ones you can safely drop.
Keep these:
- Company name and role title
- Date applied
- Current status (one of: Queued / Applied / Interviewing / Offer / Rejected)
- Date of last contact or last status change
- Link to the job posting - it disappears when the role closes
- Any specific follow-up date you committed to
- Which version of your CV you sent, if you tailor it per role (see how to write a CV that gets through ATS filters in the UK)
Drop these:
- A freeform notes column that becomes a wall of text no one reads
- Salary fields at the top of the funnel - you don't have reliable data yet
- Source tracking per application - useful in aggregate across your whole search, useless per role
- Priority ratings - everything feels high priority when you are actively searching
The goal is a tracker light enough to actually maintain and complete enough to act on. Five fields beats fifteen.
Methods that work at different search scales
Under 20 applications: a simple spreadsheet is fine
A Google Sheet with four columns - Company, Role, Date Applied, Status - and colour-coding by status is genuinely sufficient at this scale. If you have fewer than 20 active roles and your search has been running under a month, the spreadsheet is not your bottleneck.
What makes a spreadsheet work at small scale:
- Sort by status, not by date. You want to see everything in the same stage together.
- Colour the Status column only, not the whole row. Full-row colour creates noise that makes the table harder to read.
- Add a "Next Action" column if you find yourself missing follow-ups. One field, one sentence.
Where this breaks down: when the number of rows gets large enough that you spend more time scrolling than deciding. Typically around application 25-30.
20-50 applications: you need a pipeline view
At 20+ active applications, a list stops working. You need a view that shows you the stage of every role without scanning every row.
A Kanban board - columns for each status, one card per application, cards move across columns as they progress - gives you immediate visual clarity about where your pipeline is concentrated and where things have stalled.
This is achievable in Notion with some setup time, in Trello with a free account, or with a purpose-built job search tracker.
What to look for in any Kanban setup:
- The date of last update visible on each card without clicking into it
- Fast status changes - drag-and-drop, not a dropdown buried in a modal
- An obvious way to see stale cards - anything that hasn't moved in 7+ days should stand out
50+ applications or 3+ months in: you need the system to work for you
At this scale, the time cost of manual tracking compounds. You are spending meaningful time each week just keeping the record accurate. This is the point where automated follow-up nudges, timestamp-based alerts, and integrated job search start returning real time savings.
The search itself looks different too. You are likely running 3-5 interview processes simultaneously with different contacts, different timelines, and different follow-up windows. A system that surfaces "Interviewing for 21+ days with no update" is not optional - it is the only way to make sure nothing falls through.
The follow-up timing that actually converts
Your tracker's primary job is to tell you when to act. Here is the timing that holds up across most hiring processes:
After applying (no response): follow up at day 7-10. A single sentence: "I wanted to confirm my application for [role] arrived - happy to provide anything else you need." Anything longer reads as desperation and gets skimmed.
After a first interview: a thank-you email within 24 hours. Not a LinkedIn message - email reaches the hiring manager directly and is easier to save. One specific thing from the conversation that reinforced your interest, one sentence on why you are a good fit, two paragraphs total.
After the interview (no decision after 7 days): follow up with a timeline question, not a status check. "Could you give me a sense of the timeline from here?" is a question that gets answered. "Just following up on my application" doesn't.
When it goes quiet past day 14: one more touch, then move it to Stalled in your tracker. Keep the entry - these roles resurface more often than you'd expect. But stop holding emotional space for it while actively waiting.
The candidates who convert aren't necessarily the ones with the strongest CVs. They are the ones who follow up at the right time, in the right way, because they know exactly where each role stands.
Choosing a tracking tool
Most job seekers move between three options at different points in their search.
Google Sheets - free, flexible, good for short searches or small pipelines. Breaks down at scale and requires manual effort to maintain accuracy.
Notion or Airtable - more powerful views (Kanban, calendar, gallery), still require setup time and discipline to update. No built-in follow-up nudges. Good if you are already in the Notion ecosystem.
Purpose-built trackers - tools built specifically for job searches have features spreadsheets cannot: automatic follow-up reminders, integrated job search across multiple boards, status history, and in-app notifications when things go stale.
The question is not which tool is objectively best. The question is which one you will actually use consistently. A spreadsheet you update every day beats a sophisticated tracker you abandon after a week.
What RolePilot does differently
RolePilot is a free job search tracker and job board aggregator built around the pipeline principles above.
The tracker is Kanban-based: five columns (Queued, Applied, Interviewing, Offer, Rejected), drag-and-drop status updates, and timestamps on every change. The view is designed around the question "what needs my attention right now" rather than "what have I applied to."
What it adds beyond the basic tracking structure:
Built-in staleness alerts. If a role has been in Queued for five days, you get an in-app notification and an email nudge. If you have been in Interviewing for 21 days with no update, the system flags it. This is the follow-up timing described above, automated.
Integrated job search. Instead of finding roles across four separate job boards and copying details into your tracker, RolePilot searches across Reed, Adzuna, JSearch, and Google Jobs simultaneously. Results surface into a single feed. One click saves a role directly to your pipeline.
No credit card. No trial period. The full tracker - Kanban, timeline view, status history, notifications - is free. AI CV tailoring to a specific job description is a Pro feature launching later this year.
You can try it at role-pilot.com.
The system that works
Track every application. Use a pipeline view from the start - not after the spreadsheet fails at application 30. Timestamp everything. Build your follow-up schedule around dates, not memory. Let the system tell you what needs attention rather than holding your pipeline in your head.
The job search is not a lottery. The candidates who move fastest through hiring processes are the ones with the clearest view of their own pipeline - because that clarity is what makes every follow-up, every conversation, and every decision happen at the right time.
See also: