Build a League Schedule Your Umpires Can Actually Cover

Quick answers

• How many simultaneous games can my league schedule? Count the umpires you can actually count on for your busiest night, divide by crew size, then knock off 15–20% for real life — 14 reliable umps on two-umpire crews works out to about six simultaneous games.
• How do I stretch a small umpire roster across more games? Cluster games at the same complex with staggered start times (Field 1 at 6:00, Field 2 at 8:00) so one crew works back-to-back games on the same drive.
• What scheduling pattern burns out umpires fastest? The 9pm Friday finish followed by the 8am Saturday first pitch — build a rest gap across that overnight seam or your best people start finding reasons to be unavailable.
• What’s the simplest way to build a fair season schedule? The circle (polygon) round-robin method: fix one team in place, rotate the rest a spot each round, and every round produces the same number of games — which means the same staffing demand every week.
• How much turnaround time between back-to-back games? A seven-inning softball game plus warmup and paperwork runs about two hours, so don’t schedule the second game to start before the first realistically ends.

Every umpire problem I’ve ever had traces back further than it looks. The no-show on a Tuesday, the ump who quit in July, the game that started with one guy behind the plate and nobody on the bases — those feel like assignment problems. Most of them are schedule problems wearing a disguise.

Here’s the thing nobody tells you when you take over a league: the schedule gets built first, usually by whoever handles the fields or the teams, and then it gets handed to the person staffing umpires. By the time it reaches you, the damage is baked in. You can’t assign your way out of a schedule that asks for six simultaneous games when you have four umps free that night.

So this post is about the step upstream — designing a baseball or softball season schedule that your actual roster can actually cover. If you build it right, the assignment part gets boring, which is exactly what you want.

Start with the number that matters: how many games can you staff at once?

Before you place a single game, figure out your real ceiling. Not how many umpires you have on the roster — how many you can count on being available at the same time on a typical game night.

Do the math honestly:

• Count umps who are genuinely available on your busiest night (say, weeknights after 6pm). Not the guy who works one Saturday a month. The dependable core.
• Divide by your crew size. Two-umpire games? Divide by two. Solo plate-only rec games? That’s your count directly.
• Knock off 15–20% for the person who’s sick, on vacation, or double-booked. There’s always one.

Say you’ve got 14 reliable weeknight umps and you run two-umpire crews. That’s seven crews on paper, call it six once you account for real life. Six simultaneous games is your ceiling on a weeknight. If the schedule someone handed you has eight games starting at 6:30 on a Wednesday, no assignment tool on earth fixes that. You’re short two crews before you begin.

Write that ceiling number down. It’s the single most useful constraint you have, and almost nobody calculates it before the season.

Cluster games so one crew can work more than one

Umpires travel. A crew that drives 25 minutes to work one game and drives home has given you one game for a whole evening burned. A crew that works back-to-back games at the same complex has given you two — same drive, same night, and usually a happier ump because the pay adds up.

So when you’re laying out the schedule, cluster on purpose:

• Same complex, staggered start times. If Field 1 goes at 6:00 and Field 2 goes at 8:00, one crew covers both. That doubleheader for the crew costs you nothing extra in bodies.
• Keep a field “family” together. If your league plays across three parks, try to concentrate a given night’s games at one or two parks rather than spreading thin across all three. Every extra location is another crew that can’t be shared.
• Mind the turnaround. A seven-inning softball game plus warmup and paperwork can run two hours. If you want the same crew on both, don’t schedule the second game to start before the first realistically ends. A 90-minute gap that becomes a 20-minute scramble makes people quit.

Clustering is the highest-leverage thing you can do. It effectively stretches a small roster into covering more games without recruiting a single new person — and recruiting, as anyone who’s tried it knows, is the hard part. (If that’s your real bottleneck, we wrote a whole piece on recruiting and keeping umpires.)

Stop scheduling the pattern that burns people out

There’s one scheduling pattern I see over and over, and it quietly torches your best umpires: the 9pm Friday finish followed by the 8am Saturday first pitch.

Think about what you’re actually asking. Someone works a night game, gets home near 10, unwinds, sleeps a few hours, and is back at the yard before most people have coffee. Do that to a volunteer or a semi-retired guy working for gas money a couple of times and he starts finding reasons to be unavailable. You never hear “I’m burned out.” You hear “sorry, can’t make it that weekend,” and then you hear it more often.

Some fixes that cost you nothing:

• Give a rest gap across the overnight. If someone closes a Friday night, don’t be the one who also pencils them into the Saturday opener. This is an assignment-level fix, but it’s far easier when the schedule itself doesn’t cram the last Friday game against the first Saturday one.
• Front-load Saturdays with your morning people. Some umps love an early game and are gone by noon. Some are night owls. Build the schedule so those preferences have somewhere to land.
• Don’t stack a single ump’s whole week into 48 hours. Spread the load. A fairness view helps here — more on that below.

The schedule can’t read minds, but it can stop creating the collisions. When the games are spaced sanely, humane assignments become possible. When they’re jammed, you’re choosing which good ump to overwork.

Use a simple round-robin so the games fall out evenly

You don’t need scheduling software with a genetic algorithm to build a fair season. For most small leagues, a plain round-robin does the job and — crucially — produces an even distribution of games across nights, which is exactly what makes staffing predictable.

The classic method is the circle (or “polygon”) method. Here’s the short version for an even number of teams:

1. List your teams in two rows. With six teams, that’s 1-2-3 on top and 6-5-4 on the bottom. Each column is a matchup: 1v6, 2v5, 3v4. That’s round one.
2. Fix team 1 in place. Rotate every other team one spot clockwise around it.
3. Read off the new columns for round two. Repeat until every team has played every other team once.

With an odd number of teams, add a phantom “bye” team; whoever draws the bye that round sits out.

Why bother with the structure instead of eyeballing it? Because a round-robin naturally gives you the same number of games per round — which means the same staffing demand week to week. No surprise week where suddenly nine games land on one Tuesday. Predictable demand is the whole game when your roster is fixed.

Once you’ve got the round-robin rounds, map them onto your calendar and your field ceiling. If a round has more games than you can staff simultaneously, split it across two nights or stagger start times at a shared complex. This is where your ceiling number and your clustering plan earn their keep.

Sanity-check the finished schedule against your umpires

Before you call it done, run the schedule past the constraints you set up top:

• No time slot exceeds your simultaneous-game ceiling. Count the 6:30 games. If it’s more than your crew count, move one.
• Games are clustered where they can be. Are two games at the same park stacked so one crew can take both?
• No brutal overnight turnarounds built into the last-Friday / first-Saturday seam.
• Blackout reality checked. If half your umps coach on Sunday afternoons, don’t schedule your marquee Sunday slate against it. Getting availability in before you assign saves the whole month; here’s how to collect blackout dates without the chaos.

If it clears all four, you’ve done the hard part. The assignments will practically make themselves.

Getting the schedule into your assignment tool

Once the season is built — usually in a spreadsheet, because that’s where these things live — you don’t want to retype it game by game into whatever you use to assign crews. That’s how typos become wrong-field no-shows.

Build the season in your spreadsheet, then import it as a CSV. Date, time, field, home, away — one row per game, and the whole season lands at once. From there you assign crews (or let an auto-suggest rank your umps by fewest games worked so the load stays even), and the tool watches the fairness math for you across the season. That’s the payoff of doing the schedule design first: you built even demand into the calendar, and now the assignments inherit it.

A good schedule doesn’t guarantee a smooth season. But a bad one guarantees a rough one — and no amount of clever assigning digs you out of a schedule that asks for umpires you don’t have.

Frequently asked questions

What if someone else builds the schedule and just hands it to me?

Get your ceiling number to them before they build. You don’t need a seat at the whole table — one sentence does most of the work: “We can staff six simultaneous games on a weeknight, don’t schedule more than that in one slot.” Most schedule-builders aren’t ignoring your umpires on purpose; they’ve just never been given the constraint.

How do rainouts and makeup games fit into this?

Makeups are where a clean schedule goes to die, because they concentrate demand — three rained-out games all want the same open Thursday. Hold two or three open dates on the calendar from the start, and when you rebook, apply the same rules: cluster makeups at one complex and recount the time slot against your ceiling before you confirm.

Should I schedule team doubleheaders to save umpire nights?

Generally yes. Two games back-to-back at one field is exactly the clustering this post argues for — one crew, one drive, two games covered. The one thing to manage is the crew itself: flip who’s behind the plate between games, because a doubleheader on the dish in July heat is how you turn a favor into a resignation.

How far before opening day should the schedule be finished?

A few weeks minimum. Your umps can only file blackout dates against real dates, so the schedule has to exist before availability collection means anything — and covering a hole is easy with three weeks’ notice and nearly impossible with three days’. A schedule finalized the week of opening day forfeits both advantages.

Built your season and want the crews handled without the retyping? Start a free 14-day trial — no credit card — or email hello@umpcrew.com and we’ll set it up for you.