Conditional Questions in a Form

  • Updated

Who this feature is for

  • Dashboard Users with access to Forms in the Assignar Web App.
  • Those responsible for building and distributing Forms to workers.

Conditional Questions can be used to create smarter Forms. They allow your workers to bypass irrelevant questions and only show questions based on answers to previous questions in the form. 

 

Video Overview

 

How to set up a conditional question

  1. Create a parent question
    This must be a closed-ended question (Yes/No, dropdown, or multiple choice)
    Example:
    “Are the brakes working ok?” (Yes / No)
  2. Create the follow-up question
    This is the question you only want to appear when a specific answer is selected.
  3. Enable Conditional on the follow-up question and configure:
Should DisplayTwo options will show - Yes or No. This refers to if you would like the conditional question to show.
When the questionSelect which question you would like the current question to be conditional off
Has the valueTwo options will show. Any value or specific value. This is where you will define if this question will show if a specific condition has been met.
Enter valueIf you have chosen a specific value in the previous drop down field, the specific value will need to be entered here. It is important to note that it needs to be exactly as is in the previous question as it will pick up the exact spelling, spacing and lettering. 
  1. Save and publish the form
    Changes will not apply until the form is published.

 

In this example, if the worker answered Yes, the form can be continued. If No, the follow-up question appears then you can ask "Please take a photo of the defect"

Screenshot 2025-11-03 at 10.38.51 AM.png

 

Important limitations

  • Conditional questions can only reference one parent question
  • Only one trigger answer is supported
  • Conditional logic cannot reference questions in other question groups
  • AND / OR logic and chained conditions are not supported
  • Conditional logic is answer-based, not user-based (no role-based visibility)

 

Example of what this might look like for your worker:

 

 

Was this article helpful?

4 out of 4 found this helpful