Page routing & branching
Send respondents down different paths between pages based on their answers.
Routing decides which page comes next. By default pages run in order, but you can add branches so that an answer on one page jumps to a different page — or straight to submission.
How branches are evaluated
- A respondent finishes a page and the page’s fields pass validation.
- Each branch on that page is checked in order. The first branch whose conditions match decides the next page.
- If no branch matches, the page’s default next page is used (or simply the next page in sequence).
- A branch can point to a specific page or to Submit, which ends the form.
Skipped pages
Pages with their own entry condition are skipped automatically when that condition isn’t met, and routing advances past them. The builder guards against loops, so you can’t accidentally create a path that never ends.
Tip
Routing uses the same conditions as conditional logic. For multi-select answers, contains matches any selected option.
Still need help?
A dedicated support form is coming soon. In the meantime, jump back into the product or reach the team from the contact page.
HigherStack