> 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/strategy-guide/strategy.md).

# Overview

For strategists and drive coaches. (Drive coaches can do everything a strategist can, for now, plus mark teams **Not a fit**.) You read all the team data, plan our matches, keep the team list and run alliance selection. You can also check the Audit, make calculated values and ask scouts questions.

## During qualifications

* **Read the data:** [Teams and match entries](https://docs.raidrobotics.org/raidscout/strategy-guide/teams-and-entries.md).
* **Plan our next match:** [Our matches](https://docs.raidrobotics.org/raidscout/strategy-guide/our-matches.md).
* **Keep the data honest:** work through [the Audit](https://docs.raidrobotics.org/raidscout/scout-lead-guide/audit-and-rescouts.md) with the scout leads.
* **Ask for what's missing:** send scouts a [question](https://docs.raidrobotics.org/raidscout/scout-guide/questions.md), in the app or from Slack.

## Building toward alliance selection

1. **Say what matters** in [Pick Priorities](https://docs.raidrobotics.org/raidscout/strategy-guide/pick-priorities.md): profiles for first and second pick, each with weighted criteria.
2. **Fill the team list** from Pick Priorities, then adjust it by hand on [the team list](https://docs.raidrobotics.org/raidscout/strategy-guide/team-list.md).
3. **Settle close calls** with [Sorting Games](https://docs.raidrobotics.org/raidscout/strategy-guide/sorting-games.md) and the students' [pick lists](https://docs.raidrobotics.org/raidscout/strategy-guide/my-picklists.md).
4. **Check fit** with [Alliance Compatibility](https://docs.raidrobotics.org/raidscout/strategy-guide/alliance-compatibility.md).
5. **Practise** with [Mock Alliance Selection](https://docs.raidrobotics.org/raidscout/strategy-guide/mock-alliance-selection.md).

## At alliance selection

Use [Track Alliance Selection](https://docs.raidrobotics.org/raidscout/strategy-guide/track-alliance-selection.md) in the stands to record picks as they happen. The team list is the only list used.


---

# 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/strategy-guide/strategy.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.
