---
title: "How to Keep Track of Applicants Without an ATS (2026 Guide)"
description: "Four honest ways to track applicants without an applicant tracking system, what each one really costs, and how to pick by hiring volume rather than company size."
url: https://zjcv.com/journal/track-applicants-without-ats/
canonical: https://zjcv.com/journal/track-applicants-without-ats/
author: "Zen Job CV Team"
published: 2026-06-16
updated: 2026-06-16
category: "Research"
tags: ["ats alternatives", "applicant tracking", "recruitment tools", "cv screening", "hiring ops"]
lang: en
---

# How to Keep Track of Applicants Without an ATS (2026 Guide)

> **TL;DR** You can track applicants without an ATS using a structured spreadsheet, a shared inbox, a dedicated screening tool, or a lightweight ATS. Pick by how many roles you run at once and how many applications each pulls, not by company size. Whatever you choose, it must do five things: collect every application in one place, standardize CVs, record a reason for each decision, stay auditable, and delete on a schedule. Zen Job CV fits the high-volume-single-role case as a screening layer; it is not a pipeline manager for many simultaneous roles.

You can keep track of applicants without an applicant tracking system, and for a small team it is often the better choice. The workable options, from lightest to heaviest, are a structured spreadsheet, a shared inbox with disciplined labelling, a dedicated screening tool that ranks applicants for you, or a genuinely lightweight ATS. Which one fits depends on how many roles you run at once and how many applications each one pulls. What every version needs in common is the part teams skip: one place every application lands, a written record of why each decision was made, and a deletion schedule. Miss those and you do not have a tracking system, you have a pile.

The reason this question gets asked at all is that a full ATS is priced and built for a bigger operation than most teams running it. Independent pricing guides put mainstream ATS tools at roughly [30 to 120 US dollars per user per month](https://www.selectsoftwarereviews.com/blog/ats-pricing-short-guide), before implementation, migration and integration costs, and much of that spend buys workflow automation a two-person team will never switch on. Pricing structures vary further, from [per-user to per-job and flat monthly tiers](https://toggl.com/blog/applicant-tracking-system-pricing-guide), and the sticker price rarely includes implementation, data migration or the integrations that make an ATS worth having.

## Why teams want to avoid a full ATS

Three reasons come up again and again, and all three are legitimate.

The first is cost against use. An enterprise ATS is designed for high-volume, multi-recruiter hiring with approval chains, requisition management and reporting. A team hiring for two or three roles a year uses a fraction of it and pays for the whole thing. The second is setup weight: configuring stages, scorecards, permissions and job-board integrations is a project, and for occasional hiring the project never pays itself back. If most of your applications simply arrive by email, [parsing resumes out of your inbox](/journal/parse-resumes-from-email/) may be the only automation you actually need. The third is ownership. Once candidate data lives inside a platform, exporting it, deleting it on request, and answering "where is every copy of this person's data?" can become harder, not easier, which matters directly for the [GDPR obligations that apply to candidate data](/journal/gdpr-rules-for-cv-screening/).

The organizing side of this, keeping applications tidy rather than choosing a tool, is covered in [how to organize job applications](/journal/how-to-organize-job-applications/), and the team-collaboration side in [what a shared recruitment inbox is](/journal/what-is-recruitment-shared-inbox/). None of that means you should track applicants in your head, or in a personal inbox where the rest of the team cannot see them. It means the tool should match the volume.

## The options, compared

Here is the honest comparison across the four realistic approaches.

| Approach | Best for | Real cost | Where it breaks down |
|---|---|---|---|
| Structured spreadsheet | 1 to 2 roles, low volume | Free | No CV storage, manual entry, easy to fork into private copies |
| Shared inbox with labels | A team fielding a careers address | Free to low | Search is weak, no ranking, no audit trail |
| Dedicated screening tool | High volume on one role | Low, often a free tier | Not a full pipeline manager for many simultaneous roles |
| Lightweight ATS | Several roles at once, small team | Low to mid monthly | Still setup, still a platform to migrate off later |

The pattern in that table is that the right answer moves down the list as your simultaneous-role count and application volume rise, not as your company headcount rises. A fifty-person company hiring once a year is a spreadsheet. A five-person agency screening two hundred applicants a week is not.

## What "tracking" actually has to do

Whatever tool you pick, an applicant-tracking process has to do five things, and it is worth naming them because the tool is only as good as whether it covers all five.

| Job the process must do | What good looks like |
|---|---|
| Collect | Every application in one shared place, not a personal inbox |
| Standardize | CVs readable in one view regardless of format |
| Decide with reasons | A recorded reason next to every advance or reject |
| Stay auditable | Answer "why was this person set aside?" months later |
| Delete on schedule | A retention rule that actually runs, not a good intention |

A spreadsheet can do the first three if you are disciplined. It struggles with the last two, because the reasons live in your memory and nothing deletes itself. A retention rule is not optional either: the Dutch supervisory authority treats [deletion within four weeks of a procedure ending](https://www.autoriteitpersoonsgegevens.nl/en/themes/employment-and-benefits/job-applications/personal-data-of-applicants) as the norm, extending to a year only where the candidate has consented. That is usually the point where a team outgrows the spreadsheet: not when it gets slow, but when someone asks a question about a decision made four months ago and there is no answer on file.

## A worked example

Take a ten-person design studio hiring one mid-level designer. The ad pulls 180 applications in two weeks. A full ATS here is overkill: there is one role, one hiring manager, and no second opening on the horizon. The right first system is a shared spreadsheet plus a CV folder, and the studio can run the whole role from it, right up to the first pass.

The moment it strains is predictable. Reading 180 CVs to a consistent standard is the better part of a working day, and by the last third the reviewer is skimming faster than they did at the start. That is not a discipline failure, it is what sustained attention does, and it is exactly where a first pass stops being even-handed. So the studio's better setup is the spreadsheet for stage tracking plus a screening tool for that one heavy first pass: the tool produces the ranked shortlist and the near-miss list, and the spreadsheet holds who is at which interview stage. Neither tool is doing the other's job, and the studio never buys a platform it would have to migrate off six months later.

Change one number and the answer changes. If the same studio were filling six roles at once, the spreadsheet would fracture into six tabs nobody keeps in sync, and that is the case where a lightweight ATS finally earns its monthly cost. The lesson is that the decision turns on simultaneous roles and volume, not on how the tool makes the team feel.

## A workable spreadsheet method

If you are starting from nothing, a spreadsheet plus a shared folder is a legitimate first system, and it is better than a half-configured ATS nobody maintains.

Give it one row per candidate and columns for: name, role, source, date received, your must-have criteria as yes or no, a one-line reason, current stage, and a link to the CV in a shared drive. The two disciplines that make it work are that everyone edits the same copy, never a personal download, and that the reason column is never left blank. The reason column is the whole value: it is what turns a list of names into a decision you can defend.

The place a spreadsheet quietly costs you is the first pass. Reading and entering two hundred CVs by hand is hours of work, and consistency fades over a long session, which is where the [documented biases in fast screening](/journal/bias-aware-blind-cv-screening/) creep in. That is the specific job a screening tool takes off you.

## Where a screening tool fits, honestly

This is where Zen Job CV sits, and it is worth being precise about what it does and does not do, because the category is full of overstatement.

Zen Job CV is a screening layer, not a full pipeline manager and not an inbox product. You bring applications in by uploading them or forwarding them, it standardizes every CV into one view, and it produces a ranked shortlist with the criteria each candidate met and missed, plus a near-miss list so nobody strong is silently dropped. It keeps the audit trail and applies your retention rule. What it is not: it does not connect to your mailbox and watch it, it is not a Kanban board for running ten roles at once, and it never makes the hiring decision, it ranks and explains so a person can. If your problem is "one role, far too many applicants," it fits well. If your problem is "ten roles at once and I need stages and approvals," a lightweight ATS is the better tool and it would be dishonest to say otherwise.

For teams under about fifty people the honest recommendation is usually the smallest thing that covers all five jobs above. That is a disciplined spreadsheet at low volume, a screening tool once one role starts pulling hundreds of applicants, and a lightweight ATS only when you are genuinely running several roles in parallel.

## Migrating off a spreadsheet later

If you do outgrow the spreadsheet, the migration is painless precisely because you kept it disciplined. Because every candidate already has a source, a date, criteria and a reason, moving to a screening tool or an ATS is an import, not a reconstruction. This is the quiet argument for doing the boring parts from day one: the retention rule, the reason column, the single shared copy. They are also exactly what an auditor or a candidate exercising [their data rights](/journal/gdpr-rules-for-cv-screening/) will ask about, so the discipline pays twice.

## Which approach to choose

Start by counting two numbers: how many roles you hire for at once, and how many applications your busiest role pulls. If both are low, a structured spreadsheet is genuinely enough and anything more is procurement for its own sake. If one role floods you, add a screening tool for the first pass and keep the spreadsheet for stage tracking. If several roles run in parallel, that is the one case where a lightweight ATS earns its monthly cost. The mistake is reaching for the heaviest tool because it feels more professional; the professional move is matching the tool to the volume and keeping the record clean enough to defend.

## Quick answers

**How do you keep track of applicants without an ATS?** Put every application in one shared place, record a reason next to every decision, and set a deletion schedule. A structured spreadsheet plus a shared CV folder covers low volume; add a dedicated screening tool once a single role pulls hundreds of applicants. The tool should match your volume, not your company size.

**What is a lightweight ATS, and how is it different from a spreadsheet?** A lightweight ATS adds stages, candidate records and basic automation without the setup weight of an enterprise platform, so it suits a small team running several roles at once. A spreadsheet is free and flexible but holds no CVs, keeps no audit trail, and forks easily into private copies, which is where it stops scaling.

**Is a spreadsheet GDPR-compliant for tracking candidates?** It can be, if you run it correctly: one shared copy rather than personal downloads, only job-relevant fields, a documented retention period, and a way to delete one candidate on request. The Dutch supervisory authority treats deletion within four weeks of a procedure ending as the norm, extending to a year with the candidate's consent.

**When should you not use a screening tool?** When your real problem is running many roles in parallel rather than volume on one role. A screening tool ranks and explains a single pile of applicants well; it is not a pipeline manager for ten simultaneous openings with stages and approvals. That is the one case where a lightweight ATS is the honest recommendation.

**How many applicants is too many for a spreadsheet?** The limit is rarely the row count, it is the first pass. Once reading and entering CVs by hand runs to hours and consistency starts to fade over a long session, the spreadsheet is costing you good candidates. That is the point to add a tool that does the ranking, while the spreadsheet can still hold stage tracking.

---

Source: https://zjcv.com/journal/track-applicants-without-ats/
Author: Zen Job CV Team