A refund policy for a product assumes one clear question: did the item come back, or did the download never happen. An events or ticketing refund policy has to answer four separate questions instead, because a ticket can fail an attendee in four different ways: the event gets canceled outright, the event gets postponed to a date that hasn't been set yet, the attendee simply changes their mind while the event is still happening as planned, or the attendee buys a ticket and never shows up. Each of those has a different fair answer, and writing one paragraph that tries to cover all four is how an events business ends up with a policy that reads reasonably and still generates a dispute the moment a real cancellation happens.
There's a second complication that a coaching business or a SaaS company never runs into: if you sell tickets through a platform like Eventbrite, Ticketmaster, or a similar hosted checkout, a meaningful chunk of your refund policy isn't actually yours to set. The platform has its own rules for canceled and postponed events, and those rules apply to your attendees whether or not your published page says something different. Writing a refund policy without knowing where that line sits means publishing promises you may not be able to keep, or missing protections your attendees already have regardless of what you wrote.
The four refund triggers, and why one paragraph can't cover all of them
The cleanest way to structure an events refund policy is around the trigger, not around a single blanket rule. A refund request always starts with one of four situations, and the fair (and, for a canceled event, often legally required) answer is different for each one.
An event that's canceled outright is the least ambiguous case: the thing the attendee paid for didn't happen, and the standard expectation, often backed by the ticketing platform's own terms, is a full refund of the ticket price. A postponement is different and gets its own rule below, since "the event didn't happen yet" isn't the same as "the event isn't happening." An attendee who wants their money back while the event is still on as scheduled is a straightforward application of whatever cancellation window you've set, the same logic a subscription or a digital product uses. A no-show is different again, and worth its own section, because nothing about the event failed the attendee; the ticket did what it was supposed to do.
How much of this a ticketing platform already decided for you
If you sell tickets through Eventbrite, the platform's own policies sit on top of whatever you publish, and they cover more ground than most organizers expect before actually reading the fine print. Eventbrite's Canceled Event Policy requires organizers to refund every attendee if an event is canceled or simply doesn't take place, and organizers are expected to respond to refund requests within five business days; if an organizer doesn't handle that, Eventbrite can issue the refunds itself and charge the cost back to the organizer's account. Postponements run on a separate clock: Eventbrite gives an organizer 90 days after announcing a postponement to lock in a new date, during which refunds are largely at the organizer's discretion, but if no new date is set within that window, Eventbrite requires the organizer to honor refund requests for a further 45 days, or until a new date is announced, whichever comes first. Underneath both of those, Eventbrite's own service and payment-processing fees are non-refundable regardless of what happens to the ticket, with a narrow exception where an organizer can request a fee credit, manually, after a full event cancellation.
What your policy can set vs. what Eventbrite already enforces
| What you can set | Eventbrite enforces | |
|---|---|---|
| Event canceled outright | Nothing, really | Full refund within 5 business days |
| Event postponed, new date set within 90 days | Whether to offer refunds at all | Deferred to organizer discretion |
| Event postponed, no new date after 90 days | Nothing | Mandatory refund for 45 more days |
| Attendee cancels, event unaffected | Refund window and fee coverage | Enforces your configured window |
| Eventbrite's own service and payment fees | Nothing | Non-refundable except by discretion |
The practical takeaway isn't that your own refund policy is pointless. It's that the policy you publish should be written to sit consistently on top of the platform's baseline instead of contradicting it. A page that promises "no refunds under any circumstances" is misleading if you sell through a platform that requires refunds on cancellation regardless of what you wrote, and an attendee who reads your page, gets denied, then finds the platform's own help center saying otherwise is exactly the kind of gap that turns into a chargeback or a platform complaint instead of a quiet resolution. If you use a different platform (Ticketmaster, a venue's own box office, a niche ticketing tool), check that platform's organizer terms for the same three things: what it requires on cancellation, how it handles postponement, and whether its fees survive a refund, before you publish language that assumes you have full discretion.
No-shows aren't cancellations, and treating them the same is a mistake
A no-show is the case events businesses most often forget to address explicitly, and it's also the one where a vague policy causes the most friction. An attendee who buys a ticket, doesn't request a refund in advance, and simply doesn't come has not experienced any failure on the organizer's part. The ticket was valid, the event happened as described, and the seat, table, or entry slot was held for someone who chose not to use it. That's a fundamentally different situation from a canceled or postponed event, but a policy that only talks about "refunds" in general terms, without saying what happens after the event has already taken place, leaves the door open for a no-show attendee to argue their case looks the same as a legitimate cancellation request.
- Refunds are handled on a case-by-case basis.
- No mention of what happens if the ticket holder simply doesn't attend.
- Tickets are non-refundable and non-transferable once the event has taken place, attended or not.
- A no-show isn't a cancellation. Refund requests must be submitted before the event's start time.
The specific version closes the gap a vague policy leaves open: it states plainly that the clock that matters is the event's start time, not whether the attendee eventually shows up, and it says so before a dispute happens rather than as an improvised answer to a support ticket. This is also where a refund policy and a chargeback tend to intersect for events specifically. A no-show attendee who disputes the charge with their card issuer weeks later, rather than requesting a refund before the event, is filing a chargeback on a ticket that was fully delivered, and a clear, dated no-show clause is the documentation that helps you contest that dispute rather than simply eat the loss.
Postponement needs its own rule, separate from cancellation and separate from a no-show
Postponement is the trigger organizers most often leave out entirely, usually because it feels like a variant of cancellation rather than its own category. It isn't. A canceled event is not happening at all, full stop, which is why a full refund is the standard, often platform-required, answer. A postponed event is still going to happen, just not on the original date, and the fair question changes from "do I get my money back" to "does my existing ticket carry over, and if the new date doesn't work for me, what's my window to ask for a refund instead." Writing one clause that only says "refunds are available if the event is canceled or postponed" and stops there leaves exactly that second question unanswered, which is the same gap Eventbrite's own postponement rules are built to fill on your behalf if your policy doesn't.
A workable postponement clause states three things directly: that an existing ticket is automatically valid for the new date once one is announced, how long an attendee has to request a refund instead if the new date doesn't work for them, and what happens if no new date gets announced within a defined window. That third piece matters more than it looks; an indefinitely postponed event with no stated fallback is functionally the same as a cancellation from the attendee's perspective, and a policy that doesn't say so is asking attendees to wait indefinitely for an answer nobody's committed to giving them.
Building this into your policy
An events or ticketing refund policy that holds up in practice separates its four triggers instead of blending them into one general statement, states its postponement rule with a concrete fallback window rather than leaving it open-ended, and is written to be consistent with whatever your ticketing platform already requires rather than contradicting it. If you're also drafting the entry and conduct terms that sit alongside this policy, the terms and conditions for an events or ticketing website is the companion document: that one covers who gets let in and who's liable if something goes wrong at the venue, while this one covers the money.
Our Refund Policy Generator builds an events-specific version of this: it asks how you handle event cancellation, postponement, and no-shows separately, rather than assuming one clause covers all three, so the trigger-specific language above ends up in your published policy by default instead of by memory.
The information in this article is for informational purposes only and should not be construed as legal advice on any matter, and does not create a lawyer-client relationship.
