> 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/offers/offer-form.md).

# The offer form

An offer is written for an artist and then covers one or more of their performances, each with its amount.

**Artist**: an artist from your database, or a typed name for an act you have not created yet.

**Status**: *wishlist*, *draft*, *sent*, *confirmed*, *declined* or *signed*.

**Performances and amounts**: the lines of the offer, added from the artist's performances. Amounts are only visible with the money rights.

**Terms**: the conditions printed on the offer PDF.

**Internal notes**: never leave the office; the artist does not see them.

Editing an offer that was already sent creates a new version; the older versions stay readable on the offer.


---

# 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/offers/offer-form.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.
