Skip to main content

Scoring

Assign numerical values to answer options in questions to quantify responses and calculate overall scores for submissions.

Updated this week

Survey Scoring allows you to assign numerical values to answer options in your surveys, making it easy to quantify responses and calculate overall scores for submissions. This feature is particularly useful for measuring satisfaction levels, evaluating performance, or creating weighted feedback systems.

Which Question Types Support Scoring?

Currently, scoring is available for:

  • Single Select questions (radio buttons)

  • Multiple Select questions (checkboxes)

Other question types like NPS, CSAT, Rating, and Freeform do not currently support custom scoring. Please reach out to support if you have use cases for these.

How to Enable Scoring

  1. Create or edit a Single Select or Multiple Select question

  2. Go to Advanced Options for the question

  3. Check the "Enable scoring" checkbox

  4. Assign scores to each answer option using the Score input field that appears next to each option

  5. (Optional) Set a score for the "Other" option if you have it enabled

How Scoring Works

Score Assignment

  • Each answer option can have any numerical score (positive, negative, or zero)

  • You can leave some options without scores (they default to 0)

  • The "Other" option can also be assigned a score

Score Calculation

  • Single Select questions: The score equals the value assigned to the selected option

  • Multiple Select questions: Scores are added together for all selected options

  • Final submission score: All scores from scored questions in the same submission are combined into a total score

Important Notes

  • Scores are calculated per submission, not per individual question response

  • All feedback responses within the same submission will show the same total score

  • Only questions with scoring enabled contribute to the total submission score

  • Scores are recalculated automatically when responses are added, updated, or deleted

Viewing and Using Scores

Dashboard

View scores directly in your dashboard by clicking the information (i) icon next to individual responses. The total submission score will be displayed there.

CSV Exports

When you export survey data to CSV, scored submissions will include a "Score" column showing the total calculated score for each submission.

API and Webhooks

Scores are included in both API responses and webhook payloads, allowing you to programmatically access scoring data for integration with other systems.

Data Analysis

Scores provide a quantitative way to:

  • Rank submissions by overall satisfaction or performance

  • Identify trends in feedback quality

  • Create weighted averages across different response categories

Example Use Cases

Product Feedback (Multiple Select):

  • "Easy to use" = 2 points

  • "Great design" = 2 points

  • "Too expensive" = -3 points

  • "Missing features" = -1 point

Employee Performance Review:

  • "Exceeds expectations" = 4 points

  • "Meets expectations" = 2 points

  • "Below expectations" = 0 points

  • "Needs improvement" = -2 points

Best Practices

  1. Be consistent with your scoring scale across similar question types

  2. Consider using negative scores for unfavorable responses to create more meaningful totals

  3. Test your scoring logic with sample submissions to ensure the calculations work as expected

  4. Document your scoring system so team members understand how scores are calculated

  5. Use scoring strategically - not every question needs to be scored

Limitations

  • Scoring is currently only available for Single Select and Multiple Select questions

  • Scores are integers only (no decimal values)

  • Historical data from before scoring was enabled won't have scores calculated

Missing Something?

If you have any questions or feature requests related to scoring, please reach out to support.


This scoring feature gives you powerful quantitative insights into your survey responses, helping you make data-driven decisions based on weighted feedback from your users.

Did this answer your question?