> 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-lead-guide/pit-assignments.md).

# Pit assignments

**Manage › Pit assignments** decides who pit scouts which team. It opens first in **Manage** before matches start.

## Assign pits

{% tabs %}
{% tab title="Phone" %}
![Manage › Pit assignments showing All, with Auto-assign and Assign on each team's tile, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-24498c124049804a70b3588b99e1cdacb4741bcb%2Fmanage-pit-assignments-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Manage › Pit assignments showing All, with Auto-assign and Assign on each team's tile, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-bdb33d516227402287c7e2ad2596f985f7d1ca57%2Fmanage-pit-assignments.jpg?alt=media)
{% endtab %}
{% endtabs %}

* **One team at a time:** tap **Assign** on the team's row, then pick a **Pit scout** (or **Nobody**).
* **Auto-assign:** tap **Auto-assign**, uncheck anyone who isn't pit scouting, and confirm. Teams nobody has yet are shared out evenly between the scouts you leave checked, grouped by pit row. Teams already given out stay as they are.

The filter has **No scout** for teams nobody has been given yet. Teams without a scout show a **No scout** badge; scouted teams show **Done**.

Scouts see their pits under **Scout › Pits** and on Home. If Slack is set up, a scout gets a ping when they're assigned a pit.


---

# 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-lead-guide/pit-assignments.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.
