> 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/team-list.md).

# The team list

**Alliance Selection › Team list** is the one list used at alliance selection. Strategists keep it; everyone can see it. Strategists land here when they open **Alliance Selection**.

## The board

Every pick list is a board:

* **Bank**: teams not placed yet.
* **Tier 1** (first pick), **Tier 2** (second pick), **Tier 3** (backups).
* **Not a fit**: teams that won't work with us.

On a wide screen the bank is on top and the tiers sit in columns. On a phone the tiers stack and the bank opens in a drawer from the bottom.

{% tabs %}
{% tab title="Phone" %}
![The team list with Card fields, the tiers and the bank, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-b3155d90a3ace5a3ab127bd1cf63ba111955f9f4%2Fteam-list-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![The team list with Card fields, the tiers and the bank, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-e092bdcfee8066525cb00e4623d1cf39f2410498%2Fteam-list.jpg?alt=media)
{% endtab %}
{% endtabs %}

## Build it

1. Fill it from [Pick Priorities](https://docs.raidrobotics.org/raidscout/strategy-guide/pick-priorities.md) with **Fill team list** (also in the board's empty-list notice and ⋯ menu).
2. Adjust by hand:
   * **Drag** a team between tiers. A team dropped on another takes its place.
   * Or **tap** a team to pick it up, then tap a team to put it in that place, or use the bar that appears: up, down, a tier, **Not a fit**, **Back to the bank**.
3. **Add from bank** on a tier suggests the bank's best teams for it. Pick Priorities uses the first profile for Tier 1 and the second for the rest. Choose how it ranks them with **Suggest by**.
4. **Fill empty spots** (⋯ menu) keeps every placed team and tops each tier up to 8.

The bank sorts by Pick Priorities, Sorting Games, both, scouted points or xP.

## What cards tell you

* **Games rate it higher**: Sorting Games put this team clearly above the one before it. The bar offers to move it up.
* **Higher than the model** / **Lower than the model**: the team sits a round higher or lower than Pick Priorities would put it.
* **Coach: not a fit**: the drive coach flagged it. A notice lists any such team still in a tier, with one tap to move it.
* **Pit scouted** / **No pit report**.
* Numbers on cards are places on the alliance selection screen. Picked teams show crossed off.

When the top two suggestions are a close call that Sorting Games hasn't settled, **Ask Sorting Games** sends the pair there.

## Card fields

Scout leads and strategists choose what the cards show with **Card fields** (up to 6). That choice is also the year's default for everyone's own lists. **Back to the game's defaults** undoes it.

## Not a fit (drive coaches)

On a team's card, **Coach: Not a fit…** marks it, with a note on what you saw. Only strategists and drive coaches see it. **Clear coach's Not a fit** takes it off.


---

# 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/team-list.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.
