Choosing hiring software · 6 min read
How to choose an applicant tracking system
The right applicant tracking system makes your current hiring process faster and easier to follow. This guide shows how to work out what you need, compare options on the same terms and test them before you commit.
Start with how you hire today
An applicant tracking system (ATS) holds your job openings, applicants and hiring decisions in one place. The right one makes your current process faster and easier to follow. The wrong one adds clicks and gets ignored. So before you look at any product, write down how hiring works now.
Pick two or three recent hires and trace each one from the moment the role was approved to the signed offer. Note who did what, where the information lived and where things slowed down. If you have not mapped your stages yet, our guide to designing a hiring pipeline is a good place to start. Then answer these questions:
- How many roles do you open in a typical quarter, and how many applicants does each one get?
- Who takes part: recruiters, hiring managers, interviewers, approvers, outside agencies?
- Where do applicants come from: your careers page, job boards, referrals, agencies?
- Where do things get stuck: screening, scheduling, feedback, approvals or offers?
- What do you report on today, and to whom?
The answers tell you what problem you are actually solving. A team buried in CVs needs strong screening. A team that loses days chasing interview feedback needs good collaboration and reminders. A team hiring across several sites needs clear permissions and shared reporting.
Turn problems into requirements
Next, turn each pain point into a requirement you can test. Write requirements as outcomes, not features. 'Hiring managers can leave feedback from their phone in under a minute' is testable. 'Mobile app' is not. Then sort every requirement into three groups:
- Must have: you will not buy a system without it. Keep this list short, ideally under ten items.
- Should have: valuable and worth paying a little more for, but you could work around it.
- Nice to have: features you would use now and then. These should rarely decide the outcome.
Typical must-have areas include:
- Job posting: an apply link, a careers page or embed, and a simple way to reach the job boards you use.
- Screening: a consistent way to compare applicants against the job's requirements, not just keyword search.
- Pipeline: stages that match your process, with notes and feedback attached to each applicant.
- Scheduling: a way for applicants to book interview times without long email chains.
- Collaboration: roles and permissions, so each person sees what they need and nothing more.
- Reporting and export: basic metrics and a way to get your data out.
- Data protection: consent, retention and deletion controls.
Ask the people who will use the system every day to review the list. Recruiters and hiring managers often spot gaps that a buyer misses. For every criterion in one scannable list, use our ATS selection checklist.
Build a shortlist and a scoring sheet
Look for three to five systems that clearly meet your must-haves on paper. More than that and the comparison turns into noise. Fewer and you have nothing to compare against.
Before any demo, set up a simple scoring sheet so every option is judged the same way. List your requirements down the side and the systems across the top. Score each requirement from 1 to 5 and give the most important ones a higher weight. For example:
- Screening against job requirements: weight 3
- Pipeline stages and team feedback: weight 3
- Ease of use for hiring managers: weight 3
- Interview scheduling: weight 2
- Reporting and export: weight 2
- Setup effort and support: weight 2
Multiply each score by its weight and add up the totals. The number will not make the decision for you, but it stops the most polished demo from winning by default. Agree on the weights before you see any product, not after.
Use the same script for every demo so the scores stay fair. Our list of questions to ask in a hiring software demo covers what to ask and what to watch for.
Test it with a real role
A demo shows you the system at its best. A trial shows you how it behaves with your work. Wherever possible, run your top one or two options against a real or recently closed role.
- Pick a role with a fair number of applicants and a hiring manager who will give honest feedback.
- Load the job description and a set of real CVs, handled under your normal privacy rules.
- Move a handful of applicants through every stage: screening, interview, feedback, offer and rejection.
- Ask the hiring manager to review applicants and leave feedback without any training. Watch where they get stuck.
- Pull one report and one data export to see what you can actually get out.
Pay attention to everyday tasks. How many clicks does it take to reject an applicant with a polite message? Can an interviewer find the right scorecard? Does the shortlist make sense when you compare it with your own judgment? Small frictions repeated hundreds of times matter more than a feature you will use twice a year. In Spark Careers Enterprise, each CV is scored against the job's requirements, with the matched and missing skills listed and a short summary, so during a trial you can check whether the ranking matches how your team would judge the same applicants.
Look at cost, setup and data
The price on a website is rarely the full cost. Ask each vendor to put the following in writing:
- How pricing works: per user, per job or a flat fee, and what changes when you add users or open more roles.
- Setup and training: what is included, what costs extra and how long a typical setup takes.
- Support: how you contact support, which hours it covers and how quickly it responds.
- Contract terms: length, notice period and any automatic renewal.
- Data: where it is stored, who can access it and how you get all of it back if you leave.
Count the internal cost too. Someone has to set up jobs, stages, templates and permissions, and someone has to train the team. A cheaper system that takes months to set up can cost more than a pricier one that is running in a week.
Data deserves its own check. Confirm the system lets you record consent, set how long applicant data is kept and delete it on request. Check the employment and data protection rules where you hire, and make sure the system supports them without manual workarounds.
Decide and plan the rollout
Bring the scores, trial notes and cost figures to the people who will sign off. Talk through the top two options, not every option. If the scores are close, choose the system your hiring managers found easiest to use. Getting busy managers to use a new tool is usually the hardest part of any rollout.
Plan the switch before you sign:
- Choose a start date and one or two pilot roles.
- Set up your stages, email templates, scorecards and user roles.
- Decide what to bring across from your old process and what to archive. If you are coming from spreadsheets, our guide to moving hiring off spreadsheets covers the steps.
- Train recruiters first, then hiring managers, in short sessions tied to real tasks.
- Review after the first month: what is working, what is being skipped and what needs changing.
A good choice is the system your team actually uses, every day, for every role. Judge each option against that test and the decision becomes much clearer.
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.