Recorded Finalist Standing With a Dated Re-Entry Route

Record, for every finalist who cleared the bar and received no offer, the cohort size, the class of reason and a dated stage the record re-enters at when a requisition at the same level opens.

Intervention I-017 Actor: recruiter process Scope: organizational Cost: low Evidence: hypothesis

On the canonical path

Declined, with a reason that can be acted on — Not every candidate is hired, and a decline is not a deviation. What makes it part of this path is that it arrives, it names the stage it happened at and the criterion that decided it, and it says whether applying again is worth anything.

This entry is one of the things that holds that commitment up.

What it looks like when this intervention is in place

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

The closing record, and what it leaves behind reconstruction

Title: req #4471 · closing record

Outcome: cleared every round · not selected · cohort: 4 finalists, 1 offer · reason class: cohort ranking — domain overlap
Standing: finalist · re-entry at the technical panel until 14 March · applies to any L4 requisition in Engineering
d0 Sent with the decline: the cohort size, the class of reason, the re-entry stage and the date it runs to.
w11 req #4471 reposted → 2 standings matched → both records enter the recruiter queue at the panel stage
Where the requisition closed unfunded rather than filled, the reason class reads funding withdrawn and the standing is recorded on the same terms.

What to notice: A ranking cannot be turned into a fault, and this does not try. It records what the ranking was and what the record is entitled to afterwards, so the outcome leaves something behind it.

What this targets

Expected effects

M-002 becomes a recorded outcome: the cohort size and the class of reason sit in the record and in what is sent, instead of arriving as a decline with no account of the group
B-010: a requisition that closes with more finalists than offers leaves standings behind it that outlast the closing
P-002: a reposted requisition matches against the standings recorded against its previous run, and the stage a matched record re-enters at is stated

What to measure

finalist_standing_record_rate
finalist_reentry_rate
reposted_requisition_match_rate

From each side

The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.

Candidate

What reaches them: A decline naming the cohort size, the class of reason, and the stage and date the record re-enters at.
What it means from there: The outcome was a ranking in a group of a stated size rather than a fault found in the rounds, and the record has a stated life after the decision.
What happens next: Applies again inside that date and enters at the stated stage, instead of starting the loop from the screen.

Recruiter

What reaches them: A required reason class and a cohort count on the closing record, and a queue where matched standings sit alongside new applications.
What it means from there: The outcome has to be classified before the requisition can be closed, and a comparison is one of the classes the taxonomy contains.
What happens next: Records the class, sends the cohort size and the re-entry date with the decline, and works the matched standings when a requisition at that level opens.

Hiring manager

What reaches them: Two records arriving at the panel stage on a reposted requisition, each with the previous panel's scores attached.
What it means from there: The evidence the earlier loop produced is reusable up to the date on the standing; after that the record re-enters at the screen like any other.
What happens next: Runs the panel on the standing rather than the full loop, or lets the standing lapse where the level or the profile has moved.

Share card png This page as markdown json