Skip Logic

Skip logic specifies which question or ending follows an answer. The route needs a stated condition and a specific destination; “skip irrelevant questions” is an intention, not an implementable rule.

Consider a fictional workshop form. Q1 asks whether someone attended before. Selecting yes shows Q2 about a session preference; selecting no leads to E-not-attended. The no path must omit Q2. Clear wording helps someone choose an answer, while the route determines what they see afterward.

A useful specification pairs stable question and choice IDs with next-state IDs. Keep required or optional status beside the table. If unanswered behavior or an Other choice lacks a destination, the owner has a requirement to resolve before building. The survey branching plan shows how to make that packet reviewable.

Typeform's logic reference discusses choice-driven branches and multiple-selection combinations. A single-choice table cannot settle which route wins when several answers are selected. Define those combinations separately instead of applying a convenient default.

When evaluating Typeform, run known responses through its actual preview and record the entire question sequence. Use the survey logic test workflow to compare that observation with the approved path. A locally consistent route model is useful evidence about the specification, but it does not prove which rules the form saved. Question quality and navigation quality both need review, with different evidence for each.