Applicant tracking system (ATS)

Prism

The system that manages candidates from application to offer, which should receive evaluation results only after a person has reviewed them.

What is an applicant tracking system?

An applicant tracking system manages candidates through a selection process, from the first application to the final offer. It holds applications, records each stage a candidate passes through and keeps the history of every decision. Admissions offices use equivalent systems for the same purpose. Evaluation tools exchange data with the ATS, receiving applications from it and returning results to it.

Also called: ATS, Admissions management system, Recruitment system

Why results should enter the ATS only after review

Once a score appears in the applicant tracking system it tends to be treated as a decision, and later stages filter on it automatically. An unreviewed automated score that enters the record can therefore shape an outcome nobody actually decided. Passing only reviewed results back to the ATS keeps the system of record aligned with accountable decisions. It also means that every status in the ATS can be traced to a named reviewer.

  • Downstream stages often filter candidates automatically on recorded scores.
  • Reviewed results keep the system of record aligned with accountable decisions.
  • Every status change can be attributed to a named reviewer.
  • Candidate data shared with evaluation tools can be limited to what they need.

How an applicant tracking system works

  • Applications for a role or programme are read from the ATS.
  • Only the fields the evaluation requires are passed to it.
  • Evaluation results and evidence are held for human review.
  • Reviewers confirm or override each result with a reason.
  • Reviewed results and status changes are written back to the ATS.
  • Each write-back records the reviewer and the time of the decision.

How an applicant tracking system is evaluated

ATS integration is evaluated on the accuracy of what is exchanged and on the control over what is written back. Check the following on each cycle:

  • share of written results that carry a named reviewer
  • unreviewed results that reached the ATS
  • candidate fields shared beyond what evaluation required
  • mismatches between evaluation records and ATS statuses
  • time from review to updated status in the ATS

Limitations, risks and common failure modes

  • Automated scores are written directly and treated as decisions downstream.
  • Status codes differ between systems and candidates land in the wrong stage.
  • Full candidate profiles are shared when only a few fields were needed.
  • Overrides made in the ATS never return to the evaluation record.

All 315 terms