Rule Stages can be used to skip a stage, fast-track applicants, or auto-reject applicants. Rule Stages can be used to automatically move applicants to another stage in any Opening, or to update their profile based on certain criteria (e.g. responded to "Are you over 21?" with "No").
Rule Conditions and Criteria
Here is the list of logic criteria, and the actions you can build rules on:
If (Conditions)... | ...Then (Actions) | |
---|---|---|
Learning Status/Result | ||
Personality Test Score | ||
Applicant Duplicate Status | ||
Background Check Status | ||
Applicant Field | Move to the stage... | |
Applicant Label | Move to another opening | |
Document has been Uploaded | Update application data with... | |
Score Card Result | ![]() |
Move to the stage... |
Document Signing status |
What's Covered
Add a Rule Stage
- Select Applicants and select Applicant Table from the dropdown menu.
- Within the applicant table, select Settings.
- Select Edit Workflow.
- On the top left, click on the Add rule button.
- Give your Rule Stage a title, choose the rule type, and specify where you want to add it in the workflow.
- Click the blue Add Rule Stage button to confirm.
- Click on the green Add rule button to add a rule. You can add multiple rules to the same Rule Stage for a cleaner workflow (instead of a workflow with many Rule Stages back to back).
- Fill the logic condition(s).
- Give it an action(s) in response to the condition criteria.
Multiple Actions
The action can also perform multiple actions to your rules. For example, you can simultaneously move the applicant AND update their profile IF they meet the criteria.
- Give an action for applicants who don't meet the logic.
Moving to Reject
If you choose to reject an applicant as the action, keep in mind that rejection reasons are customizable in your company settings and can have specific message templates applied and sent if the applicant lands in the rejected stage. For more information on this, visit this resource.
- Select Save changes.
Placement of the Rule Stage
In order for the rule to apply for the applicant to pass through the Rule Stage,
The Rule Stage MUST be placed after the stages that collect the information you are building the criteria for. For example, the Rule Stage is based on a field (age_requirement = yes). You cannot place this Rule Stage before the Data Collection stage that asks the question "Do you meet the age requirement?" question because all the applicants who have gone through this Rule Stage will not have this field yet.
Rules Cannot Retroactively be Applied
All future applicants going through this rule stage who match the rule set will be move/updated according to your rule, but any applicants in the stage after the ruling stage will not.
Multiple Value Condition
You can add multiple numerical values to a rule condition. For example, if you are trying to sort applicants with a rule stage by zip code, you can list all of the zip codes in one comma-separated list, instead of creating multiple rules.
Make sure to select Is in this list and you'll need to input the numerical values separated by a comma (no space).
In this example, all applicants that have a zip code 94112, 94103, or 94121 will be moved to the next stage. If their zip code is not in the list above, they would not meet this rule's criteria and based on the actions we set for "if applicant does not meet any rule, then..." the applicants would be rejected.
Complex Conditions
You can also build more complex logic where you string together multiple conditions using "OR" or "AND".
For example, if the applicant answers "No" to over 18 years old AND "No" to having a car AND "No" to having a Driver's License THEN they will be moved to Rejected with a custom reason "Does not meet requirement". Otherwise, the applicant will move forward to the next stage.
Comments
0 comments