Skip to main content

Managing applications in the pipeline

Every application belongs to one job and moves through the stages configured for that job.

Common stages​

A pipeline might run Applied → Screening → Evaluation → Interview → Offer → Hired. Admins can rename and reorder the stages to match how your organisation works.

The Kanban pipeline board with a column per stage and candidate cards showing score, tags and time in stage
The pipeline board, with applications in each stage.

Moving an application​

  1. Open the job and its candidates area.
  2. Select the application you want to work on.
  3. Move it to the next stage from the board or from the action inside the application.
  4. Check which forms, emails or automated actions were triggered.
warning

Changing a stage can send an email, assign an evaluator, create an event or reject the application automatically. Read the confirmation dialog before you continue.

Inside an application​

Depending on the pipeline, an application can have areas for comments, screening, tests, documents, evaluations, events, offers, emails and activity.

Bulk actions​

After a focused review session, handle the group at once instead of opening each application:

  1. Tick the applications in the list.
  2. Choose an action on the toolbar that appears — move stage, reject, send email or tag.
  3. Check the number of applications in the confirmation box, then confirm.
warning

Bulk actions trigger automation exactly as single actions do. One confirmation can send dozens of emails at once.

Ending an application​

An application leaves the pipeline in a specific state — hired, rejected, withdrawn or archived — with a reason your organisation defines. See Rejections and outcomes.