Two days before your event, a guest emails: something came up, they can't make it, and they'd like their money back. You've already paid the venue deposit, confirmed the caterer's headcount, and ordered materials for the number of people who bought in. You want to be kind. You also can't un-spend money that's already gone. Without a policy to point to, you're negotiating from scratch, in the moment, with someone who's disappointed — and whatever you decide quietly sets a precedent for the next person who asks. This is the fight a written policy prevents before it starts.
A refund and cancellation policy is the set of rules that decides, in advance, who gets money back and how much — so the answer to "can I get a refund?" is a lookup, not an argument. The whole discipline fits in one line: decide the rules before you sell, publish them where guests can't miss them, and make people agree to them at checkout before their card is charged. Do that, and almost every refund question answers itself.
One thing before the template, and it matters: this is a plain-English guide and a starting point, not legal advice. Consumer-protection law varies by country and state, and in some places it can override whatever your policy says — certain jurisdictions require cooling-off periods or refund rights you can't sign away. Nothing here cites a specific statute, because the rules that bind you depend entirely on where you and your guests are. Have a local lawyer review your policy, and check the consumer rules that apply where you host, before you put it in front of paying guests. Treat everything below as a draft for that conversation, not a finished document.
What does a refund policy actually need to cover?
A good policy answers every predictable "what if" before it happens, in language a guest can read in under a minute. Vagueness is what creates disputes, so the goal is to leave no obvious question unanswered.
At minimum, cover these:
- The refund schedule. How much a guest gets back, tied to how far before the event they cancel. This is the core, and it's almost always tiered rather than all-or-nothing.
- The deposit. Whether any part of the payment is non-refundable, and how it interacts with the schedule above.
- What happens when you cancel. Guests forgive a lot if they know, up front, exactly what you owe them when you're the one who has to call it off — a minimum-headcount cut-off, a force-majeure clause, and their choice of a refund or a credit.
- Transfers and name changes. Whether a guest can send someone else in their place instead of cancelling.
- Credits. When you offer a credit instead of cash, and how long it lasts.
- No-shows. What happens to the money when someone simply doesn't turn up.
- How to request a refund, and how long it takes. The email to write to, what to include, and the processing time so nobody wonders where their money went.
A policy that covers those seven areas handles the overwhelming majority of situations you'll ever face. It pairs naturally with your other host paperwork — most importantly a signed liability waiver, which does a separate legal job but lives in the same "agree before you attend" moment at checkout.
How should refund windows work?
Refund windows should be tiered: a full refund if a guest cancels early, a partial refund in the middle, and none once the seat is effectively spent. The logic is simple and easy to explain to a guest — the closer to the event they cancel, the less of their money you can still recover, because your own costs lock in as the date approaches.
Think of it as three bands. Early (say, a month or more out): you have time to resell the seat, so a full refund minus the deposit costs you little. Middle (a couple of weeks out): the seat is harder to fill and some per-head costs are starting to commit, so you keep a share. Late (the final week): catering counts are final, materials are bought, and the seat is spent whether the guest shows or not — so no refund, though you can still offer a transfer or a credit as a goodwill gesture.
Here's an illustrative schedule you can adapt. The exact days and percentages should track your costs and how easily you can resell a seat — a supper club with a fixed food count locks in sooner than a large outdoor meetup.
| Time before the event | Refund | Notes |
|---|---|---|
| 30+ days | Full refund, minus the deposit | Plenty of time to resell the seat; only your booking costs are exposed |
| 14–29 days | 50% of the ticket, minus the deposit | Harder to resell; some per-head costs are starting to lock in |
| 7–13 days | 25%, or a full credit toward a future event | Catering and materials counts are usually final by now |
| Under 7 days / no-show | No refund; transfer or credit at your discretion | The seat is effectively spent whether they show up or not |
The percentages above are illustrative and internally consistent — full, then half, then a quarter, then nothing, with the deposit always kept on top. Tie each threshold to a real moment in your budget: the day your venue balance is due, the day your caterer needs a final number. If you're not sure where your costs fall, the math in is hosting an experience profitable? and how much to charge for an experience will help you set thresholds that protect your margin.
Should the deposit be non-refundable?
Yes — a non-refundable deposit is the single most useful clause in the whole policy, and it belongs at the top. The deposit is the slice of the payment that never comes back, no matter when a guest cancels. It protects you from the moment someone books, because that's the moment you start committing money and turning other people away from the seat.
Set it at roughly what it costs you to hold a spot: the per-head amount you commit early, plus a fair contribution to your fixed costs. Then make its status unmistakable in writing — "the deposit of [amount] is non-refundable in all cases" — so it never comes as a surprise. Every tier of your refund schedule is then calculated on the amount paid minus this deposit, which is why the two clauses have to be written together.
The deposit mechanics — how large to make it, when to collect the balance, and how to word it so guests accept it as normal — are a whole topic on their own. The companion guide, how to collect deposits for an event, covers the deposit side in full; this policy is where you state how that deposit behaves when someone cancels.
What happens when YOU cancel?
When you're the one who cancels, the default should be a full refund of everything the guest paid — deposit included — or their choice of a full credit toward a future event. You broke the deal, not them, so the non-refundable deposit stops applying. Say this plainly in the policy; it's the clause that earns you the most goodwill, because it tells guests their money is safe with you even in the worst case.
Two mechanisms sit inside this clause. The first is a minimum headcount with a cut-off date: state that the event needs at least a set number of guests, and name the date by which you'll decide whether it runs. If you don't hit the number by the cut-off, you cancel and refund — and because the cut-off comes before your own non-refundable costs commit, you're not out of pocket for a room that was never going to fill. The second is a force majeure clause: the standard "events outside our reasonable control" language covering severe weather, illness outbreaks, venue closure, government restrictions, and the like. If one of those forces your hand, the same promise applies — a full refund or a credit.
One honest limit to state in the clause: you refund what guests paid you, but you're not responsible for their separate costs — the flights, the hotel, the time off. Encourage guests to consider their own travel insurance for anything they book around your event. Your exposure to a forced cancellation is also exactly what host-side coverage exists for; the event insurance overview and the deeper event liability insurance guide cover event-cancellation coverage, which can reimburse your sunk costs when weather or illness shuts the day down and you've just refunded everyone.
Can guests transfer their spot or get a credit?
Almost always, yes — and building both into the policy from day one turns two potential arguments into routine, one-line answers. A transfer keeps the seat filled and paid; a credit keeps the money and the guest inside your world. Both usually beat a cash refund for everyone involved.
Transfers and name changes. Let a guest send someone else in their place, at no charge, up to a few days before the event. It costs you nothing, the seat stays sold, and you often gain a brand-new person in your audience. Ask for the new guest's name and contact details so your list stays accurate and any required waiver gets re-signed under the right name, and note that the original guest stays on the hook for the booking until you confirm the swap. A full room is a full room, whoever's sitting in the seat — which is the same reason a strong transfer clause quietly helps you keep experiences full.
Credits. When a guest cancels inside a paid tier, or in a genuine emergency, offering a credit toward a future event is often the move that feels most generous while keeping money you may have already spent. Put boundaries on it: a credit is valid for a set window (twelve months is common), applies to an event of equal or lesser value, has no cash value, and can't be swapped back into a refund. Those limits keep an open-ended credit from becoming an open-ended liability on your books. One practical note — a credit isn't a refund, so how it lands come tax time can differ from cash back; the taxes on event income guide is a useful primer, though your accountant is the real authority here.
How do you handle chargebacks?
A chargeback is a guest disputing a charge through their bank instead of asking you for a refund, and the way you handle them is mostly prevention — you build the defense long before one is ever filed. A clear policy the guest agreed to at checkout, a confirmation email that restates the terms, and a friendly, prompt paper trail are exactly the documentation a card processor wants to see when it decides who's right.
A few habits keep disputes rare and winnable:
- Publish the policy at the point of sale and keep a record that the guest agreed to it. Agreement before payment is the strongest single piece of evidence you can have.
- Reply to every message quickly and like a human. Most chargebacks are frustration, not fraud — someone who felt ignored reaching for the only lever they know. A same-day reply defuses most of them.
- Send a confirmation email that names the event, the date, and the refund terms. It's both a courtesy and a timestamped record.
- Keep your notes even for no-shows. A short, factual trail of what was agreed and when is what turns a dispute in your favor.
- When a refund is genuinely owed, pay it before it becomes a dispute. A dispute typically costs you a fee on top of the refunded amount, so paying promptly is cheaper as well as kinder.
You won't win every dispute. But a host who publishes a clear policy, agrees it up front, and documents the whole exchange loses far fewer than one who runs on trust and memory.
Where should the policy live so it's enforceable?
A policy only carries weight if the guest genuinely agreed to it before paying, so it has to appear in three places: at checkout, behind a required checkbox, and again in the confirmation email. Where a policy shows up decides whether it's a shared agreement or a page nobody saw — and a policy a guest meets for the first time in the refund email they didn't want to send is worth almost nothing.
Put it everywhere it counts:
- At checkout, in view before payment. Visible on the same screen where the card details go in, not buried three clicks away.
- Behind a required checkbox. "I have read and agree to the Refund & Cancellation Policy," un-checkable-past. This is the moment agreement is recorded, and it's the moment that matters most in a dispute.
- In the confirmation email. Restate the key terms — deposit, refund windows, how to request a refund — so the guest has them without hunting, and so there's a timestamped copy in their inbox.
The single rule that makes a policy enforceable: publish it before you sell, not after. A policy a guest sees for the first time when they ask for their money back carries almost no weight. One they had to tick a box to agree to before their card was charged is a completely different conversation. Write it first, show it at checkout, repeat it in the confirmation email.
This is far easier when the same system runs your sales page, your checkout, and your emails, so the policy rides along automatically instead of being something you remember to paste in. Fitting it into your overall setup is part of the wider how to host an event workflow — the policy is one line item in a launch, but it's the line item that saves the worst afternoons.
The refund and cancellation policy template (copy, paste, adapt)
Below is a plain-English, jurisdiction-neutral template you can copy and adapt. Fill in the bracketed placeholders, delete anything that doesn't apply to your event, and adjust the days and percentages to match your own costs.
Read this first — same disclaimer, louder, because it's about to matter most: the template below is general information and a starting point, not legal advice. Consumer-protection laws vary by country and state, and some can override parts of this policy — a few jurisdictions mandate cooling-off periods or refund rights you cannot waive. Don't publish this as-is. Adapt it, then have a local lawyer review it against the rules where you and your guests actually are.
REFUND & CANCELLATION POLICY — [EVENT NAME]
Last updated: [DATE]
1. DEPOSIT (NON-REFUNDABLE)
Your booking is confirmed when you pay [the deposit of
[DEPOSIT AMOUNT] / the full ticket price of [TICKET PRICE]]. The
deposit of [DEPOSIT AMOUNT] is non-refundable in all cases, because
it covers costs we commit on your behalf as soon as you book. Every
refund below is calculated on the amount you paid, less this deposit.
2. REFUND SCHEDULE (WHEN YOU CANCEL)
If you cancel your booking, your refund depends on how far before the
event you tell us, in writing:
- [30]+ days before the event: full refund, less the deposit.
- [14]-[29] days before: 50% refund, less the deposit.
- [7]-[13] days before: 25% refund, OR a 100% credit toward a
future [EVENT NAME] event, less the deposit.
- Fewer than [7] days before, or no-show: no refund. A transfer
or credit may be offered at our discretion.
The date that counts is the date your written cancellation reaches us
at [REFUND EMAIL], not the date you decided.
3. TRANSFERS & NAME CHANGES
You may transfer your spot to another person at no charge up to [3]
days before the event. Email [REFUND EMAIL] with the new guest's
name and contact details so we can update our records and send them
any required forms. The original guest remains responsible for the
booking until we confirm the transfer.
4. CREDITS
Where a credit is offered, it is valid for [12] months from the
original event date, applies to any [EVENT NAME] event of equal or
lesser value, and has no cash value. A credit cannot be exchanged
for a refund.
5. NO-SHOWS
If you do not attend and have not cancelled in writing under the
schedule above, no refund or credit is due. In a genuine emergency,
we may offer a credit at our discretion.
6. IF WE CANCEL OR RESCHEDULE
This event requires a minimum of [X] guests, confirmed by [CUT-OFF
DATE]. If we cancel the event for any reason — including not reaching
the minimum, or an event outside our reasonable control (see Force
Majeure) — you may choose EITHER a full refund of everything you
paid, including the deposit, OR a full credit toward a future event.
If we reschedule, your booking moves to the new date; if the new date
does not work for you, you may choose a full refund or a credit
instead.
7. FORCE MAJEURE
"Force majeure" means events outside our reasonable control,
including severe weather, natural disaster, fire, illness outbreaks,
government restrictions, venue closure, or loss of essential
services. If such an event forces us to cancel or reschedule, we will
offer a full refund or a credit as set out above. We are not
responsible for your separate costs, such as travel or accommodation,
so please consider your own insurance for those.
8. HOW TO REQUEST A REFUND OR TRANSFER
Email [REFUND EMAIL] with your name, the name of the event, and your
order or booking number. We aim to reply within [2] business days.
9. PROCESSING TIME
Approved refunds are returned to your original payment method within
[10] business days. Depending on your bank or card provider, it may
take a few additional days to appear on your statement.
10. AGREEMENT
By completing your booking, you confirm that you have read and agree
to this Refund & Cancellation Policy.
That's the whole shape of it — short, readable, and honest about both sides. Keep the language plain, keep the numbers tied to your real costs, and let your lawyer tune the wording for where you host. A policy a guest can actually understand is worth far more than a wall of clauses nobody reads.
Related guides
Round out the paperwork before you sell your first seat:
- How to Collect Deposits for an Event
- Liability Waiver for In-Person Events (+ Template)
- Do You Need Insurance to Host an Event or Experience?
- Event Liability Insurance: What It Covers and Costs
- How to Host an Event: A Step-by-Step Guide for Creators
- How Much to Charge for an Experience
- How to Set a Cut-Off Date and Minimum Headcount
- What Is a Deposit? Definition for Experience Bookings
Frequently asked questions
Do I have to give refunds at all?
It depends entirely on where you host and where your guests are. In many places you're free to set your own refund policy, so long as you publish it clearly and guests agree before they pay. But some jurisdictions mandate refund or cooling-off rights that a policy can't override, and consumer-protection rules vary widely. So the safe answer is: set a fair, published policy, and check the local rules that apply to you. This is general information, not legal advice — a local lawyer can tell you what your minimum obligations actually are.
Can I keep the deposit if someone cancels?
Usually yes, if you made the deposit clearly non-refundable and the guest agreed to that before paying — which is exactly why a non-refundable deposit belongs at the top of the policy and behind the checkout checkbox. The one big exception is when you cancel the event: at that point most policies refund the deposit too, because the guest didn't break the deal, you did. Local consumer rules can also affect what you're allowed to keep, so confirm yours before relying on the clause.
What if I have to cancel the event?
Offer a full refund of everything the guest paid — deposit included — or their choice of a full credit toward a future event, and say so in the policy up front. A minimum-headcount cut-off date lets you make that call before your own costs commit, so you're not refunding out of pocket. A force-majeure clause covers the weather-and-disaster cases. And because a forced cancellation can leave you eating sunk costs even after refunding, event-cancellation insurance is worth pricing in.
What about chargebacks?
Handle them mostly by preventing them. A policy the guest agreed to at checkout, a confirmation email that restates the terms, quick and human replies, and a friendly paper trail are the exact documentation a card processor wants when it decides a dispute. Most chargebacks are frustration rather than fraud, so fast, kind communication heads off the majority. And when a refund is genuinely owed, pay it before it becomes a dispute — a dispute usually costs you a fee on top of the refund.
Where should guests see the policy?
In three places: on the checkout screen before payment, behind a required "I agree" checkbox, and again in the confirmation email. The checkbox is the one that matters most, because it records that the guest agreed before their card was charged — the strongest evidence you can have if a dispute is ever filed. A policy nobody had to agree to is barely a policy at all. Publish it before you sell, not in the refund email nobody wanted to send.
A refund policy isn't the exciting part of hosting, and that's exactly why getting it right up front pays off — you write it once and it does the arguing for you every time after. Decide the tiers, make the deposit non-refundable, promise a clean refund or credit when you're the one who cancels, and show the whole thing at checkout so guests agree before they pay. Do that, and the email that used to ruin your afternoon becomes a thirty-second lookup. If you'd rather not stitch that together by hand, Meuse lets you set your own refund rules and shows them at checkout, so every guest agrees to the terms before their card is charged — and the policy is working for you from the first sale, not from the first dispute.
