How to write a bounce house rain and cancellation policy

Rain is the one thing you can’t control and can’t refund your way out of. The operators who get review-bombed over weather aren’t the ones who called off a windy setup — they’re the ones whose customer had no idea the policy existed until the argument in the driveway. A clear policy, agreed to before the booking, turns a bad-weather day from a fight into a form you both already signed.

This guide covers what a good rain and cancellation policy contains, sample language you can adapt, and — just as important — how to apply it in a way that protects your reviews as well as your calendar. It’s general guidance for operators, not legal advice; have a local attorney review your final terms.

Why the policy matters more than the refund

A weather policy does three jobs at once:

It sets expectations before money changes hands. The customer knows what happens if it rains, so a cancellation is a known outcome, not a betrayal.
It protects your deposit and your reserved date. You held a Saturday for this booking and turned away others. The policy defines what you keep for that.
It gives you cover to make the safe call. When you stop a setup for wind, you’re enforcing a term both sides agreed to — not improvising.

The refund amount matters far less than whether the customer saw it coming. Buried policy text is what generates the one-star review; a clear, up-front policy the customer signed is what prevents it.

What every rain and cancellation policy should cover

1. Who can call off for weather, and when. State plainly that you reserve the right to cancel or refuse setup for unsafe conditions — high wind, storms, saturated ground — for safety reasons, and that this decision is yours as the operator. Give a cutoff (for example, a decision made by a certain hour on the morning of the event).

2. What the customer gets when weather cancels. Spell out the options. Common approaches:

Reschedule / rain check: the deposit or full payment applies to a future date within a set window. This is the operator-friendly default — you keep the revenue, the customer keeps their party.
Partial refund: you refund the rental minus a non-refundable deposit that covers your held date and prep.
Full refund minus deposit: clean and simple, if you’d rather not manage rain checks. Pick one primary path (most operators lead with reschedule) and state it clearly.

3. Customer-initiated cancellations — a separate tier. Weather is one thing; “we changed our mind” is another. Define:

A non-refundable deposit that holds the date.
A cancellation window (e.g., cancel more than 7 days out for a fuller refund; less than 48 hours, deposit is forfeited).
What happens to same-day cancellations.

4. Your wind and safety threshold. Tie the policy to the safety reality: you will not operate above your units’ safe wind limit or in conditions the manufacturer prohibits. This connects the paperwork to the anchoring and wind guidance and makes clear the call is about safety, not convenience.

5. How reschedules work. The window to use a rain check, whether it’s subject to availability, and whether it carries to the next season. Vague rain checks become disputes; dated ones don’t.

Sample language to adapt

Use this as a starting point and have it reviewed locally — every state treats deposits and refunds a little differently:

Weather & safety. For the safety of guests, [Operator] reserves the right to cancel or decline setup due to unsafe conditions, including sustained winds or gusts near the manufacturer’s limit for our units, thunderstorms, or saturated ground. This decision rests with [Operator] and will be made by [time] on the day of the event when possible.

If we cancel for weather. You may reschedule to any available date within [90 days] at no additional charge, and your deposit and payment transfer to that date. If you prefer not to reschedule, [state your refund terms].

If you cancel. A deposit of [amount/%] holds your date and is non-refundable. Cancellations more than [7 days] before the event receive [refund terms]; within [48 hours], the balance beyond the deposit is [refunded/forfeited].

Rain checks are valid for [90 days], subject to availability.

Fill the brackets with your real numbers, keep the tone plain, and don’t hide it — the policy should be visible in the quote and inside the contract the customer signs.

Put the policy where the customer will actually see it

A policy no one reads is a policy that doesn’t exist. The fix is to make it a first-class part of the contract, not fine print on a website footer. The strongest setup:

The weather and cancellation terms sit inside the contract the customer e-signs, alongside the waiver — so agreeing to book is agreeing to the policy.
The customer gets a copy automatically with their confirmation.
Nothing is buried, and there’s a signed timestamp proving they saw it.

This is a core part of how BounceDay handles bookings: the waiver and weather policy are built into the e-sign contract, read and signed before the deposit is paid — so the terms are never a surprise on the day.

Applying the policy without earning a bad review

The policy protects you legally; how you use it protects your reputation. Two principles:

Lead with the reschedule, not the refund fight. “Saturday’s looking unsafe — let’s move you to next weekend, no charge” keeps the customer’s party alive and keeps you paid. It’s the outcome almost everyone actually wants.
Show your work. When you make a weather call, show the customer why — the actual forecast, the wind numbers, your threshold. “Here’s the forecast, here’s our limit, here’s the safe move” lands completely differently than “sorry, our policy says no refund.”

That “show the forecast, then decide” posture is deliberately how BounceDay’s weather feature works: on Crew and up, a flag surfaces the raw NWS forecast, the time it was pulled, and your own threshold — then you send a one-tap reschedule offer if you decide to. BounceDay flags the weather; you make the call. It never auto-cancels and never auto-reschedules, because the decision — and the customer relationship — is yours.

FAQ

Should I refund for rain? That’s your policy to set, but most operators lead with a reschedule or rain check rather than a cash refund — you keep the revenue and the customer keeps their party. Whatever you choose, put it in writing before the booking.

Can I keep the deposit if the customer cancels? A non-refundable deposit is standard because you held the date and turned away other bookings. Define the exact terms in your contract, and check your state’s rules on deposits — see contracts, deposits, and waivers explained.

Who decides to cancel for weather — me or the customer? You, as the operator, for safety reasons. Your policy should state clearly that you reserve the right to cancel or decline setup in unsafe conditions, and give a decision cutoff time.

How do I avoid bad reviews over weather? Make the policy visible and signed before the event, lead with a reschedule instead of a refund fight, and show the customer the actual forecast and your safety threshold when you make the call. Surprise is what generates the one-star review, not the rain.

Where should the policy live? Inside the contract the customer signs, next to the waiver — not buried on a website. A signed, timestamped agreement is what makes the policy real.

Never argue about the policy in a driveway again

BounceDay puts your waiver and weather policy inside the contract the customer e-signs, and surfaces the forecast so you can offer a one-tap reschedule on your terms.

Join the waitlist