Quizzes
20,021 views
25 min · 2 min read
7 steps
Advanced

How to design branching logic for adaptive quizzes in Typeform

Adaptive quizzes keep learners engaged by tailoring questions to their responses. This guide walks you through designing branching logic in Typeform so your quizzes feel personal, efficient, and fair. Follow the steps to plan, implement, and test a quiz that adapts to each respondent in meaningful ways.

Verified by pleasexplain editors
  1. Step 1: Define learning goals clearly

    Write 2–4 specific objectives the quiz should measure (for example: recall of facts, problem-solving steps, or diagnostic level). Prioritize up to 5 goals so branching decisions remain focused and manageable.

    [Illustration: a notepad with 3 bullet-point learning goals and a pen]

  2. Step 2: Map user journey on paper

    Sketch a flowchart showing initial question, three main paths, and endpoints; limit branches to 3–5 levels deep to avoid complexity. Use boxes for questions and arrows for conditional paths to visualize where adaptivity occurs.

    [Illustration: hand-drawn flowchart with boxes and arrows, three main branches]

  3. Step 3: Choose branching criteria

    Decide concrete rules that trigger branches, such as score thresholds (0–2 = remediation, 3–4 = practice, 5 = mastery) or specific wrong answers that reveal misconceptions. Keep each rule simple and testable.

    [Illustration: sticky notes listing rules like 'score <3' and 'specific answer X triggers follow-up']

  4. Step 4: Design question pools

    Create 12–20 questions grouped by difficulty or topic; assign each question metadata: difficulty (easy/medium/hard), topic tag, and point value (1–3). This lets Typeform route respondents based on tags or accumulated score.

    [Illustration: spreadsheet view with columns: question, difficulty, topic, points]

  5. Step 5: Write clear branch messages

    Draft 1–2 sentence transitions that explain why the quiz is adapting (for example: 'You’ll see extra practice on fractions to strengthen your basics'). This keeps users motivated and reduces confusion when paths change.

    [Illustration: a text box showing a short transition message with friendly tone]

  6. Step 6: Build logic in Typeform incrementally

    Implement branches one section at a time: add an initial question, then one conditional follow-up, and test. Limit each test cycle to 10–15 minutes and confirm conditions (answer equals, score greater than) behave as expected.

    [Illustration: computer screen showing Typeform logic tab with a single rule configured]

  7. Step 7: Simulate users and iterate

    Run 10–20 mock submissions covering all branches, record where users land and time spent. Refine questions, thresholds, or messaging if more than 10% of runs produce dead ends or confusing paths.

    [Illustration: clipboard with checklist and sample quiz responses being ticked off]


  • Keep total quiz length under 20 questions for a 5–12 minute completion time to reduce drop-off.
  • Use point values 1–3 to make scoring simple and transparent; avoid fractions or uneven scales.
  • Tag questions with multiple topics if they assess more than one skill; this enables flexible routing.
  • Use 'Jump to' logic for quick branching and 'Logic Jumps' for conditional flows; name each rule clearly for maintenance.
  • Provide a short summary page at the end showing score, recommended next steps, and one resource link per outcome.
  • Limit feedback per question to 1–2 sentences; longer explanations can be offered on follow-up pages or emails.

  • Avoid creating more than 3 branching conditions from a single question to prevent unmanageable complexity.
  • Do not rely solely on a single question to determine major pathway changes; use 2–3 corroborating items when stakes are high.
  • Be careful with sum-based branches if respondents can skip questions; always define defaults for missing answers.
  • Test for unreachable content: ensure every question has at least one incoming path so no pages are orphaned.

Was this guide helpful?