> 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/set-up-an-event.md).

# Set up an event

Do this before the event, in **Event setup**.

## Events

**Add an event** for each competition or practice day. If you give it its **TBA event key** (and the **Nexus event key** if it's different), RAIDLogs syncs our match schedule: from The Blue Alliance every 5 minutes and from Nexus every minute while the event is on. **Sync schedule now** fetches it right away. Without a key, number matches by hand.

## Batteries

Label each battery with a number and add it here, so every match records which one was in the robot. A battery that's done can be marked **Retired**.

## Mechanisms and signals

Programmers set these up once a season; see [Signals and mechanisms](https://docs.raidrobotics.org/raidlogs/programmers/signals-and-mechanisms.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/raidlogs/pit-crew-guide/set-up-an-event.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.
