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

# Advancing

Advancing is the preparation of a performance: everything that has to be arranged between booking and show day. The page opens on an overview of every performance, and each row opens the performance's own dossier.

### Overview

One row per performance, one column per part of the module. Every cell is an icon that reads the state from that part's own data and links to the page where you change it: nothing is ticked on the overview itself.

**Rows**: the artist, the stage, the day and the start hour. Performances with the nearest unmet checklist deadline come first. Filter by name, stage or day, and on the Checklist column by *has a deadline* or *overdue*. The artist name opens the dossier.

**States**: *to do* (empty circle), *in progress* (blue), *done* (green), *blocked* (pink), *paused* (orange) and *not applicable* (a dash: this performance does not need it).

**Columns**: grouped as Artist, Production, Accreditation, Travel & stay and On site. A column only shows when its part of the module is switched on in the [settings](https://docs.eventication.com/event/artists/settings.md).

* **Portal**: *to do* without a portal link, *in progress* once a link exists but was never opened, *done* once the artist opened it, *paused* when the portal is closed.
* **Contacts**: the number of contacts with an e-mail address; *to do* when there are none.
* **Checklist**: settled items / all items. *Blocked* when a deadline has passed, the count turns orange when one is close. The column is absent when no checklist items are configured.
* **Technical rider**, **Hospitality rider**, **Special rider**: *to do* until the rider holds lines or documents. With rider feedback switched on, *in progress* shows answered lines / all lines until every line is confirmed or denied.
* **Touring party** and **Guestlist**: accredited people / the maximum. *Done* once the maximum is reached (or without a maximum, as soon as someone is accredited), *not applicable* when the maximum is zero. Guestlist is absent when the module handles no guests.
* **Transport**: every ride of the performance, flights included. *Not applicable* when the performance needs no transport, *to do* without rides, *blocked* as soon as one ride is delayed, *in progress* while a ride is still to book, booked or planned, *done* once every ride is confirmed or further. Cancelled rides do not count.
* **Accommodation**: *not applicable* when the performance needs no accommodation, *in progress* with confirmed bookings / all bookings while one is still provisional, *done* once every booking is confirmed.
* **Dressing room**: *done* once the performance has a dressing room slot.
* **Briefing**: *to do* until a briefing exists, *in progress* until it is sent, *done* once it was e-mailed to the artist.

{% hint style="info" %}
The **Follow-up** tab next to the overview lists the open checklist items one per row, nearest deadline first.
{% endhint %}

### The dossier

**Checklist**: the phases and items you configure in the module [settings](https://docs.eventication.com/event/artists/settings.md). Deadlines can be fixed dates or relative to the show. Each performance tracks its own state per item, and reminder e-mails can chase the artist for what is still open.

**Riders**: the hospitality and technical rider of the performance. See [Riders & feedback](https://docs.eventication.com/event/artists/riders.md).

**Accommodation, transport and dressing room needs**: per performance you record what the act needs; the [accommodation](https://docs.eventication.com/event/artists/accommodation.md), [transport](https://docs.eventication.com/event/artists/transport.md) and [dressing room](https://docs.eventication.com/event/artists/dressing-rooms.md) pages read from this.

**Itinerary**: the performance's day schedule (pickup, soundcheck, show, ...), also visible in the artist portal.

**Briefing**: the information sheet for the artist, built from the event-wide venue, parking and contact blocks in the settings plus the papers of this performance.

{% hint style="info" %}
The artist can fill in part of the advancing themselves through the [artist portal](https://docs.eventication.com/event/artists/artist-portal.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/advancing.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.
