Rejection rate

The claim: one percentage can show funnel quality

Teams often want one number to describe how selective a search was. A stage-level rejection rate can help them see where recorded decisions occur. For example, divide the candidates explicitly declined during screening by the candidates who entered that screening cohort, using a stated cut-off date.

That is a definition, not a verdict. A high or low rate does not say whether the role brief was sound, the candidate pool was suitable, or candidates had a fair experience.

The counter-case: stage movement is not a decision log

It is tempting to call everyone who did not advance “rejected.” That folds together candidates who withdrew, candidates held for later review, and applications with no recorded outcome. It also turns a gap in process data into an employer decision that may never have been made.

The distinction matters because each status calls for a different response. A withdrawal may call for a reason code if the candidate offers one. An open application calls for a review of the case. An explicit rejection calls for a recorded decision and whatever communication the employer has chosen to send.

What we would track

At Join we sell recruiting software, so weigh this recommendation accordingly: record the events before calculating the percentage. Keep explicit rejections, withdrawals, and open applications separate; set the cohort and reporting date; then inspect the underlying records alongside the rate. JOIN’s Pipeline management documentation supports stage management and Rejected application views, but it should not be read as evidence for a broader reporting feature.