> 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-guide/scout-a-match.md).

# Scout a match

Open **Scout › Matches**. The top shows **Your next shift**, and the list shows **My matches** by default. Switch to **4469's** to see only our matches, or **All** for every match. **My shifts** lists your shifts, and **Practice** opens a practice match.

{% tabs %}
{% tab title="Phone" %}
![Scout › Matches with Practice, My shifts and the My matches / 4469's / All filter above the matches, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-11d6173fd364c6c2ed6eaac84df57495eab1187c%2Fphone-matches.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Scout › Matches with Practice, My shifts and the My matches / 4469's / All filter above the matches, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-dab27b4c13d11c13387bb9bac9eeaa8b39fef6be%2Fmatches-laptop.jpg?alt=media)
{% endtab %}
{% endtabs %}

## Scout your robot

1. Tap a match where you have a seat. Your robot's form opens straight away.
2. Fill it in as the match plays. The form scrolls from auto through teleop to endgame; counters sit two to a row on a phone, and the points add up as you go.
3. Add **Notes** for anything the numbers miss.
4. Tap **Save**.

{% tabs %}
{% tab title="Phone" %}
![A match form (Practice) with the Auto questions, counters with − and +, and the points total and Save at the bottom, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-d20f5b802da2982608a0f7a0c2375211077e1df7%2Fphone-match-form.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![A match form (Practice) with the Auto questions, counters with − and +, and the points total and Save at the bottom, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-05e5249a0ccf49ba7d6229a6fdc1ba16b8edd1a6%2Fmatch-form-laptop.jpg?alt=media)
{% endtab %}
{% endtabs %}

After you save, **Saved** shows how many entries you've saved at this event and **What's next**: your next match, one tap away.

If you leave the form before saving, your answers are kept. Coming back shows **Answers restored**, with **Discard them** if you want to start over.

## Another robot

**Different robot** shows all six robots of the match. You can only save the robot your seat is on, unless you were handed a robot to rescout.

Tapping a match where you don't have a seat asks **Which robot are you watching?**

## Not on the schedule

If you're not on the schedule, or your shifts are done, pick **All** to scout any match the scout lead asks you to.

## Practice

**Practice** opens the real form for a made-up match, so new scouts can learn it. Watch any match, on video or in your head, and fill it in. Points add up live, and **Save** only shows **What would have been recorded**. Nothing is sent to the team's data. Tap **Practice again** to go another round.


---

# 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-guide/scout-a-match.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.
