Skip to main content

Adding Conditions to Hiring Workflow Stages

Define conditions a candidate has to meet before moving to the next stage in the hiring workflow

Written by Emilia Carvell

You can add conditions to a hiring workflow stage so a candidate can only be moved into that stage once the conditions are met. Conditions only apply to forward moves. Moving a candidate back, rejecting or withdrawing always works.

This keeps your funnel accurate and stops candidates skipping steps or reaching Hired or Onboarding stages before they should.

✅ Permissions

You need Manage jobs or Company settings permissions.

🔒 Availability

This setting is turned off by default. Contact our Support team to get it enabled for your account!


Adding Stage Conditions

You can set conditions on stages in a job template (these are inherited by any job using the template) or an individual job.

A stage can carry more than one condition. When it does, all of them must be met before a candidate can move in.

To add a stage condition:

  1. Open the job or job template.

  2. Click Edit.

  3. Select Edit Stages.
    ​

  4. Edit the stage you want to add a condition to.

  5. Click Add Stage Condition (at the bottom of the panel).
    ​

  6. Select an option from the list of available condition.

  7. Define the condition settings.

  8. Click Add.
    ​

  9. Click Save Stage.

ℹ️ Note

Candidates already past a stage when conditions are switched on are not blocked or moved back.

⚠️ Caution

Stage conditions are a hard block in this version. There is no override available at this time.


Triggering Stage Conditions

When a condition is met, the candidate can be moved to the next stage.

When a condition is not met:

  • the blocked stage shows a padlock and explains what is missing.

  • the card returns to its original stage and shows the reason on the Kanban board.

  • the block applies everywhere a stage change happens: the stage dropdown, drag on the board, workflow automations and bulk moves.


Available Conditions

You have access to the following conditions.

Condition

Description

Accepted Offer

The candidate’s most recent offer must be accepted. If a newer offer hasn’t been accepted, the condition isn’t met, even if an earlier offer was.

Actioning User

Only members of the selected Access Groups can move candidates into this stage. This is the only condition you can add to the Rejected stage, so it doesn’t block automated rejections such as knockout questions.

Completed Interviews

An interview must have taken place on the selected stages. A scheduled interview counts once its end time has passed. No-shows and cancelled interviews don’t count.

Completed Scorecards

A scorecard must be submitted on the selected stages. You can require one from every interviewer, or just one in total.

Application Tags

The candidate must have any, all, or none of the selected tags.

Previous Stages

The candidate must have been in the selected stages before entering this one. Imported candidates are exempt.

Application Answers

The candidate’s answers to application form questions must have a specific value. For example: “Question X equals Y” or “Question X has been answered”. This works with text, number, date, multiple-choice and yes/no questions.

Application Custom Fields

The candidate's answers to custom fields on the application must have a specific value. This works with text, number, date and dropdown fields, among others.

Did this answer your question?