How to Choose an Applicant Tracking System: A Buyer's Guide

Most failed ATS purchases share one cause: nobody wrote down what was broken. Before any demo, document the current process on one page.

Capture:

• Open requisitions per quarter and average applicants per requisition.
• Time from requisition approval to posting, and from application to first contact.
• Who touches a candidate: recruiters, coordinators, hiring managers, interviewers, and how many log in rarely.
• Where candidates are tracked today (email, spreadsheets, an older system) and what gets lost.
• Which roles are high-volume (hourly, seasonal, retail, shift work) and which are low-volume professional searches.

Those answers separate two product styles. High-volume hiring needs fast mobile applications, text messaging, automated screening questions, and self-scheduling. Professional recruiting needs strong pipelines, referral tracking, talent pools, and structured interview scorecards. Few tools excel at both, so decide which matters more.

Keep must-haves under 12. Longer lists make every product look equal and push the decision to price.

Core functional checklist

• Job creation with approval workflows and templates
• Multiposting to job boards, with clear rules on which boards cost extra
• Career page and mobile-friendly application flow
• Resume parsing and duplicate detection
• Configurable pipeline stages per job family
• Interview scheduling that syncs with email and calendars
• Scorecards and structured feedback
• Offer letters, approvals, and e-signature
• Candidate communication: email templates and, if needed, text messaging
• Reporting on source, stage conversion, time to fill, and recruiter workload

Applicant data is regulated data. Federal rules set minimum retention, and your ATS must let you meet them without manual workarounds.

According to the EEOC, employers must keep personnel and employment records for one year, and for involuntarily terminated employees, one year from the date of termination. Payroll records under the age discrimination rules must be kept for three years. When a discrimination charge is filed, relevant records must be preserved until final disposition of the charge or any lawsuit based on it. In ATS terms, that means:

• A legal hold function that suspends automatic deletion for specific requisitions or candidates.
• Auto-purge rules you can configure, rather than fixed vendor defaults.
• Exportable records of who viewed, moved, or rejected a candidate.
• Required, standardized disposition reasons for every rejection.

State and local rules, including those on automated employment decision tools, salary range posting, and criminal history inquiries, vary and change. Ask each vendor which jurisdiction-specific features exist, and confirm your obligations with counsel, since a vendor cannot take them over.

Hire-to-HRIS and Form I-9

Once a candidate is hired, the ATS should hand data to your HRIS cleanly. Form I-9 is a separate process: USCIS says to retain it for three years after the date of hire or one year after employment ends, whichever is later. If an ATS includes onboarding or I-9 features, check where the form is stored and how retention dates are calculated, or confirm that your HRIS handles it.

Fairness and automated screening

If a product ranks, scores, or filters candidates automatically, treat it as a selection procedure you are responsible for. Ask what data the model uses, whether adverse impact testing has been done and documented, and whether you can turn it off. Keep a human decision step on every rejection path.

An ATS that does not connect to the rest of your stack creates double entry on the day of hire.

Ask for a live hire-to-HRIS handoff using test data, not a slide.

Recruiters will tolerate a clumsy tool. Hiring managers will not, and they decide whether your data is complete. During demos, have an actual hiring manager review candidates, submit feedback, and approve an offer. Count clicks and watch for confusion. Test the candidate side on a phone too: apply to a job and time it. Long or broken mobile applications lose candidates, especially in high-volume hiring.

Also check accessibility. Candidates with disabilities must be able to apply, so ask how the application flow handles screen readers and what accommodation request options exist.

Pricing models include per user, per active job, per employee, tiered by company size, or flat annual fee. Compare them on your own volumes.

Build a three-year cost sheet:

• Subscription fee and any annual escalator
• Implementation and data migration fees
• Paid job-board postings and sponsored listings
• Add-ons: text messaging, assessments, background-check integration, advanced reporting
• Extra users, locations, or career sites
• Support tier and training
• Early termination and renewal terms

Ask what happens to price at renewal. A low first-year price with a high escalator is common.

1. Shortlist three to five products that meet every must-have.
2. Give each vendor the same script: three real job types, five sample candidates, one offer.
3. Score each criterion from 1 to 5, with weights agreed in advance.
4. Include recruiters, a hiring manager, HR operations, IT, and finance as scorers.
5. Check references of similar size and hiring pattern, and ask about implementation and support problems.
6. Request a sandbox or pilot with a live requisition when possible.

Suggested weights: workflow fit 30 percent, usability 20 percent, integrations 15 percent, compliance and reporting 15 percent, price 10 percent, vendor support 10 percent. Adjust for your situation, but set them before demos.

Allow time for migrating open requisitions and candidate history, building the career site, and training. Decide how much history to import, since old data carries retention and privacy obligations. Name an internal owner and pick a go-live date away from peak hiring. Measure at 30, 60, and 90 days:

• Time to first contact
• Time to fill
• Hiring-manager feedback completion rate
• Candidate drop-off during application

• The vendor cannot show a retention or legal hold setting.
• Key reports require paid services.
• References are only companies far larger or smaller than you.
• Pricing appears only after multiple calls and changes between conversations.
• Data export is described as possible but is not documented.

1. How are retention periods configured, and can we suspend deletion on specific records for a legal hold?
2. Can we export all candidate data, notes, and audit logs in a standard format if we leave, and at what cost?
3. Which fields transfer to our HRIS at hire, and is the sync automatic?
4. What automated scoring or ranking features exist, and what bias testing is documented?
5. Which job boards are included in the subscription, and which cost extra?
6. What is the implementation timeline for a company our size, and who does the migration?
7. What are the renewal terms, price escalators, and cancellation notice period?
8. What uptime commitment and support response times are in the contract?
9. How do you handle state and local rules, such as pay transparency fields and notices?
10. Can a hiring manager complete every task without training?

• Write down your hiring volume, roles, and process problems before the first demo.
• Limit must-haves to a short list and score every vendor with one script and weights set in advance.
• Verify retention, legal hold, and audit trails, because federal retention rules apply to the records your ATS holds.
• Test the HRIS handoff and the hiring-manager experience, where implementations most often fail.
• Price the full three years, including add-ons and renewal escalators.