> 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.md).

# Overview

Scouts are the team's eyes. Everything strategy decides, from match plans to the pick list, starts with what you record.

## Your event, in order

1. **Before the event:** [**pre-scouting**](https://docs.raidrobotics.org/raidscout/scout-guide/pre-scouting.md)**.** Watch videos and read about each team.
2. **Until qualifications start:** [**pits**](https://docs.raidrobotics.org/raidscout/scout-guide/pits-and-photos.md)**.** Visit the pits you're assigned and fill in the pit form, with photos.
3. **During qualifications:** [**matches**](https://docs.raidrobotics.org/raidscout/scout-guide/scout-a-match.md)**.** Watch your robot in each match of your shift and save its form.

**Home** always shows what's next for you: your next pit, your next match, robots you've been handed to [rescout](https://docs.raidrobotics.org/raidscout/scout-guide/rescouts-and-something-to-do.md), and [questions](https://docs.raidrobotics.org/raidscout/scout-guide/questions.md) for you. When you have nothing assigned, it offers **Something to do**.

## Also for scouts

* [No connection](https://docs.raidrobotics.org/raidscout/scout-guide/no-connection.md): what happens when you save with no signal.
* **My Picklists** and **Sorting Games** under **Alliance Selection**: your own pick list and quick games that help build the team's. See [My Picklists](https://docs.raidrobotics.org/raidscout/strategy-guide/my-picklists.md) and [Sorting Games](https://docs.raidrobotics.org/raidscout/strategy-guide/sorting-games.md).
* **Data** and **Our matches**: every team's numbers and our match plans, to read.

## Good scouting

* Watch only your robot. Count as it happens, not from memory after.
* Fill in **Notes** with what the numbers miss: a robot that tipped, defense it played, a mechanism that broke.
* If you miss something, say so in **Notes** rather than guessing.
* Once matches are being scouted, Home shows the **Scouting leaderboard**: matches you've scouted and your accuracy, the share of your entries the Audit didn't flag.


---

# 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.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.
