Blackout Dates Done Right: Collecting Umpire Availability Without the Chaos

There’s a specific flavor of dread every commissioner knows. You’ve just sent out the weekend assignments, you’re finally sitting down to dinner, and your phone buzzes: “Hey — I’m at my niece’s wedding Saturday, I told you back in March.”

And the thing is, he probably did tell you. It’s in a text thread somewhere between a rainout question and a photo of his new shin guards. You just didn’t have it in front of you when you clicked assign.

That’s the whole problem in one sentence. Umpire availability isn’t hard to collect — it’s hard to keep somewhere you’ll actually look at the moment you’re making a decision. Let’s fix that with an actual system instead of a better memory.

Why availability goes stale

Availability has three enemies, and they’re all boring:

1. It lives in the wrong place. Texts, a Facebook group, a hallway conversation after a game. None of those are where you build the schedule.
2. It’s a one-time snapshot. Somebody tells you their June in March, then life changes and nobody updates you.
3. You check it too late. You assign first and find out about the conflict when the angry text arrives — which is the most expensive possible time to learn it.

If your bigger headache is that everything lives in one giant thread, we went deep on that in why the umpire group text works until it really doesn’t. This piece is narrower: just the availability half of the problem, done right.

The four-part system

You don’t need software to run this. You need four habits. Software just makes them automatic, and I’ll get to that. Here’s the whole system.

1. Collect blackout dates before the season starts

Send one clear ask before you assign a single game. Not “let me know if you have conflicts” — that’s an invitation to say nothing. Ask a specific question with a deadline:

“Reply by Friday the 14th with any dates this season you absolutely cannot work. Weddings, vacations, work trips, kid’s graduation — whatever it is. If I don’t hear from you, I’ll assume you’re open.”

A few things make this work:

• Give a date range and a deadline. “The season runs April 6 to July 20. I need your blackouts by March 30.”
• Ask for hard conflicts only. You’re not collecting preferences here — “I’d rather not do Tuesdays” is a different conversation. You want the dates that will make someone a no-show.
• Make it easy to reply. One channel, one format. “Text me the dates” beats a form nobody fills out, if that’s what your crew will actually use.

Collect it once, up front, and you’ve eliminated most of the season’s surprises in a single afternoon.

2. Give umps a standing way to update mid-season

Here’s where most leagues fall down. You get everyone’s blackouts in March, feel great about it, and then in June somebody’s daughter schedules a wedding and there’s no obvious place to tell you. So they don’t — until they see the assignment.

You need a standing channel, not a one-time ask. The rule is simple: there is always one place to update availability, and every ump knows what it is. Whether that’s “text me the moment you know” or a shared doc or a slot in the app, the point is that the answer to “how do I tell you I can’t make a date” is never “figure it out.”

Say it out loud at the start of the season and repeat it once mid-season: “If something comes up, here’s exactly how you tell me. The earlier the better — I can always cover a game with three weeks’ notice and rarely with three hours’.“

3. Set the “no blackout on file = assignable” ground rule

This one’s the backbone, and it changes the whole dynamic. State it plainly and stick to it:

If you don’t have a blackout on file for a date, you’re considered available for it.

This does two things. It puts the burden where it belongs — on the ump who knows their own calendar, not on you to chase everyone. And it gives you a clean, fair answer when someone bails last-minute on a date they never flagged. You’re not being a hardnose; you set the rule in March and everybody agreed to it.

The catch is you have to honor your side. If someone did file a blackout and you assign them anyway, the rule dies instantly and everyone goes back to defensive texting. Which brings us to the last piece.

4. Check availability at assignment time — not after

The whole system exists to serve this one moment. When you sit down to assign a game, the question isn’t “who’s good for the plate here” — it’s “who’s good for the plate here and isn’t blacked out.” Those have to be the same lookup, or the blackout list is just decoration.

If you’re on a spreadsheet, that means the blackouts live next to the schedule, not in a separate document you keep meaning to cross-reference. If you’re on paper, it means the list is physically in front of you. However you do it, the availability check happens before the assignment is final, so the conflict never becomes an assignment in the first place.

Do this consistently and the angry Saturday-night text mostly disappears. Not because your umps got more reliable — because you stopped assigning them to games they already told you they couldn’t work.

Where software quietly earns its keep

Everything above works on a spreadsheet. It just leans hard on you being disciplined every single week, and July has a way of eroding discipline. This is exactly the seam where a tool built for umpire availability tracking pays for itself.

In UmpCrew, the four habits stop being habits and become the default:

• Umps set their own blackout dates in the app, on their own time. That’s your standing mid-season channel, built in — when a wedding pops up in June, the ump adds the date and you don’t have to remember a text.
• The “no blackout on file = assignable” rule becomes literal. The auto-suggest only offers you umps who are actually open for that date, and it ranks them by fewest games worked so you’re being fair while you’re being available-aware. You’re not cross-referencing anything.
• The check happens at assignment time by design. A blacked-out ump doesn’t surface as an option for that game. The conflict can’t become an assignment.

That last point is the whole ballgame. It moves the availability check from after the angry text to before the mistake — which is the entire difference between a system that works and one that just makes you feel organized.

Availability sits right alongside the other two things that quietly wreck schedules: unfair game counts and last-minute holes. If those are on your list too, the 5 mistakes commissioners make assigning umpires covers all three together.

The short version

• Collect blackouts before the season with a specific ask and a deadline.
• Keep one standing channel for mid-season updates, and make sure everyone knows it.
• Set the ground rule: no blackout on file means you’re assignable — and honor your half by never assigning over a filed conflict.
• Check at assignment time, so a conflict never becomes an assignment.

Do those four things — on paper, on a spreadsheet, or in an app — and you’ll trade a season of surprise weddings for a season of quiet Saturdays. That’s a good trade.

If you’d rather your umps just keep their own blackout dates current so you never have to chase them, start a free 14-day trial — no credit card, and we’ll help you import your schedule.