> 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/transport/ride-form.md).

# The ride form

The form follows the ride's type: every type asks only for what it needs.

**Every ride**: the passenger (a performance, or a typed name for a crew ride), the day, the route (each end is the venue, an accommodation, an address-book entry or free text), pax, a note and documents (tickets, vouchers, confirmations).

**Rides with a pickup** (everything except flight and train): a pickup time and an optional pickup point.

**Flight and train**: a departure and arrival moment, the flight or train number, the operator, the class, the booking code (PNR) and a booking reference, plus who pays the ticket (the event or the artist).

**Taxi**: the taxi company (one of your suppliers, or free text), how the fare is settled (on the event account, with a voucher, or the artist pays) and the name board.

**Own fleet** (transfer with own driver, shuttle, own vehicle): the driver and vehicle from your [fleet](https://docs.eventication.com/event/artists/transport/drivers-and-vehicles.md), the number of cars and the type of car.

**Fixed price and luggage info**: when a price was agreed and what is in the trunk.

{% hint style="info" %}
The type itself cannot be changed afterwards: a flight form and a transfer form ask different things, so a miskeyed ride is deleted and recreated.
{% 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/transport/ride-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.
