How to schedule referees without living in a spreadsheet

Before any of the mechanics, there are two choices that determine whether the season is tolerable. Both get made by accident in most organizations, which is why the season is not.

One document is the schedule. Not the spreadsheet and the group chat. Not the spreadsheet and the printout at the field. One place where an assignment is true, and everything else is a copy of it that is allowed to be out of date. Almost every officiating disaster — two referees at one game, no referee at another, someone who swears they were told — is two documents that disagreed.

Availability comes before assignment. Assigning first and checking later feels faster because you get a schedule out on Tuesday. You then spend Wednesday to Friday renegotiating it one person at a time, and every renegotiation is a message, a reply, and an edit in a document someone else may also be editing.

The league gives you the games — usually as a PDF, a portal export, or an email with a table in it. The first job is turning that into rows you can work with, and the shape matters more than the tool.

One row per position, not one row per game.A game needing three officials is three rows. This looks redundant for about a minute and then pays for itself every single week, because “what is still open” becomes a filter instead of a visual scan across columns. That is the shape the free spreadsheet template uses.

Each row needs enough for an official to show up at the right place:

• Date and start time — and end time if you have it.
• Location, written the way you would say it out loud. “Harborside Complex — Field 1”, not a venue code from the league portal.
• Level or division. This is what decides who is eligible, so it has to be on the row and not in a second document.
• Teams, so people know what they walked into.
• The position name. Center, AR1, AR2; plate and bases; referee 1 and 2. Use your sport’s words.

Most pools live half in a phone’s contacts, half in last year’s registration export, and half in the assignor’s head. The list needs four things per person, and one of them is almost always missing:

• Name, spelled one way, used consistently everywhere.
• Mobile number and email address.
• Which channel they actually answer on. This is the missing one. Some officials read email within the hour and never open a text from an unknown number; plenty are the reverse. Sending everything to everybody on both channels trains people to ignore both.
• Level, grade or certification, plus anything else you sort by — travel radius, age groups they will not take, whether they can be trusted with a rivalry fixture.

Update it once, before the season, and then only when something changes. A pool that is rebuilt every August from scratch loses exactly the notes that were expensive to learn.

Ask for it in a structured form with a deadline. Not “let me know when you’re free” — that produces replies like “most Saturdays, not the 19th, and Sundays after 1 unless it’s in Rivermill”, which is a sentence you will re-read every week for four months.

What you want is one row per person per date they have told you about, with a status you can filter on. And a rule you hold to: silence is not availability. Someone who has said nothing has told you nothing, and assigning them is a guess you will pay for on Friday.

The detail is in how to collect referee availability before the season — what to ask, when to ask it, and how to keep it from going stale by October.

Do not start at the top of the list. Start with the games that have the fewest eligible people — the highest level, the furthest venue, the Sunday 8am — because those decisions constrain everything else. Filling the easy games first means discovering at row 40 that the only three people who can take the varsity fixture are already booked.

Then, in rough priority order:

1. Hard constraints first

   Availability and eligibility. Someone unavailable or not qualified for the level is not a candidate, however convenient.

2. Then the schedule shape

   Travel and timing. Two games at one complex is a good day for an official; the same two games forty minutes apart is a game that starts late.

3. Then fairness and development

   Workload spread, and putting newer officials where they will actually improve — which usually means next to someone experienced rather than alone at the quietest game. That balancing act is its own subject: how to assign referees fairly across a season.

Assign the whole block before you send anything. If assignments go out as you make them, every change you make afterwards is a second message to someone who has already read the first one.

An official working four games this weekend should get one message about their weekend, not four messages about four games. This is the difference between a schedule that feels organised and one that feels like being pestered.

The message needs to survive being read at a traffic light:

• Date, time, position.
• Venue, specific enough to navigate to.
• Level and teams.
• How to accept or decline, in one action.
• Who to contact if something is wrong.

Send it on the channel that person actually reads. An email to someone who lives in text messages is not communication; it is a record that you tried.

An assignment nobody has accepted is a plan, not a schedule. This is the step that most often gets skipped, because it feels like administration on top of work already done. It is the step that decides whether Saturday works.

Give it structure:

• A confirmation deadline that is far enough ahead to do something about it. Wednesday for a Saturday, not Friday afternoon.
• One follow-up for anyone who has not replied. One, not four.
• A record of when each person confirmed. “I’m sure they said yes” is not a record.
• A rule for what happens at the deadline — usually that an unconfirmed assignment goes back into the pool rather than being hoped about.

Games move, fields flood, people get sick on Friday at 9pm. The difference between a small problem and a bad one is almost entirely about the order you do things in — specifically, whether you update the schedule before or after you start texting people.

Update first, then communicate. If you text a replacement before the assignment record changes, there is a window where the schedule says one thing and someone’s phone says another, and that window is where two officials show up for the same game.

The full sequence is in what to do when a referee cancels at the last minute.

Everything above collapses without this, so it is worth being blunt about what it means in practice.

• Every change is made in the schedule first, then communicated. Never the other way round.
• Nobody else edits it. If two people assign, they need one shared document, not two copies and a reconciliation habit.
• Verbal agreements get written down the same day. An acceptance somebody gave you at a field is real — record it, so the schedule matches reality rather than matching the messages that happened to go through a system.
• Anything you print or export is stamped with when it was produced, so it is obvious when someone is holding a stale copy.

None of the above requires software. Assignors ran seasons like this for decades on paper, and a spreadsheet does the first four steps perfectly well — that is why the template exists.

What a spreadsheet cannot do is steps five and six. It will not send anything, so every assignment is a message you compose, and every confirmation is a reply you read and then transcribe into a cell. That transcription is the actual work, and it is also where the source of truth quietly stops being true.

That is the specific gap Ref Grid fills: assignments go out by text and email from the same place you made them, officials accept or decline through a link without needing an account, and the reply lands against the game rather than in your inbox. Whether that is worth paying for depends on how big your pool is and how often things change — here is the honest version of that comparison.