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

# Coverage

**Manage › Coverage** shows how much of the event we've scouted and who has done what. It opens first once matches start.

## What's on it

{% tabs %}
{% tab title="Phone" %}
![Manage › Coverage with Pit scouting, Match scouting and Data requests, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-61eeb5d9226bcd56d709dce2644d052821d7e43d%2Fmanage-coverage-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Manage › Coverage with Pit scouting, Match scouting and Data requests, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-82f55702bdd04918dca8134f6a5f40cb1d87ce7d%2Fmanage-coverage.jpg?alt=media)
{% endtab %}
{% endtabs %}

| Card                      | What it shows                                                                                                                                                       |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Pit scouting**          | How many pits are done, with **Open pits** to go to the list                                                                                                        |
| **Match scouting**        | How many robots in played matches have an entry (**robots watched**), with **Open matches**                                                                         |
| **Robots nobody watched** | Robots in played matches with no entry, and who each has been handed to for rescout                                                                                 |
| **Teams short on data**   | Teams with no pit data or with matches nobody watched                                                                                                               |
| **Data requests**         | Questions still open, with **Open requests**                                                                                                                        |
| **Scouts**                | Each scout's **Seats** (robots the schedule gave them in played matches that they saved), **Pits** (their assigned pits that are done) and when they **Last saved** |

A scout who didn't save a seat they were given shows a red **missed** badge next to their seats. Hover it to see which matches.

## Handing out rescouts

**Hand out rescouts** opens **Data › Audit**, the one place robots are handed out to rescout. Robots handed out there show here with the scout's name. See [The Audit and rescouts](https://docs.raidrobotics.org/raidscout/scout-lead-guide/audit-and-rescouts.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/scout-lead-guide/coverage.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.
