Logic conditions for all question types

You can apply two conditions, to any type of question, disregarding their type. A question can either be answered or skipped by the respondent. But you have the flexibility to trigger a logic rule, simply under any of the cases.

So, for any question (disregarding its type, or if it is optional or not), you will always see the following two items in its respective “Condition list”:

Choose a condition
  • is entered (question is answered)
  • is not entered (question is skipped)

By choosing any of these two, you are asking our system just to check if the question is answered or not. In this case, it doesn’t matter what respondents provide as answers. The only thing that is important is that they have responded to the question or not.

Logic Flow #1

survey logic, if answer to the following questionanswer to the following question

Do you have pets?
Choose a condition
  • is entered (question is answered)
  • is not entered (question is skipped)
  • is
  • is not
  • Yes
  • No

The example above shows an optional question with single choice input. Every optional question has the two options of “is entered” and “is not entered“, in its respective “condition” options list.

Keep in mind that all our question types can be set to have required answers. This is a setting that you manually should turn ON, in most cases (unless you choose “Limited” or “Ranked” voting types). Otherwise by default, all questions have “optional” answers.

A mandatory question will naturally be always answered, because respondents have to respond to it to go to the next page or to be able to sumbit the survey. Therefore, for a mandatory question, if you setup a logic rule that is supposed to be triggered in case a question is “answered”, this rule will most probably be always true. Just make sure you are not making an illogical flow, using this method.

However these logic conditions can be smartly used, when designing different logic flows that affect each other. That is why they are displayed there oth for optional and mandatory questions.


Let’s say you have a mandatory question in your survey and want to make sure that respondents fill it it, and explain them why you need that information. But you naturally do not want to put too much information for all respondents and populate your survey an make it intimidating for them to respond. Therefore, you can easily make a logic flow like this:

IF > the mandator question is skipped > THEN > show > section break X

and in the “section break x” you explain why that information is vital for you and why they have to fill it in. This way, only those people who actually did not answer that question will receive this information, as soon as they click on the “next page” or “submit” button. This is while all the others who answer won’t be bothered with loads of unnessecary infromation.

NEXT: logic conditions (rules) for questions with text input