Recruitment Tracker TemplateThe columns that matter, and when to ditch the sheet
A recruitment tracker is the cheapest hiring tool you will ever build. A single spreadsheet, nine columns, one row per candidate. This guide gives you the exact structure to copy, the two columns most teams forget, and an honest read on the day a sheet starts costing you more than it saves.
The nine columns that carry a recruiting pipeline
Candidate
Name + email
Role
Which req
Source
Where they came from
Applied
Date in
Stage
Applied to Hired
Owner
Who is chasing
Last activity
Days since contact
Next step
The one action
Rating
1 to 5
Most first hires get tracked in someone's head, then in an inbox, then in a panic. You know the version: a hiring manager asks where the frontend candidate is, and you spend four minutes scrolling Gmail to answer a question that should take four seconds. A tracker fixes that. It is not clever. It just holds every candidate for a role in one grid so you can answer "who is where" without thinking.
I have built recruiting operations that ran on spreadsheets and ones that ran on a full ATS, and the truth is a good spreadsheet beats a badly used ATS every time. The tools most people search for on Smartsheet or grab from an Indeed hiring resource are fine starting points. The problem is never the template. It is that nobody agrees on what each column means or who updates it.
So this is two guides in one. First, the tracker structure that works, including the parts most templates leave out. Then the part nobody likes to write about: the point where a sheet stops being free, because the hours you pour into keeping it alive are worth more than a tool. If you already know you are past that line, skip ahead to our take on hiring software for small business.
First principles
What a recruitment tracker is (and is not)
A recruitment tracker is a logbook. Each row is a candidate. Each column answers one question about that candidate: who are they, where did they come from, what stage are they in, who owns the next move. Read across a row and you know the whole story. Scan down a column and you see the shape of your pipeline.
What a tracker is not: a system that does anything. It will not email a candidate, book an interview, or warn you that someone has been sitting in the screen stage for nine days. It records. It does not act. Keep that distinction in your head, because it explains every limitation later in this guide, and it is the exact line between a tracker and an applicant tracking system.
The reason a tracker still beats memory is simple. Human working memory holds about four things at once, per cognitive research on working memory capacity. A pipeline of thirty candidates across five stages is not something you hold in your head. It is something you write down. The tracker is just the place you write it.
The structure
The nine columns every tracker needs
Templates fail in two directions. Some have four columns and cannot answer a real question. Others have thirty and nobody fills them in. Nine is the number that survives contact with a busy week. Here is what each one is for.
Candidate
Name plus a way to reach them. Put the email in the same cell or the next one. If you ever need to export or search, you will be glad it is structured.
Role
Which requisition they applied to. Skip this and a multi-role sheet turns into a guessing game the moment two jobs are open.
Source
Where they came from: job board, referral, LinkedIn, careers page. This is the column that later tells you which channel is worth paying for.
Application date
The day they entered your pipeline. It anchors every speed metric you will ever want to calculate.
Stage
One field, one value, from Applied to Hired or Rejected. This is the spine of the whole sheet. More on how to build it below.
Owner
The one person responsible for the next move. Shared ownership is no ownership. A blank here is why candidates go cold.
Last activity
The date of the last real contact. Sort by this and your neglected candidates float to the top instantly.
Next step
The single next action, written as a verb: 'Send screen invite', 'Chase panel feedback'. Not a status. An instruction.
Rating
A 1 to 5 gut score after each touchpoint. Rough is fine. It lets you sort a pile of maybes into a shortlist in seconds.
The upgrade
The two columns almost every template forgets
The nine above will run a clean pipeline. Two more turn a logbook into something you can learn from. Most free templates leave them out because they are slightly annoying to maintain. Add them anyway.
Rejection reason. When you move someone to Rejected, write one short reason: not enough backend depth, salary too far apart, ghosted after screen, filled the role. After twenty rejections you can read this column top to bottom and see the pattern. If half your rejections say "salary too far apart", your job post has a comp problem, not a sourcing problem. That is a real insight a blank tracker never gives you.
Days in stage. A small formula, =TODAY()-[stage entry date], that counts how long a candidate has sat in their current stage. Sort by it and your stalled candidates are right at the top. This is the single most useful column for spotting where your process drags, and it maps directly to the stage-aging idea in our guide on how to reduce time to hire.
Here is the catch, and it is the whole point of this article. Both columns need to be updated by hand, every time, by a human who remembers. Miss a few and the data lies. That fragility is not a flaw in your discipline. It is the nature of a tool that cannot update itself.
Build it
How to build the stage column in Google Sheets or Excel
The mistake I see most often is a tab per stage. Applied on one sheet, Interview on another, Offer on a third. It feels organized for a week, then you spend your life cutting rows between tabs and losing history. Do it with one column instead.
In Google Sheets, select the Stage column, open Data, then Data validation, and add a dropdown with your stages in order. In Excel it is Data, then Data Validation, then List. Then add conditional formatting so each stage gets a color. Now the pipeline reads like a heat map. One glance tells you if everyone is stuck at Screen or bunched at Final.
One Stage column, seven values, color-coded with conditional formatting
Keep the list short and ordered. If your stages need a legend to explain them, the pipeline is too complicated for the people who have to update it.
Make it last
Four rules that keep a tracker alive past week three
Every team can build a tracker. Almost none keep one current. The sheet does not die from a missing column. It dies from ambiguity about who touches it and when. These four rules are what separate a living tracker from a graveyard tab nobody trusts.
One owner per row, always
The Owner column is never blank and never lists two people. If nobody owns the next move, nobody makes it. This one rule prevents most cold candidates.
Update at fixed times, not when you remember
Ten minutes after every interview, and a five-minute sweep each morning. A tracker updated 'whenever' is a tracker updated never.
Never delete a candidate, move them to Rejected
Deleted rows erase your history and your rejection-reason data. You also lose the silver medalists worth calling when the next role opens.
One tab per role, not per stage
Roles are the natural split because they have different owners and pipelines. Stages live in a column. This keeps every candidate's full history on one screen.
Your tracker already knows where it hurts
Prepzo turns the same pipeline into a system that collects applications, screens them, and updates every stage on its own. No formula to maintain, no row to overwrite.
Try Prepzo freeThe honest part
Where a spreadsheet quietly stops working
A tracker has three limits, and they are structural, not fixable with a better template. It has no memory, so nothing reminds you a candidate has gone quiet. It has no voice, so it cannot reply to the applicant who emailed back an hour ago. And it has no lock, so two interviewers editing the same row will overwrite each other and never know it happened.
None of that matters for one role and one recruiter. All of it matters the moment you have three roles, four interviewers, and candidates who expect a reply the same day. That is exactly when the sheet starts leaking good people, and it does it silently. Nobody logs the candidate who took another offer because your follow-up sat in a draft for two days.
The table below is the clearest way I know to see the line. The left column is what a spreadsheet genuinely does well. The gaps are not template problems. They are the jobs a logbook was never built to do.
What a sheet does, and where it quietly stops
The decision
When to switch from a tracker to an ATS
The trigger is not a feeling. It is arithmetic. Add up the hours your team spends copying rows, chasing feedback, and manually replying to candidates. Multiply by a loaded hourly rate. If that number beats the price of a tool, the spreadsheet is now the expensive option. For most teams that crossover lands around the third open role.
There is also a quality cost that never shows up in the sheet. Slow, inconsistent follow-up is the top driver of candidate drop-off, and LinkedIn's research on candidate experience is blunt about how much a slow process costs you in acceptances. A tracker cannot fix that, because the fix is action, and a tracker only records.
The four signals that you have crossed the line:
- Three or more roles open at once, so a single sheet becomes a maze of tabs.
- More than one interviewer per role, which means feedback lives in Slack, not the tracker.
- A compliance need to show you evaluated everyone consistently, which loose notes cannot prove.
- Candidates dropping off because replies and scheduling are too slow to keep them warm.
If two of those are true today, you are past the tracker. The good news is that modern tools are not the six-figure enterprise ATS of a decade ago. An AI applicant tracking system can collect applications, screen them against your criteria, and keep every stage current without a single manual update. That is the part a spreadsheet was never going to do.
Moving on
How to move your tracker into a real system
The nice thing about doing the tracker properly is that the migration is trivial. Your columns are already the fields an ATS expects. Candidate, role, source, stage, owner, rating: those map one to one into any decent system. Export the sheet to CSV and most tools will import it in a few minutes.
The habits carry over too. The discipline of one owner per row becomes assigned pipeline owners. Your Stage column becomes the pipeline board. Your rating becomes a scorecard. You are not throwing work away. You are handing a well-organized pile to a machine that will keep it organized for you. For the full playbook, our ATS migration checklist walks through it step by step.
My honest view: build the tracker first, even if you already suspect you will outgrow it. A month on a spreadsheet teaches you exactly which stages matter, where your funnel leaks, and what you actually need from a tool. That clarity makes the eventual switch faster and the tool cheaper, because you buy the thing you need instead of the thing a demo sold you.
Keep the pipeline, drop the busywork
Prepzo runs the process a tracker can only record: applications collected, candidates screened, stages updated, follow-ups sent. Unlimited users on every plan, starting at $49 a month.
See Prepzo in actionFrequently Asked Questions
What is a recruitment tracker template?
It is a spreadsheet that logs every candidate for an open role in one place: name, source, current stage, last contact date, interviewer notes, and next step. The point is to see the whole pipeline at a glance instead of hunting through your inbox for who is where.
What columns should a recruitment tracker have?
At minimum: candidate name, role, source, application date, current stage, owner, last activity date, next step, and a rating. Teams that hire in volume also add rejection reason and days in stage, because those two columns tell you where your funnel leaks and where it stalls.
Is a spreadsheet enough to track recruiting?
For one or two open roles and a single person managing them, yes. A spreadsheet is honest and free. It breaks down once you have multiple roles, multiple interviewers, and candidates who email you back, because a sheet cannot send a reply, schedule an interview, or stop two people from editing the same row.
How do I track candidate stages in Google Sheets?
Use a single Stage column with a dropdown (Data, then Data validation) listing your stages in order: Applied, Screen, Interview, Final, Offer, Hired, Rejected. Add conditional formatting so each stage gets a color. That gives you a visual pipeline without any add-ons.
When should I switch from a spreadsheet to an ATS?
When the admin work costs more than the tool would. The usual triggers are three or more open roles, more than one interviewer per role, a compliance need to show consistent evaluation, or candidates dropping off because replies are slow. At that point a spreadsheet is quietly losing you good people.
Is a recruitment tracker the same as an ATS?
No. A tracker records what happened. An applicant tracking system runs the process: it collects applications, screens them, schedules interviews, stores scorecards, and reports on the funnel. A tracker is a logbook. An ATS is the machine.
Resources & Further Reading
Related Guides
- What Is an Applicant Tracking System?
The difference between a logbook and a system
- Hiring Software for Small Business
What to buy when the spreadsheet stops scaling
- The ATS Migration Checklist
Move your data without losing history
- How to Reduce Time to Hire
Why days-in-stage is the column that matters
External Sources
- Smartsheet: Applicant Tracking Templates
Free downloadable spreadsheet starting points
- Indeed: Applicant Tracking Spreadsheet
A basic template and how to use it
- LinkedIn: Candidate Experience
What slow follow-up costs you in acceptances
- SHRM: Talent Acquisition
Benchmarks and process best practices
