The Umpire Handbook: A Copy-and-Use Outline for Your League

Quick answers

What is an umpire handbook? A short written document that spells out your league’s pay, arrival, uniform, rainout, availability, conflict, and discipline policies so umpires don’t have to ask — or argue.

How long should it be? Short enough that people actually read it — aim for 4 to 8 pages, not a rulebook.

What should an umpire handbook include? Pay rates and payment timing, arrival and uniform expectations, rainout policy, blackout/availability process, conflict-of-interest rules, the ejection and discipline process, and who to call when.

Do I really need one for a small rec league? Yes — the smaller your staff, the more every disagreement lands on you personally. A handbook moves those disputes from your phone to a document.

The point of a handbook: turn arguments into lookups

Here’s the pattern every commissioner eventually recognizes. The same five questions come at you over and over, usually by text, usually at 9:40 on a game night: When do I get paid? Do I wear black or navy? What happens if it rains? Can I turn down a game? What do I do after I toss a coach?

You answer them one at a time, slightly differently each time, and six weeks later two umpires are quoting you two different answers to the same question — both swearing you told them that.

A handbook fixes this. Not because it’s official-looking, but because it replaces “let me ask Erik” with “it’s on page 3.” Every policy you write down is one less argument you have to litigate in real time. That’s the whole value. It’s not bureaucracy; it’s you reclaiming your Tuesday nights.

The mistake people make is treating the handbook like a legal document — forty pages nobody opens. Don’t. The best handbook is the one your newest teen ump reads cover to cover the week before their first game. Keep it short, keep it plain, and put the stuff they’ll actually look up near the front.

The outline — copy this structure wholesale

Here’s the full skeleton. Steal it. Each section below is one or two paragraphs in your actual document, not a chapter.

1. Welcome and who runs this

One short paragraph. Who you are, what the league is, and the single most important thing you want an ump to know walking in. Set the tone — you want these people to stay, not just show up once.

2. Pay rates and payment timing

This is the section people flip to first, so put it near the top. Be specific:

• Rate by level and position. A 10U game isn’t a 16U game; a plate isn’t the bases. List the dollar figure for each.
• How you pay — cash at the field, Venmo, check, payroll.
• When you pay — same night, end of week, end of month. Say it plainly.
• What happens on a rainout — do they get a partial game fee if they showed and it got called after first pitch? (More on rainouts below — decide it here and write it down.)

Vague pay policy is the fastest way to lose good umps. If you’re still settling on numbers, we broke down honest 2026 rates by level in our pay guide, and there’s a worksheet for the whole line item in the umpire budget post.

3. Arrival and uniform expectations

Short and non-negotiable. Spell out:

• How early — 15 minutes before first pitch is a common standard; 30 for a plate ump who needs to inspect the field and meet coaches.
• Uniform — shirt color, pants, hat, plate gear. If you lend equipment, say how to get it and return it.
• What “ready” looks like — indicator and brush in pocket, phone on silent, the stuff a new ump genuinely doesn’t know to do.

4. Availability and blackout dates

Tell umps exactly how to tell you when they can’t work — and by when. The worst version of this is availability living in a hundred scattered texts you have to remember. Give them one channel and one deadline.

• How to submit blackout dates (app, form, whatever you use).
• The cutoff for the schedule each week.
• What happens if they go dark and don’t respond.

If collecting availability is your current headache, that’s its own project — we walked through doing it without the chaos in this post on blackout dates.

5. Conflict-of-interest rules

The section nobody thinks to write until it burns them. Decide and state:

• An ump won’t be assigned to a game involving their own kid’s team, or a team they coach.
• What to do if they realize a conflict after the assignment — who they tell, how fast.
• Gifts, side bets, favoritism — a plain line that says don’t.

You don’t need legal language. You need one clear rule so that when a parent accuses your ump of favoring their nephew’s team, you can point to the policy and the assignment and be done.

6. Rainout and weather policy

Weather is the single most common game-night chaos event, so this section earns its keep. Cover:

• Who makes the call and by when.
• How umps find out — the exact channel, so nobody drives 40 minutes to a dark field.
• Pay on a called game (tie this back to section 2).
• Rescheduling — do they get first dibs on the makeup, or does it go back in the pool?

Rainouts are messy enough that we gave them a full survival guide — point your umps to the rainout and reschedule playbook if you want the long version, but your handbook should carry the short version.

7. Ejections and game management

Your umps need to know you have their back before they need it. Lay out:

• When an ejection is appropriate (judgment, but give them the categories: unsportsmanlike conduct, arguing balls and strikes, contact, etc.).
• The mechanics — how to eject cleanly and get back to the game.
• Who they report it to and when — a short note to you that night, not a novel.
• That the league backs a correctly-handled ejection. Say it out loud.

Protecting umps from the sideline is bigger than a handbook paragraph, but the paragraph is where it starts — more on the full approach in how leagues actually protect their umpires.

8. Discipline process (for the umps themselves)

The flip side of ejections. What happens when an ump no-shows, shows up unfit, or gets a serious complaint? Keep it fair and written:

• First no-show: a conversation. Repeat: removal from the schedule.
• How complaints are handled — you talk to the ump before any action, every time.
• An appeal path, even an informal one. People accept consequences they saw coming.

9. Who to call when — the cheat sheet

End with a one-page contact box people can screenshot:

• Can’t make a game / running late → text [name/number] by [when].
• Rainout question → check [channel].
• Payment question → [name].
• Problem at the field / safety issue → [name], call don’t text.
• Equipment → [name].

This page alone prevents half your game-night texts from going to the wrong person at the wrong time.

Rolling it out so people actually read it

A handbook nobody reads is just a document that makes you feel organized. Give it a fighting chance:

1. Keep it to a handful of pages. Ruthless editing beats completeness.
2. Hand it out at your preseason meeting and walk the contact page specifically.
3. Get a one-line acknowledgment — a reply text, a checkbox, a signature. “I read it” matters when you later need to enforce it.
4. Revisit it once a year. Every policy in there exists because something happened. Add the new ones; cut the dead ones.

If you’re building the handbook as part of a bigger “get this league organized” push, pair it with a real assignment system so the availability and who-to-call sections aren’t just promises. When an assignment goes out, an instant SMS to the ump with date, field, and teams does the handbook’s job automatically — and a fairness view backs up whatever rotation policy you wrote down.

Frequently asked questions

Should the handbook be the same for baseball and softball?

Mostly, yes — pay, arrival, conduct, and contacts are shared. Break out only the parts that genuinely differ, like rate by level or any sport-specific mechanics, so you’re maintaining one document instead of two.

Who should sign off on the handbook?

You, and ideally your league board, so the discipline and pay sections carry weight beyond just your opinion. Then get a lightweight acknowledgment from each umpire that they’ve read it.

How is a handbook different from an umpire training program?

The handbook is policy — what the rules are. Training is skill — how to actually call a game. New umps need both; we laid out a practical training program that pairs naturally with the handbook.

What if I change a policy mid-season?

Send the one-line change to every ump through the same channel you use for assignments, and update the document. Don’t rely on a quiet edit nobody saw — surprise policy changes are how you lose trust.

If you’d rather not build the whole thing from a blank page, we’ll help you stand up your league — handbook policies, schedule import, and all — just email us and we’ll set it up for you.