Checks and warnings when moving candidates
The checks that can refuse a stage move, the warnings that let it through, and what to do when a bulk move only partly works.
The checks that can refuse a stage move, the warnings that let it through, and what to do when a bulk move only partly works.
This is for anyone who can move candidates between stages on a job: Admin and HR users, the job's recruiter, and hiring managers where your organisation allows it. The ways to move a candidate are in Moving candidates through pipeline stages.
Checks that refuse a move
The checks run in this order. The first three refuse the move. The last two normally let it through with a warning.
- Permission and stage visibility. The messages are "You are not permitted to move candidates between pipeline stages", "You do not have visibility to the target stage" and "You do not have visibility to the source stage". A bulk move that includes a hidden source stage is refused as a whole.
- Shortlisting review incomplete. When a stage has shortlisting checklists with assigned reviewers, a candidate cannot move forward until enough of those reviewers have submitted their evaluation. By default every assigned reviewer is needed. A stage can set a lower minimum. Only assigned reviewers count, and a reviewer who has submitted still counts if the checklist was saved again afterwards. The same rule decides when a candidate shows Awaiting scoring on the Shortlisting tab. The red message has the title Failed to move candidate and reads, for example, "Shortlisting review is incomplete for: Essential Criteria (1/2)". Chase the missing reviewers, or open the Shortlisting tab to see who has not finished.
- Pass threshold not met. If a checklist on the stage has a pass threshold and the candidate's evaluations fall below it, the message is Shortlisting Threshold Not Met: this candidate has not met the required pass threshold for the current stage, so review their shortlisting scores before progressing. A candidate with no evaluations yet is not held by this check.
The shortlisting checks apply to forward moves only, meaning a move to a stage further along the pipeline than the one the candidate is in. Moving a candidate backwards is never blocked by them.
Warnings that let the move through
- Interview feedback. If the stage the candidate is leaving has a feedback pass score and the average is below it, you see "Interview feedback score {score} is below the required threshold of {threshold}". If the stage needs a minimum number of feedback responses and fewer have arrived, you see "Only 1 of 2 required interview feedback responses have been submitted." (with your own numbers). The candidate is still moved. This applies to forward moves only.
- Right to work. Moving a candidate whose right to work is not verified into an Offer stage goes ahead with the warning "Right to work verification has not been completed. Please ensure compliance before making an offer." Some organisations are set up so that the move is refused instead, with "Right to work verification must be completed before progressing to the offer stage". Verify the candidate first. See Right to work and governance. This check applies to any move into an Offer stage, forwards or backwards.
Warnings from a single move appear together in one amber message under Candidate moved successfully. Bulk moves do not show them, apart from the note about candidates with no valid email address, which is described in What happens after a candidate is moved.
When a bulk move only partly works
Candidates are moved in batches of 25. If some candidates move and others are refused, the message reads "{n} moved, {n} failed". It then names the people who were not moved, in the form "Not moved: Name, Name.", listing up to 10 names and then "and N more". It does not give reasons. Open a candidate who did not move and move them on their own to see the reason.
If your session ends or your permissions change partway through a large move, the batches that had not started are not attempted, and the message says "{n} was not attempted because your session or permissions changed." If Recruit could not confirm what happened to a batch, you see "Could not confirm: Name, Name. Refresh to check them before trying again." Refresh the page and check those candidates before moving them again.
If none of the candidates move, the message is Failed to move candidates, followed by the reason when the whole request was refused, for example a permission or visibility problem. A fully successful bulk move reads "{n} candidate(s) moved successfully".
Rejecting several candidates at once reports its results in the same way. See Rejecting candidates.