Survey Branching Logic — Skip, Display, Piping, Carry-Forward (4 Types Explained)

If you've ever designed a questionnaire, you've run into this: some questions shouldn't be shown to certain respondents, some should appear only after a specific answer, some should dynamically reference earlier choices. Branching logic is how you handle all of that — but the moment you start using it, another question shows up: "Which type of branching do I actually need here?" Skip logic? Display conditions? Piping? Carry-forward? The names overlap, but the mechanics are meaningfully different.

This guide walks through the four types of branching logic used in real survey projects — what each one is for, when to reach for which, and the typical failure modes that sink well-intentioned designs. Not a feature reference — a decision guide for the person actually building the survey.

1. How Many Types of Branching Logic Are There — The Four at a Glance

Here's the big picture. Each mechanism is for a different job, so learn them by role, not by name.

Feature	What it does	Main purpose
Skip logic	Jumps past questions	Don't show irrelevant questions to ineligible respondents
Display conditions	Shows/hides a question	Add targeted follow-up questions to specific groups
Piping	Inserts a previous answer into the next question	"Tell us about {the product you chose earlier}"
Carry-forward	Passes prior selections as the next question's choices	"Which of the ones you chose is most important?"

These four combine. The cleanest-looking surveys in production are usually running a tight combination of all four under the surface. Kicue's full implementation details live in the branching logic documentation.

2. Skip Logic — Jumping Past Irrelevant Sections

The foundational branching tool. "If the respondent answered A, jump to Q10." It skips the question(s) entirely.

Typical uses

• Screeners: Route non-qualifying respondents straight to a thank-you screen
• Non-users: Skip all usage-based questions for respondents who haven't used the product
• Major forks: Split the survey into "has purchased" and "has not" tracks

Common design pitfalls

1. Jump target doesn't exist — "Go to Q15" set up when the survey only has 14 questions anymore, after a later edit
2. Overlapping skips cause loops — A→Q5, B→Q3 combined with other skips occasionally traps respondents in a cycle
3. Forgetting that skip destinations might need display conditions too — The question you jumped TO might itself need filtering, which skip logic alone doesn't provide

When to reach for skip logic

When you want to eliminate cognitive load for whole groups of respondents — not just hide, but actually skip past. Different from display conditions in that the question genuinely doesn't exist in their flow.

See skip logic setup for the Kicue implementation details.

3. Display Conditions — Showing a Question Only to Some

"Show this question only if they answered B." It conditions the question's existence on prior answers. The effect looks similar to skip logic, but the design mindset is different — conditionally add rather than conditionally skip.

Typical uses

• Targeted follow-ups: "What's the reason?" shown only to respondents who said "Dissatisfied"
• Segment-specific questions: Question A for men, Question B for women
• Score-triggered questions: Ask NPS Detractors (0–6) for improvement ideas

Common design pitfalls

1. Condition logic doesn't match intent — "Gender = Female AND Age = 30s" set up as "Gender = Female OR Age = 30s," quietly serving the question to unintended groups
2. Required field + hidden question = stuck respondent — A required question that's not visible traps the respondent permanently
3. The referenced question was skipped earlier — If the question that the display condition references has already been skipped, the condition can't evaluate

When to reach for display conditions

When you have a single core survey, and want to add a few extra questions for specific groups. If instead you're routing respondents through fundamentally different surveys, skip logic keeps the structure clearer.

See display conditions setup for Kicue details.

4. Piping — Inserting a Prior Answer Into the Next Question

"Tell us about the Product A you chose in Q1." Piping injects the respondent's earlier answer into the text of a later question.

Typical uses

• Product evaluation: Follow up on the most-used product by name
• Follow-ups on multi-select: For each service the respondent said they use, ask about it individually
• Name / attribute personalization: "About your work at {company}…"

Common design pitfalls

1. No prior answer breaks the sentence — If {product} is blank, the question reads "About , tell us…"
2. Multi-select piped as if singular — "About {A, B, C}, tell us…" is awkward and often unclear (the fix: combine with carry-forward rather than naïve piping)
3. Surface-text mismatches — "Smartphone" shows for some respondents, "iPhone" for others who answered in free text; may or may not be desirable

When to reach for piping

Piping turns the survey into a personalized experience from the respondent's perspective. "The survey remembered what I said" genuinely lifts trust and response quality.

See piping setup for Kicue details.

5. Carry-Forward — Reusing Prior Choices as the Next Question's Options

Use the respondent's selections from an earlier question as the choice set for a later question. Typically paired with multi-select questions.

Typical uses

• Narrowing-down questions: Q1 "Which of these services have you used?" (multi-select) → Q2 "Which one was most useful?" (single-select, drawing from Q1's selections)
• Importance scoring: Pick top 5 in Q1, then rate each for importance in Q2
• Ranking: Only rank the items you actually selected

Common design pitfalls

1. Zero options carried — Respondent picked "None of these," leaving the next question with no choices. Needs display conditions to handle this case
2. Order-of-options ambiguity — Does the next question preserve selection order, or reset to original display order? Tool-dependent behavior
3. Too many carried options exhaust the respondent — 20 items carried into a ranking question creates a straightlining problem

When to reach for carry-forward

Whenever you want a "multi-select → deep-dive" two-step question. Combine with piping to ask individual follow-ups for each carried selection.

See carry-forward setup for Kicue details.

6. A Combined Design Example

In practice, you combine these. Here's a new-product purchase-intent survey using all four:

Q1. Which of these products do you currently use? (multi-select)
    [Brand A] [Brand B] [Brand C] [None of the above]
    ↓
    → "None" skips to Q5
    ↓
Q2. Of the products you selected, which do you use most? (single-select)
    Carry-forward: only Q1's selections appear as options
    ↓
Q3. How satisfied are you with [Q2 answer]?
    Piping: Q2's answer appears in the question text
    ↓
Q4. Display condition: only if Q3 = "Dissatisfied"
    What specifically drove the dissatisfaction? (free text)
    ↓
Q5. Any products you'd like to try in the future? (free text)

This design uses all four mechanisms:

• Skip logic: Routes non-users past the use-based questions
• Carry-forward: Q1's multi-select becomes Q2's option list
• Piping: Q2's answer appears in Q3's question text
• Display condition: Q3's answer controls whether Q4 appears

Different respondents experience very different surveys, but you manage one coherent flow as the designer.

7. Editorial Take — The Four Design Mistakes We See Constantly

Reviewing survey designs, the same failure patterns keep coming up. We've been blunt about these elsewhere; we'll be blunt about them here.

1. Don't over-branch "just in case." Branching looks powerful, so designers reflexively add more. The result: the designer loses track of their own flow. Add branching only when you genuinely need it. When in doubt, don't branch — keep everyone on the same path. Simplicity scales better than cleverness.

2. Question-number drift silently breaks your references. Edit the survey later, and skip targets or piping references can end up pointing at nothing. Tools like Kicue manage references by question ID and track changes automatically. Tools that use literal question numbers will let you ship a broken flow with no warning.

3. Logic conditions almost never match intent on first draft. "A AND B" set up as "A OR B" is the classic one, and you won't notice it from the editor alone. Always pilot every branch. If you don't walk the survey through every conditional path before launch, you'll find out in production data that a bunch of respondents got questions they shouldn't have.

4. Branching isn't free — it can exhaust respondents. Carry-forward can hand off 20 items into a ranking question, which is an instant straightlining factory. Branching that reduces irrelevant questions is good; branching that makes the visible questions heavier is counterproductive. Pair with the response-rate fundamentals — branching should help cut load, not add it.

8. Branching Logic in the Survey Tool Kicue

Kicue ships with all four mechanisms built in:

• Skip logic — per-condition "jump to question" or "end survey" routing (details)
• Display conditions — AND / OR compound conditions (details)
• Piping — inject prior answers into question text, option text, and section headers (details)
• Carry-forward — pass multi-select answers into the next question's options (details)
• ID-based references — references survive question renumbering automatically
• Full-path preview — walk every branching route before launch

Upload an Excel / Word / PDF questionnaire and Kicue's AI parses branching logic along with the rest of the structure, then generates a live web form.

Choosing the right tool — Free plan limits, branching support, AI capabilities, and CSV export vary widely across tools. See our free survey tool comparison to find the right fit for this approach.

Recap

The four branching types, organized by job:

1. Skip logic — jump past whole sections; major survey forks
2. Display conditions — show a question to specific groups only; follow-ups and segment-specific additions
3. Piping — inject prior answers into later question text; personalized experience
4. Carry-forward — reuse prior selections as the next question's option set; multi-select deep-dives

Combine them, but don't over-branch. Keep asking "does this branch actually add value?" Always pilot every route. These two habits prevent nearly every branching failure we've seen.

The survey designs that land well in practice are the ones where the respondent experience feels simple, while the underlying logic is precisely targeted.

---

Build surveys with full branching logic straight from an uploaded questionnaire file — try Kicue, a free survey tool with skip, display, piping, and carry-forward baked in.