How to build a quiz with different results based on score

Start from the maximum possible score, not from the result names. Add up the best option on every single-choice question, plus every positive option on multi-select questions. That number is your ceiling, and every band has to fit under it.

Three or four bands is the practical range. Two bands turns the quiz into pass or fail, which is fine for a certification check but flat for a lead magnet. Five or more bands mean each result covers only a few points, so one careless click moves someone to a different result and the quiz feels random.

Take an 8-question 'How ready is your team for remote work?' quiz. Each question has four options worth 0, 1, 2 and 3 points, so the maximum is 8 x 3 = 24 and the minimum is 0.

Equal thirds give bands of 0 to 8, 9 to 16 and 17 to 24. Before you accept that, ask what an average respondent scores. If most options people pick are the 2-point ones, the typical total is around 16, which sits on the border of the middle and top bands. Nudge the top band to 18 to 24 so 'ready' means clearly above typical, not just typical.

Check the edges too: with whole-number points, 8 and 9 are adjacent and no total falls between them. If you use half points anywhere, a total of 8.5 is possible and would match no band, so either make ranges continuous (0 to 8.5, 9 to 16.5) or keep every point value a whole number.

Name bands after what the person should do next, not after a judgement. 'Start here', 'Close the gaps' and 'Ready to scale' travel better than 'Poor', 'Average' and 'Excellent', and they give each result screen an obvious call to action.

Weight a question when it predicts the outcome better than the others, not because it feels important. In a remote-readiness quiz, 'Do you have written processes for handovers?' tells you more than 'Do people have a second monitor?', so it can carry 0 to 6 points while the monitor question stays at 0 to 3.

Keep the weights coarse. Doubling or tripling a question is easy to reason about; weights like 1.35 are hard to explain and create the half-point gaps described above. After weighting, recompute the maximum and redraw the bands, because the old cutoffs no longer mean what they did.

On a 'tick everything that applies' question, someone who ticks every box collects every point. If some options are wrong or unhelpful, give them 0 or negative points so ticking everything does not win. In Zunoform, the maximum for a multi-select is the sum of its positive options, so negative options pull a respondent's total down without changing the ceiling.

Ties only exist in answer-mapped quizzes. If 'Planner' and 'Connector' each collect three matching answers, the software has to pick one, and most tools pick by the order of your result screens. Typeform's help centre says the ending listed first wins a tie. Zunoform does the same: the Ending page that comes first in your form wins, and a respondent who matches nothing gets the fallback Ending you chose.

You can make ties rare instead of just predictable. Use an odd number of mapped questions when you have two results. Map each option to one result only, never two. And add a tie-breaker question near the end that maps strongly to one result, such as 'If you could only keep one of these, which would it be?'

Score-range quizzes avoid ties entirely as long as ranges do not overlap. If they do overlap by mistake, Zunoform resolves it the same way, in Ending page order, and a total that matches no range goes to the fallback Ending.

Write the results first this time. Three to five types, each with a one-paragraph description and a next step. Then write questions where every option is an honest expression of exactly one type. If an option could belong to two types, rewrite it or cut it.

Six to ten questions is enough. With four types and eight questions, each type has eight chances to collect a match, which spreads results sensibly. Fewer than five questions produces a lot of ties; more than twelve adds drop-off without making the result more accurate.

Finally, test it against yourself and two colleagues who know the types. If someone who is obviously a Planner lands on Connector, the mapping has a leak: find the option that sent them there.

Not natively. Google Forms quiz mode lets you give each question a point value, set an answer key, add feedback for right and wrong answers, and release the score immediately or after manual review. It has no setting that shows a different confirmation screen depending on the total.

Section branching does not solve it either. 'Go to section based on answer' works on multiple choice and dropdown questions, and it routes on one answer at a time. It cannot add up a score first and then branch on the total.

Often, yes. If a quiz shows your result the instant you click submit, with no request to a server in between, the scoring happened in your browser, and the browser needed the correct answers and point values to do it. They are in the page, readable by anyone who opens developer tools and searches for one of the answers.

For most quizzes that does not matter. A personality quiz or product finder has nothing to leak; someone who reads the mapping has only spoiled their own result. It matters when the score has consequences: a pre-employment screen, a certification check, a graded test.

Here is how Zunoform handles it, stated precisely. The point values, marked correct answers, explanations, grade bands and outcome rules stay on the server: they are not in the form the browser loads. When the respondent submits, the server scores the answers, stores the total, percentage and grade on the response, and sends back only what the result screen shows: the score, the chosen result, and, if you turned on the answer recap, which questions were right plus the correct answer for the ones they missed. The result appears a moment after submitting rather than instantly.

One exception. If the quiz uses the live {{score}} variable anywhere, for example a statement that says "You have {{score}} points so far", a result screen that prints it, a score in a redirect URL, or logic that branches on the score, the browser has to add the points up as people answer, so those forms still send the point values and correct answers with the page. Score cards, answer recaps and score-range results do not need it. The Score quiz settings in the builder tell you which case your form is in. Even with the key hidden, there are no timers or proctoring, and someone could learn answers by submitting several times unless you limit it to one response per person, so keep high-stakes exams on a dedicated testing tool.

Zunoform fits if you want score-range or answer-mapped outcomes, points per option, correct answers and letter grades without paying first: all of that is on the free plan, which allows 500 responses a month. The score and grade are stamped on each response, so they show in your responses and ride along in webhook payloads.

It is the wrong pick for timed or proctored exams (there are no quiz timers or lockdown mode), for quizzes that must show a live running score and still keep the answer key private, and for teams who need more than 500 free responses a month; Google Forms and Tally have no monthly response cap on their free plans. If you are staying on Google Forms, the Sheets formula above is the cheapest route.