What to do when a referee cancels at the last minute

Change the schedule before you contact anybody, and confirm one person before you release the others.

Nearly every cancellation that turns into a genuine mess breaks one of those two. Text five people at once and two say yes — now you have to un-invite someone, and one of them will show up anyway. Text a replacement before the record changes and, for a while, the schedule says one thing and a phone says another. That window is where two officials arrive for one game and where none arrive for the other.

Everything below is that rule, in order, with the parts that go wrong called out.

1. 1. Establish what is actually happening

   Which game, which position, and are they definitely out. “I might not make it” is not a cancellation, and treating it as one costs you an official. Ask directly: are you out, or are you unsure and will confirm by a time I give you?

   If they are unsure, set the time — “tell me by 8pm” — and start step two anyway. You can stand a replacement down; you cannot conjure one at 7am.

2. 2. Open the position in the schedule

   Before any other message goes out. The assignment becomes open, the original official is released, and the game now shows as short.

   Do not delete the record that they were assigned and cancelled. That is information — for the conversation later, and for next season’s assigning.

3. 3. Build the shortlist before you contact anyone

   Five minutes here saves an hour of messages. Filter to people who:

   • — are not already working at that time;
   • — are qualified for the level;
   • — have not told you they are unavailable that day;
   • — can realistically get there.

   Then order it. Nearest first is usually right for a same-day cancellation. For a Wednesday cancellation before a Saturday, order it by who is light on games — a gap is a chance to even out the season rather than a chance to lean on the same reliable person again.

4. 4. Ask one person at a time — with a deadline

   “Can you take Field 3 at 9am Saturday? Let me know within the hour and I’ll lock it in.” The deadline is what makes sequential asking viable; without it you wait indefinitely for one person and lose the afternoon.

   Broadcasting to everyone at once is faster and creates the double-acceptance problem. It is defensible for a genuine same-day emergency, but say so explicitly in the message — first to reply gets it — so the people who miss out know why.

5. 5. Confirm, then write it down immediately

   A yes in a text message is not the schedule. Record the assignment against the game the moment you get it, before you send anything else. This is the step that gets skipped under time pressure and it is the one that causes the conflicting-version problem.

6. 6. Send the replacement a full assignment, not a confirmation

   They agreed to a sentence in a text. They now need the same information everybody else got: date, time, position, venue as you would say it out loud, level, teams, and who to contact. Do not assume the person who said yes to “Field 3 at 9” knows which complex, which teams, or what they are running.

7. 7. Tell the people the change affects

   Usually a short list, and usually not everybody:

   • — The rest of the crew. They are working with someone new. One line is enough.
   • — The site or home club, if they keep a list of who is expected.
   • — The league, only if the game is going ahead short-staffed or is at risk.

   The official who cancelled does not need a further message, and the rest of the pool does not need to know at all.

Sometimes there is nobody. It is worth deciding the ladder in advance, in daylight, rather than at 7:40am:

• Reduce the crew. Most competitions have a rule for running a game with fewer officials than usual. Know what yours says before you need it.
• Move a crew member up. An assistant taking the centre with a club-supplied assistant on the line is often better than a postponement, and it is a real development opportunity for someone.
• Cover it yourself, if you are qualified and available. Assignors do. Just make sure it is a choice, not a reflex — an assignor at a game is an assignor not answering their phone.
• Escalate to the competition. Postponement is their decision, not yours. Give them the facts early rather than a surprise at kickoff.

• Record the cancellation and roughly why. Illness, work, double-booked, no reason given. One cancellation is life; the pattern is the thing you need, and you will not remember it in March.
• Update their availability if the cause was not a one-off. Someone whose shift pattern changed will cancel again next Saturday unless the record changes.
• Note who stepped in. Both because they deserve the credit and because it is real workload that should count in the balance later.
• Have the conversation, if there needs to be one.Third morning-of cancellation from the same person is a conversation, not a grudge quietly applied to next month’s assignments.

The failure this whole process is designed to prevent is subtle: not “nobody showed up”, but “two people believed different true-sounding things”.

• The schedule changes first. Always. Messages describe the schedule; they never are the schedule.
• One person makes the change. If two assignors are covering for each other, one of them owns this game until it is filled.
• Nothing is confirmed in a group chat. A group chat has no record of who agreed to what, and everybody reads it as though it was addressed to someone else.
• Anything printed or exported earlier that day is stale by definition. Say so when you hand it over.

The process above works on paper and works in a spreadsheet. What it costs you there is the bookkeeping: you are the thing keeping the schedule, the text thread and the shortlist in step, at the exact moment you have the least attention to spare.

In Ref Grid, a decline reopens the position rather than overwriting the record that someone said no, so step two happens on its own. The roster and the games are in one place, so step three starts from who is not already working at that time instead of from a cross-reference — the “has not told you they are unavailable” half still comes from wherever you collect that, because Ref Griddoes not hold it. And the replacement gets the same assignment message as everybody else, from the same place the schedule lives, which is what stops step five and step six drifting apart.

If you are running this out of a spreadsheet today, the free template has the columns that make the shortlist step quick — one row per position, with an explicit status.