> 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/pre-scouting.md).

# Pre-scouting

Pre-scouting happens before the event, from videos and past events, so strategy knows every team before we arrive. Open **Scout › Pre-scout**.

{% tabs %}
{% tab title="Phone" %}
![Scout › Pre-scout with the To do / All filter and a tile per team, Done ones showing who pre-scouted them, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-321d0f6bc6d89d629f4aa46db79b490e2093495f%2Fprescout-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Scout › Pre-scout with the To do / All filter and a tile per team, Done ones showing who pre-scouted them, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-80245a7c7c77ddc3272fac5140fae606e3320967%2Fprescout-laptop.jpg?alt=media)
{% endtab %}
{% endtabs %}

## Pre-scout a team

1. Pick a team from the list, or use **Find a team**. **To do** shows teams nobody has pre-scouted yet; **All** shows every team.
2. Watch their matches from earlier events (The Blue Alliance has videos) and read anything they've posted.
3. Answer the form's questions.
4. Under **Notes**, say **What did you see?**: what they do well and what they struggle with.
5. Add a **Video or page link** to what you watched.
6. Tap **Save**. The team is marked **Done** in the list.

When every team is done, the list says **Every team is pre-scouted.**

Pre-scouting answers show on the team's page and can be weighed in [Pick Priorities](https://docs.raidrobotics.org/raidscout/strategy-guide/pick-priorities.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-guide/pre-scouting.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.
