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

# Riders & feedback

Each performance carries a hospitality and a technical rider: the document the artist supplied, and the itemised lines your team works from.

**Rider documents**: uploads with version history. Artists can upload these themselves through the portal.

**Rider lines**: each line is a [product](https://docs.eventication.com/event/artists/rider-products.md) from your catalog (or free text), with a quantity, unit, location (stage or dressing room) and note.

**Feedback**: every line can be answered as *pending*, *confirmed* or *denied*. Denying opens a page where you can offer an alternative ("cola instead of energy drink"). Answers can be given from the row menu or on the line's form, and every change is logged.

**Feedback PDF**: the answered rider as a document for the artist, with pending lines visibly open. It can also be read in the artist portal.

{% hint style="warning" %}
A **denied** line is dropped from the order forms, totals and unpack list in [Purchasing](https://docs.eventication.com/event/artists/purchasing.md): you will not order what you refused. Only the per-performance view keeps showing it, marked denied. Pending lines still count.
{% endhint %}

Switching rider feedback off in the settings hides all answers; they come back untouched when it is switched on again.


---

# 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/riders.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.
