How conditional logic works on application forms
Show or require a question only when a candidate has answered an earlier question in a particular way.
Show or require a question only when a candidate has answered an earlier question in a particular way.
Conditional logic lets an application form change as the candidate fills it in. A question about previous names can stay out of sight until someone says they have used another name. You set the rule on the question you want to control, and it points back at an earlier question whose answer decides what happens. Rules can also hide a whole repeatable section or page, which is covered in "Hiding whole sections and pages on an application form".
Who can set it up
System Admin and HR users can add and change conditions. Members, agencies, hiring managers and interviewers cannot edit application forms. You can work in a template (Settings, then Application Form Templates) or on a job's application form once the job has been approved. The controls are the same in both places. See "Building an application form" for the basics of adding questions and pages.
Show a question only when an earlier answer matches
- Open the form and find the question you want to control, the one that should appear or disappear.
- Select the arrow that opens its details (Edit field details).
- Tick Show this field conditionally.
- In the first list (labelled Show when field), choose the earlier question that decides it.
- In Operator, choose how to compare the answer.
- Enter or choose the value to match.
- Select Save.
For example, to show Previous names only to people who answered Yes to Have you used any other names?, open the details of Previous names, choose Have you used any other names? as the trigger, leave the operator as equals and pick Yes.
When you tick the box, Recruit fills in the first earlier question in the list, the operator equals and a blank value. Change all three to what you mean before saving. Unticking the box removes the rule.
- equals and does not equal compare the whole answer. For a dropdown or a Yes/No question, this is the usual choice.
- contains and does not contain look for the value anywhere inside the answer. Use them for free text, or for a Multi-select question where the candidate can tick several options.
- is empty is true when the trigger question has not been answered. is not empty is true once it has. Neither needs a value, so the value box disappears.
Comparisons are exact and treat capital letters as different, so yes does not equal Yes. If the trigger is a Dropdown or Multi-select question, you pick the value from its list of options, which avoids typing mistakes. For any other type you type the value.
A few types behave in particular ways. A checkbox reads true when ticked and false when not, and an untouched checkbox counts as false from the start. A Multi-select answer is treated as its ticked options joined by commas, so equals only matches when the candidate ticked exactly that one option. Use contains to match one option among several.
Require a question only when an earlier answer matches
Requiring a question is separate from showing it. To make a question mandatory only in some cases:
- Open the question's details.
- Make sure the ordinary Required switch is off. While it is on, Require this field conditionally is locked, and its tooltip says that required fields cannot be shown conditionally.
- Tick Require this field conditionally and build the rule in the same way as above.
- Select Save.
The question stays optional unless the rule is met, and then the candidate must answer it. Once a conditional requirement is on, the Required switch is locked the other way round, with the message that the field is required by a condition. Clear the condition first if you want to set Required by hand.
You can use both kinds of rule on one question. A question that is hidden is never required, whatever the requirement rule says. The standard questions that every application needs, such as first name and email address, are always required. They cannot be hidden conditionally, and the option is unavailable with a tooltip saying so.
Combine several rules
Select Add condition to add another rule to the same question. Each rule has its own trigger question, operator and value. Once there are two or more, a list labelled Match conditions appears:
- All conditions (AND): every rule must be true.
- Any condition (OR): one true rule is enough.
An example of AND: show Licence number only when Do you drive for work? equals Yes and Country equals United Kingdom. An example of OR: show Please explain when Have you ever been dismissed? equals Yes or Have you left a job by agreement? equals Yes.
Select the X beside a rule to remove it. Removing the last rule turns the condition off. All rules on a question share one setting. You cannot mix AND and OR within a single condition.
Which questions can be a trigger
Only questions above the one you are editing. The list follows the order a candidate meets the questions: first by page, then by position on the page. Every question on earlier pages is available, plus the questions above it on its own page. Questions below it, or on later pages, are not offered.
The first question on the first page has nothing above it, so both condition switches are unavailable and a note tells you to move the question below another one. The same applies to a question you drag to the top.
A question inside a repeatable section can use questions in that same section, or questions outside any section, as triggers. It cannot use a question from a different repeatable section. Inside a section the rule is checked entry by entry, so a question can show in the first entry and stay hidden in the second. See "Repeatable sections: employment history, education and references".
What candidates see when a question is hidden, and what happens to answers they have already typed, is explained in "Hiding whole sections and pages on an application form".