Pipeline Stages | CONFIRM Docs

Every candidate sits in exactly one pipeline stage at a time. Stages give your team a shared view of where each applicant stands, and CONFIRM moves candidates between many of them automatically based on screening and interview outcomes.

Looking for a quick definition of a specific status — including the round-numbered statuses used in multi-step pipelines? See the Status Reference.

Stage reference

Stage	What it means	Type
Applied	The candidate just entered the system and hasn’t started screening yet.	Active
Awaiting Screening	Queued for the AI screening call — including retry and voicemail attempts.	Active
Ineligible for Screening	Blocked before screening could happen (for example, blocklisted or failing a pre-screen rule).	Terminal
Eligible (Awaiting Scheduling)	Passed screening; waiting for an interview to be scheduled.	Active
Failed Screening	Completed the screening call but didn’t meet the knockout criteria.	Terminal
Client Screening	Going through your team’s own screening or review steps.	Active
Client Request Interview	Your team has requested an interview with this candidate.	Active
Pending Evaluation	An evaluation has been sent (or is ready to send); waiting for results.	Active
Interview Scheduled	An interview is booked.	Active
Reschedule Requested	The candidate asked to move a scheduled interview.	Side-step
No Show	The candidate missed a scheduled interview.	Side-step
Past Interview	The interview happened; a decision (hire, next round, or reject) is pending.	Active
Awaiting Recruiter Action	The automated flow paused; a recruiter needs to decide what happens next.	Side-step
Failed Interview	The candidate wasn’t successful after interviewing.	Terminal
Hired	The candidate was hired.	Terminal (success)
Rejected	The candidate was removed from consideration by your team, or withdrew.	Terminal
Do Not Contact	The candidate should not be contacted again.	Terminal
Refused Recording	The candidate declined call recording, so the screening call couldn’t proceed.	Terminal

Active stages are on the main path toward a hire. Side-step stages are temporary detours — the candidate returns to the main flow once you act (for example, rebooking after a no-show). Terminal stages end the process.

In Flow vs. Closed

For reporting and filtering, stages are grouped:

In Flow — Applied, Awaiting Screening, Eligible (Awaiting Scheduling), Client Screening, Pending Evaluation, Interview Scheduled, Past Interview.
Closed — Hired, Rejected, Do Not Contact, Refused Recording, Failed Screening, Ineligible for Screening, Failed Interview.

The status filter on the Candidates page has its own Active and Closed presets; its Closed preset covers only Hired, Rejected, and Do Not Contact so that failed-screening candidates stay in your working set. See Filters and Saved Views.

Automatic transitions

CONFIRM advances candidates without manual work when outcomes are clear:

A new application enters as Applied and moves to Awaiting Screening when ready to be called.
A screening call that meets the criteria moves the candidate to Eligible (Awaiting Scheduling).
A screening call that misses knockout criteria moves them to Failed Screening.
Candidates blocked before screening go to Ineligible for Screening; refusing call recording goes to Refused Recording.
Booking an interview moves the candidate to Interview Scheduled; afterwards they move to Past Interview.

Manual transitions

Three actions on the candidate profile move candidates by hand:

Advance — the primary button that moves the candidate to their next step (its label changes with the stage: Start Screening, Schedule Interview, Send Evaluation, Hire, and so on).
Reject — ends the process, with the outcome recorded (rejected or withdrew).
Override Status — moves the candidate to any valid stage outside the normal flow, with a required reason kept in their history.

Per-job pipeline configuration

Each job can configure its own workflow — interview rounds, evaluations, and review steps — in the Pipeline tab of that job’s console. The stages above are the building blocks; the job’s pipeline determines which of them apply and in what order.