Skip to main content
Require answer marks selected fields mandatory while When matches — respondents must fill them before progressing or submitting (if visible on the current page). Use with Show blocks for conditional required follow-ups.

​
When to choose this

Block-level Required toggle sets the default; logic Require overrides while rule matches (subject to last-wins ordering).

​
Exact behavior

  • Sets required: true on targets while When is true.
  • Hidden fields are never required — engine forces required off if field not visible (Hide, other page, or default hidden).
  • Validation runs on current visible page before Next — future-page required fields do not block yet.
  • Last matching rule wins vs Make optional on same target.
  • Does not Show fields — pair with Show blocks if follow-up starts hidden.
Intelligent validation: Required fields hidden by logic or on future pages are ignored until visible — users are not blocked by questions they cannot see.

​
What changes on fill

​
Configure in Studio

1

Open a rule

Prefer Branch or Add condition on the parent field for local follow-ups.
2

Build When

Condition that should trigger mandatory follow-up.
3

Show follow-up (if hidden)

Add Show blocks on same or earlier rule if targets start hidden.
4

Add Require answer

Select follow-up block(s).
5

Preview validation on Fill

Try Next/Submit without filling — should block with field error when visible.

​
Worked examples

​
“Other” specification

When Plan equals Other → Show blocks Please specify + Require answer Please specify

​
Call-back phone

When “Call me back” equals Yes → Show blocks Phone + Require answer Phone

​
Enterprise compliance

When Plan equals Enterprise → Require answer DPA contact email
Assumes field already visible on canvas.

​
Urgent notes

When Notes contains urgent → Require answer Phone

​
Test on fill

1

Trigger When

Asterisk / required indicator appears on targets.
2

Leave required empty on current page

Next or Submit blocked with validation message.
3

Fill required field

Progress allowed.
4

Revert When

Required indicator may disappear — field may revert to default optional.
5

Hide required field

Submit not blocked by that field.

​
Common mistakes

  • Require on hidden follow-up without Show.
  • Require on Page 2 field while testing Page 1 submit — may not block until that page visible.
  • Fighting Make optional rules — fix order or exclusive When.

​
Troubleshooting

Field hidden or When false — check Show/Hide state.
Another visible required field on current page — not necessarily your logic target.
Later Require rule still matches, or block default is required — add Make optional rule.
Require action missing or overridden — add action or reorder rules.
Last modified on September 7, 2026