Build a Form with Conditional Logic

Not every question needs to be answered by every user - and that’s where conditional logic comes in. Also known as branching logic, this feature lets you create smart, responsive forms that adapt based on user input. Instead of overwhelming users with irrelevant questions, you can show only what matters to them. This keeps forms shorter, more focused, and easier to complete.

Add a Conditional Question

To create a conditional question, you must first include at least one preceding question in your form that uses a multiple-choice, multiple-select, or dropdown response type. These response types are required because they provide the structured answer options that conditional logic relies on.

Step 1: Enabling Conditional Questions

By Default, the “Allow conditional questions” option is not enabled. You must select the radio button and then select the “Apply” button to save the configuration. Only one of the Question Display options can be enabled at a time.

1. Log in to the Admin App.

2. Navigate to Menu > Library > Form Builder.

3. Open an existing form or create a new one.

4. Locate the Question Display section.

5. Select the radio button for Allow conditional questions.

6. Click Apply to save your changes.

Step 2: Identify Whether a Question Can Be a Conditional Question

When creating or editing questions in the Form Builder, the system now clearly indicates whether a question type is eligible for conditional logic:

Eligible Types:

• Multiple Choice
• Multiple Select
• Dropdown

UI Indicator:

• If the selected question type can be used as a condition, a label appears: “Can be a Condition”.
  
• If the selected question type cannot be used as a condition, the label reads: “Cannot be a Condition”.
  

Step 3: Creating a Conditional Question

1. Click New > Question.

2. Define the question text, response type, and options.

3. Go to the Conditional tab (active only if conditional questions are enabled).

4. Choose Ask this question if….

5. Choose one of the following:

• • All of the following conditions are met – All conditions must be true for the question to be shown.
  • Any of the following conditions are met – Only one condition needs to be true. 

Step 4: Defining Conditions

When setting up a conditional question, each condition row defines the logic that determines whether the question will be displayed to the form user. These conditions are evaluated in real time during form completion.

Each row includes three key components:

1. Question Selector (left column): A dropdown list of all eligible questions in the form that appear before the current question and use either multiple choice, multiple select, or dropdown response types. These are the only question types that can be used as triggers for conditional logic.

2. Criteria Selector (middle column):

• • For Multiple Choice or Dropdown: Equals or Does not equal
    
    

• • For Multiple Select: Includes the answer or Does not include the answer.
    

3. Response Value Selector (right column): A dropdown list of all possible answers for the selected question. Select the specific response that should trigger the conditional question.

4. Once you’ve defined a condition, you can click Add a Condition to include additional logic or Apply to save your configuration. If you need to remove a condition, simply click the Remove button next to the corresponding row.

In the configuration below, the conditional question will be displayed to the form user only if their response to the preceding question is either “Very Satisfied” or “Satisfied.” This ensures that the follow-up question is relevant to the user's experience and supports more targeted data collection.

Section-Level Branching

In addition to individual questions, entire sections of the form may be hidden if the conditions for displaying them are not met. For example, if a section is designed to collect feedback only from dissatisfied employees, and the user selects a satisfied response, that section will not be shown or assigned.

In multi-user workflows, this means:

• The section will not be routed to the assigned user.

• No notification will be sent for that section.

• The workflow will automatically skip to the next applicable section.

This intelligent routing ensures that each participant in the workflow only receives the sections relevant to their role and the context of the submission.