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

# Schedule and shifts

**Manage › Schedule** splits the qualification matches into shifts and puts a scout in each of the six seats. Make it once the match schedule is out.

## Make the schedule

{% tabs %}
{% tab title="Phone" %}
![Manage › Schedule with Matches per shift, Remake shifts and Fill empty seats, and Who's scouting how much, on a phone](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-bea20e220d43b97127cfdcba71fc7f7261966be0%2Fmanage-schedule-phone.jpg?alt=media)
{% endtab %}

{% tab title="Laptop" %}
![Manage › Schedule with Matches per shift, Remake shifts and Fill empty seats, and Who's scouting how much, on a laptop](https://1889380250-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsyFsjdnN8G0ek8iqW8Gt%2Fuploads%2Fgit-blob-8b5a6f21fb6a42097fe0271b3caad9f779cfd6b6%2Fmanage-schedule.jpg?alt=media)
{% endtab %}
{% endtabs %}

1. Under **Make the schedule**, set **Matches per shift**.
2. Tap **Make shifts**.
3. Tap **Fill empty seats**, uncheck anyone who isn't scouting at this event, and tap **Fill**. Seats are shared out among the scouts you leave checked.

**Who's scouting how much** shows each scout's number of shifts, and a warning when someone has shifts back to back. The description says how many seats are still empty.

## Change it

* **Change one seat:** choose a different scout (or nobody) from that seat's list in the shift.
* **Remake shifts:** use a different shift length. Do this before people start scouting.
* **Empty every seat** (in the ⋯ menu): the shifts stay; everyone is taken off them.
* **Start over:** clears every shift and who's in it.

## What scouts see

Each scout sees **Your next shift** on **Scout › Matches** and **Your next match** on Home, and tapping their match opens their robot's form. If Slack is set up, scouts get a ping when their shift is 3 matches away.

Seats a scout didn't save show as **missed** on [Coverage](https://docs.raidrobotics.org/raidscout/scout-lead-guide/coverage.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/schedule.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.
