Applicant tracking system features worth paying for, writing applicant tracking system requirements you can score, which recruitment software features get used in practice, and how to choose an applicant tracking system without a hundred row matrix
Feature lists in this category run to hundreds of rows and are scored by people who will use about twelve of them. A requirements document that reflects that proportion produces a better decision in less time than an exhaustive matrix, because an exhaustive matrix rewards the vendor with the most complete list rather than the product your hiring managers will open.
- $499median advertised EOR price, per employee per month
- 7vendors with a verified published price
- 8hiring markets with measured demand
Figures on this page come from the EOR Compass Pricing Index: 7 vendors with a verified published price, median $499 per employee per month, checked against each vendor's own pricing page.
- 7 vendor price pages verifiedevery figure matched verbatim to the vendor's page
- Quoted and dated, never estimatedlast verification pass 2026-08-18
- 8 hiring markets coveredcoverage evidenced by vendors' own country pages
Writing requirements you can actually score
- List the twelve things done weekly. Post a job, screen, reply, schedule, scorecard, offer, and the reporting somebody asks for. If a requirement is not on that list, it belongs in a second tier that breaks ties rather than in the comparison.
- Score demonstrated rather than claimed. Three states: shown on our data, described, absent. A described feature is not dishonest and it is not evidence, and separating them changes which product wins more often than any weighting does.
- Give the manager a vote. Have a hiring manager complete one review in each finalist. Their two minute reaction predicts adoption better than the whole matrix, and adoption is the only thing that decides whether the purchase works.
The features used every week
Application capture that works on a phone, a candidate list a manager can read, templated replies, interview scheduling against real calendars, and a scorecard. That is close to the whole of the daily value, and a product that does those five well beats one that does forty adequately.
Scheduling deserves particular attention because it is the largest purely mechanical time cost in hiring. A product that resolves three calendars and a candidate's availability without email is saving hours a week that nothing else on the list touches.
The features demonstrated once and never used
Sourcing extensions, CV parsing accuracy, video interviewing, and the analytics suite. Each is real, each demonstrates well, and each requires either volume or a dedicated recruiter to pay off. Below that threshold they are cost and screen clutter.
The honest way to handle them is a second tier in the requirements document: nice, scored, and never allowed to outrank a weekly feature. Vendors will push them up the agenda because that is where they differ from each other.
Requirements nobody writes down and everybody needs
Data export, permissions granular enough to keep salary and notes away from the wrong eyes, candidate deletion for retention duties, and an audit trail of who changed a decision. These are the requirements that matter in the year you have a dispute or a subject access request.
They are also the ones vendors answer honestly when asked directly and vaguely when not asked at all. Put them in the document as pass or fail rather than as scored rows.
How to choose when two products tie
Break the tie on the manager experience and the exit. The manager experience decides whether the data stays real; the exit decides what the next decision costs. Both are more durable than any feature gap you can measure in a demonstration.
If they still tie, take the cheaper one on a shorter contract. A genuine tie means the difference is below the resolution of your evaluation, and flexibility is worth more than a coin toss.
Common questions
- How long should an ATS requirements document be?
- One page of weekly features scored, a short pass or fail list for data and permissions, and a second tier for everything else. Longer documents reward the vendor with the longest feature list.
- Is CV parsing worth scoring?
- Only at volume. Below a few hundred applications a month, parsing errors cost less time than the meetings spent comparing parsing claims.
- Should candidates rate the experience?
- Yes, and it is the most neglected input. A product with a slow or broken application form loses you candidates silently, and only candidates can tell you.
Get a shortlist for your hiring plan
Coverage by country
- Employer of record vendors covering Singapore
- Employer of record vendors covering Mexico
- Employer of record vendors covering Spain
- Employer of record vendors covering Colombia
- Employer of record vendors covering United Kingdom
- Employer of record vendors covering France
- Employer of record vendors covering Hungary
- Employer of record vendors covering New Zealand
Sources
Cite or embed this figure
The median advertised EOR price per employee per month in the EOR market was $499 in August 2026, across 7 verified vendor price pages recorded in EOR Compass Pricing Index.
Cite as: "EOR Compass Pricing Index", updated 2026-08-18, https://eorcompass.com/hr-payroll/applicant-tracking-system-features/.