Guide · 6 min read
Multi-page forms and branching logic
Updated 2026-09-17
TL;DR
Multi-page forms group fields into steps, and branching rules send each respondent to a different next page (or straight to submit) based on their answers.
A single long page works fine for a short form, but once you're past ten or so fields, splitting into pages usually raises completion rates — people can see progress and tackle one topic at a time. Branching goes a step further: instead of everyone seeing the same pages in the same order, the form routes each respondent down a different path based on what they've already answered.
Why split a form into pages
Breaking a form into pages groups related fields together — contact details on one page, project details on the next — so respondents aren't confronted with a long scroll of unrelated questions at once. It also gives you a natural place to show a progress indicator, which reduces drop-off on longer forms.
There's a balance: too many pages with only one or two fields each adds friction from extra clicks. Group by topic, not by field count.
How branching rules work
Each page can carry branching rules that are checked when someone reaches the end of it: if a set of conditions all match, the respondent is sent to a specific page (or straight to submission) instead of the next one in order. If no rule matches, the form falls back to the normal sequential order.
Rules are checked in order and the first full match wins, so put your most specific branch first and a catch-all default last if you need one.
Designing a branch that makes sense
Branch on answers that meaningfully change what's relevant next — a service type, a yes/no gate question, a customer type — not on minor details that only tweak wording. A useful test: if two branches would ask nearly the same questions, they probably don't need to be separate branches.
Keep an eye on symmetry: if branch A skips five questions that branch B still asks, make sure that's intentional and that respondents in either branch still reach a sensible submit page.
Common branching patterns
A qualification gate at the start ("Are you a current customer?") that sends new leads and existing customers down different paths is one of the most common uses. Another is skipping an entire section for respondents who indicate it doesn't apply to them, like shipping address questions for a digital-only order.
Surveys often branch on an early satisfaction score, sending low scores toward a page asking what went wrong and high scores toward a referral question, without cluttering either group's path with the other's questions.
Testing before you publish
Because branching changes the order fields are seen, it's worth walking through the form yourself as a respondent for every branch before publishing, not just the default path. It's easy to build a branch that skips a page a later branching rule still expects to have been filled in.
In YeetForm, pages carry an ordered list of fields and optional branching rules described in the form schema; the AI editing agent can add a page or wire branching for you when you describe the flow you want.