Pipeline stage types and settings
A reference for every stage type and every setting inside a pipeline stage: team access, emails, decision rules, auto-advance and sub-statuses.
A reference for every stage type and every setting inside a pipeline stage: team access, emails, decision rules, auto-advance and sub-statuses.
This reference is for Admin users editing a pipeline template under Settings > Hiring Process > Pipeline Templates, and for Admin, HR and hiring leads editing a job's own pipeline. The stage editor is the same in both places. Open a stage by selecting the arrow on its row. Each expanded stage has a short plain-English summary at the top, then up to four sections.
Stage types
The Stage Type dropdown decides how Recruit treats candidates in the stage.
| Type | What it does |
|---|---|
| Application received | Only offered on the first stage. It is the inbound stage where new applications land. It has no evaluation form, but it carries the application emails and the auto-advance setting described below. |
| Screening / shortlisting | Takes a default shortlisting checklist. Candidates cannot be moved forward until the required reviewers have finished and the pass threshold is met, if checklists are attached to the stage. |
| Interview | Takes an interview evaluation form. Scheduling is set to calendar-based when you choose this type. Interview stages are the ones that appear on the job's Events tab, so a job needs at least one to schedule interviews. |
| Video interview | Only shown if your organisation has the video interviewing add-on. Takes a video interview template. See "Video interviews with HireFlix". |
| Assessment | No type-specific settings. Use it to label an assessment step. |
| Offer | Moving a candidate here runs the right to work check. Depending on your organisation's setting, the move is either allowed with a warning or blocked until right to work is verified. Candidates in an Offer stage are never auto-rejected. See "Right to work and governance". |
| Custom | No type-specific settings. Use it for anything else, such as Hired. |
Changing a stage's type clears any feedback form or checklist that does not belong to the new type. Stages themselves cannot be colour-coded. Only sub-statuses have colours.
Stage Basics and Team Access
Stage Name and Stage Type are under Stage Basics. Names are up to 100 characters and must be unique within the pipeline.
Team Access has three checkboxes: Recruiters can see candidates at this stage, Hiring managers can see candidates at this stage and Interviewers can see candidates at this stage. Tick none and everyone on the job can see the stage. Tick some and only those job roles can. Admin and HR users always see every stage. A person who moves a candidate must be able to see both the stage the candidate is leaving and the one they are entering.
Candidate Experience
- Email sent on stage entry: choose an email template, or No automated email. The email goes to the candidate each time they are moved into the stage from a different stage. Moving to the stage they are already in sends nothing. On the first stage this control is replaced by the application emails below.
- Auto-reject after (days): a whole number from 1 to 365, or empty for no auto-reject. Once a day, overnight, Recruit rejects every active candidate who entered the stage more than that many days ago. The clock starts from their most recent move into the stage. The rejection reason recorded is "Auto-rejected: exceeded N days in stage", and the candidate receives the stage's rejection email if one is set, otherwise the job's default. Offer stages are never auto-rejected.
- Rejection email for this stage: choose a rejection template for this stage, or leave it on Use default rejection email.
The first stage has two email pickers and both are required: Application started email (sent once, when the candidate first saves or moves past page one of the form) and Application complete email (sent once the candidate submits the finished form). Until both are chosen, Save Changes is disabled with the message "The Applied stage needs both an acknowledgement email and an application complete email." If a job using the stage has a multi-page application form, include the resume link in the started email so candidates can return to it. See "Stage automations and rejection emails" for how the templates work.
Decision Rules
Shown on screening and interview stages.
- On a screening stage, Default Shortlisting Checklist (optional) picks from your active checklists. Jobs made from the template start with that checklist attached. See "Building shortlisting checklists".
- On an interview stage, Interview Evaluation Form (optional) picks from your interview feedback forms. See "Building an interview feedback form template".
Video interview stages have their own Video Interview section with a Video Interview Template (optional) picker.
Once a job has its own pipeline you can set more on the interview stage: Pass Threshold and Minimum Respondents, the number of interviewers who must submit feedback. Moving a candidate forward when the threshold is not met, or too few have responded, shows a warning but does not block the move. Screening thresholds do block. Minimum respondents cannot be higher than the number of interviewers in the stage's pool.
Advance on completion
The first stage has one extra control, When the application is complete, advance candidate to. The default is Don't advance automatically. Pick a later stage and candidates are moved there as soon as their application is complete. The move is recorded in their history like any other, and the stage entry email for the new stage is sent. Only stages after the first can be chosen. If you delete or move the chosen stage the setting is cleared.
Sub-statuses
Sub-statuses let recruiters tag candidates within a stage, for example "Attempt to contact 1", "Attempt to contact 2". In the stage's Sub-statuses section, type a name (up to 100 characters), select Add, then drag to reorder, pick one of eight colours, rename by editing the text, or delete with the bin icon. Deleting a sub-status never fails: candidates who had it lose it. In a template, sub-status changes are saved with Save Changes. On a job's pipeline they are saved immediately.
Recruiters set a candidate's sub-status from the candidate's own page, and also from a dropdown on each row of the job's Shortlisting tab when the stage has sub-statuses. Under Settings > Team & Access > Roles & Permissions, the switch Allow hiring managers to edit a candidate's sub-status is off by default. While it is off, only Admin, HR and the job's recruiter can change a sub-status. Interviewers can never change one.