What is applicant tracking?

Applicant tracking, explained#

Without a system, hiring happens in an inbox. CVs arrive as attachments, feedback lives in chat threads, and nobody is sure who has been contacted. An ATS gives every candidate one record and every role one pipeline, so a small team can hire without losing people along the way.

The core pieces are the same across tools. A role with its description and requirements. A public careers page or job post where people apply. Application forms with screening questions. A pipeline of stages, typically applied, screening, interview, offer and hired, plus closed outcomes such as rejected or withdrawn. Notes and scorecards from each interviewer. And communication with the candidate at each step.

Good applicant tracking is also about fairness and memory. Structured questions and consistent stages make candidates comparable. Recording why someone was rejected protects the company and helps the next search. Candidates who were a near miss can be found again for the next role.

Larger ATS products add sourcing, job-board distribution, interview scheduling and compliance reporting. Small teams usually need far less: a careers page, a clear pipeline, notes, and a smooth handover when someone is hired. The handover is often the weakest point: the new person has to be re-entered in payroll, the team directory and every tool, which is where details get lost.

For example, a startup opens a designer role and posts it on its careers page. Forty people apply. The founder screens them down to eight, two teammates interview five and leave notes, one candidate gets an offer, and the rest are marked rejected with a reason, all on one board.