The Quiet Cost of Always Being Reachable

Most businesses have someone whose phone number everyone seems to have. Staff, customers, suppliers, the security company, the landlord. If something is unclear, they are the person to try. If something goes wrong out of hours, they are the person who gets the call.

Nobody appointed them to this. There is no on-call rota with their name on it and no allowance for it in their contract. It simply happened, usually because they were reliable, because they answered once and then again, and because the business had no other arrangement.

This Moment is about that role: the unofficial, always-reachable person, and what the arrangement quietly asks of them.

Reachable is not the same as working

Being reachable is not the same as working, which is part of why its cost is easy to miss. The always-reachable person may get only a handful of calls in a week. Many evenings nothing happens at all.

But reachability has a cost even when nothing happens. The phone has to stay on and nearby. Plans are made with a small reservation: will I have signal there, can I step out if something comes up. Attention is never entirely given to whatever else is going on, because part of it is listening for the phone.

It would go beyond the evidence to claim that everyone in this position experiences that as a burden. Some people are comfortable being the dependable one; for some it is part of why they enjoy their role. What can be said is that the arrangement has a structure, and the structure consumes something, whether or not a call ever comes.

Why availability becomes unwritten

In larger organisations with round-the-clock operations, reachability is usually formalised. Incident tools such as PagerDuty describe escalation policies that notify whoever is currently on call according to a schedule, and move to the next person if the first does not respond in a set time. The point of such systems is that availability is defined: it belongs to a role and a time slot, not to whichever individual happened to answer last time.

Smaller businesses rarely need anything that elaborate. But the absence of any arrangement has a predictable result. When there is no defined route for out-of-hours questions, the questions follow the path of least resistance, which is the person most likely to answer. Each time they answer, the path gets a little more established.

The WHO and ILO make a related point in their guidance on healthy teleworking. Among their recommendations is that organisations agree on a common system to signal availability for work, and that managers respect it. That guidance was written about remote work, but its underlying observation applies widely: when availability is not explicitly agreed, it tends to expand.

An illustrative case

Consider an illustrative example, not a real business: a Polokwane property management company with about twenty staff, looking after residential complexes for body corporates and landlords.

In this scenario, the operations manager has become the after-hours contact for almost everything: gate motors failing, water leaks, tenants locked out, contractors who cannot find a key. Residents have their cellphone number from an old notice. Contractors call them because they once sorted out an access problem late at night. The owner forwards urgent messages to them because they always know what to do.

There is no formal standby arrangement. The operations manager handles a few calls a week, sometimes none. They also have not switched their phone off on a weekend in a long time.

The human tax

The first tax is presence: the ability to be fully where one physically is. A dinner, a match, a long drive or an afternoon asleep can all be partly occupied by the possibility of a call.

The second is autonomy: the practical freedom to decide when one is off. The always-reachable person can, in principle, switch off. In practice, they know that if they do, the call will go nowhere, and something may go wrong that they could have prevented.

The third is energy, spent less in the calls themselves than in the low-level vigilance between them.

What could realistically change

The aim is not to make the business unreachable. Some situations genuinely need a response at night. The aim is to make reachability a deliberate arrangement rather than an accident.

Decide what genuinely needs an out-of-hours response. A burst pipe may; a question about next month's levy statement does not. A short written list makes it easier for everyone, including the person answering, to say "that can wait until morning".
Route out-of-hours contact to a role, not a person. A dedicated number or shared address that can be passed between people, rather than one individual's cellphone.
Share the load. Even a simple rotation between two or three people means each has weeks that are genuinely off. Where that is not possible, an agreed arrangement with a contractor or answering service may be.
Make availability visible. Microsoft's support documentation for Teams describes quiet time on mobile devices, which silences notifications on a schedule, and notes that others cannot see that someone is in quiet time, so a status message is needed to communicate availability. The tool is useful, but the documentation makes the deeper point: switching off only works if other people know.
Recognise the role. If someone is genuinely on standby, that is work. Treating it as such, in contracts, time off or pay, makes the arrangement honest.

What changes first, and for the business

The first change is that out-of-hours contacts go somewhere defined, and the always-reachable person stops being the default destination. Calls that do not need an immediate answer start waiting until morning, because there is a shared understanding that they can.

For the business, the outcome is resilience. Out-of-hours response no longer depends on one individual being available and well. Mellorca has looked at this risk directly in the cost of key-person operational dependency and argued in why key-person dependency is a systems problem that it is a matter of design rather than personality.

The human dividend

The dividend is autonomy and presence. On the weeks they are not covering, the person who used to be always reachable can be genuinely unreachable, and know that nothing is falling through because of it. On the weeks they are covering, they know what they are covering and for how long.

That predictability matters. A defined week of standby, followed by a week off, is a different thing to live with than an open-ended expectation that never quite switches off. It gives the person back the ability to decide where their attention goes.

The trade-offs

Some responsiveness may be lost. A rotation means the person answering may know less about a particular issue than the one who used to handle everything. Response may be slower or less informed at first.
Customers may notice. Residents or clients used to calling a familiar person directly may find a shared number less personal.
Formal standby has a cost. Paying or compensating for on-call time makes a hidden cost visible, which some businesses will find uncomfortable.
The person may resist. For some, being the one who can always be reached is part of their identity at work. Changing it needs care and conversation, not just a new number.

Why it matters

The cost of always being reachable is quiet precisely because it usually produces nothing visible. No overtime claim, no incident report, no complaint. Just a person who has not fully switched off in a long time.

Mellorca's reading is that availability should be designed, not inherited. Deciding who is reachable, when, and for what, returns to that person something that rarely appears on any list of business benefits: the ability to be entirely somewhere else. Related Moments look at nearby pressures: the inbox that follows you home and the notification you check before you sleep.

Sources and further reading

Crucial changes needed to protect workers’ health while teleworking (last verified 10 October 2026)
Escalation Policy Basics (last verified 10 October 2026)
Quiet time in Microsoft Teams for mobile devices - Microsoft Support (last verified 10 October 2026)