Building surveys

Yes / No

A two-way choice, shown as buttons, radios or a toggle.

A two-way answer such as Yes/No or Agree/Disagree.

Try an answer, then check it. Turn Required off to try leaving it blank.

Try this question

Have you attended this workshop before?required

Interactive example. Answers stay on this page and are not submitted. Reset or changing the configuration clears answers and restores Required.

All settings

Select + in the editor, choose Yes/No Question, then select the question and open Content.

All questions also have Title and Description. Replace the starter title with your question; Description is optional and starts blank. Use it for instructions that should remain visible while answering. The defaults below are for a newly added question, not necessarily the example above. The example starts with Required on so you can try validation; real new questions default to optional.

SettingDefaultBehaviour and availability
True LabelYesWording for the true answer.
False LabelNoWording for the false answer.
Display StyleButtonsChoose Buttons, Radio or Toggle.
Must Be TrueOffUnder Validation. Present in the editor but currently not enforced; see below.
RequiredOffUnder Validation. Requires an answer before continuing when this question is shown.

Labels do not change the stored meaning

You can label the two choices “Attended” and “Did not attend”, for example. The answers still represent true and false. Check the label as well as the selected value when building a condition or piping the answer into a later sentence.

Compare Buttons, Radio and Toggle in the example. Buttons and Radio let someone explicitly choose either answer. A toggle looks off before it is used, but an untouched toggle is not necessarily a recorded No. With Required on, test it untouched, then switch it on and back off.

Must Be True is not currently enforced

The current answer validator accepts either true or false when Required is on. Enabling Must Be True does not reject No. Do not rely on that switch to enforce an affirmative acknowledgement. Start and Content blocks have separate required acknowledgement checkboxes.

Test both routes

For ordinary routing, Required means “answer this question”, not “answer Yes”. Preview both Yes and No and check any branch they trigger. If you only want to ask a follow-up after Yes, put that requirement in the branch rather than in the label.

Branching and piping

Open Advanced → Conditional Logic to route from an answer. In fields that offer { }, use piping to insert an earlier answer. Plan requirements apply to advanced logic, expressions and option attributes; these are separate from the Content settings above.