How to Write Terms & Conditions for a Paid Experience

Nobody books your experience because of the terms and conditions — your fans show up for you, not the fine print. But the day something goes sideways — a guest demands a refund the week of, a storm closes the venue, someone gets hurt on a hike, a buyer disputes the charge two months later — the terms are the only thing standing between "we sort this out calmly" and "this becomes an argument you might lose." Event terms and conditions are the boring paragraph nobody reads and everybody relies on. Write them before you sell a single ticket, not after your first dispute teaches you which clause you were missing.

The good news: you do not need a forty-page contract. A paid experience — a workshop, a supper, a weekend away, a multi-day trip — needs a focused set of clauses that each answer one question: when X happens, who is responsible and what happens next? This guide walks those clauses one at a time, hands you adaptable sample language for each, and shows you where the terms have to live so they actually hold up. Treat every sample here as a starting point you rewrite in your own words and for your own event.

Terms and conditions vs. a waiver: you likely need both

People conflate these two documents, and the conflation gets hosts in trouble. They do different jobs.

Your terms and conditions are the commercial agreement: what the guest is buying, what it costs, when they can get their money back, how they're expected to behave, and what happens if the event changes. It governs the transaction.

A liability waiver is narrower and heavier. It's the document where a participant acknowledges the risks of a specific activity and agrees not to hold you responsible for certain harms. Waivers carry their own rules — some jurisdictions demand very specific wording, a separate signature, and conspicuous formatting, and some won't enforce them at all for gross negligence. If your experience has any physical or "assumption of risk" component — fitness, hiking, water, cooking with knives and heat, alcohol — you want a proper standalone waiver in addition to your terms. Our liability-waiver template and walkthrough covers that document specifically; this guide is about the commercial terms that sit around it.

So the mental model is: terms and conditions govern the money and the relationship; the waiver governs the risk. One references the other, but they're not interchangeable.

The twelve clauses your event terms and conditions should cover

Below are the clauses that earn their place in almost any paid experience. For each, you get what it's for, what usually goes wrong without it, and a short sample you can adapt. Rewrite them in your own voice — copied-and-pasted legalese that doesn't match your event is exactly the kind of thing that reads as boilerplate and gets picked apart.

1. What the ticket includes — and excludes

The single most common dispute isn't about money. It's about expectations. A guest thought lunch was included; it wasn't. They assumed transport from the airport; you assumed they'd arrange it. Spell out precisely what the price buys and, just as importantly, what it doesn't.

Your ticket includes: [e.g., all instruction and materials, three catered meals per day, and shared lodging for two nights]. It does not include: [e.g., travel to and from the venue, airport transfers, alcohol, travel insurance, or personal expenses]. Anything not explicitly listed as included is the responsibility of the guest.

That last sentence does a lot of quiet work. It flips the default from "if it wasn't excluded, it must be included" to the reverse.

2. Payment, deposits, and balance due

Say what's owed, when, and what a deposit means. Be explicit about whether a deposit is a non-refundable commitment or simply a first installment, because guests will assume whichever interpretation favors them.

A deposit of [amount or %] is due at booking to reserve your place. The remaining balance is due by [date or "X days before the event"]. The deposit is [non-refundable / refundable until DATE] and secures your spot; places are not held without it. If the balance is not received by the due date, we may release your place to someone on the waitlist.

Deposit amounts in samples like this are illustrative — pick a figure that reflects your real up-front costs, and see how much it actually costs to host an event if you're setting that number for the first time.

3. Cancellations, refunds, and credits

This is the clause guests read most carefully, so it's the one to write most clearly. State what happens when a guest cancels at different points before the event — usually a tiered structure where refunds shrink as the date approaches — and whether you offer cash back, a credit, or nothing past a cut-off.

Cancellations more than [X] days before the event: full refund less the deposit. Between [X] and [Y] days: 50% refund or full credit toward a future event. Fewer than [Y] days: no refund, as costs are already committed. All cancellations must be made in writing to [email].

Don't try to compress your whole cancellation strategy into the terms — the terms state the policy; the host's playbook for handling cancellations and no-shows covers how you actually work each scenario, backfill from a waitlist, and word the awkward message. The policy in your terms and the playbook you run should match.

4. Transfers and name changes

Guests who can't come will ask whether they can send a friend instead. Decide in advance. Allowing transfers is a cheap way to avoid a refund fight and keep the seat filled — but set conditions so it doesn't become a headache.

If you can't attend, you may transfer your place to another person up to [X] days before the event at no charge, provided the new guest agrees to these terms and completes any required forms. Transfers requested after that date may not be possible due to catering and rooming commitments.

5. Code of conduct and removal rights

For most events this never gets used. For the one where it does, you'll be very glad it's there. Reserve the right to remove a guest whose behavior endangers or seriously disrupts others — and make clear that removal for cause doesn't come with a refund.

We want every guest to feel safe and welcome. Behavior that harasses, endangers, or materially disrupts other guests, staff, or the venue may result in removal from the event without a refund. We reserve the right to make that decision at our reasonable discretion.

Keep the language firm but not lurid. The point is to have a clear basis to act, not to intimidate the ninety-nine guests who'd never need it.

6. Assumption of risk and limits on liability

Here the terms shake hands with your waiver. In the terms, acknowledge that participation carries inherent risks and set a reasonable ceiling on what you're liable for — commonly capped at the amount the guest paid. Enforceability of liability caps varies a lot by jurisdiction, which is exactly why this clause wants a lawyer's eyes.

Participation in [activity] carries inherent risks, which you accept by attending. To the fullest extent permitted by law, our total liability arising from your participation is limited to the amount you paid for your ticket. This does not exclude any liability that cannot be excluded by law.

That final sentence matters. Trying to disclaim liability you legally can't disclaim can get a whole clause thrown out — so the "except where the law says otherwise" carve-out protects the rest of it. Anything involving physical risk still needs the dedicated liability waiver.

7. Photo, video, and media release

If you plan to photograph the event and use those images to promote the next one, get permission in the terms. Give guests a clear way to opt out, because a guest who didn't want their face on your sales page and finds it there anyway is a genuine problem.

We may take photos and video during the event for promotional use. By attending, you consent to appearing in that content. If you'd prefer not to be featured, tell us in writing before the event and we'll do our best to accommodate you.

8. Changes to schedule, venue, or lineup

Real events change. A guest instructor cancels; the sunrise session moves because of weather; the venue swaps one room for another. Reserve the right to make reasonable changes without it counting as a breach — while promising to tell people.

We reserve the right to make reasonable changes to the schedule, activities, staff, or venue where necessary. If a significant change materially affects the experience you booked, we'll notify you as soon as possible and, where appropriate, offer a suitable alternative.

The word "material" is doing the balancing here: small swaps are your call, big ones trigger a conversation.

9. Force majeure

The clause everyone learned the hard way. Force majeure covers events genuinely outside your control — natural disasters, government restrictions, the venue burning down — and defines what happens when one makes the event impossible. Be honest with yourself here: a credit-based force majeure clause protects your cash flow, but guests remember how they were treated when things went wrong.

If circumstances beyond our reasonable control (including natural disasters, extreme weather, government restrictions, or venue closure) prevent the event from going ahead, we will offer a credit toward a rescheduled or future event where possible. Cash refunds in these circumstances are subject to costs already committed to third parties, which may not be recoverable.

10. Insurance and personal responsibility

Set expectations about who insures what. Make clear that the guest is responsible for their own travel insurance, health cover, and belongings — and note that you carry your own event coverage without implying it protects them personally.

You are responsible for arranging your own travel and health insurance and for the safety of your personal belongings. We are not responsible for loss or damage to personal items. We maintain our own event insurance, which does not extend to your personal cover.

If you haven't sorted your own policy yet, start with whether you need event insurance at all — the terms shouldn't reference coverage you don't have.

11. Governing law and how disputes are handled

Close by naming the law that governs the agreement and how disputes get resolved. This matters more than it looks: without it, a guest in another state or country can create real ambiguity about where and under whose rules a dispute plays out.

These terms are governed by the laws of [your state/country]. Any dispute will first be addressed through good-faith discussion, and if unresolved, handled in the courts of [jurisdiction].

Whether you can bind an out-of-state guest to your home jurisdiction is exactly the kind of question a local lawyer answers — but stating your intended governing law is far better than leaving it blank.

A copy-and-adapt terms skeleton

Here's the shape those clauses take as a single document. Fill the brackets, delete what doesn't apply to your event, rewrite the tone to sound like you, and — one more time — have a lawyer review it before it's binding.

[Event name] — Terms & Conditions Last updated: [date]

1. Your booking. Booking a place means you accept these terms on behalf of yourself and anyone in your party. 2. What's included. [Inclusions]. Not included: [exclusions]. 3. Payment. Deposit of [amount] at booking; balance by [date]. [Deposit terms]. 4. Cancellations & refunds. [Tiered policy]. All cancellations in writing to [email]. 5. Transfers. [Transfer policy and deadline]. 6. Conduct. [Removal-for-cause language]. 7. Risk & liability. [Assumption of risk; liability cap; "except where law prohibits"]. 8. Media. [Photo/video consent and opt-out]. 9. Changes. [Right to make reasonable changes; notice]. 10. Force majeure. [Credit/refund treatment for events outside your control]. 11. Insurance. [Guest responsible for own cover]. 12. Governing law. Governed by the laws of [jurisdiction].

By completing your booking, you confirm you've read and agree to these terms.

That last line is not decoration — it's the point where agreement is captured, which is what the next section is about.

Where your terms have to live to be enforceable

A perfect set of terms sitting in a document nobody saw is close to worthless. For terms to bind a guest, you generally need to show they had a genuine opportunity to read them and clearly agreed. Practically, that means:

• A visible checkbox at checkout — an unticked "I have read and agree to the Terms & Conditions" box that the guest must actively check, with the words "Terms & Conditions" linking to the full text. Pre-ticked boxes are weak-to-void in many places.
• The full terms one click away, not buried three menus deep. If a guest can't find them, a court may decide they never agreed to them.
• A copy in the confirmation email, or a permanent link to them, so there's a record of what applied at the time of booking.
• A dated version. If you change your terms, keep the old versions — a guest is bound by the terms that were live when they booked, not the ones you wrote later.

If you're selling through a hosting platform like Meuse, the checkout and confirmation flow is where that agreement gets captured cleanly, with the checkbox and the record handled as part of the booking rather than something you bolt on. However you sell, the principle is the same: agreement has to be active, visible, and recorded.

Mistakes that quietly make terms unenforceable

Even solid clauses fail when the surrounding practice is sloppy. The usual culprits:

• Burying agreement. No checkbox, or a pre-ticked one, or terms linked in tiny grey text. If you can't demonstrate the guest agreed, the document may not bind them.
• Overreaching. Trying to disclaim liability you legally can't (for your own gross negligence, say) can poison a clause — and sometimes a whole section. Reasonable, law-aware limits hold up; sweeping ones invite a judge to strike them.
• Contradicting yourself. Terms that promise "full refunds anytime" in one line and "no refunds within 30 days" in another give the guest the more generous reading. Your terms, your checkout copy, your emails, and your cancellation playbook all have to say the same thing.
• Changing terms retroactively. You can update terms going forward; you can't quietly rewrite the deal for people who already booked.
• Copying someone else's terms whole. Another host's document references their venue, their jurisdiction, their event's risks — not yours. Borrow the structure, write your own substance.
• Never involving a lawyer for the binding version. For a low-stakes free meetup, fine. For a paid multi-day experience with real money and real risk, a single review is cheap relative to one dispute.

If your event has an entity behind it, terms also interact with how you've set up liability generally — worth understanding whether you need an LLC or similar structure before you decide how much personal exposure your terms are really shielding.

When a guest disputes the charge: how your terms earn their keep

The moment your terms prove their value is rarely a lawsuit. It's a chargeback — a guest who cancelled late, didn't get the refund they wanted, and simply called their bank to reverse the payment. When that happens, the card networks run a structured process, and you (the merchant) get one chance to respond with evidence. What counts as evidence? Overwhelmingly: proof of what the guest agreed to, and proof you delivered it.

This is where an agreed set of terms turns an argument into a paper trail. A strong chargeback response for a "service not as described" or "cancellation" dispute usually leans on a few things working together:

• The agreed terms themselves, showing the cancellation and refund policy the guest accepted at checkout.
• A record of that agreement — the timestamped checkbox tick, the confirmation email containing or linking the terms, the booking record.
• Evidence you honored the policy — the refund you did issue under the tiered structure, or correspondence showing you offered the credit your terms promised.
• Proof of delivery or availability — that the event ran as described, or that the guest chose not to attend an event that was ready for them.

Notice how every clause in this guide quietly feeds that response. The inclusions clause rebuts "not as described." The cancellation clause rebuts "I was owed a refund." The record of agreement rebuts "I never agreed to that." Terms don't guarantee you win a dispute — banks have their own leanings, and some decisions feel arbitrary — but the merchant who can show a clear, agreed, consistently-applied policy wins far more often than the one relying on a screenshot and a story.

Two practical habits make this real. Keep your policies identical everywhere a guest encounters them, because a dispute reviewer who spots a contradiction sides with the buyer. And keep records automatically rather than hoping to reconstruct them later — the timestamp on the agreement is often the most persuasive single item in the file. Selling through a platform that captures agreement and delivery as part of the booking, like Meuse, means that evidence exists without you assembling it by hand at the worst possible moment.

Start simple, then tighten

You don't have to draft all of this in one sitting to sell your first ticket. Start with the four clauses that cause the most disputes — inclusions, payment and deposits, cancellations, and conduct — get those clear and agreed at checkout, and add the rest as your events grow in size and stakes. A short, honest, clearly-agreed set of terms beats a long, borrowed one nobody signed. Get the bones right, keep your policy consistent everywhere a guest reads it, and have a professional review the version that has to hold. For the broader picture of running the event those terms protect, our guide on how to host an event ties the pieces together.

Frequently asked questions

Are terms and conditions accepted online actually legally binding?

Generally yes — if the guest had a real chance to read them and took a clear, active step to agree, like ticking an unticked box next to a working link. These "clickwrap" agreements are widely upheld. What weakens them is passive agreement: pre-ticked boxes, hidden links, or terms a guest could plausibly say they never saw. Enforceability still varies by jurisdiction, so treat "binding" as "much stronger when agreement is active and recorded."

Do I need both terms and conditions and a waiver, or is one enough?

For most paid experiences with any physical component, both. The terms govern the commercial deal — money, changes, conduct. The waiver handles assumption of risk for the specific activity and often has its own formatting and signature rules. One doesn't substitute for the other; a refund clause won't protect you from an injury claim, and a waiver won't tell a guest when their balance is due.

Can I change my terms after tickets are already sold?

For future bookings, yes — update them anytime and keep the old versions dated. For guests who already booked, no: they're bound by the terms that were live when they paid, and you're bound to those too. This is why keeping dated copies matters. If you genuinely need existing guests to accept a change, you have to ask them and get fresh agreement, not edit the document under them.

How long should terms for a small event be?

As long as it takes to cover the clauses that apply to your event, and no longer. A one-evening workshop might need six tight clauses; a week-long international trip needs all twelve and then some. Length isn't the goal — clarity is. A guest should be able to skim your terms and know what they bought, when they can get money back, and how to behave.

What happens if I don't have any terms and a dispute comes up?

You fall back on default consumer law, your payment processor's rules, and whatever you said in emails and on your sales page — usually a weaker position than a clear agreement would have given you. Payment disputes and chargebacks, in particular, tend to favor the buyer when the seller can't point to agreed terms. No terms doesn't mean no rules; it means the rules are set by others, often less in your favor.

Should a lawyer write my terms, or can I adapt a template myself?

Adapting a well-structured template yourself is a reasonable way to draft — it's how many hosts start. The step worth paying for is a review of the version that becomes binding, especially the liability, force majeure, and governing-law clauses where local rules bite hardest. Draft to save time; get a professional to check before the document has to protect you for real.