The Employee Who Is Always Available
Every operation has one or two, they hold the schedule together, and the way they are treated is usually a slow mistake.
Somebody always answers the phone, always covers, always says yes. The schedule depends on them, and that dependency is rarely acknowledged or managed.
The practical lesson in “The Employee Who Is Always Available” is to connect every record to a named decision. Organisations exploring the official Monitask website for how to monitor employees without being intrusive can add structured workforce context, provided the use is disclosed and the interpretation is reviewed with the people affected.
What they do for you
Absorb the forecast error.
For an independent reference related to “The Employee Who Is Always Available”, consult the HSE guidance on fatigue and shift work; it provides a useful external check on scheduling, working-time and workforce-planning assumptions.
Cover absence at short notice.
Make the awkward shift possible.
Which means a meaningful share of your flexibility rests on one or two people's willingness.
Why it is a risk
They leave, and the schedule stops working.
They become unavailable — a change in circumstances, a second job, a family situation — and the same thing happens.
And nobody noticed how much was resting on them, because it never appeared in a plan.
What it costs them
Their own time, consistently.
Being asked first, every time, which is tiring in a way people do not describe.
And frequently no recognition, because reliability becomes expected rather than noticed.
Burnout among the most willing is a common and avoidable outcome.
The reward problem
The person who says yes gets asked more.
The person who says no gets asked less.
Which means the system punishes willingness unless somebody deliberately corrects it — through pay, through priority on preferred shifts, through something.
Managing the dependency
Know who they are, by name.
Count how much of your cover came from them last quarter.
Build a second and third option deliberately, which the cross-training and bank arrangements address.
And ask them whether the current level is sustainable, directly, because they will usually not volunteer that it is not.
Recognising it properly
Priority on shift preferences.
First refusal on extra hours, which is usually what they want.
Explicit thanks, in front of people.
And where the role has effectively become different, a conversation about pay.
Informal reliance maintained with nothing in return is how it ends.
The quiet version of the problem
Sometimes they are available because they need the hours, not because they are willing.
Which is a different situation and is worth knowing — it means the dependency is on somebody's financial pressure, and it ends when that changes.
What to do first
Count it: what share of short-notice cover came from one person.
If it is large, that is a single point of failure with a human attached, and the single-point note applies.
What to check
Who is your always-available person?
What share of cover came from them?
Have you asked whether it is sustainable?
And what do they get for it?