When the Decider Is the One Who Is Off

Every arrangement in this section assumes somebody is there to operate it. The case nobody prepares for is the one where the missing person is the scheduler, the duty manager, or the only person who knows the call-out list.

The practical issue in “When the Decider Is the One Who Is Off” is easier to manage when operational time records can be checked without treating activity as intent. For teams exploring employee monitoring for performance reviews, open the official page can add time and project context, provided collection is proportionate, employees can review inaccuracies and consequential decisions receive human review.

It is not a rare case. Those roles are usually held by one person, they are as likely to be ill as anybody else, and when they are the operation loses both a pair of hands and its entire ability to respond.

For an independent benchmark relevant to “When the Decider Is the One Who Is Off”, consult the Cloudflare zero-trust overview. Use it to test scheduling, working-time limits, attendance records, employee rights and exception handling against the real operation rather than treating a software report as self-explanatory evidence.

What goes missing with them

Knowledge: who is on the list, who said yes last time, who is near their hours limit, which agency to ring, what the rate is, which client needs telling.

Access: the scheduling system, the phone with the numbers in it, the agency portal login, the folder.

Authority: the delegation, where one exists, is usually written against the individual rather than the role.

Relationships: the agency contact who answers for them, the part-time worker who will do it as a favour for them specifically.

The first three are fixable in an afternoon. The fourth is the reason the stand-in morning takes twice as long even when everything else is in place.

Making the knowledge leave the person

Everything this collection recommends writing down is also the answer here: the requirement, the call-out list with constraints, the order of routes, the authority, the notification list, the reduction plan.

An operation with those six documents can be run by somebody who has never done it. An operation where they live in one person's head cannot, and the test is not hypothetical — it happens several times a year.

Access, which is the easy part

Shared credentials are a bad answer and the usual one. The better version is named accounts for a deputy, granted in advance, tested once.

The phone is the common failure: the numbers are in a personal mobile and the person is asleep with it. The call-out list belongs on paper or in a shared system, and the moment it is only in somebody's contacts it has become a single point of failure.

Authority written to the role

If the delegation names a person, it lapses when they are away. Writing it against a role, with a named deputy for that role, is a one-line change that is almost always missing.

The deputy also needs to know they are the deputy. A substantial share of these failures is somebody discovering at six forty that they are in charge.

The scheduler's absence specifically

Worse than the duty manager's, because the effects are delayed. A scheduler off for two weeks means the rota for the fortnight after is not built, and the operation discovers this when it should have been published.

Rotas should be built further ahead than the absence they must survive. Where one person builds them, a four-week horizon means a two-week absence is survivable and a one-week horizon means it is not.

Testing it

Pick a week and have the deputy run the mornings, with the usual holder available but not involved.

What this surfaces is everything that is not written down, in a controlled way, with the person who knows it still available to explain. It takes a week of slightly slower mornings and it is the only reliable way to find out what is actually in somebody's head.

Most operations will not do this, and the second-best version is to ask the holder to spend an hour writing down what they would need to tell somebody. The list is always longer than they expect and it is the specification for the six documents.

The documents are the deputy

The point of writing everything down is not tidiness. It is that an operation whose morning depends on one person's knowledge has a single point of failure in exactly the place that is least survivable.

Treat the duty folder as the deputy. If it is complete, anybody competent can run the morning badly but adequately, which is the whole requirement. If it is not, the operation has designed itself so that a scheduler's cold determines whether a shift is covered, and no amount of goodwill from the people on duty compensates for that.