Applicant Disposition
Recording the specific reason a candidate exited the pipeline — not qualified, withdrew, filled by another candidate — rather than leaving the record blank.
Applicant disposition is the recorded reason a candidate exited a requisition's pipeline without being hired — not qualified, withdrew, position filled by another candidate — rather than simply leaving their status blank or deleted.
Every candidate who doesn't get hired for a requisition gets tagged with a specific disposition code at the point they exit the pipeline, chosen from a defined list (not qualified, withdrew, failed screen, offer declined, position filled by another candidate, and so on) rather than a generic "rejected" catch-all. That specificity is what makes the data usable later: a funnel report can show exactly where and why candidates are dropping out, and a search for candidate rediscovery can distinguish a strong runner-up (worth reaching out to again) from someone who was never qualified in the first place.
Why the specific reason matters later
Of 50 applicants to a requisition, 30 get dispositioned as "not qualified," 12 as "withdrew," 5 as "position filled by another candidate," and 3 as "failed background check." Months later, a similar role opens. A search for candidates dispositioned as "position filled by another candidate" — a signal they were genuinely strong, just not first choice — surfaces exactly the 5 people worth reaching out to first, a distinction a generic "rejected" tag on all 50 candidates would have erased entirely.
In staffing & high-volume hiring
Beyond basic hygiene, disposition data is what a compliance-minded staffing operation needs on file to show that rejected applicants were considered and declined for a documented, consistent reason rather than an arbitrary one. It's also the data that later reporting depends on — a funnel report showing where candidates drop off is really just applicant dispositions rolled up across every requisition.
Common mistakes
- Using one generic "rejected" disposition for every non-hire, which erases the distinction between a strong runner-up worth rediscovering later and someone who was never qualified.
- Deleting applicant records instead of dispositioning them, which loses both the compliance record and the rediscovery value of that candidate's history.
- Leaving disposition blank on candidates who simply go quiet or ghost, rather than tagging that outcome specifically — it's a real, trackable pattern worth its own code.
Related terms & reading
Applicant Disposition FAQ
Why not just delete a rejected applicant's record instead?
Deleting the record loses the reason and the history, which matters both for compliance record-keeping and for future candidate rediscovery — a well-dispositioned "not qualified" for one role might still be a great fit for a different one later.
How many disposition codes should a company use?
Enough to distinguish the meaningfully different outcomes (not qualified, withdrew, failed a specific check, lost to another candidate) without so many granular codes that recruiters stop applying them consistently.
Does disposition data help with more than rediscovery?
Yes — aggregated across many requisitions, disposition data reveals funnel-wide patterns, like whether a particular stage (screening, background check) is where most candidates are actually dropping out.
Build a faster, smarter hiring engine.
Start your 30-day free trial — no setup fees, no contracts. Or see ATS Mako in action.
30-day free trial · No setup fees · No long-term contracts