Conditional Survey Logic
Show or require survey questions based on earlier answers using show-when and required-when rules.
Conditional logic keeps surveys short and relevant — questions appear or become required only when they're actually needed. You configure logic per question inside the question editor dialog, on the Survey questions tab of a sign type.
Two kinds of rules
Each question has two independent rule editors:
- Show when… — controls whether the question is visible to the contractor.
- Required when… — makes the question required only when its conditions are met.
When you set a Required when… rule, it governs the question's required state instead of the plain required toggle.
Building rules
Rules are AND/OR trees, so you can combine several conditions. Each leaf condition compares an earlier answer using one of these operators:
- equals
- not equals
- is one of (in)
- is not one of
- is answered (truthy)
- is not answered (falsy)
A question can only reference questions that appear before it — references are forward-only. Order your questions so that anything used in a rule comes first.
Limits
To keep rules manageable, there are two limits:
- Maximum nesting depth of 3 groups.
- Maximum 8 rules per group.
If a rule feels like it's outgrowing these limits, that's usually a sign to simplify the question flow.
Test before you save
- Click Preview to open a contractor-style preview sandbox.
- Try different answers and confirm questions show, hide, and become required exactly as you intended.
- Adjust your rules and preview again until the behaviour is right.
- Save your changes from the Survey questions tab.
The Dependencies tab shows which questions depend on which — handy for spotting tangled logic or checking what might break before you reorder or remove a question.