The 7:40am phone call is part of the trade: "I can't make it in". Fever, a sick child, a car that will not start. It will happen this month, it will happen next month, and no planning on earth will eliminate it. What planning can eliminate is everything that usually follows: the panic, the carpet-bombing round of calls, the whole day decided over the phone between two stressed people at 7:43.

Absence management is not played at the moment of the call. It is played earlier, in the most prosaic way possible: by having already decided what happens.

Plan B gets written with a cool head

The 7:43 improvisation always produces the same two moves: calling everyone and hoping for a yes, or calling the same person who always says yes. The first is a lottery. The second is a mortgage on someone's patience, and it eventually defaults.

The alternative costs one hour, once: writing the absence protocol. Who gets notified and how (a call, not a message that might get read). In what order replacements are sought, by what criterion (rotation, not likability). What happens if nobody can come: which activities get cut first, how the day gets reorganised in reduced form. That sheet turns the emergency into a procedure, and a procedure can be delegated: the deputy, even the least experienced person, knows what to do without having to invent it.

The reduced day is designed, not endured

The piece almost nobody prepares: the reduced version of the day. If we are two instead of three, what do we NOT do today? The improvised answer is always the same, "everything as usual but faster", and it is the worst one: service degraded everywhere, team burnt, errors in clusters.

The designed answer is a priority list: with one absence the backroom tidy-up goes, with two the secondary counter closes an hour early, the till never goes uncovered no matter what. Deciding it beforehand means the reduced day is a different day, not a failed one.

Whoever covers is a resource, not a plug

Every covered absence is someone who changed their plans for the store. If that passes as simply owed, the willingness runs out fast; if it is recognised (the explicit thank-you, the overtime ledger that balances, priority on their next swap request), it renews. The coverage log exists exactly for this: to make today's generosity tomorrow's visible, remembered credit.

And watch for the opposite signal: if covers always fall on the same two people, you do not have a flexible team. You have two people quietly ripening a resignation.

The pattern matters more than the episode

Last thing, manager to manager: a single absence deserves zero suspicion, and treating it suspiciously poisons the relationship with everyone. The pattern, however, deserves eyes: always Saturdays, always after the heavy shifts, always the same person. An absence log (date, weekday, preceding shift) surfaces in ten minutes what memory muddles for months. And sometimes what surfaces is not a person problem: it is a badly built shift grinding down whoever lands in it.

Seeing at a glance who can cover, keeping count of swaps and extra hours, reorganising the day in two taps: that is Sked Solve's day job, and the site shows how it does it.