We Read 159,079 Signed Event Contracts. Here Are 14 Things Yours Is Probably Missing.

If you run an event business, your contract is the most overlooked tool in your operation. You wrote it once. Maybe you copied it from another operator. Maybe a friend who's a lawyer looked at it back in 2019. Then you put it in your booking flow and forgot about it.

None of this is legal advice. All of it is what we saw when we looked at the data.

We pulled and analyzed 159,079 signed event contracts from event businesses on Check Cherry's platform, spanning photo booth operators, DJs, mobile bartenders, photographers, videographers, venues, game truck operators, and casino party providers. We classified the clauses, counted what's there and what's not, and read deep samples across every service type.

The findings are stark.

None of this is because event business owners are careless. It's because the contract is the thing that runs in the background, and the friction of updating it never wins against the rest of the job. These gaps matter most if you run your business on modern booking software like Check Cherry, which is designed to make it easy for both operators and clients to do business: booking, paying, adjusting add-ons, all through a single client portal. The booking experience has long outpaced the contract language behind it. So below are fourteen specific gaps we found, why each one matters, and what to add.

The 14 things missing from most event contracts

1. Configuration error grace

Found in virtually none.

This is the most common honest mistake in event work. You set up a package wrong. You priced a 5-hour booking at the rate of a 3-hour booking. You forgot an add-on. The client signed. You discovered the error a week before the event. Now what?

Modern event businesses run on software. Pricing logic, automated invoicing, online booking, package configuration, add-on selection. These tools let you handle more bookings with less friction, and they're the reason the industry has scaled the way it has. They also create more places for things to go wrong. A typo in a package setup. A pricing rule that didn't update. A new add-on accidentally bundled into the wrong tier. A platform bug. The tradeoff for the speed and ease is that errors occasionally get baked into bookings that are technically already signed.

Across the contracts we read, the answer is always the same: nothing in the contract addresses this. You either eat the loss, have an awkward renegotiation, or cancel and refund. None of those are good outcomes.

What to add: A configuration error grace clause that gives you a defined window to resolve honest setup mistakes. Something like:

The full refund is the safety net for the client. The good-faith effort is the safety net for you. Time-bounded so it can't be abused. Note the passive "is identified." Errors might be caught by you, by your client, or by the software itself; the clause covers all three.

2. Modification authorization

Found in almost none.

Almost nobody pre-authorizes routine changes without requiring a re-signature. Everyone else is stuck. When a client wants to add a 360 booth a month before the wedding, the modern booking experience says "click here to add it." The contract says "we need to redo the whole agreement."

Most operators just ignore the contract problem and add the upgrade anyway. Technically, they're operating outside the original signed terms.

What to add: A modification authorization clause that pre-authorizes the kinds of changes that happen routinely. Limit it to changes that don't move the event date, don't change the primary venue, don't shift the total by more than ten percent, and don't materially alter the type of service. Within those limits, agreement through any reasonable means (including a client portal click) is authorized under the original signature. Anything bigger gets a written amendment.

This is what allows the modern booking experience to be legally sound.

3. Online booking and client portal authorization

Found in about 1 in 20.

If you give your clients the ability to update their own bookings through online booking or a client portal, you're probably letting them add an add-on, change a backdrop, or swap a package tier. Whether you enable this varies. Some operators love the self-service flow. Others prefer to handle every change themselves. Many turn it on for some bookings and off for others. This is exactly the kind of friction Check Cherry is designed to remove for operators and the clients booking with them, and Check Cherry lets you toggle portal access on a per-booking basis. But the vast majority of contracts don't say a word about whether portal-driven changes are authorized under the original agreement.

What to add: Conditional language that covers portal-driven changes when they're allowed, without requiring re-signature. Something like:

The "where" framing matters. If portal access is disabled for a booking, the clause is inert. If you turn it on later, it activates automatically. Pair this with the modification authorization clause above and you've covered the most common point of confusion in modern event booking.

4. Mutual indemnification

Found in fewer than 1 in 5.

Indemnification is the clause that says "if something bad happens, this side covers the other side." In the contracts we read, About four in ten have any indemnification at all, but only a fraction make it mutual. The rest only protect the operator. The client gets nothing in return.

This is the first thing a corporate client's legal team strikes. Schools, government clients, and most companies with a real procurement function won't sign a one-sided indemnification. You either lose the deal, or spend two weeks negotiating.

What to add: A mutual indemnification clause that covers each party for claims arising from their own negligence, with exceptions for gross negligence and willful misconduct. Workable phrasing might read:

Mutual indemnification doesn't weaken your protection. It strengthens the contract's enforceability and opens the door to higher-value B2B work.

5. Image use opt-in, not perpetual royalty-free

Almost no contract has opt-in. A small fraction have perpetual royalty-free.

The standard pattern is: operator owns all images and can use them for marketing forever. Some contracts make this explicit with "perpetual, royalty-free, worldwide license." Most just assume it.

For retail wedding clients, this usually doesn't come up. For corporate events, school events, private clients, and high-profile individuals, it's a problem. Sometimes a confidentiality problem. Sometimes a brand problem. Always a redline.

What to add: Default to a limited license. You can use images for portfolio purposes like your website and tagged social media posts. Anything broader (paid ads, promotional materials, third-party publications) needs the client's explicit opt-in. Clients who want to opt in can. Clients who don't, won't have a reason to redline.

Most retail clients will opt in. Corporate clients will appreciate the choice. Either way, you've removed a friction point.

6. Reasonable refund windows

More than half of contracts make everything non-refundable.

The most common pattern we saw: "all deposits are non-refundable, and the balance is due X days before the event." Some go further: "all payments are non-refundable from the moment of signing."

This sounds like protection but it's actually a trap. A client who paid 50% three months out and then has a genuine emergency two weeks before the event isn't going to fight you in court for the refund. They're going to leave a one-star review and tell everyone they know. Your contract gave you the legal right but the wrong commercial outcome.

What to add: Tiered refund windows tied to how far out the cancellation occurs. The best operators we read use language like: full refund (minus deposit) up to 90 days out, 50% refund 14 to 90 days out, no refund within 14 days. The deposit stays non-refundable but the rest scales. This is what reasonable clients expect, and it dramatically reduces dispute risk.

One quick note on naming. What you call the initial payment matters more than most operators realize. "Deposit" implies refundable in many jurisdictions. "Retainer" implies a non-refundable engagement fee. "Booking fee" is the soft middle ground. If your contract calls the payment a "deposit" but you want non-refundable behavior, the legal weight of that clause is weaker than if you'd called it a retainer or a booking fee. Pick one term, use it consistently throughout the contract and your invoices, and make sure the surrounding language matches. Check Cherry lets you set this label across your contracts and proposals in one place under Payment Settings.

7. Mutual confidentiality

Found in almost none.

Of the contracts that mention confidentiality at all, almost all of them protect the operator's pricing and quote information. Almost none protect the client's information.

For corporate clients, this is a red flag. Their event details, guest list, and internal communications belong to them. A contract that says "you cannot share our quote" but is silent on whether you can share their event details is going to get redlined.

What to add: Mutual confidentiality. Each party agrees to keep the other party's confidential information confidential, with the standard exceptions (publicly available, legally required disclosure, etc.). Costs you nothing, removes a redline, signals you've thought about this.

8. Setup access window and idle time

Setup access window: fewer than 1 in 10. Idle time fees: about 1 in 10.

The classic event nightmare: you show up at the venue at the contracted setup time. The venue isn't open. Or the venue is open but the previous event hasn't finished tearing down. Or the loading dock is blocked. You wait 45 minutes. Now you're behind, and the event still starts on time. You did extra work, you absorbed extra stress, and the contract is silent.

The smartest operators we read have idle time language that says something like:

What to add: Two paired clauses. First, define when the venue must give you access. Typically 1 to 2 hours before the contracted start time, or whatever your equipment requires. Second, an idle time fee that activates if access is delayed. A reasonable rate is somewhere between $50 and $150 per hour depending on your service. You've turned a chronic frustration into something predictable.

9. Late start by client and overtime mechanics

Found in fewer than 1 in 10.

The wedding is supposed to start at 6 PM. The bride is running late. You've been ready since 4. Ceremony finally starts at 7:15. Cocktail hour pushes back. Reception pushes back. The end time the client signed for is suddenly 90 minutes from now and they want you to "stay a little longer."

The vast majority don't address this. The implicit answer is usually "operator stays until contracted end time, then leaves," but no one wants to be the bad guy.

What to add: Two pieces. First, the event ends at the contracted end time regardless of when it started, unless you agree in writing to extend. Second, overtime mechanics that kick in if the client wants you to stay: a per-hour rate (most operators charge between $100 and $300 per hour depending on service), payable that night or before equipment leaves the venue. Operators with this language report way fewer awkward end-of-event conversations.

10. Backup operator and equipment plan

Found in about 1 in 10.

Your primary photographer gets in a car accident at 5 AM the morning of the wedding. Or the main DJ booth has a hardware failure during sound check. Or you have COVID. What happens?

In almost all contracts, nothing about this is written down. The operator scrambles, the client panics, and either the day is saved or it's not. Either way, the legal position is murky.

What to add: A clause that authorizes you to provide a comparable substitute (qualified staff, equivalent or better equipment) if your primary plan can't perform. Set the bar: "comparable skill and experience" for staff, "equivalent or better quality" for equipment. This protects you when you do the right thing under pressure, and gives the client confidence that you have a plan.

11. No-show by client

Found in almost none.

You drove out, you set up, you waited. The client never showed. Maybe they forgot. Maybe they didn't realize they had to be there. Maybe they ghosted. Almost no contracts say anything about this.

What to add: Define what counts as a client no-show (typically failure to be present at the contracted start time for more than 30 to 60 minutes without prior communication), and state the consequence. Most operators in the rare contracts that address it say: full contracted fee due, no refund. You did the work. You're owed.

12. Staff safety and harassment

Explicit staff safety language is almost nonexistent. Any harassment provision at all: fewer than 1 in 5.

Your team works at events where guests are drinking, often celebrating hard, sometimes for hours. Photo booth attendants, bartenders, photographers, videographers, and DJs all spend long stretches in close contact with people whose behavior may slip. Sometimes a guest gets handsy. Sometimes a guest gets aggressive. Sometimes a guest threatens.

In the contracts we read, fewer than 1 in 5 use the word "harass" anywhere. Roughly 1 in 8 mention threats to staff specifically. A tiny handful address sexual or physical misconduct. Almost none have explicit "staff safety" language or say you still get paid in full if you have to leave for safety reasons.

This is a real operational risk and a real staffing risk. If you employ attendants, bartenders, photographers, or anyone who works your events, having no contractual framework for guest misconduct means three things: you have no clean basis to leave an unsafe event, you eat the cost when you do leave, and you can't credibly tell prospective staff that you take their safety seriously.

What to add: A staff safety and conduct clause that does three things:

The framing matters. This isn't a "we might leave at any time for any reason" clause. It's a "we treat our team's safety as a constraint, the client is on notice, and we're not absorbing the cost of misconduct that isn't our fault" clause.

13. Pre-event payment, with Net-30 for verified business clients

Net-30 and corporate AP language: almost none.

The default we saw is "balance due 7 to 30 days before event" or "balance due day-of." That's the right default for retail clients. If a wedding client stiffs you on $800, the realistic recovery option is small claims court, which most operators rationally won't pursue.

But schools, government clients, and established corporations operate on different cycles. They pay reliably, but their accounts payable runs Net-15 or Net-30. They can't cut you a check the day of the event. If your contract has no language for invoicing terms, you're either turning down corporate work or you're rebuilding your contract for each B2B booking.

What to add: Default the contract to pre-event payment. Then add an optional addendum or section that's enabled only for verified business clients (W-9 on file, certificate of insurance, established business with payment history). For those clients, Net-30 invoicing is available with specific terms (late fee schedule, dispute window). The default protects you against retail risk. The addendum unlocks higher-value B2B revenue.

14. Force majeure with named triggers

Found in about half of contracts.

Every event business that survived the COVID era learned the hard way what "beyond our control" actually means. The contracts that held up were the ones that said so on paper, in specific terms, before anyone needed to argue about it.

Before 2020, most contracts either had no force majeure clause at all or buried a one-line "acts of God" mention in the cancellation section. That language didn't hold up well when real disputes hit. And even today, a meaningful share of signed contracts (especially in photo booth, photography, and other smaller event verticals) still lack named-trigger force majeure language. The half that do address it often stop at the abstract phrase.

That abstract phrase is the problem. A clause that says only "acts of God" is meaningfully weaker than a clause that names pandemic, government shutdown, severe weather, civil unrest, and infrastructure failure. When triggers aren't specifically listed, courts and clients argue ambiguity, and the operator usually loses the argument or eats the cost to avoid one.

What to add: A modern force majeure clause that does four things:

• Names the triggers. Don't leave it abstract. Specifically name pandemic or public health emergency (including governmental orders), natural disasters (severe weather, fires, floods, earthquakes), war, terrorism, civil unrest, infrastructure failure (utilities, transportation, telecommunications), and government action.
• Requires prompt notice. The party affected must notify the other party promptly. Without notice, the clause shouldn't protect them.
• Imposes a mutual mitigation duty. Both parties make reasonable efforts to limit the impact, including rescheduling and substitution where possible.
• Defines a termination threshold. If the disruption lasts more than thirty days, either party can terminate without penalty.
• Handles deposits cleanly. Non-refundable amounts stay non-refundable, but you'll make a reasonable effort to apply them toward a rescheduled event within twelve months. That balances business protection with client-friendly handling.

Open your current contract, find your force majeure clause, and check whether it actually names the triggers. If it stops at "acts of God," it isn't doing the work.

6 more gaps worth knowing about

Beyond the fourteen above, these clauses are widely missing and worth checking:

• Insurance held by provider. Found in fewer than 1 in 5. Most contracts demand client insurance but don't mention the operator's.
• Governing law and jurisdiction. Found in roughly a third. Most don't specify which state's laws apply in a dispute.
• Music licensing acknowledgment (ASCAP/BMI/SESAC). Found in about 1 in 5. DJ-specific. Real legal exposure if you're playing copyrighted music at commercial events without acknowledging who carries the license.
• Power and WiFi failure at venue. Found in fewer than 1 in 10. Photo booths and modern DJ setups depend on both. The vast majority don't address what happens when the venue's infrastructure fails.
• Final delivery timeline for photos and videos. Found in about 1 in 7. Photographers and videographers verbally promise "2 weeks" or "30 days." Most don't enforce a deadline.
• Capped fees with disclosure. Found in fewer than 1 in 5. "Additional fees may apply" without a ceiling is one of the most common corporate redlines.

6 clauses to strike from your contract right now

Some clauses are common in these contracts but actively work against you. Either they won't survive corporate review, they signal that you're hostile to your clients, or they're legally weak. Strike them.

• Non-disparagement clauses (a small fraction have them). Corporate clients won't sign these (free speech concerns), and they signal to retail clients that you expect them to want to complain. Net negative.
• Perpetual royalty-free worldwide image licenses (a small fraction). Use the opt-in pattern from section 5 instead.
• Pricing or quote confidentiality clauses (a small fraction). Corporate procurement departments are required to disclose costs internally. This will get struck.
• Chargeback dispute waivers (about 1 in 8). Banks won't enforce these regardless of what your contract says. They make you look like you have something to hide.
• COVID-19 waivers (about 1 in 5). Outdated. Replace with a clean modern force majeure clause that covers pandemics generally.
• "Sole discretion" cancellation language (about 1 in 7). Operators reserving the right to cancel "at any time, for any reason, in their sole discretion" looks predatory. Replace with objective criteria.

Smart language worth copying

A few rare clauses we found that are worth borrowing:

• Equipment uptime SLA (nearly a third of contracts). Pattern: state an operational uptime percentage (commonly 80%) and a defined remedy for downtime beyond that (typically a pro-rated refund). Sets professional expectations and limits liability without requiring you to absorb every micro-malfunction.
• Security guard scaling (venue-specific). Pattern: tie security requirements to guest count or event risk profile, with defined thresholds (for example, one licensed guard above a moderate guest count, additional guards above a higher threshold). Removes ad-hoc negotiation per booking.
• Payment-leverage from videographers. Pattern: state explicitly which deliverables are gated on full payment. Edited content, preview files, raw footage, and project files all on a no-pay-no-delivery basis. Translates well to other deliverable-based services like photography, design work, and custom video reels.
• Mutual indemnity from casino party operators. Already covered in section 4. Worth re-reading.
• Equipment substitution authorization (a small share have it). Pattern: clarify upfront that the package describes the features and capabilities the client is buying, and that the specific equipment serving those features may vary based on availability. Protects you when a primary unit is in repair, supports incremental upgrades between bookings, and pre-empts the "but I saw the white booth on your website" conversation.

What to do this week

If you've read this far, you're probably looking at your own contract and wondering how many of the fourteen gaps apply. Most operators find more gaps than they expected.

Three steps:

The fairness shifts (mutual indemnification, image opt-in, reasonable refunds, mutual confidentiality) and the operational reality clauses (setup access, late start, backup plan, no-show) can roll out over the following weeks.

If you run your business on Check Cherry, your contract lives right alongside your bookings. You can build the clauses in this article into your terms, and they apply automatically to every booking. Configuration error grace, modification authorization, and online booking authorization fit naturally into the modern booking experience your clients already expect.

Check Cherry is booking and client management software built for DJs, photographers, and event professionals. A contract that actually fits how you work is one piece of how we help operators run modern businesses without the friction.