> 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/raidlogs/pit-crew-guide/report-card.md).

# The report card

A match's page opens on its **Report card**. The match list shows each match's result, like "2 to fix" or **All clear**.

## Check before next match

At the top, a short ranked list of what to look at before the next match, each with where on the robot and why. The checks decide what's wrong; a model only ranks and explains, and every item has to come from a finding of this match. When nothing fired, the card just says all clear. A debrief posted after the checks rewrites the list about 20 seconds later.

## Findings

Below the list, what each check found, most urgent first, with the device, its mechanism, the match time and what to look at. Findings from experimental checks show separately and don't count.

If the checks' thresholds changed since the report was made, the card says so: click **Check again**. **Check again** also comes back if a run is taking too long.

## Drive team debrief

What the drivers posted in Slack about this match. See [Debrief from Slack](https://docs.raidrobotics.org/raidlogs/drive-team/debrief-from-slack.md).

## Ask about this match

Type a question about the match, like "why did the elevator stall in auto?". Claude reads the match's logged signals to answer it. Each question costs a few cents, billed to the team's Anthropic key.

## Log files

The match's files, with **Add files**, **Download**, **Edit tags**, **Delete file…** and **Delete match…**. **Open in AdvantageScope** opens the match's logs in AdvantageScope in the browser.


---

# 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/raidlogs/pit-crew-guide/report-card.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.
