> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidscout/scout-lead-guide/calculated-values.md).

# Calculated values

**Data › Calculated** makes numbers from the match questions, worked out for every match entry and averaged per team. For example, **Teleop coral** adds up the four teleop coral levels. Scout leads, strategists, drive coaches and admins can make them.

Each calculated value becomes:

* a column you can add in **Data › Teams**,
* a field for pick list cards,
* something a [Pick Priorities](https://docs.raidrobotics.org/raidscout/strategy-guide/pick-priorities.md) profile can weigh.

Each card shows the formula in plain words and the top teams at the active event.

{% tabs %}
{% tab title="Phone" %}
![Data › Calculated with Auto Coral and Teleop Coral, each with its formula and top five teams, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-070b57edbbd21e85640b0a0155dd989159dfe96e%2Fdata-calculated-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Data › Calculated with Auto Coral and Teleop Coral, each with its formula and top five teams, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-2005fa5567827fabd010cc26cce77d80e45e61e1%2Fdata-calculated.jpg?alt=media)
{% endtab %}
{% endtabs %}

## Make one

1. Tap **New calculated value** and give it a **Name**.
2. Choose how to make it:
   * **Add up questions**: tick the questions, grouped by part of the match. **Count** adds the answers: pieces scored, and a yes / no counts as 1. **Points** adds what each answer scores at the point values in **Manage › Forms**, so it follows any change there.
   * **Formula**: numbers, questions, + − × ÷ and brackets, for example `(teleNet * 4 + teleProcessor * 6) / 2`. A yes / no counts as 1 or 0. `points(question)` is what its answer scores, like `points(teleCoralL4)`. Use **Pick a question** to insert one.
3. Check **Preview at this event**.
4. Tap **Save**.

A value that adds up counters is in pieces; one that adds up points is in pts. The unit shows on its card, its Teams column, pick list cards and its Pick Priorities name.

## Change or delete one

Use the ⋯ menu: **Edit** or **Delete…**. Deleting says what uses it first. No answers are lost.

The first calculated value saved for 2025 turns the built-in game into a saved copy.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.raidrobotics.org/raidscout/scout-lead-guide/calculated-values.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
