What it is
An applicant tracking system (ATS) is the system of record for hiring. It holds job requisitions, candidate profiles, applications and every step a person takes from first contact to accepted offer or rejection. Recruiters, hiring managers and interviewers work from the same record instead of passing resumes through email.
The core objects are simple. A requisition describes a role, its budget owner, location and approval state. A candidate profile holds contact details, resume, work history and consent settings. An application links one candidate to one requisition and carries a stage, owner, source and activity history. Notes, emails, interview feedback and attachments hang off that application.
An ATS is not a payroll system, an HRIS or a sourcing tool, though it connects to all three. It does not decide who to hire. It makes the process visible, repeatable and auditable. For IT, it is a business application with user accounts, integrations, data retention rules and a support owner.
How it works
Most hiring starts with a requisition and an approved job description. The ATS publishes that role to your careers page and, through feeds, to job boards. Applications arrive by web form, email parsing or manual upload. The system parses resumes into fields, checks for duplicates and can ask knockout questions before a recruiter sees the record.
Candidates move through pipeline stages that match your process, such as screen, hiring manager review, interview loop, offer and hired. Each stage can have an owner, a service level for response and required fields. Recruiters send templates from the ATS, log calls and emails, and schedule interviews through calendar integration. Interviewers get a scorecard and an interview kit tied to the role family, so feedback lands in one place.
Offer approval usually runs as a workflow with defined approvers. When a candidate accepts, the ATS triggers an onboarding handoff to HR or IT, often by webhook or HRIS integration. Background checks and e-signature tools connect through APIs or native integrations.
Reporting comes from the same data. You can see time to hire, source, stage conversion and reasons for rejection. Role-based permissions control who sees salary, feedback and candidate contact details. Audit logs and retention settings let administrators show who changed what and when.
Why it matters for a business
A shared record reduces lost candidates. When resumes live in inboxes, a hiring manager can screen a candidate and forget to tell the recruiter. The candidate waits, then takes another offer. An ATS assigns an owner and a next step, so the handoff is visible.
It gives finance and HR leaders numbers they can defend. You can show where candidates drop out, which sources produce hires and how long each stage takes. Those numbers are only as good as the disposition codes and stage rules you enforce, so set them before you need the report.
It also makes hiring easier to audit. Permissions, retention rules and activity logs show who accessed a record and what changed. That matters when someone asks why a candidate was rejected or when a former employee's data should be removed. Set retention rules that match your policy and test them before an audit request arrives.
The operational case is simpler: hiring volume grows, and spreadsheets stop scaling. Two recruiters can share a spreadsheet, but five cannot do it without duplicate records, missed replies and arguments about the latest version.
Common mistakes
The first mistake is copying every step of your current process into the tool. A pipeline with twelve stages slows everyone down and hides the real decision points. Use a small set of stages that match how you actually decide, then add exceptions only when they earn their place.
The second is treating the ATS as a resume pile. If interviewers do not get scorecards, if recruiters do not log disposition reasons and if hiring managers do not close out candidates, the reports are fiction. Set required fields at stage transitions and review them in the first month.
The third is weak integration work. Calendar, email, careers page, job boards and HRIS handoff all need testing with real accounts. A broken calendar sync or a careers page that hides salary fields will push the team back to email within a week.
The fourth is skipping ownership and training. Someone needs to own user administration, templates, stages and data quality. Write a short admin guide and train hiring managers on the scorecard, not just recruiters on the pipeline. Plan the migration of open roles before you switch off the old inbox.
How to get started
Map the hiring process you use now. List the roles, the stages, who approves a requisition, who interviews and who makes the offer. Note where candidates get stuck and which fields finance or HR need for reporting. This is the specification you will configure against.
Choose the minimum data model. Define required fields for requisitions and candidate profiles, stage names, disposition codes, scorecards and retention rules. Decide which integrations are must have on day one and which can wait. Keep permissions simple at first, then add restrictions for salary and feedback.
Run a pilot with one or two role families. Import open roles, connect the careers page and calendar, send a test application through every stage, and check the reports. Fix the template and stage rules before you invite every hiring manager.
Train recruiters and hiring managers, publish the admin guide and review time to hire, source and stage conversion after the first hiring cycle. You can configure a tool yourself, hire a specialist, or use a fixed scope package such as Cloudverg's Recruiting system implementation at $9,500/month, which covers stages, scorecards, job board feeds, scheduling, offer approval, onboarding handoff and reports in 3 to 4 weeks.
Frequently asked questions
Is an applicant tracking system the same as a CRM?
No. An ATS tracks job requisitions, candidates and hiring stages. A CRM tracks sales accounts, contacts and opportunities. Some vendors sell both, but the workflows, permissions and reports are different.
Do small companies need an applicant tracking system?
If you hire a handful of people a year and one person runs every search, a shared inbox and a structured folder can work. Once two or more managers interview, or roles stay open for weeks, an ATS gives you a shared record and reminder. The value comes from consistent stages and feedback, not from the software alone.
What should I check before buying an ATS?
Check stage flexibility, scorecards, calendar and email integration, careers page and job board feeds, role-based permissions, audit logs, reporting and data export. Ask how onboarding handoff works and how retention rules are configured. Run a test application through every stage before you sign.