> 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/pick-priorities.md).

# Pick Priorities

**Alliance Selection › Pick Priorities** scores every team by what we say matters for each pick, and fills the team list. Strategists and drive coaches open it.

## Profiles

{% tabs %}
{% tab title="Phone" %}
![Pick Priorities on the First pick profile, with Fill team list and a slider and share for each criterion, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-f1b54a3246201aec0e54274d43d4a0ea55d002db%2Fpick-priorities-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Pick Priorities on the First pick profile, with Fill team list and a slider and share for each criterion, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-12315969b2becf3658f4fbc91534489cfbd20250%2Fpick-priorities.jpg?alt=media)
{% endtab %}
{% endtabs %}

A model has profiles, for example **First pick** and **Second pick** (up to 4). Each lists criteria under **What matters**, each with a slider for how much it matters. The percentage is its share of the score; together they make 100%. **Add a profile like this one** copies the current profile as a starting point.

## What a profile can weigh

Use **Add something that matters…** to add criteria:

* **Our scouting**: points, the bad-match floor, recent form.
* **Reliability**: breakdowns and fouls.
* **Fit with us.**
* **Any question** from the match, pit or pre-scout form, and the season's calculated values.
* **Match13** xP, and the **event rank**.
* **The students' pick lists** and **Sorting Games** answers.

## How the score works

Each number is scaled 0 to 100 across the teams here (best 100, worst 0), then averaged by weight. A team we have no number for gets the event's average for it. **Thin data** marks teams with little to go on.

Sliders re-rank the teams at once. **Save** shares the model with every strategist (**Saved for every strategist**). During alliance selection, teams still to pick come first.

A new event starts from the last event's weights. **Reset this event's model** (in the ⋯ menu) goes back to those, or to the app's starting weights.

## Fill the team list

**Fill team list** puts the top 8 by the first profile into Tier 1, and the next 16 by the second profile, among the teams left, into Tiers 2 and 3. With one profile, it fills all three. Teams marked **Not a fit** stay there, and 4469 is never placed. It asks first, and you can undo it. Save before filling.

**Fill only the team list's empty spots…** (⋯ menu) keeps every team placed by hand and tops each tier up.

The **Team list** column shows each team's tier and place on the list as it stands. It's marked **Higher than the model** or **Lower than the model** when that is eight or more places from where Fill would put it, so hand edits are shown, not overwritten.

## Students' pick lists

**Select students' pick lists…** (⋯ menu) opens the review of everyone's lists. Untick a list to leave it out of "Students' pick lists". See [My Picklists](https://docs.raidrobotics.org/raidscout/strategy-guide/my-picklists.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/strategy-guide/pick-priorities.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.
