Guide · 6 min read
Quiz and scoring forms: how to build them right
Updated 2026-09-17
TL;DR
A scored form works by giving each answer a point value, totaling them with a calculated field, and using branching logic to route respondents to different pages or outcomes based on where their total lands.
A quiz or scored assessment is a form with two extra jobs on top of collecting answers: doing the math and deciding what happens next. Whether it's a lead-qualification quiz, a personality test, or a knowledge check, the same three pieces make it work: point values per answer, a running total, and branching based on the result. This guide covers how to structure each piece.
Assign point values to answers
Every scored question needs its answers mapped to a number, decided before you build the form, not while you're building it. For select or multiple-choice questions, this is usually straightforward: each option gets a fixed point value based on how it should count toward the outcome.
Keep the scale simple, like 0-5 or 1-10 per question, rather than inventing a different range for each field; it makes the total easier to reason about and easier to debug later.
Total the score with a calculated field
Once every scored question has a numeric answer, a calculated field can sum them with a formula referencing each question, updating live as someone answers. This turns individual answers into a single number you can act on, without the respondent seeing any of the math.
Weight questions unevenly on purpose if some matter more than others: a calculated field's formula can multiply specific answers before summing, not just add them at face value.
Branch on the result
Once you have a total, branching logic decides what respondents see next: which results page they land on, whether they qualify for a follow-up, or which product recommendation to show. Set branching rules on the score ranges you actually care about (0-40 low, 41-70 medium, 71-100 high) rather than a rule per point.
Put the branching rule on the page after the scored questions, checking the calculated total, so the routing happens automatically once the last scored answer is in.
Design for clarity, not cleverness
Respondents shouldn't need to guess that a form is scoring them unless that's the point (a quiz). For assessments used for screening or lead qualification, decide upfront whether to show the score to the respondent at all, since revealing it can change how honestly people answer later questions in a multi-part form.
Test the math before publishing
Run through every branch path yourself with deliberately chosen answers (lowest possible score, highest possible score, and a middle case) before publishing, since a single wrong point value can silently misroute every respondent who picks that answer.
In YeetForm, a calculated field totals scores live from a formula referencing the other fields, and page branching routes respondents to different pages based on that score, all configurable by describing the logic in plain English to the AI agent or building it directly.