> For the complete documentation index, see [llms.txt](https://docs.iowacityrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iowacityrobotics.org/competitions/regionals/setup-and-practice-matches.md).

# Setup & Practice Matches

Some regionals have a preload day where teams can come in to set up their pits; during these days the pits will not be open and you cannot work on your robot, you can send in a small team to set up the pit and then leave the venue.&#x20;

The first day will have teams coming in, setting up pits, getting checked in, getting inspected, and then participating in practice matches. There will be a shorter schedule of practice matches that don't impact your record, but allow you to get practice competing on the field. Some regionals will have further practice matches for teams after the scheduled matches have completed. This will be filled using the queue line, where teams can fill in during practice matches during scheduled matches. To join the queue line, a team must have an inspected robot.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.iowacityrobotics.org/competitions/regionals/setup-and-practice-matches.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
