Contracts and documents turn booking information into agreements that can be sent, reviewed and signed. The best flow starts before the booking: prepare templates, business identity, signing settings and rider defaults so every booking can produce the right document with less manual editing.
Client contracts
- Use contract templates to define the text, placeholders and document structure that should be reused.
- Use booking contract actions from the booking overview to create, preview, send and track the contract.
- The contract status cards help you see whether a contract is missing, sent, signed, incomplete or needs attention.
- Signing contacts come from the booking relation and contact roles, so keep relation data accurate.
Riders
Use riders for technical and hospitality information that belongs with the agreement. Add the rider to the artist, use the AI PDF upload when an existing rider should become editable text, and assign the rider to the contract that should include it. Refer to the embedded rider as the rider in user-facing workflows; it keeps the rider content inside the generated contract flow instead of as a loose attachment.
Purchase contracts
Purchase contracts or booking confirmations are sent to suppliers or team members from booking costs. The important requirement is the relation: connect a creditor or relation to the relevant cost line, or make sure the booking has the relation that should receive the document. This is also connected to purchase invoices, because the same supplier relation is used to understand which costs are booked, contracted and invoiced.
Related settings
- Business identity and document layout influence how generated documents look.
- Contract template and signing settings influence which messages are sent and how signing is handled.
- Artist riders and artist defaults influence which documents are available in booking contracts.