Booking Contract Template

In plain language: Identifies the client and the service provider by their full legal names and confirms the nature of the engagement — who is hiring whom and for what.

Common mistake: Using a stage name or trade name instead of the registered legal entity or individual's full legal name. If a dispute arises, enforcing a contract against a name that doesn't appear on any government record is far more difficult.

In plain language: Specifies the exact date, start and end times, and venue address for the engagement, removing any ambiguity about where and when performance is expected.

Common mistake: Listing only the event date without specifying load-in, soundcheck, or performance end times. Disputes over overtime or setup delays almost always trace back to a contract that only stated a single time.

In plain language: Describes exactly what the service provider is expected to deliver — set length, number of sets, specific duties, deliverables, or performance format.

Common mistake: Describing the scope in general terms like 'live performance' with no duration or format detail. Without specifics, the client may expect a full evening show while the artist plans a 30-minute set.

In plain language: States the total booking fee, the deposit amount due to secure the date, when the balance is due, and the accepted payment methods.

Common mistake: Describing the deposit as 'refundable' without specifying the conditions under which it is returned. An ambiguous deposit term turns every cancellation into a dispute.

In plain language: Sets out what each party owes the other if the engagement is cancelled or postponed — including kill fees, deposit forfeiture, and any notice requirements.

Common mistake: A one-sided cancellation clause that only addresses client cancellations. If the performer cancels and no reciprocal obligation is stated, the client may be left with a deposit forfeited and no legal remedy.

In plain language: Incorporates the performer's or provider's technical and hospitality requirements as a binding obligation of the client, and clarifies who bears the cost of meeting them.

Common mistake: Attaching a rider but failing to state it is 'incorporated by reference' in the main contract body. A rider that is not contractually incorporated is an informal wish list, not an enforceable obligation.

In plain language: Excuses both parties from performance obligations when an event beyond anyone's control — pandemic, natural disaster, government prohibition — makes the engagement impossible.

Common mistake: Omitting a force majeure clause entirely. Without it, a party unable to perform due to a genuine emergency may still be liable for breach — an outcome courts in many jurisdictions will still enforce if the clause is absent.

In plain language: Defines whether the client may record, livestream, photograph, or broadcast the performance, and who owns any recordings made.

Common mistake: Saying nothing about recording rights and assuming the default is 'no recording allowed.' Clients often record events as a matter of course — without a clause addressing this, enforcement is difficult and disputes are common.

In plain language: Each party agrees to cover the other's losses caused by their own negligence or breach, and caps the maximum financial exposure of the service provider to the total fee paid.

Common mistake: No liability cap for the service provider. Without one, a performer could theoretically be held liable for consequential damages — lost ticket sales, venue fees — that far exceed the booking fee.

In plain language: Specifies which jurisdiction's law governs the contract and how disputes are resolved — court, arbitration, or mediation — and where proceedings must take place.

Common mistake: Leaving governing law blank or using a jurisdiction that has no connection to either party's location. A mismatched governing law clause forces one party into a foreign legal system to enforce basic terms.

A booking contract is a legally binding agreement between a client and a service provider — such as a performer, speaker, DJ, photographer, or venue — that confirms a specific engagement on a defined date, at an agreed fee, and under stated conditions. It protects both parties by establishing what is owed if either side cancels, fails to perform, or delivers something different from what was agreed.

Any individual or business that pays for or provides a time-specific service tied to a particular event date should use a booking contract. This includes musicians, DJs, bands, keynote speakers, photographers, videographers, event planners, venue managers, corporate event coordinators, and entertainment agencies. If a date is confirmed and money is changing hands, a signed contract is essential before any deposit is paid.

At minimum: the full legal names of both parties, event date and location, performance or service scope, total fee and deposit amount, payment schedule and accepted methods, cancellation and rescheduling policy, force majeure clause, technical rider (if applicable), intellectual property and recording rights, indemnification, and governing law. Missing any of these creates gaps that disputes will fall into.

Yes — a booking contract is generally enforceable as a binding agreement when it contains the essential elements of a valid contract: an offer, acceptance, consideration (the fee), and mutual intent to be bound. Both parties must sign before it becomes fully binding. Courts in most jurisdictions will enforce clear written booking contracts, including non-refundable deposit clauses and cancellation penalties.

For standard engagements — a local band at a corporate event, a photographer at a wedding, a speaker at a conference — a well-drafted template is typically sufficient. Consider engaging a lawyer for high-value bookings (fees above $10,000), touring agreements across multiple jurisdictions, talent engaged through a union or guild, or where IP rights in recordings have significant commercial value.

If the contract includes a reciprocal cancellation clause, the performer is typically obligated to refund the deposit and pay a kill fee to the client. Without such a clause, the client may have a general breach of contract claim but no pre-agreed remedy. This is why a symmetric cancellation clause — covering both sides — is one of the most important terms to include. Force majeure cancellations are typically handled separately, with neither party owing the other a penalty.

A booking contract focuses specifically on engaging a performer, speaker, or service provider for a defined date — covering their fee, scope, and obligations. An event contract is broader and may govern the entire event operation, including venue, catering, AV, and multiple vendors under one agreement. For multi-vendor events, separate booking contracts with each provider are more common and easier to manage than a single omnibus event contract.

In most booking arrangements, the deposit is non-refundable upon signing because the service provider turns down other engagements on that date as soon as the contract is executed. The deposit compensates for that opportunity cost. The contract should state this explicitly — 'the deposit is non-refundable upon execution of this Agreement' — and the cancellation clause should confirm what happens to the deposit under each cancellation scenario.

Notarization is not required for a booking contract to be enforceable in most jurisdictions. A signed (including e-signed) contract with dated execution is legally sufficient. Notarization may be prudent for very high-value engagements or where one party is overseas and the document may need to be enforced through a foreign court, but it is not the standard practice for ordinary booking agreements.