Conditional logic and pages

Two features that make a long form feel short.

Conditional logic

A question can be set to appear only when an earlier answer matches. Open the question and add a condition: show this when [earlier question] is [value].

Typical uses:

• Ask "which model do you own?" only after someone says they're an existing customer
• Ask for a reason only when the rating is 3 or below
• Skip a whole section that doesn't apply to their role

Hidden questions are never required and never stored — a branch someone didn't see can't block their submission or leave a stray answer in your export. Answers to questions that get hidden after being answered are discarded on submit for the same reason.

Multi-page (step view)

Turn on step view to show one section per screen, with a progress bar and a Back button.

Worth doing when:

• The form is longer than about eight questions
• There are distinct stages — about you, your order, confirm
• You've grouped questions into sections already

Not worth doing for short forms — a three-question form split across three screens feels slower, not faster.

Progress is kept as someone moves between steps, so going Back to fix an answer doesn't lose anything.

Attempts

Under settings you can limit respondents to one attempt. Combined with identity verification, that's what turns a form into something you can use for assessment rather than a poll.

On plans allowing multiple attempts, each one is recorded separately so you can see improvement across tries.

Testing branching forms

Before you share it, walk every path:

1. Preview the form.
2. Take the "yes" branch to the end and submit.
3. Take the "no" branch and submit.
4. Check the response inbox — each should show only the questions that path asked.

Branching is the single most common source of "the form didn't work" reports, and almost always because one path was never tried.