Scheduling 38 volunteer umpires with one spreadsheet

Club admin is a constraint problem

For the umpire schedule at HSCM, the problem is simple on paper: three pools (H1, H2, U21), 38 names, and a season full of games that all need two umpires.

In practice it is a constraint puzzle. Some umpires only want youth games. Some can only do home games. Some are also playing that day. Some are unavailable for weeks at a time. Nobody is paid, and you cannot manage them like a regular team.

That mix of constraints matters more than any tool you pick. The tool only needs to do one thing well: make those constraints visible so you can move pieces around without surprises.

Why a spreadsheet still beats an app

There are plenty of apps that promise to automate schedules, send reminders, and collect availability. They are good at communication. They are less good at letting you see the whole problem at once.

A basic spreadsheet has a few advantages for this kind of club work:

• Global view. You can see all games, all umpires, and all pools in one grid.
• Fast editing. Copy, paste, drag, try different solutions, and undo when it breaks.
• Custom rules. You can bake your own logic into the sheet instead of fitting everything into someone else’s model of how a club should work.

The spreadsheet is not smarter than an app. It is just more honest about the mess.

Three pools, not one big list

A first simplifying decision is to stop treating 38 umpires as one group. At HSCM, the schedule is built around three pools:

• H1
• H2
• U21

Each pool has its own games and its own expectations. Some umpires move between pools, some do not. The sheet reflects that. Instead of one giant column of names, there are clear sections or tags for each pool.

This limits the search space when you are assigning a game and makes it easier to see when one pool is overloaded while another still has spare capacity.

I wrote about this earlier in Why my posts now start with five bullets.

Hard rules first, preferences second

The real work is not filling cells, but deciding the rules that fill them.

Some rules are hard and non-negotiable:

• Certain umpires only do youth games.
• No one umpires and plays at the same time.
• Maximum number of games per person per weekend.

Other rules are softer:

• Try to spread less popular time slots fairly.
• Keep travel and waiting time reasonable.
• Avoid giving someone three early mornings in a row.

The spreadsheet is built around the hard rules first. Those rules can be encoded in simple ways: columns that flag youth-only umpires, checks for overlapping times, counts of games per person.

Preferences sit on top of that. They are handled manually, once the hard constraints are satisfied. This order matters. If you start with preferences, you end up with a schedule that looks friendly until you hit the first impossible weekend.

Making conflicts visible before anyone calls

The real cost of a bad schedule is not a messy sheet. It is the calls and last-minute messages when someone notices a conflict that should have been obvious.

The goal is to see those conflicts before anyone else does. The sheet helps by turning them into visible signals instead of surprises.

A few simple patterns help:

More on this in my article Why I finally deleted NotePlan.

• Color for conflicts. Use formatting to highlight double bookings, youth-only umpires on the wrong lines, or people over their agreed maximum.
• Count per person. A small summary area that lists each umpire and how many games they have in a period makes overload visible quickly.
• Time checks. Basic formulas that compare game times for the same person and flag overlaps or impossible gaps.

The sheet does not fix the conflicts. It just makes them hard to ignore. You can then move assignments around while you still have options, instead of patching holes at the last moment.

Volunteers are not a team you can direct

Scheduling umpires looks like managing a roster, but the social rules are different. These are volunteers. They are doing the club a favor. You cannot treat them like a squad you can rotate however you want.

That changes how you think about constraints:

• “Only youth games” is not a complaint. It is a boundary that makes volunteering sustainable for that person.
• “Not on Sundays” may be the difference between having that umpire or not having them at all.
• Last-minute changes burn trust faster than they solve problems.

The spreadsheet helps here because it forces you to confront the real distribution of work. If you see the same names in the hard slots every week, you know you are leaning on a small group too much, even if nobody has said anything.

As a board member, that awareness is part of the job. The tool does not create respect for volunteers, but it can keep you honest about how you use them.

Simple structure of the sheet

The exact layout matters less than being consistent. A workable pattern looks like this:

• Rows for games, with date, time, field, pool, opponent, and level (youth/senior).
• Two columns for umpires per game.
• Extra columns for flags: youth-only, home-only, unavailable, max-per-weekend.
• A separate area or tab that summarizes per-umpire stats and highlights overload or gaps.

With that in place, most of the work is moving names around and watching the flags. The value is in having the constraints where you can see them, not in having the computer decide for you.

Read also I Would Rather Publish 600 Useful Words.

Where an app still fits

Even if the schedule lives in a spreadsheet, there are places where an app can help:

• Sending reminders.
• Collecting availability or blackout dates.
• Sharing last-minute changes quickly.

The important part is to keep the roles clear. The spreadsheet is the source of truth for the constraint problem. Apps are distribution and communication layers on top of that. If you let the app own the logic, you lose the ability to tune the rules to your actual club.

Tools follow rules

Scheduling 38 umpires is not about finding the perfect piece of software. It is about deciding which constraints are hard, making those constraints visible, and respecting the fact that volunteers are not employees.

Once those rules are clear, a plain spreadsheet is usually enough. If it is not, the problem is probably not the tool.