Scheduling Umpires for a Tournament Weekend: Everything League Play Doesn't Prepare You For

A league season is a marathon you run one Tuesday at a time. A tournament is a sprint you run for two straight days with no sleep in between.

I say that as someone who’s done both. Running our church league on a weekly cadence is comfortable — same fields, same crews, a schedule I set once in March and mostly leave alone. Then we host our summer invitational, and every assumption I’ve built my season on goes out the window inside the first three hours.

If you’re about to assign umpires for a weekend tournament and you’re treating it like a busy week of league play, stop. It’s a different animal. Here’s what actually changes, and how to plan for it.

The core difference: you’re scheduling a day, not a week

In league play, an umpire works one game and goes home. Your unit of planning is the game, spread thin across a calendar.

In a tournament, an umpire is on-site all day and works four or five games back to back. Your unit of planning is the person’s day — a continuous block from their first plate to their last out, including the gaps and the walking-between-fields time. That single shift in thinking fixes most of the mistakes I see first-time tournament schedulers make.

So before you assign anyone, you build the day grid.

Building the day grid

Pull up the field map and the time slots and lay it out as a physical thing. Most tournaments run games on a rolling clock — 90-minute or 105-minute time limits, staggered starts across four or six fields so the diamonds are never all flipping at once.

Your grid has two axes: fields across the top, time slots down the side. Every cell is a game that needs a crew. Now you fill it — but not the way you fill a league week.

A few rules I follow:

• Assign crews to a rotation, not to individual games. Figure out how many two- or three-person crews you need to cover the peak hour (when the most fields are live at once), then flow those crews through the day. A crew works Field 3 at 9:00, walks to Field 1 for 11:00, breaks, comes back at 2:00.
• Leave slack between a crew’s games. A 90-minute time limit is a limit, not a guarantee. Extra innings, protests, and slow pace push games long. If you butt two games right against each other and the first runs 20 minutes over, your crew is late to the second game with no cushion. Build in at least 20–30 minutes between the scheduled end of one game and the start of the next for that crew.
• Account for field-hopping. If your complex is spread out, walking from the far diamond back to the main field eats real time. Try to keep a crew on the same field for consecutive games when you can. It’s faster and it’s less confusing for everyone.
• Stagger your start times if you have any control over the bracket. Tournament directors set the game schedule, but a good one will talk to you. If every field starts at 9:00 sharp, every field flips at 10:30 sharp, and you have a crunch. Ask for a 15-minute stagger between fields.

If you’ve never built a grid like this, it looks a lot like the step-by-step league schedule — just compressed into a single sheet where the rows are hours instead of weeks.

Cap consecutive games — for real

Here’s the one that bites people. A motivated ump will tell you they can work six straight. Behind the plate. In July. Do not take them up on it.

Plate work is physically brutal — squatting a couple hundred times a game, in gear, in the heat. Judgment goes before the legs do. An ump on game five behind the dish is a worse ump than the same person on game two, and that’s when you get the blown call that follows you home in an email Sunday night.

What I do:

• Cap plate assignments at three per person per day, ideally with a break in the middle. Rotate them to the bases for the extra games.
• Cap total games at four or five per day depending on heat and game length. Five short 60-minute rec games is different from five full seven-inning battles.
• Rotate plate and bases within the crew every game. Nobody catches all day. This is the same fairness logic that keeps your season crews happy — I wrote about the mechanics of that in how to rotate crews fairly, and it matters even more when the games are stacked.

Cap it in the grid before you assign, not on the fly at noon when someone’s cooked.

Meal and heat breaks are part of the schedule, not an interruption

In league play you never think about feeding your umpires. In a tournament you have to, because there’s no dinner-at-home to go back to.

Block a real meal break into every crew’s day — 45 minutes minimum, and stagger the breaks across crews so you’re never short-handed. If you can put a few dollars of concession credit or a sandwich in each ump’s hands, do it. It costs almost nothing and it’s the difference between an ump who comes back next year and one who doesn’t.

Heat is the bigger safety issue. If you’re running a July tournament in real heat:

• Put a cooler of water and ice at every field, not just the main one.
• Shorten the plate rotation on the hottest afternoon slots — two games behind the dish, then bases.
• Build in a genuine sit-down break for any crew working the peak-heat window.
• Watch your people. An ump who’s quiet, stumbling, or not sweating is a medical situation, not a toughness contest. Pull them.

None of this happens unless it’s in the grid ahead of time.

Tournament pay: day rates change the math

League pay is almost always per game — I laid out honest rates by level here if you’re setting that. Tournaments are where a lot of leagues switch to a day rate, and it’s worth understanding why.

A day rate — a flat number for the whole day regardless of exact game count — does a few useful things:

• It’s simple to communicate and simple to pay. One number, one check.
• It protects the ump against a light day. If their bracket finishes early or a game gets forfeited, they still get paid for showing up and blocking the whole day.
• It protects you against the marathon day. If extra innings push a crew to a sixth game, you’re not doing per-game math at 8 p.m.

The tradeoff: a day rate has to be set high enough that the possible long day feels fair, or your best umps will do the math and work the league that pays per game. My rule of thumb is to price the day rate at roughly what four or five games would earn per game, then round up a little for the commitment of blocking the whole weekend. Some directors split the difference — a day rate plus a per-game bump after game four. That’s fine too, as long as everyone knows the deal in writing before Saturday.

Whatever you choose, write it into the assignment. “Saturday, $X for the day, report to Field 2 at 8:30” removes every argument before it starts.

The real challenge: communicating day-of changes

This is where tournaments live or die, and it’s the part league play never trains you for.

Brackets shift hour to hour. A game runs long and the whole afternoon slides. A team forfeits and a slot opens. A crew’s second game moves from Field 4 to Field 1. In league play you’d email everyone Wednesday and they’d read it Thursday. On a Saturday, nobody is checking email. They’re at the field, in gear, phone in their back pocket.

So your communication has to work in real time, on the device they actually have on them:

• Everything goes to the phone, immediately. Not a printed sheet from Friday night that’s already wrong by 10 a.m.
• Every change includes field, time, and teams — because an ump who just finished a game needs to know exactly where to walk next, not go hunting for you.
• You need a fast way to fill an open slot. When a forfeit opens a game or an ump has to leave, you want to offer that game out and have someone claim it in seconds, not run around the complex looking for a spare body. If day-of no-shows are your recurring nightmare, we went deep on handling them here.

A group text sort of does this — until you’re managing four separate crews and the thread becomes noise nobody can follow. (We wrote a whole piece on why the group text eventually breaks, and a tournament weekend is exactly the pressure that breaks it.)

This is the one spot where I’ll point at the software directly. When I move a crew’s game or open a forfeited slot in UmpCrew, the affected umps get an instant text and push notification with the new field, time, and teams and a one-tap calendar update — no group-thread archaeology, no wondering if they saw it. On a day when the schedule is moving under your feet, that’s the whole ballgame.

The night-before checklist

Before you go to bed Friday, confirm:

1. The full day grid is built, with slack and breaks in it.
2. Every crew knows their first field, first time, and report time.
3. Consecutive-game and plate caps are set and nobody’s over.
4. Pay is agreed and in writing.
5. Water and shade are handled at every field.
6. You have a real-time way to push changes to phones — and a way to fill an open slot fast.

Do that and a tournament weekend is still long, still hot, and still a little chaotic. But it’s the good kind of chaos — the kind you planned for.

If you’d rather not build the grid alone, start a free 14-day trial and set your first tournament up in an afternoon — or email hello@umpcrew.com and we’ll set it up for you.