> 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/track-alliance-selection.md).

# Track Alliance Selection

**Alliance Selection › Track Alliance Selection** is for the stands during alliance selection. Everyone can follow along; strategists record what happens.

## Before selection starts

* Make sure [the team list](https://docs.raidrobotics.org/raidscout/strategy-guide/team-list.md) is final. It's the only list used here.
* One strategist records. Everyone else just watches.
* Open this tab on a charged phone or laptop with a good connection.

## What's on screen

{% tabs %}
{% tab title="Phone" %}
![Track Alliance Selection after The Blue Alliance posted the alliances, with 4469's highlighted and Our next pick, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-5af24dd8e1e707933478568332392a11a471837c%2Fphone-track-alliance-selection.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Track Alliance Selection after The Blue Alliance posted the alliances, with 4469's highlighted and Our next pick, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-0d947b9585ec65cb84ef9e3448fcabb2e659296a%2Ftrack-alliance-selection-laptop.jpg?alt=media)
{% endtab %}
{% endtabs %}

* **Our next pick** at the top.
* The alliances as they form, in a header that stays in view.
* The team list in order as a table: **Ours** (our pick list rank), **Event** rank, **Record**, points per match by phase and xP.

## Record selection (strategists)

As each alliance picks:

1. Tap the team the alliance on the clock picks.
2. If the team says no, tap **Mark declined** on its row. A declined team can't be picked after that.
3. If the alliance runs out of time, tap **Timed out**. The alliance is skipped, asked again after each later turn before play moves on, and the round waits for its pick.

Made a mistake? Tap **Undo** on the message that appears after each pick. **Start over** (⋯ menu) clears every pick and decline recorded here.

Serpentine order and captains moving up follow FRC's rules. Once The Blue Alliance posts the alliances, they take over.

## The table

Tap a column heading to sort for a last-minute decision; any column but **Ours** lists every team, best first. Either way, teams still available come first, then captains, then picked and declined teams.

**Columns** chooses which stats show. Phones start with **Ours**, **Event** and points so rows fit without scrolling sideways. The choice is remembered on this device.


---

# 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/track-alliance-selection.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.
