An Applicant Tracking System that lets desks close a vacancy without a documented close reason leaves win/loss learning, client truth and pipeline hygiene in chat. Require a structured close reason on every closed vacancy — filled, client cancelled, on hold became permanent, role withdrawn, filled elsewhere, or other with a short note — without vanity metrics or promising that artificial intelligence replaces recruiters.
This matters for recruitment agencies, staffing, secondment, executive search and in-house recruitment. A vacancy close reason is distinct from candidate rejection reasons (why a person left the pipeline), from a confirmed placement start date (when the hire begins before close), from a target fill date (the fill aim set at open), from a structured vacancy brief (what the role needs) and from a single role owner (who owns the vacancy). Close reason answers why the vacancy left the open board — recorded at close, not invented in a quarterly review.
Why closing vacancies without a documented close reason breaks desk learning
Closing a role with “done” or a blank status looks tidy and still poisons later work. Typical failure modes:
- Desks cannot see whether they won the work (filled) or lost it (client cancelled, filled elsewhere, withdrawn)
- Client conversations stay political because the Applicant Tracking System never stored why the vacancy ended
- Win/loss coaching becomes storytelling because free-text notes hide patterns across desks
- On-hold roles that quietly become permanent disappear from review without a coded path
Candidate rejection reasons explain why a person did not progress; they do not explain why the vacancy itself closed. Closing without a documented close reason turns every ended role into a rumour.
What a documented close reason means
Define it clearly in the Applicant Tracking System:
- Close reason — a structured code on the vacancy at close: filled / client cancelled / on hold became permanent / role withdrawn / filled elsewhere / other with a short required note
- Named desk owner — the signed-in user who closed the vacancy and selected the reason; not “desk”, not a shared mailbox
- At close — the reason is required when the vacancy status moves to closed (or equivalent), not as an optional note weeks later
- What it is not — a candidate rejection reason, a confirmed placement start date, a target fill date, a structured brief or a single role owner field
If close reason stays optional, desks skip it under volume and invent stories only when a manager asks. The habit only works when the Applicant Tracking System blocks vacancy close until a close reason is present — and requires a short note when the code is “other”.
How to require a documented close reason in the Applicant Tracking System
Process beats goodwill. In the Applicant Tracking System:
- On vacancy close, require a structured close-reason code from a short controlled list
- Block the close until the code is present; for “other”, require a short free-text note (not a blank field)
- Keep close reason on the vacancy record, separate from candidate-level rejection codes
- When the reason is filled, pair close with a confirmed placement start date so “filled” is not hope without a start
Pair this with a single role owner so someone owns the close decision, and with standardised rejection reasons so people-level exits stay distinct from vacancy-level close codes.
Alerts and desk review without vanity metrics
Alert on vacancies closed with blank or “other”-without-note reasons, and on long on-hold roles that never resolve to a coded close. Do not invent “close-reason completeness scores” or leaderboards of who picks the nicest codes. In the next desk meeting, review the mix of filled versus client cancelled versus filled elsewhere, which “other” notes cluster, and whether permanent on-holds were closed with the right path. That review is quieter than a full win/loss rebuild and more honest than vanity charts.
Where artificial intelligence may help — and where it must not
Artificial intelligence may suggest a close-reason code from placement status, client email language or similar past closes for a human to confirm. It must stay secondary. Artificial intelligence does not replace recruiters, does not invent a win or loss the desk never agreed and does not clear a vacancy-close gate without a recorded human confirmation. Humans own close decisions. The Applicant Tracking System stores the close reason, the owner and when the vacancy closed.
How this sits next to rejection reasons, start dates, fill dates, briefs and owners
Documented close reasons complement other Applicant Tracking System habits:
- Standardised rejection reasons explain candidate exits; close reasons explain why the vacancy left the open board
- A confirmed placement start date proves when work begins before a filled close; it does not replace the close-reason code
- A target fill date from day one sets the fill aim at open; close reason records how the vacancy actually ended
- A structured vacancy brief defines the role; close reason is the end-of-life code beside it
- A single role owner owns the vacancy; they still need an explicit close reason at close
Without a required documented close reason, ended vacancies hide whether desks won or lost work. With it, every closed role carries a coded why — or an explicit other with note — before the Applicant Tracking System treats the vacancy as closed.
A practical week to introduce documented close reasons
One week in the Applicant Tracking System:
- List recently closed vacancies with blank or free-text-only close notes and backfill structured codes with owners
- Turn on requiring a close-reason code (and note for “other”) before vacancy close commits
- Agree the short code list (filled / client cancelled / on hold became permanent / role withdrawn / filled elsewhere / other) and keep “other” notes reviewable
- Close silent close paths with blank reasons or route them through a desk queue
- In the next desk meeting, review the close mix, “other” clusters and remaining blank-reason exceptions
That habit is quieter than a full reporting project. It is also how vacancies stop closing on hope while the real win/loss reason lives only in chat.
Document the close reason — then learn from every ended vacancy
If your Applicant Tracking System allows a vacancy to close without a documented close reason, desk learning will stay on guesswork. Require the structured close reason — with a short note when the code is other — at close. Keep artificial intelligence as a suggester only. Then explore the product or book a demo — we walk through BoldATS vacancy close-reason discipline in your segment.