Handling last-minute absences without spending your evening on the phone

Finding a replacement looks like one question and is really three, answered simultaneously and mostly from memory.

Who is qualified for that post. Who is not already working, on holiday or unavailable. And who is not already well into overtime for the week, because the easiest person to call is often the one who has already worked five days.

Only the first of those is stable. The other two change daily, and they live in different places: the schedule, a holiday list, a mental note about someone’s hours, and a chat conversation where somebody mentioned they were away this weekend. Reassembling that picture under time pressure is what makes a fifteen-minute problem into a forty-minute one.

In most restaurants, every replacement request travels through one person, sequentially. The manager writes to one colleague, waits, gets no answer, writes to the next, gets a maybe, calls a third.

Sequential asking is slow for an obvious reason: each round trip costs the response time of one human being. Eight candidates asked one at a time can easily take an hour. The same eight asked at once takes as long as the fastest of them to reply.

The instinct against asking everyone at once is understandable. Managers worry about two people accepting, or about looking disorganised in front of the team. Both worries are about the absence of a mechanism rather than about the approach. In a group chat there is no mechanism: nobody knows whether someone has already said yes, so either two people volunteer and one is disappointed, or nobody does because everyone assumes a colleague will.

Offering a shift properly means the offer is visible to everyone eligible, the first acceptance closes it, and the schedule updates. Once that exists, broadcasting is obviously better than sequential calling.

Ask any manager who covers most of the last-minute shifts and they will name two or three people without hesitating. Ask them how many times those people have covered this month and the answer is a guess.

That gap matters more than it looks. The staff who always say yes are usually the most committed ones, and they are the ones who leave. They rarely leave over the covers themselves. They leave because it was never acknowledged, because nobody else was ever asked, and because the request kept coming on their day off.

Making cover requests visible to the whole eligible group fixes part of this automatically, since the shift goes to whoever wants it rather than to whoever is easiest to reach. Keeping a record of who covered and how often fixes the rest, mostly by making the imbalance impossible to overlook.

Most teams have never explicitly agreed what to do when someone cannot come in. There is a vague expectation of a phone call, which produces a different behaviour from each person, and a lot of very late notice.

Three sentences are usually enough. Who to notify and how, whether a message is sufficient or a call is required, and by when. Anything after that deadline means calling rather than messaging, because a message that nobody sees is not notice.

The point is not discipline. It is that a shared rule converts an awkward personal moment into a procedure, and people notify earlier when they know exactly what they are supposed to do. Half of the "he told me an hour before" cases are people who did not know they could tell you the previous evening.

The last part of an absence is the part that gets skipped. Someone covered, so the operational problem is closed, and nobody records what actually happened.

Three weeks later there is a payroll question nobody can answer. Was that day sick leave or a swap. Did the person who covered work their planned hours or the two extra hours they actually did. Did the original person work a different day to compensate, and was that agreed or assumed.

These are small amounts individually and they add up to a monthly argument. They also make it impossible to see patterns, and patterns are the useful information: one person absent every second Saturday, or a Thursday that generates a call almost every week because it is chronically understaffed.

The fix is unglamorous. The replacement is recorded in the schedule, not just in the conversation, and the hours actually worked are logged by the person who worked them rather than reconstructed at month end.

Absence handling works when four things are true, and none of them require sophisticated software.

What they do require is that a shift stops depending on one person being reachable.