PeopleOpsClub logo
PeopleOpsClub
Browse Categories

ATS

An ATS (applicant tracking system) is [recruiting software](/categories/recruiting-software) that stores every job opening and applicant, moves candidates through defined hiring stages, and records who did what and when. It collects applications from career pages and job boards, schedules interviews, captures interviewer feedback, and produces hiring reports such as time-to-fill.

Updated 630 wordsPeople operations glossary

This entry defines the term and its data model. For the full walkthrough of features and buying questions, read the guide What is an ATS?. To compare products, start with the ATS category.

How an ATS works

An ATS is built around three linked records: the job (usually opened from an approved job requisition), the candidate, and the application that connects one candidate to one job. A candidate who applies to two roles has one profile and two applications, each with its own stage.

  1. Intake. Applications arrive from the career site, job boards, referrals, and sourcing. The ATS parses resumes into structured fields and flags duplicates.
  2. Stages. Each application sits in exactly one candidate stage, such as Applied, Phone screen, Interview, Offer, or Hired. Moving it forward or rejecting it is logged with a timestamp.
  3. Collaboration. Interviewers submit interview scorecards in the system, and hiring managers see feedback in one place instead of scattered emails.
  4. Offer and handoff. The offer is generated and approved, and on acceptance the hire's data passes to the HRIS for onboarding.
  5. Reporting. Because every stage change is timestamped, the ATS can calculate time-to-fill, stage conversion rates, and source of hire.

An ATS differs from a recruiting CRM. The ATS manages people who have applied to a specific job. A CRM manages relationships with people who have not applied yet. See recruiting CRM vs ATS for how the two fit together.

Example

Illustration: a company opens a customer-support role and receives 320 applications. The ATS log shows 64 passed the resume review (20%), 24 completed a phone screen (37.5% of 64), 8 reached the final interview (33%), 2 received offers, and 1 accepted. The requisition was approved on March 3 and the offer was accepted on April 11, so time-to-fill was 39 days.

The stage timestamps also show where time went: 12 days between application and phone screen, 9 days waiting for final-interview panel slots. Those two gaps account for 21 of the 39 days, which tells the team to fix scheduling before anything else.

Related terms

Common mistakes

  • Too many stages. Twelve stages with vague names means recruiters skip updates, and stage reports stop matching reality. Five to seven clearly defined stages is easier to keep accurate.
  • Not recording rejection reasons. Without a reason code you cannot tell whether candidates fail on skills, pay expectations, or location, so you cannot fix the job post.
  • Feedback outside the system. Scorecards sent over chat leave no record for audits or future hiring decisions.
  • Treating the ATS as a sourcing tool. Most ATS products manage applicants well and passive prospects poorly. Plan for a CRM if you do a lot of outbound sourcing.
  • Ignoring data retention. Candidate data rules vary by country and state. Set retention and deletion rules instead of keeping every resume forever.

Is an ATS only for large companies?

No. Small companies use an ATS once hiring runs through more than one inbox or spreadsheet. The benefit starts as soon as two or more people review the same candidates, because feedback and status live in one place.

Does an ATS reject candidates automatically?

Only if someone sets it up to. Knockout questions, such as work authorization or a required license, can reject applications automatically. Most ranking features suggest an order but leave the decision to a recruiter. Review any automated rule for bias and legal risk before switching it on.