A spreadsheet can track applicants well for a few roles with modest volume. Use one tab per role, a row per candidate and columns for source, date applied, status, scores, reviewer, interview dates, decision with a one-line reason and a dated next step. Restrict access, limit personal data to what you need and delete it on a schedule. Move to software when volume climbs to dozens of applicants per role, several people review at once, versions drift or you need automatic communication and an audit trail. The sheet is a sound start, and its limits are predictable.
Many small teams run a good hiring process on a spreadsheet for years.
Setup: one workbook, a few tabs
| Tab | Purpose |
|---|---|
| Roles | One row per open role: title, owner, status, date opened |
| Candidates (per role) | One row per applicant, with all the columns below |
| Scorecard | Criteria, weights and anchors for the role. See screening scorecard |
| Messages | Templates for acknowledgement, invitation and rejection |
| Retention | Dates for deleting data, based on your retention policy |
Columns for the candidate tab
| Column | Notes |
|---|---|
| ID | A unique number, so names are not needed in notes |
| Name and email | Only in the restricted tab |
| Source | Job board, referral, careers page, agency |
| Date applied | Starts the clock |
| Knock-out answers | Yes or no for each |
| First-pass bucket | Yes, maybe, no |
| Scores | One column per criterion |
| Total or band | Calculated; see resume ranking vs scoring |
| Reviewer | Initials |
| Reason | One line of evidence |
| Stage | Applied, screen, interview, final, offer, hired, rejected |
| Stage date | Date of the last change |
| Next step and date | What to do and when |
| Message sent | Acknowledgement and decision messages |
| Delete by | Retention date |
Use drop-down lists for stage and bucket, so that entries are consistent.
Rules that keep it clean
- One owner per role, who maintains it.
- Update it the same day something happens.
- Do not store information about protected characteristics, and keep notes factual.
- Use the same criteria for every candidate.
- Lock the scorecard and the formulas.
- Use filters or views, not a re-sorted master, so that rows stay stable.
Privacy and access
A spreadsheet holds personal data, so treat it that way.
- Share only with people involved in hiring, and use access controls.
- Avoid copies in email and on personal devices.
- Keep a retention date per row, and delete or anonymise on time. See GDPR and recruitment data and how long to keep candidate data.
- Respond to access and deletion requests. See candidate subject access requests and right to erasure for candidates.
- Do not put resumes in a shared folder with open permissions.
Handling the resume files
Store resumes in a folder with a naming pattern such as "RoleID-CandidateID.pdf", and link from the sheet. Keep the folder restricted. Do not forward resumes by email to many people. If you ask hiring managers to review, give them access to only that role's folder or view.
Where a spreadsheet struggles
| Problem | What happens |
|---|---|
| Volume | Reading and scoring 200 resumes by hand is slow and inconsistent. See high-volume resume screening |
| Many reviewers | Versions drift; scores are overwritten |
| Communication | Messages are sent by hand and forgotten |
| Reporting | Funnel numbers need manual formulas |
| Audit trail | No record of who changed what |
| Candidate access | Hard to meet requests for data |
| Intake | Applications arrive by email in many formats |
None of these is a reason to avoid a spreadsheet at the start. They are signals for when to change.
When to move
Consider software when two or more are true:
- You regularly receive more than 50 applications per role.
- Three or more people review candidates.
- You have missed follow-ups or sent inconsistent messages.
- You need to show how decisions were made.
- You hire in several roles at once.
See spreadsheet vs ATS for a fuller comparison and applicant tracking system alternatives for small teams for options.
What software adds
A tool can take applications through a form per role, parse the resumes into structured fields, score them against your criteria, keep notes and decisions in one place and send messages. Resume World does this, with the evidence for each score shown, and it has a free plan to try; see AI resume screening software and job application forms. The best preparation for any tool is a good scorecard, which you can build in the spreadsheet first.
A sample row
"ID 0147 | Source: referral | Applied 12 Oct | Knock-outs: pass | Bucket: yes | Scores: 4, 3, 4, 2 | Reviewer: JT | Reason: led team of 6, owns billing escalations; no documentation evidence | Stage: phone screen | Next: call Tue 21 Oct | Delete by: 12 Apr."
A row like this tells anyone on the team what happened and what comes next, which is the whole point of a tracking sheet.
Common inquiries regarding this topic.
Can you track applicants in a spreadsheet?
Yes, for a small number of roles and applicants. A well-structured sheet with a row per candidate, a status column and dated next steps works. It becomes hard to manage as volume, hiring managers and compliance needs grow.
Yes, for a small number of roles and applicants. A well-structured sheet with a row per candidate, a status column and dated next steps works. It becomes hard to manage as volume, hiring managers and compliance needs grow.
The Resume World Team
VerifiedProduct & hiring research, Resume World
We build the screening engine behind Resume World. Everything here comes out of working on resume parsing, scoring and hiring workflows day to day — including the parts that turned out harder than expected.
See more than just keywords.
Resume World extracts verifiable evidence from every applicant against role criteria and delivers an explained, ranked shortlist. 100% free to start with zero card required.


