The Contactability Levy: Auditing the Cost of Out-of-Hours Quick Questions

The always-on invoice is rarely itemised. A director sends a one-line message at 21:40; a delivery lead answers at 22:05; a supplier is copied; a decision is half-recorded; and the next morning two people rework the same task because neither knows who owns the final call. Individually, such exchanges look trivial. Collectively, they impose a contactability levy on UK teams: a recurring charge paid in fractured attention, duplicated effort and delayed judgement.

For organisations in 2026, the issue is not whether people can be reached. Most can. The question is whether the organisation has decided when reachability is worth its cost, and whether that decision is visible in how work is planned, escalated and reviewed.

The question behind the question

An out-of-hours message is often a symptom rather than a cause. It may signal that a decision right sits too high, that a handover note is incomplete, that a supplier interface is unclear, or that a deadline was accepted without a workable plan. Treating every after-hours query as an unavoidable emergency hides the operational weaknesses that generate it.

The first task is therefore diagnostic. Leaders should ask what the message was really requesting: a fact, a permission, a judgement, a reassurance, or simply a record that someone had thought about the issue. Each carries a different cost and a different remedy. A request for a fact may be solved by better documentation. A request for permission may point to unclear delegated authority. A request for reassurance may reveal a gap in confidence or competence that training, not contactability, should address.

What contactability actually costs

Contactability cost is not limited to overtime or out-of-hours allowances. It includes context switching, reduced recovery time, rework caused by incomplete exchanges, and the slower decisions that occur when ownership is blurred. It also includes the quieter cost of people keeping one eye on messages during what should be protected time.

A useful audit begins with a two-week contact log rather than an opinion survey. Teams should tag messages received outside contracted hours by sender, recipient, topic, whether the response required action, and whether the matter could have waited until the next working day. The log should cover all channels used for operational contact, including chat, email and calls, but it need not capture content. The purpose is pattern recognition, not surveillance.

Four measures are enough to make the issue visible:

• Volume and distribution: how many after-hours contacts occur, and whether they cluster around particular roles, suppliers or deadlines.
• Response latency versus decision latency: how quickly people reply compared with how quickly a decision is actually made and recorded.
• Rework attributable to incomplete exchanges: where the next morning produces duplicate effort because an after-hours answer lacked context or authority.
• Ownership ambiguity: how often the same issue is reopened because no one was clearly accountable for the final call.

These measures should be reviewed by team and by process, not used to rank individuals. The aim is to find where contactability is substituting for design.

Urgency versus convenience

Not every after-hours question is an emergency, and not every emergency arrives after hours. A simple triage test helps. A matter is genuinely urgent if it involves a safety or regulatory obligation, an irreversible deadline, or material customer harm that cannot wait until the next working day. If none of these applies, the default should be asynchronous handling.

That distinction protects real emergencies. When everything is treated as urgent, escalation routes lose credibility and on-call arrangements become a general help desk. Teams then either over-respond to routine queries or under-respond to the one that matters. A written triage rule, agreed with line managers and tested against recent examples, gives people permission to wait without feeling negligent.

Boundaries that protect delivery

Boundaries should be explicit, practical and owned by management. A team might adopt a default response window for non-urgent queries, a named escalation route for genuine incidents, and a quiet-hours convention that applies to internal messages unless the triage test is met. Decision rights should be documented so that routine questions do not travel upwards simply because a senior person is visible online.

Handover discipline matters as much as response discipline. A short end-of-day note covering open decisions, next actions and known risks reduces the need for evening clarification. Where out-of-hours cover is contractually required, it should be defined by event type, response expectation and compensation, not by an assumption that someone will always answer.

Employers should also take advice on contractual terms and working time obligations. The operational point is simpler: a boundary is not a ban. It is a statement that contactability is a designed service, not an ambient expectation.

Making the boundary stick

Boundaries fail when they are announced once and never reviewed. A monthly review of the contact log, alongside incident and delivery metrics, will show whether the new arrangements are reducing rework or simply displacing it. If genuine emergencies are still being missed, the escalation route needs refinement. If routine queries continue to arrive, the underlying decision rights or documentation need attention.

The objective is not to make people unreachable. It is to make contactability intentional, measurable and proportionate. UK teams that audit the always-on invoice can reduce avoidable drag, clarify ownership and preserve the responsiveness that genuine emergencies require.