Applicant tracking systems for in-house recruiting teams

What does an applicant tracking system actually do?

An applicant tracking system (ATS) is the record of every hiring process: the approved requisition, the job advert and where it was posted, each applicant, who reviewed them, what interviewers said and how the offer was made. Its practical value is consistency. When every candidate moves through the same stages with the same scorecards, hiring managers stop working from their inboxes and you can show why a decision was taken.

Most products also handle job board distribution, a branded careers page, interview scheduling, email templates, offer letters and basic reporting such as time to hire and source of hire. Beyond that, the market splits: some tools add a sourcing CRM for passive candidates, others lean into high-volume screening, and others are deliberately simple for companies hiring a handful of people a year.

An ATS does not fix a weak hiring process on its own. It makes the process visible, which is useful precisely because it shows where candidates stall, which interviewers are slow to give feedback and which sources produce hires rather than applications. Before buying, write down your current stages, approval steps and who owns each one; that document becomes both your requirements list and your configuration plan.

Should you buy a standalone ATS or use your HR suite's recruiting module?

Many HRIS and HCM suites now include a recruiting module, which makes this the first real decision. The trade-off is depth of recruiting features versus a single employee record.

If you choose a standalone ATS, confirm how the hire record passes to your HRIS. A reliable integration that creates the employee profile on offer acceptance removes a surprising amount of re-keying and error.

What should you compare before you shortlist?

Run each vendor through the same questions, ideally using one of your real open roles in the demo.

How are applicant tracking systems priced?

Small-business tools usually charge a flat monthly fee tied to the number of active job openings or users. Mid-market and enterprise vendors typically price annually by employee headcount, sometimes with a minimum contract value, and quote add-ons such as CRM, advanced analytics, onboarding or premium job board packages separately. Implementation and data migration fees are common above small-business tier.

Watch the metric. A per-job model can become expensive when you keep evergreen roles open, while a per-employee model charges you for growth that has nothing to do with recruiting volume.

Ask for renewal caps in writing. Recruiting volume swings with the economy, and some contracts make it hard to reduce seats or tiers when hiring slows.

What usually goes wrong?

The most common failure is hiring managers not using the system. If feedback still arrives by chat message, the ATS data becomes incomplete and reporting is meaningless. Make feedback submission part of the process, and pick the tool whose manager interface your least technical manager can use.

Other frequent problems are over-customised pipelines with a dozen stages nobody maintains, migrations that bring years of stale candidate data and create retention liabilities, careers pages that break brand consistency, and integrations with background checks or HRIS that are assumed rather than tested. Agree a small, standard set of stages, clean data before migrating, and test the end-to-end path from application to employee record before go-live.

Finally, candidate experience is easy to damage. Long application forms, forced account creation and silence after an interview reflect on your employer brand. Apply to one of your own jobs on a mobile phone during the trial and fix whatever frustrates you.

Frequently asked questions