A Wet-Weather Policy Parents Actually Accept

Every coaching program director knows the feeling. Rain is forecast, you've already called the session off, and within twenty minutes the inbox fills with variations of the same three questions. The programs that stay calm have a wet-weather policy written before week one — and they make the call at 6:30am, not after parents are already in the car: Will we get a refund? Can we make it up? Why didn't you tell us sooner?

The problem isn't the rain. It's that your wet-weather policy for sport was buried in the registration terms no one read, written in language that left room for interpretation, and never mentioned again until the dispute arrived.

This guide walks you through writing a policy that actually holds, communicating it before the season starts, and running the cancellation process in a way that closes the loop rather than opening a thread.

Wet weather policy sport: Why most wet-weather policies fail before a drop of rain falls

The typical policy lives as paragraph fourteen of a PDF attached to the confirmation email. It says something like: "In the event of inclement weather, sessions may be cancelled at the discretion of management. Makeups or credits may be offered."

May. At the discretion. May be offered.

Every word there is a future argument. Parents — reasonably — read "may be offered" as "will be offered." They read "at the discretion of management" as "if the weather looks bad enough to me personally." When reality doesn't match their reading, they feel cheated, and they're not entirely wrong to.

A policy that leaves room for negotiation is not really a policy. It's an opening position.

The other common failure: the policy is written for a different program than the one you're actually running. Outdoor winter football sessions carry different risk profiles than indoor netball training. A camp that runs rain or shine (because you have undercover space) needs different language than one where the field is the only option. Generic templates don't survive contact with your actual setup.

What a solid wet-weather policy for sport actually covers

Before you write a word, get clear on six things:

1. Who decides — one named role, not "management" or "the committee."
2. When they decide — a specific decision time (e.g., by 7 am for morning sessions, two hours before for afternoon ones).
3. What the trigger is — field condition, official weather service warning, lightning detection, or a combination. Spell it out.
4. What parents receive — makeup session, credit, partial credit, or nothing. Be precise about which applies when.
5. How parents are told — channel, format, and the window between the call and the session.
6. What parents are not entitled to — politely and clearly.

These six questions are the skeleton. The rest is explanation and tone.

A note on refunds: your wet-weather policy and your general refund policy are related but not the same document. Your sports venue refund policy should handle the broader question of what happens when someone withdraws — your wet-weather policy handles the narrower question of what happens when you cancel. Keep them consistent; don't make them do each other's job.

How to write your wet-weather policy: section by section

Decision authority

Name the role. "The head coach" or "the program director" is clear. "Management" is not. If you have multiple sites or coaches, name who holds the call at each location — or state that the decision flows from one central role even for satellite venues.

Decision timeline

Pick a time and stick to it. For early-morning sessions, most programs find a 7 am call works: it gives families time to change plans, and it gives you time to notify before the school run starts. For afternoon or weekend sessions, two hours is generally workable. Whatever you choose, write it down, and then actually hit it — trust in the policy erodes the first time a call comes ninety minutes late.

The trigger criteria

Vague language like "unplayable conditions" invites argument. Concrete language doesn't. Some programs use:

• A named weather service (the Bureau of Meteorology is the standard reference in Australia) with a specified rainfall threshold
• A lightning warning within a certain radius from the venue (twenty kilometres is common for outdoor sport)
• Field inspection by the decision authority, with a note that if the field is assessed unfit, play is off regardless of forecast

You can combine these. What matters is that the criteria exist in writing before the season, not after a contentious call.

The makeup/credit/refund position

This is the section parents actually want to read. Be honest with yourself first: what can you actually deliver?

If you can reliably schedule a makeup session, offer it — but define the window (within the same term, for example) and what happens if a family can't attend the makeup. If you can't reliably schedule makeups because your facilities are full, say so, and offer a credit instead. If your program is priced on the basis that a small number of rain cancellations are absorbed into the per-session rate, explain that — briefly, plainly, without being defensive.

The one thing to avoid is offering a makeup that you then can't find time for. A credit that expires is better than a promise that festers.

This is also where it's worth revisiting how you've priced your coaching programs — programs priced to absorb one or two cancellations per term should say so explicitly. It's not hiding anything; it's giving parents the full picture.

What parents are not entitled to

Write this section with the same directness you'd use in person. Something like: "Same-day cancellation due to weather does not entitle participants to a full-session refund. Credits are issued at $X per cancelled session and are valid within the current term."

Clear. Fair. Final.

How to communicate your wet-weather policy so parents retain it

Writing the policy is step one. Getting it into people's heads before the season is step two — and it's where most programs still fall short.

At registration: Include a plain-language summary (three to five sentences) on the registration form itself, not buried in attached terms. Ask parents to confirm they've read it with a checkbox. This isn't legal cover — it's a nudge to actually read it.

In the welcome email: Repeat the key points in the welcome message you send after registration. A single paragraph with the decision time, the notification channel, and the makeup/credit position is enough. Keep it friendly — you're setting expectations, not issuing a warning.

In a pre-season parent communication: If you send a "season starts this week" message, drop the wet-weather summary in there too. Parents are in receipt mode right before a program starts. That's a good moment.

On your venue website: Put it somewhere findable — an FAQ page, a policies section, even a pinned post. When a parent searches their inbox and can't find the email, they'll look on your site next. Give them something to find. Sweepa's branded program pages give you a public-facing home for this kind of information without needing a separate website to maintain.

The goal isn't for every parent to memorise the policy. It's for them to be unable to say, honestly, that they were never told.

The wet-weather call: who makes it, when, and how

On the day, the process should take ten minutes, not two hours.

1. The decision authority checks conditions against the criteria at the agreed time.
2. They make the call.
3. They trigger the notification — ideally via a single action that reaches all registered families at once (email, SMS, or both).
4. They log the cancellation for record-keeping (this matters if credits or makeups are owed).

The failure mode here is a manual process: coach checks the weather, texts the assistant, assistant posts in a WhatsApp group, two families who aren't in the group miss it, one shows up anyway. A platform that lets you send a single email or SMS to everyone registered in a session removes that failure mode entirely. It's not glamorous, but it's the difference between a tidy cancellation and a half-hour of damage control.

Good parent communications tooling makes this almost invisible — you write the message once, send it to the right group, and it's done.

What to do when a parent still pushes back

Even a well-written, well-communicated policy doesn't get universal acceptance. Someone will push back. Here's how to handle it without letting it become a policy renegotiation.

Acknowledge first. "I understand it's frustrating to miss a session — I feel it too" is a real sentence that costs nothing and defuses a lot.

Point to the policy. Not as a weapon — as a reference. "As per the policy we shared at registration, same-day weather cancellations attract a credit rather than a refund. Here's how to use it." Calm, factual, done.

Don't make exceptions unless you'd make them for everyone. One custom refund is a precedent. If you make it, be prepared to make it every time, or to have an awkward conversation when you don't.

Know when to escalate and when to close it. If a parent is genuinely distressed (a hard week, a financial difficulty), a quiet conversation is worth having. If the argument is purely about principle and the policy is clear, close the loop politely and move on. Your program registration setup should give you a paper trail — confirmation emails, timestamps, checkbox acknowledgements — that lets you do this calmly.

A quick pre-season checklist

Before your next term or camp kicks off, run through this:

• [ ] Policy covers all six elements: decision authority, timeline, trigger criteria, makeup/credit/refund position, notification channel, exclusions
• [ ] Policy language is specific — no "may," no "at discretion of" without definition
• [ ] Summary included on the registration form, with acknowledgement checkbox
• [ ] Full policy linked from the welcome email
• [ ] Policy findable on your venue website or program page
• [ ] Notification process is one action, not a chain of manual messages
• [ ] Makeup/credit system is recorded somewhere you can retrieve it

If your current setup fails more than two of these, the problem isn't the rain — it's the infrastructure around the policy. Getting parent comms and registration running in one place means you're not stitching together five tools every time a storm rolls in.

Write it once. Communicate it clearly. Run a clean process on the day. The parents who push back will always exist — but the ones who feel informed and respected stay enrolled next term.