Extended definition
The ATS is the system every TA function runs on. Every requisition, every application, every interview scorecard, every offer record lives in the ATS or feeds out of it.
Modern ATSes (Workday, Greenhouse, Lever, SmartRecruiters, iCIMS, Ashby, and many others) handle the full operational workflow — req management, candidate sourcing capture, application processing, interview scheduling, scorecard storage, offer letter generation, hire records, and integration with HRIS for the start-of-employee transition. Without an ATS, recruiting at any scale becomes spreadsheet-driven and quickly impossible to manage.
With one, the operational discipline of recruiting becomes possible. ATS choice and configuration are among the longest-lived TA decisions any function makes.
What an ATS does
A modern ATS typically covers eight functions:
- Requisition management — Reqs created, approved, tracked through their lifecycle, closed when filled. The ATS is usually the system of record for what’s open, who owns it, and what stage it’s at.
- Application capture — Inbound applications from careers site, job boards, and aggregators flow into the ATS. Candidate records get created with source attribution.
- Sourced candidate capture — Outbound-sourced candidates are added to the ATS by sourcers and recruiters. Source tagging matters for downstream attribution.
- Pipeline tracking — Candidates move through pipeline stages — sourced, screened, interviewing, offer, hired. Stage transitions trigger workflows, communications, and analytics.
- Interview scorecards — Structured scorecards per interview captured in the ATS, linked to candidate records and aggregated for debrief.
- Offer management — Offer letters generated, approval workflows triggered, accepted offers transitioned to onboarding.
- Reporting and analytics — Source of hire, time to fill, pipeline conversion, recruiter productivity. The ATS is the data foundation for most TA reporting.
- Integrations — ATSes integrate with sourcing tools, interview intelligence platforms, assessment vendors, HRIS, payroll, and background check providers. The integration layer is often where TA tooling decisions actually compound or fragment.
ATS choice depends on hiring volume, role mix, geography, integration needs, and budget. Enterprise ATSes (Workday, iCIMS, SuccessFactors) suit large complex organisations.
Mid-market platforms (Greenhouse, Lever, SmartRecruiters) suit growing companies with modern stack expectations. Newer platforms (Ashby, others) compete on user experience, AI features, and analytics.
Most ATS deployments live for 5-10 years, making the choice consequential.
Why an ATS matters
The ATS is the central nervous system of recruiting. Process discipline depends on it; analytics depend on it; integrations depend on it; compliance depends on it.
ATS deployments that work well produce smooth recruiting operations, clean data, and strong analytics. ATS deployments that work badly produce the opposite — process workarounds, data quality issues, recruiter frustration.
The investment cost of replacing an ATS is large enough that most companies live with their choice for years; the consequences of choosing badly compound across the deployment lifetime.
Common mistakes and misconceptions about ATSes
- Treating the ATS as a database — It’s a workflow system. ATSes used as candidate databases without workflow discipline produce stagnant data and broken processes.
- Configuring stages without enforcing them — Stages defined in the ATS that recruiters don’t update produce noise rather than signal. Configuration discipline matters as much as initial setup.
- Choosing an ATS for features over fit — The most-featured ATS isn’t necessarily the right one. Fit with the company’s hiring volume, role mix, integration needs, and recruiter workflow matters more than feature checklists.
- Underinvesting in the integration layer — ATSes that don’t integrate cleanly with sourcing, interview intelligence, HRIS, and assessment tools produce data fragmentation. The integration design matters as much as the ATS itself.
- Failing to migrate cleanly — ATS replacements where data isn’t migrated cleanly produce permanent gaps in source-of-hire history, candidate relationship continuity, and analytical baselines. The migration is part of the deployment, not an afterthought.
Frequently asked questions
What is an ATS (Applicant Tracking System)?
An ATS (Applicant Tracking System) is the software platform that holds candidate records, manages requisitions, runs the application workflow, and tracks candidates through the hiring funnel. It's the operational backbone of modern recruiting. Every requisition, every application, every interview scorecard, every offer record lives in the ATS or feeds out of it.
What does ATS stand for?
ATS stands for Applicant Tracking System. It's the software platform that holds candidate records, manages requisitions, runs the application workflow, and tracks candidates through the hiring funnel. The ATS is the operational backbone of recruiting at any meaningful scale.
What's the best ATS?
There isn't a single best — the right ATS depends on hiring volume, role mix, geography, integration needs, and budget. Enterprise platforms (Workday, iCIMS, SuccessFactors) suit large organisations. Mid-market platforms (Greenhouse, Lever, SmartRecruiters) suit growing companies. Newer platforms (Ashby, others) compete on UX, AI, and analytics. Most ATS deployments live 5-10 years.
What's the difference between an ATS and a CRM?
An ATS handles candidates currently in active processes — application through hire. A CRM handles relationship candidates outside active processes — talent community, silver medallists, sourced contacts not yet engaged. Mature TA stacks include both, integrated together. Treating them as interchangeable produces data fragmentation.
Do small companies need an ATS?
For sustained hiring (more than 10-15 hires per year), yes. Below that volume, spreadsheet-based tracking can work but typically breaks as hiring scales. Modern mid-market ATSes have entry-level pricing that suits growing companies; the operational benefit usually outweighs the cost above modest hiring volumes.