> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/artists/stages.md).

# Stages

The stages this edition plays on. Each stage has its own page with its line-up, documents, docks and runsheet.

**Opened days**: tick the [days](https://docs.eventication.com/event/planning/days.md) a stage is in use. A stage with nothing ticked counts as closed on every day.

**Name per day**: a stage can carry a different name per open day ("Main Stage, hosted by X"). The name only exists on open days and is cleared when a day is closed. The line-up, PDFs and the artist portal all show the day's name.

**Documents**: stage plans and spec sheets, with version history. When uploading a new document or version you can notify the artist contacts of that stage's performances; they receive a mail in their own language with their personal portal link.

**Docks**: the loading docks of a stage, with bookings per supplier or performance (arrival, kind, papers such as a CMR).

**Runsheet**: the minute-by-minute schedule of a stage day, as slots with times, descriptions and assigned crew members.

{% hint style="info" %}
Day names, docks and the runsheet each have their own switch in the module [settings](https://docs.eventication.com/event/artists/settings.md).
{% endhint %}


---

# 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.eventication.com/event/artists/stages.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.
