> 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/audit-and-rescouts.md).

# The Audit and rescouts

**Data › Audit** checks our scouting against the official scores and Match13, and is where robots are handed out to rescout. Scout leads, strategists, drive coaches and admins can open it.

Work through it between matches: watch the video, then mark the item right or send it for a rescout.

## What it checks

{% tabs %}
{% tab title="Phone" %}
![Data › Audit with Flag beyond, and how many alliances, robots and missing entries are flagged, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-76345bd5a52c3fb87b7d38c0478a4f2e4acbf862%2Fdata-audit-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Data › Audit with Flag beyond, and how many alliances, robots and missing entries are flagged, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-14aed20cdbfc28190a31ec792f10268f00804cdb%2Fdata-audit-laptop.jpg?alt=media)
{% endtab %}
{% endtabs %}

| Card                            | What's flagged                                                                                                                                                                                                                                      |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Alliances that don't add up** | The points we scouted for the three robots against the official score less the fouls the alliance was given. An alliance is flagged when its gap is further from the event's typical gap than the threshold. A robot marked ⚠ looks off on its own. |
| **Robots that look off**        | Robots far from both the team's other matches and its Match13 xP. Likely the mis-scouted robot.                                                                                                                                                     |
| **Robots with no entry**        | Robots in played matches that nobody scouted. Their alliances can't be checked until they're scouted.                                                                                                                                               |
| **Scouts**                      | Each scout's matches and accuracy.                                                                                                                                                                                                                  |

The typical gap allows for points no scout records (bonuses, things you can't see), so alliances are compared with each other, not with zero.

**Flag beyond** sets the threshold for this event. It starts at 2 standard deviations; raise it to see fewer flags, lower it to see more.

## Deal with a flag

1. Tap **Watch** to open the match video (The Blue Alliance's video, or a YouTube search when there isn't one).
2. Open the item's ⋯ menu and choose:
   * **Open the entry** to see every answer.
   * **Correct it from video** to rescout it yourself.
   * **Send to rescout** to hand it to a scout. It shows on their Home under **Your rescouts**, and on **Manage › Coverage**.
   * **Checked, it's right** (or **Checked, nothing to scout** for a robot with no entry) to clear it.

Marked items show **Checked** or **Rescouted**. Changed your mind? **Not checked after all** or **Take the rescout back**.

## What a rescout does

When the assigned scout saves the rescout, it replaces the robot's earlier entries in every stat. The Audit still keeps the old entries to work out the original scout's accuracy.


---

# 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/audit-and-rescouts.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.
