The first ten minutes after a call-out

Somebody has just told you they can't make their shift, which starts in three hours. What happens in the next ten minutes decides whether this is an inconvenience or the thing that defines your day. Most operations handle it well by instinct and badly under pressure, which is the argument for having the sequence written down before you need it.

Minute one: acknowledge and confirm

Reply, and confirm the specifics: which shift, and whether they expect to be back for the next one. This takes seconds and prevents the most expensive version of the problem, which is discovering at handover that two people each thought the other had it covered. It also matters that the person calling out gets a clear answer, because ambiguity here is what turns one absence into two.

Minutes two to three: work out what has to be covered

The instinct is to replace the person. The better question is what the shift was there to do. Sometimes the honest answer is that the gap is partial: the first two hours are the ones that matter, or the position can be covered by someone already on site if a different task moves. Understanding the requirement before you start ringing round is what stops you calling in a full shift to solve a two-hour problem.

Minutes four to seven: build a shortlist, then ask in order

Don't send one message to everybody. A broadcast produces either silence or three people accepting at once, and the second is worse than the first. Rank instead, and ask in sequence.

• Who is qualified for the position and cleared to work it
• Who is genuinely available, not merely unscheduled
• Who is already near an overtime threshold, and what that costs
• Who has been asked to cover recently, and how often

The last one is the one that gets skipped, and it's the one that decides whether you can do this again next month. If the same two reliable people absorb every gap, they'll eventually stop being reliable, or stop being there. Fairness isn't a soft consideration during a call-out. It's the maintenance of the only resource that makes call-outs survivable.

Minutes eight to nine: publish it properly

Once somebody accepts, put it in the schedule rather than leaving it in a text message. The shift record is what the rest of the day reads from: who is expected, who to chase if they don't appear, what the timesheet should say. An agreement that lives only in a conversation between two people is an agreement that will be misremembered.

Minute ten: write down what happened

Record the reason, the change, and who approved it, while it's still in front of you. Two things depend on this later. The first is payroll, where an unexplained gap becomes a query weeks after anybody remembers the answer. The second is the pattern. One call-out is an event. The same person, the same day of the week, three times, is information you'll only ever have if somebody wrote it down at the time.

Then fix the ten minutes

Every step above is mechanical: check qualifications, check availability, check hours, rank, ask, record. That's exactly the sort of work that shouldn't depend on which manager is on shift, or on how busy the floor happens to be at the moment the phone rings.

“You can't prevent every call-out. You can decide, in advance, that it costs you ten minutes instead of an afternoon.”