Parties
Identify performer(s) and presenter with legal business names, contact information, and invoice recipient details to ensure accurate payment and tax reporting.
A written Music Performance Document reduces ambiguity about pay, rights to recordings, and logistical responsibilities. It protects both parties by documenting obligations, remedies for breach, and allocation of risks.
The Music Performance Document is used by performers, venues, presenters, and third-party vendors to define responsibilities and payments before an engagement.
Clear roles in the contract reduce last-minute disputes and support tax and insurance compliance for all parties.
Identify performer(s) and presenter with legal business names, contact information, and invoice recipient details to ensure accurate payment and tax reporting.
Specify event date, call time, performance duration, load-in/soundcheck windows, and any rehearsal schedule so logistics are unambiguous.
State fee structure (flat fee, percentage, door split), deposit amount and due date, final payment timing, and any expense reimbursement rules.
Attach technical rider listing stage plot, input list, backline, sound requirements, hospitality, and travel arrangements; make the rider an enforceable exhibit.
Clarify rights for live recording, broadcasting, or sync licensing; specify who may authorize recordings and the compensation for such uses.
Include cancellation windows, force majeure language, insurance requirements, indemnities, and limitations of liability to allocate event risk.
| Field | Configuration |
|---|---|
| Signature Block | Require signature and date for each party |
| Deposit Checkbox | Conditional field that appears if deposit > $0 |
| Rider Upload | Allow attachment of technical rider PDF |
| Authentication | Email link with optional SMS code |
Choose distribution channels that match your audience and evidence needs — email links, embedded signing, or in-person kiosks are common.
Ensure the chosen method captures signer attribution, timestamps, and retention that satisfy ESIGN/UETA and internal recordkeeping policies.
Commonly 14–30 days after contract execution
Often due on the day of the performance or within 7 days after
Typically required 14 days before event
Submit at least 7 days before load-in
Specify notice window and associated penalties
Mutual agreement on terms and confirmation of date.
Deposit secures the date and triggers obligations.
All parties have signed; rider and exhibits attached.
Final payment, expense reconciliation, and any post-event reporting.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | No cap | No cap | No cap |
A community school contracts with a quartet for a spring concert to define fees, parental permissions, and rehearsal times.
A local club books an indie band for a weekend show and records a deposit and rider in the contract.