Your folio
Your folio at /artists/[your-slug] is the public record of who you are and what you offer. It carries:
- A short biographical paragraph (the one a programme editor would actually print)
- Core instrument or ensemble configuration
- Base city — for travel-cost reasoning, not residency
- Repertoire highlights
- A media kit slot
The folio is searchable from /roster and from every presenter dashboard. It is also where a request-hold begins.
Declared availability
Availability is declared, not inferred. You set:
- Windows when you are open to engagements
- Blackout dates when you are not
- Travel proximity — how far you will travel from your base city without negotiation
The calendar uses this to detect conflicts when a Hold is requested.
Incoming requests
When a presenter files a request-hold on your folio, it appears in your dashboard under Requests. Each carries: the proposed date, venue, fee range, and a short message from the presenter.
You have three actions: Accept (creates a Hold), Decline (closes the request with an optional reason), or Counter — propose a revised date, fee, or programme.
Holds, quotes, and onward
An accepted request becomes a Hold with an expiry. From the Hold, you (or the office) prepare a Quote: fee, deposit schedule, technical and hospitality riders, and any conditions. The presenter accepts or declines.
Approval flips the Quote to a Contract. The Contract issues an Invoice; the Invoice, once paid, closes the engagement with a Settlement. Your platform fee, where it applies, is recorded against the engagement and visible in your statements.
The agent relationship
If you are represented, your agent's workspace can be linked to your folio. They see your incoming requests, draft quotes on your behalf, and manage holds. You retain accept-decline authority — they cannot commit you without your sign-off.
Where to next
- Request and hold, step by step — the lifecycle from the presenter's side
- Safety and trust — verification and audit
- Billing — fees, payouts, and statements