Skip to main content

Beta: Use conditions in your surveys 💡

Learn how to use questionnaire conditions in Edusign to make them dynamic, relevant, and personalized for each learner.

Written by Elliot Boucher

1. Why use conditions?

The conditions allow a questionnaire to be tailored based on:

  • Answers provided by the learner,

  • Context (for example: in-person, remote, absent),

  • The need to display only relevant questions.

In particular, this makes it possible to:

  • Shorten the questionnaire for people who don't need to see certain pages;

  • Ask additional questions only in case of a problem (technical, educational, organizational, etc.) ;

  • Avoid inconsistent answers by hiding what does not apply.


2. Basic Principles of Conditions

In an Edusign questionnaire template, you can set conditions for:

  • Show or hide an entire page based on a previous response;

  • Show or hide a question based on the answer to another question, or on a combination of answers across one or more pages.

A few important points:

  • The conditions are based on the exact values of the responses (e.g., options: “in-person,” “remote,” “I was absent”);

  • A single question can be part of multiple conditions (for example: trigger a page, then later a follow-up question);

  • The behavior you see when you click the "Test Survey" button should be identical to what learners see when the survey is sent to them.


3. Prepare your questionnaire before setting conditions

Before creating conditions, it is recommended that you:

Organize the questionnaire by page, for example:

  • Page 1: Background on Participation,

  • Page 2: Reason for absence,

  • Page 3: Technical issues, etc.

Clearly identify the key questions that trigger the logic (e.g., Q1 – Did you take the course?).

Decide in advance:

  • Which pages should always be visible,

  • Which pages should be displayed only in certain cases,

  • Which pages can be completely hidden, depending on the answer.

This preparation avoids multiplying conditions randomly and makes reviewing easier.


4. Best practices

  • Keep it simple: Start with 1 or 2 conditions, make sure they work, and then gradually add more complexity.

  • Limit the number of nested levels: too many cascading conditions make the questionnaire difficult to maintain.

  • Document your scenarios: Include a brief diagram of the conditional logic (as in the example above) in an internal note or in the model description.

  • Always test after making a change: if you change the possible answers for a key question, quickly go back to “Test the Survey.”


For more information, visit our help center.

💬 If you can't find what you're looking for, contact us via chat. 💬

Did this answer your question?