Manager Toolkit logo

Conditional Logic in Surveys

Show or hide questions based on how respondents answer.

Last updated April 2026

Conditional logic lets you create smarter surveys by showing or hiding questions based on previous answers. This keeps surveys relevant for each respondent and avoids asking unnecessary questions.

How Conditional Logic Works

When you add a condition to a question, that question only appears if the respondent's earlier answer matches the condition you set. For example, if question two asks "Are you happy with the current meeting schedule?" and the respondent answers "No", you could show a follow-up question asking what they would change.

Adding a Condition

Open your survey in the Surveys editor.
Find the question you want to make conditional. This is the question that will be shown or hidden.
Click the Conditional button on the question header to open the Conditional Display modal.
Under When this question is answered, choose the earlier question whose answer determines visibility.
Under With any of these answers, select one or more values that will reveal the conditional question. Save the condition.
A small indicator appears on the question to show it has conditional logic applied.

Supported Condition Types

Conditions work with every question type that has a finite set of answers. You pick the parent question, then select one or more answer values that will reveal the conditional question:

Yes / No

Trigger on a Yes or a No answer.

Multiple Choice

Trigger on one or more of the configured options.

Star Rating

Trigger on specific star values (1 through 5).

Emoji

Trigger on Angry, Neutral, or Happy.

Likert

Trigger on Strongly Disagree, Disagree, Neutral, Agree, or Strongly Agree.

NPS

Trigger on specific scores from 0 through 10.

Simple Text questions can't be condition sources because their answers don't fit a finite set.

Tips for Effective Branching

Keep your branching simple. One level of conditions is usually enough - deeply nested logic can confuse respondents and make results harder to analyse. Always preview your survey to test each path before sharing it with your team.

Use conditional logic to create a single survey that works for different roles or teams. Rather than sending separate surveys, add a role question at the start and branch accordingly.
When analysing results, conditional questions will show fewer responses since not every respondent sees them. The results page accounts for this and shows response counts per question.

Was this article helpful?