> ## Documentation Index
> Fetch the complete documentation index at: https://docs.feedal.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Scoring

> Assign point values to answers, accumulate a total score per session, and use the score for branching, analytics, or display.

Scoring lets you attach point values to answers and track a cumulative total across the session. Use it for quizzes, lead qualification, NPS bucketing, or any form where a numeric outcome matters.

<Info>
  Scoring is a **Pro plan** feature. The Score tab in the studio panel is locked for free plan users.
</Info>

***

## Enabling scoring

Scoring is configured per question, in the **Score** tab of the right panel.

1. Select a question node in the canvas.
2. Click the **Score** tab in the right panel.
3. Toggle **Enable scoring** on for that question.
4. Choose a scoring method and configure the values.

Each question contributes independently to the session's running total.

***

## Scoring methods

### Option map

Used with **choice questions** (Multiple choice, Checkbox, Dropdown, Yes/No, Emoji rating, Picture choice).

You assign a point value to each option. When the respondent selects that option, its value is added to the total score.

| Option label      | Points |
| ----------------- | ------ |
| Very satisfied    | `5`    |
| Satisfied         | `4`    |
| Neutral           | `3`    |
| Dissatisfied      | `2`    |
| Very dissatisfied | `1`    |

For **checkbox / multi-select** questions, the points for all selected options are summed.

### Range

Used with **numeric and rating questions** (Number, Star rating, Number scale, Opinion scale).

The respondent's answer is multiplied by a **multiplier** you set.

```
score_contribution = answer_value × multiplier
```

**Example:** Star rating with `max_stars = 5` and `multiplier = 10` → a 4-star answer contributes 40 points.

***

## Total score

The session's **total score** is the sum of all individual question contributions. It is:

* Visible in the **session detail** in the responses dashboard.
* Included in the **CSV export** as a `total_score` column.
* Accessible via the API on the session object.
* Usable as a condition value in branching edges (see below).
* Shown in the **Analytics overview** as an average score card and score distribution chart when scoring is active.

***

## Using score in branching

You can route respondents based on their **cumulative score at any point** in the form.

In the condition editor, select **Score** as the source (rather than a specific question) and use numeric operators (`gte`, `lte`, `between`, etc.).

**Example — quiz outcome routing:**

```
End of quiz
 ├── P0: Total score ≥ 80   → "Excellent" end screen
 ├── P1: Total score ≥ 50   → "Good effort" end screen
 └── Default                 → "Keep practising" end screen
```

<Tip>
  Place the routing node at the end of your scored questions so the total is
  fully accumulated before branching. Branching mid-form uses only the score
  accumulated up to that point.
</Tip>

***

## Showing score to respondents

By default, the score is **not shown** to respondents — it is used for routing and analytics only. This is intentional: most scoring setups (NPS bucketing, lead qualification, internal routing) use the score as an operational signal, not something to surface to end users.

When you explicitly want respondents to see their result — such as a quiz or certification assessment — enable the **Show score to respondent** toggle in the Score tab.

When enabled, the completion screen displays a score badge:

```
All done — thank you!
Your response has been recorded.

🏆 Your score
   42
```

The badge only appears if the respondent's `total_score > 0`. If all scored questions were skipped or returned zero points, no badge is shown.

***

## Workflow canvas indicator

Questions with scoring enabled show a **Score** badge on the workflow canvas node, so you can identify scored nodes at a glance without opening the right panel.

***

## Scoring and tagging

You can combine scoring with [tagging](/building-forms/workflow/tagging) to segment respondents. For example, tag a session as `high-value` when the score exceeds a threshold using a conditional branch that leads to a Statement node with that tag.

***

## Next steps

<CardGroup cols={2}>
  <Card title="Conditional branching" icon="code-branch" href="/building-forms/workflow/branching">
    Route respondents based on their score using numeric operators.
  </Card>

  <Card title="Results overview" icon="chart-bar" href="/results/overview">
    See average score and score distribution in the analytics dashboard.
  </Card>
</CardGroup>