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

# FAQ

## Getting in

**I signed in but only see "Your account doesn't have a role yet".** New accounts need a role. Ask a scout lead (for Scout) or an admin. See [Sign in and get a role](https://docs.raidrobotics.org/raidscout/getting-started/sign-in-and-access.md).

**I can't see a tab someone else can.** Tabs follow your roles. **Audit**, **Calculated**, **Pick Priorities**, **Alliance Compatibility** and **Mock Alliance Selection** are for scout leads, strategists and drive coaches; **Manage** is for scout leads and admins.

## Scouting

**Why can't I save this robot?** You can only save the robot your seat is on, or one you were handed to rescout. Check your seat under **Your next shift**.

**I saved with no signal. Did it go through?** It's **Kept on this phone** and sends by itself when you're back online. See [No connection](https://docs.raidrobotics.org/raidscout/scout-guide/no-connection.md).

**I saved the wrong thing.** Open the same match and robot again and save. The server keeps one entry per scout per robot per match, so it's replaced.

**What does Practice do?** It opens the real form for a made-up match. Nothing is sent to the team's data.

**Why doesn't my pit form have Robot photos?** Photo storage isn't set up yet. Tell an admin.

## Data

**Why don't the numbers match the official score?** Scouts can't see every point (bonuses, fouls), so our totals differ a bit. The Audit compares alliances with each other to find the real mistakes. See [The Audit and rescouts](https://docs.raidrobotics.org/raidscout/scout-lead-guide/audit-and-rescouts.md).

**What happened to an entry marked "Replaced by a rescout"?** Someone rescouted that robot from video. The new entry counts in every stat; the old one doesn't.

**A team has no scouted matches. Why does it have numbers?** Until we scout a team, Alliance Compatibility uses its Match13 xP, marked **xP**.

## Pick lists

**Which list do we use at alliance selection?** Only the team list. Personal lists and Sorting Games feed it through Pick Priorities.

**Will Fill team list undo my changes?** **Fill team list** replaces the tiers (it asks first, and you can undo). **Fill empty spots** keeps every placed team. Pick Priorities shows where the list and the model disagree rather than overwriting.

**Who sees my pick list?** Only you, except the list marked **Counts in Pick Priorities**, which scout leads and strategists can review.

## Reporting a problem

Click the version at the bottom of the sidebar to copy it, and send it with what you were doing and what you saw.


---

# 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/reference/faq.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.
