Rainouts and Reschedules: A Commissioner's Survival Guide

There’s a specific kind of dread that comes with checking the radar at 4:30 on a game night. You’ve got eight fields lit up, thirty-some umpires already assigned, a couple hundred parents loading kids into minivans — and a green-and-yellow blob sliding right toward your complex.

Rain is going to happen. What separates a smooth season from a miserable one isn’t whether you get weather. It’s whether you’ve got a plan for it. And here’s the thing most commissioners miss: a rainout is actually two scheduling problems wearing one raincoat.

Problem one is tonight — getting the “we’re canceled” word out to everyone before they’re standing in a puddle. Problem two shows up next week, when you have to squeeze the make-up game back onto the calendar and find umpires who aren’t already booked. Both problems are fixable. Let’s take them in order.

Part 1: A rainout policy people can actually follow

Half the chaos of a rainout isn’t the weather — it’s the confusion. Nobody knows who’s deciding, when they’ll hear, or where to look. A good policy answers three questions before the season starts, so you’re not inventing rules in the rain.

Who makes the call

Pick one person per site. Not a committee, not “whoever’s around.” One name. Usually that’s you, a field director, or the home-team coordinator at each complex. The moment you have two people who both might call it, you get the classic mess where one cancels, the other doesn’t, and half your umps show up anyway.

If you run multiple fields, delegate by site but give everyone the same criteria: standing water at the plate or bases, lightning within the count-to-30 rule, or a field the grounds crew says is unplayable. Write it down. “Unplayable is the umpire’s call once we’re on site; cancellation before game time is the commissioner’s call” is a perfectly good line to publish.

By when

Set a decision deadline and honor it. A common one is 90 minutes before first pitch for a whole-night call, with the understanding that on-site umpires can still pull the plug at game time if the field turns. The deadline matters because your umps and families are making drive decisions. An ump who lives 40 minutes out needs to know before he gets in the truck.

If the weather’s genuinely a coin flip at your deadline, it’s fair to say “we’re a go as of now, next update by 5:15.” What you can’t do is go silent. Silence makes everyone assume the worst and the best at the same time, which is how you end up with three umps at an empty field.

On what channel

Pick the one place that is the source of truth, and say it out loud to everyone: “If the game status changes, you’ll hear it by text. Not Facebook, not the group chat, not the website — text.” Then actually use that channel every single time, even on the nights it’s obvious. Consistency is what makes people trust it. The first time you cancel somewhere else, the whole system leaks.

A quick word on the league group text here, because it’s the default tool for a lot of leagues: it works fine for a small crew and falls apart fast when the roster grows. We got into exactly why in our post on the umpire group text — the short version is that “reply-all” is not a notification system.

Part 2: Getting word to your crews — tonight, fast

Coaches and parents are one audience. Your umpires are the one that costs you money and goodwill if you miss them. An ump who drives 30 minutes for a game that was called an hour ago is an ump who thinks twice about working for you next year. And good umps are hard enough to keep as it is — we’ve written a whole guide on recruiting and keeping them.

So your rainout notification needs to hit three marks:

• Instant. Not “when I get to my laptop.” The whole point is beating the drive.
• Certain. You need to know it actually reached the people assigned to those specific games, not the whole 40-person roster who now all wonder if their Tuesday is off too.
• Specific. “Field 3 and Field 4 canceled, Field 1 and 2 still on” — because a storm rarely takes down every field evenly.

This is the piece that separates a scramble from a system. If you’re assigning crews in software, the tool already knows exactly which umpires are on tonight’s canceled games — so a cancellation can fire an SMS to precisely those people in one action, instead of you thumb-typing individual texts while the radar gets worse. That’s the difference between “everybody who was working Field 3 got the text at 4:40” and “I think I got everyone, let me count again.”

Whatever you use, make the cancel text read like a human wrote it: “RAINOUT — Field 3, tonight’s 6:00 (Hawks/Jays) is canceled. You do NOT need to come. Make-up date TBD, I’ll re-confirm your assignment. Thanks — Erik.” Clear, closes the loop, no ambiguity about whether they should still head over.

Part 3: The reschedule — where double-booking is born

Now the sneaky part. Cancelling tonight feels like the emergency, but the reschedule is where quiet mistakes creep in and bite you two weeks later.

Here’s the trap: a rained-out Tuesday game gets slotted into next Thursday’s open field. Fine. But your umpires already have a Thursday schedule. If you re-crew that make-up from memory or from a stale spreadsheet, you will eventually assign someone to two games at once — or assign your one veteran plate ump to a make-up on a night he’d already blacked out.

A few habits keep you out of trouble:

1. Treat a make-up like a brand-new game, not a moved one

Don’t just drag the old row to a new date and assume the same crew rolls over. Their availability on the new date is a different question entirely. Re-check it as if you were staffing it fresh.

2. Check availability against the whole night, not just the game

Before you pencil an ump into Thursday’s make-up, look at what else Thursday holds for them. This is exactly where a scheduling tool earns its keep — assign someone who’s already working that slot and it should flag the conflict instead of letting you create a double-booking you’ll discover when one game goes uncovered.

3. Honor blackout dates on the new date too

An ump who’s available Tuesdays isn’t automatically available Thursdays. If your umps can mark blackout dates and claim open games themselves, rescheduling gets a lot less lonely — you post the make-up as an open game and let available umps grab it, instead of you playing matchmaker over text.

4. Watch the fairness math

Make-ups quietly wreck your rotation. The ump who’s easy to reach and always says yes ends up eating every reschedule, works ten more games than everyone else, and burns out by August. Keep an eye on your per-ump game counts through the reschedule crunch — that’s the whole idea behind rotating crews fairly, and a fairness view that ranks by fewest games worked makes the fair choice the easy choice.

5. Re-confirm, don’t assume

Once the make-up is crewed, send the assignment again with the new details — date, time, field, teams. The original assignment text is now wrong; don’t leave your umps guessing which one is live. A fresh “you’re confirmed for the Hawks/Jays make-up, Thursday 6:00, Field 2” closes the loop the same way the cancellation did.

A dry-run before your next storm

You don’t need fancy tools to survive a rainout. You need one decider per site, a hard deadline, one channel everyone trusts, and the discipline to re-crew make-ups like new games instead of copied ones. Do that on notecards and you’ll beat a lot of leagues running expensive software badly.

But the notification and the no-double-booking pieces are exactly the parts that get harder as your league grows — and exactly the parts that are miserable to do by hand at 4:30 on a game night. That’s the boring stuff we built UmpCrew to carry: one action cancels the right crews, and the schedule won’t let you book an ump who’s already working.

If rainout season is already testing your patience, start a free 14-day trial — no card — or just email us and we’ll set your league up for you.