Recruitment pipeline and applications

Design hiring stages, move and reject applicants, use rejection reasons and keep a full activity history.

Every application sits in one stage of its job's pipeline. Open a job to see its board.

Stages

New jobs start with the workspace default: Applied β†’ Phone screen β†’ Interview β†’ Final interview β†’ Offer. Change the default in Recruitment β†’ Settings, or change the stages on one job in its settings. Each stage has a name and a type (applied, screening, interview or offer), which is what the analytics funnel uses. Hired and rejected are outcomes, not stages, so you never have to add them.

You cannot remove a stage that still has active applicants. Move them first, so nobody is lost.

Moving applicants

  • Drag a card to another column, or use Move to on the application.
  • Select several cards to move or reject them together.
  • Every move is recorded in the application's activity history with who did it and when.

Knockout answers

If a candidate gives an answer you marked as a knockout on a screening question, the application is flagged. Flagged applications show a warning so you can look at them first. They are never rejected automatically.

Rejecting

Choose a rejection reason (you can edit the list in Settings) and, if you want, send a rejection email from a template. Rejected applications leave the board but stay on the candidate's record. Reopen puts one back in the stage it was in.

Notes, emails and tags

Add notes (visible to the hiring team), send an email from a template, and tag the candidate. Everything appears in the activity history.

Hiring

Hire on the application creates the employee record with the job's department and title, and starts the onboarding checklist chosen for the job. When the number of hires reaches the job's headcount, the job is marked filled.

See also: Interviews and scorecards, Offers.

Was this article helpful?

Recruitment pipeline and applications β€” HR & Payroll | Plenix Cloud Docs