> 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/season-forms.md).

# Season forms

**Manage › Forms** holds each season's questions: the **Match form**, the pit form and the pre-scout form, and what each answer scores. Scout leads and admins build it. A new game never needs code.

An event plays its own year's game, or the latest one before it. The 2025 game (REEFSCAPE) is **Built into the app** until someone saves a change to it.

{% tabs %}
{% tab title="Phone" %}
![Manage › Forms with Start a new season, the season picker, the form tabs and the Match form's Auto questions, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-7e47e8cedb49d494928d2e4e12fdf3edc7629fbb%2Fmanage-forms-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Manage › Forms with Start a new season, the season picker, the form tabs and the Match form's Auto questions, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-2f63bd137e54a4d7c50d652335363614ea4bf7f2%2Fmanage-forms.jpg?alt=media)
{% endtab %}
{% endtabs %}

The tabs across the top are **Match form**, **Pit form**, **Pre-scout**, **Calculated** and **Cards & reliability**.

## Add a question

1. Pick the form, then tap **Add question**.
2. Fill in:
   * **Question**: the label scouts see, for example **Coral L4**.
   * **Kind**: counter, yes / no, choice, rating, number or text.
   * **Part of the match**: auto, teleop, endgame, or the whole match (asked for the whole match; doesn't score).
   * **Points each** (counters) or **Points when yes** (yes / no), for the kinds that score.
   * **Most it can be** or **Highest rating**, where it applies, and a **Unit** for numbers.
   * **Answers to choose from** for a choice.
   * **Ask it**: **Always**, or only when another answer says so.
3. Save it.

Its saved name comes from the label when you add it and never changes, even if you relabel it later.

## Change a question

Open a question's ⋯ menu to **Edit**, move it up or down, retire it or bring it back.

* **Points change every average.** Answers already saved are scored again with the new points, so every team's averages and rankings move.
* **A question scouts have answered** can be relabelled, moved and have its points changed, but not deleted, given another kind or moved to another part of the match. **Retire** it instead: it leaves new forms, and old answers keep showing and scoring. Then add a new question for the change.
* **A choice answer scouts have picked** can be renamed or retired, not removed.
* **A question nobody has answered** can be deleted. To bring it back you'd add it again.

## Other settings

* **Calculated**: the season's calculated values. Make and change them in **Data › Calculated**; see [Calculated values](https://docs.raidrobotics.org/raidscout/scout-lead-guide/calculated-values.md).
* **Cards & reliability**: the **Card fields** every pick list card shows until a strategist picks others, and which questions count as **Broke down**, **Fouls** and **Played defense** for Alliance Compatibility and Pick Priorities.

## A new season

**Start a new season** copies the latest season to a new year, less what was retired. See [Start a new season](https://docs.raidrobotics.org/raidscout/admin-guide/new-season.md).


---

# 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/season-forms.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.
