Event management contract: the clauses you cannot leave out
Key event contract clauses with clients, venues, suppliers, performers and freelancers, in Spain and Mexico.
An event management contract must put in writing what is and is not included, how much it costs and when it is paid, what happens if someone cancels or something goes wrong, and who is liable for what. The clauses that prevent the most arguments are cancellation by either party, force majeure, an outdoor plan B, the payment schedule, image rights, data protection and confidentiality. And the client contract is not the only one: venue, suppliers, performers and freelancers each need theirs, consistent with the main one.
Important notice. This guide is practical information from event production, not legal advice. Every event, country and relationship is different, and the law changes. Before signing or sending a contract, have it reviewed by your lawyer, accountant or adviser and adapt it to your case.
Which contract for which relationship
A mid-size event can involve ten contracts. These are the ones we use most:
| Relationship | Contract | Must include |
|---|---|---|
| Client | Event management or quote acceptance | Scope, price, payments, cancellation, changes |
| Venue | Venue hire | Load-in times, capacity, exclusive suppliers, deposit, house rules |
| Hotel | Room block | Release, attrition, no-shows, rooming list |
| Suppliers (AV, catering, decor) | Supplier agreement | Deliverables, times, insurance, replacement |
| Performers and speakers | Performance or speaker agreement | Rider, duration, recording, image |
| Freelancers | Services agreement | Role, days, rate, expenses, insurance |
| Sponsors | Sponsorship | Benefits, brand use, exclusivity |
| Anyone seeing sensitive information | NDA | What is confidential and for how long |
The golden rule: whatever you promise the client must be covered in your supplier contracts. If the client can cancel free of charge up to 30 days out and the venue charges you 50% at 60 days, that gap is yours.
The basic structure of any event contract
- Parties: legal name, tax ID, address, who signs and with what authority.
- Purpose and scope: which event, date, place, guest numbers and what is included and what is not. The “what is not” prevents half of all disputes.
- Price: a figure or a reference to the attached quote, taxes, what happens if numbers change.
- Payment schedule.
- Changes: how they are requested, approved and priced.
- Cancellation by either party.
- Force majeure.
- Liability and insurance.
- Intellectual property and image rights.
- Data protection.
- Confidentiality.
- Governing law and jurisdiction.
- Annexes: quote, floor plan, rider, run of show, house rules.
The key clauses, one by one
Payments
A clear schedule protects everyone. A common example in the industry (not a rule): 50% on signing, 40% before the event and 10% once final numbers are settled. What matters:
- Specific dates or clear milestones, not “before the event”.
- What happens if a payment is late: does production pause, is there interest?
- If the price depends on registrations or bookings, the contract can refer to the attached quote as a base budget instead of fixing the figure, and explain how it is adjusted.
- Taxes: whether prices include VAT or not, always explicit.
Cancellation
Tiered by notice period and for each party: the client cancelling is not the same as the agency cancelling. An indicative example if the client cancels:
| Notice | Amount due |
|---|---|
| More than 90 days | Costs already committed |
| 90 to 31 days | 50% of the total |
| 30 days or less | 100% of the total |
Real figures come from what your suppliers charge you. Start from their cancellation terms and build the client’s on top, with a buffer.
Include guest number reductions too: how far the client can drop numbers at no cost, and from when the contracted figure is payable.
Force majeure
It covers unforeseeable or unavoidable events that prevent performance (natural disasters or orders from the authorities, for example). What to pin down:
- What is in and what is out. Low registrations, a speaker pulling out or a change in the client’s diary are not force majeure.
- What happens to the money: new date, refund of unspent amounts, which committed costs are still payable.
- Notice period and a duty to mitigate.
Plan B for outdoor events
Rain in November is not unforeseeable. Outdoor events need their own clause:
- Who decides and when to trigger plan B (for example 72 hours before, on a specific forecast).
- On what criteria: chance of rain, wind gusts or temperature above or below a threshold.
- What plan B is: marquee, indoor room, schedule change.
- Who pays for the marquee or the change, and whether it is booked in advance.
Data helps set the criteria: Meteo shows the model consensus and 20 years of history for your venue and time slot, for free. But the clause is what counts.
Liability and insurance
Who is liable for damage to people, the venue or equipment, up to what limit, and what public liability insurance each party must hold. Ask suppliers and freelancers for the insurance certificate before the event, not after an accident.
Image rights and intellectual property
- Event photos and video: who can use them and for what. If you want the event in your portfolio, ask for it in the contract.
- Guests: image consent is collected at registration, usually on the client’s behalf.
- Performers and speakers: whether the performance or talk can be recorded, where it is published and for how long.
- Music: public performance rights are a separate matter, handled by collecting societies in each country. Decide who arranges and pays for them.
- Creative work: concept, design and materials; who owns them and whether the client can reuse them.
Data protection: the processor agreement
If you run registration, rooming or check-in for the client’s guests, usually the client is the controller and you are the processor. The processing agreement should state at least which data, for what purpose, for how long, which security measures, whether there are sub-processors (the registration platform, the hotel) and what happens to the data at the end (return or deletion). Forms includes a data processing agreement for your client to sign, and Contracts has an image and data protection template.
Confidentiality and NDA
An NDA or confidentiality clause should state what is confidential, who can see it, how long the duty lasts (including after the event) and what happens on breach. For freelancers and suppliers who go backstage at a launch, signing before you share anything is the bare minimum.
What is specific to each contract
Venue. Load-in and load-out times (and what happens if you overrun), licensed capacity, the venue’s exclusive suppliers, deposit, house rules (noise, fire, rigging, cleaning) and insurance. House rules usually go in as an annex.
Suppliers. Specific deliverables, loading times, staffing, what happens if equipment fails, whether they can subcontract and penalties for delays.
Performers and speakers. Exact duration, performance time, soundcheck, technical and hospitality rider as an annex, what happens if they are late or do not show, replacement, recording and image.
Freelancers. Role, days and hours, rate, per diems and travel, who provides equipment, liability insurance and how they invoice. Careful: if the relationship looks too much like employment (long-term fixed hours, exclusivity, no autonomy), there may be employment law consequences. Get advice.
Spain and Mexico: what changes
The structure is the same; the framework is not. This is general orientation, not legal analysis:
| Topic | Spain | Mexico |
|---|---|---|
| Contract framework | Civil Code and commercial law | Federal or state Civil Code, and Commercial Code |
| Data protection | GDPR and Spain’s data protection act | Federal law on personal data held by private parties, plus a privacy notice |
| Invoice taxes | VAT (21% standard rate) and, in some cases, income tax withholding | VAT (16% standard rate), CFDI e-invoice and, in some cases, withholdings |
| Tax ID | NIF | RFC |
| Currency | Euro | Pesos or US dollars: if in dollars, set the applicable exchange rate |
| Private clients (weddings, celebrations) | Consumer protection rules | Consumer protection rules |
| Jurisdiction | Courts of a named city, or arbitration | Courts of a named state, or arbitration |
If the event happens in one country and the client is in another, state the governing law and jurisdiction explicitly. And have a professional in each country check anything touching tax and data.
How we do it with Murphy OS
In Contracts we start from templates built for the industry: event management, quote acceptance, supplier, venue hire, room block, performer, speaker, freelancer, co-production, sponsorship, NDA, image rights and data processing. You switch on the clauses that apply (cancellation by either party, force majeure, outdoor events, deposit, liability insurance, music rights, tech rider) and pick Spain or Mexico when you create it; the wording adapts, and it is also available in English.
Then the workflow: send the draft to the client by email, WhatsApp or link; they complete their details and comment; you attach the quote, floor plan or rider as annexes; you lock the version, the client signs with a code sent to their email and you countersign. You both receive the PDF with contract, annexes and a certificate with the document fingerprint. It is still a template: have it reviewed by your adviser before signing.
Common mistakes
- A client contract written without checking supplier cancellation terms.
- “Includes everything needed for the event” as the scope.
- Rain treated as force majeure at an outdoor event.
- Payments due “before the event”, with no date.
- Handling guest data with no processing agreement.
- Using the same template in Spain and Mexico without adapting it.
Before you send it for signature
- Scope with what is included and what is not.
- Price or reference to the attached quote, with taxes clear.
- Payment schedule with dates.
- Cancellation for each party, consistent with your suppliers’.
- Specific force majeure, and plan B if outdoors.
- Liability insurance for each party, with certificate.
- Image, music and creative rights settled.
- Processing agreement if you handle guest data.
- NDA with anyone who sees sensitive information.
- Governing law and jurisdiction for the right country.
- Annexes attached and reviewed.
- Reviewed by your lawyer or adviser.
Frequently asked questions
What should an event management contract include?
Parties, what is and is not included, price and payment schedule, changes, cancellation by either party, force majeure, liability and insurance, image rights, data protection, confidentiality, governing law and the annexes (quote, floor plan, rider).
Is rain force majeure for an outdoor event?
Usually not, because it is foreseeable. That is why outdoor events should have an agreed plan B with a decision deadline, clear criteria and who pays for the marquee or the change of space.
Do I need a data processing agreement with my client?
If you handle their guests' data on their behalf (registration, rooming, check-in), it is standard to sign one. It should cover which data, for what purpose, for how long and what happens to it at the end.
Can I use the same contract in Spain and Mexico?
The structure is similar, but governing law, data protection, invoice taxes and jurisdiction change. Adapt it to each country and have it reviewed by a local professional.
Does a contract template replace a lawyer?
No. A template gives you structure and reminds you of the clauses that matter, but every event is different and the law changes. Have it reviewed by your lawyer or adviser before signing.