Skip to content
Working Conditions

All questions  ·  Causes

Nobody is required to work evenings, so why does everyone?

The Erosion of Off-Hours

Availability expectations are set by observed behaviour, not by policy. What actually determines whether people can stop.

Procedure

Almost no organisation requires evening and weekend availability. Many have it anyway, because expectation is set by what people see rather than by what they are told.

How the expectation forms

A senior person sends messages at eleven at night. Nobody said to reply. Several people do, and now the ones who do not look less committed.

Someone answers on holiday and is thanked for it.

A deadline is met by weekend work and the achievement is celebrated.

Response time becomes a proxy for diligence, particularly in distributed teams where it is one of the few visible signals.

Nobody decided any of this. It emerged from individually reasonable acts.

Why it matters more than the hours suggest

Recovery requires psychological detachment, not just physical absence from work. Someone who checks messages twice on a Sunday has not detached.

Anticipation is as costly as the interruption. Not knowing whether something will arrive prevents rest even when nothing does.

It removes the trough. Demanding work with real recovery is sustainable; demanding work with permeable boundaries is the pattern that produces exhaustion.

It is invisible in every metric an organisation normally collects.

What actually works

Senior behaviour, changed. Nothing else in this note matters if leaders continue to send at midnight. If they must work then, scheduling messages to send in the morning costs one setting.

Explicit response norms. Say what response time is expected — genuinely, in hours or days — and say that outside hours the expectation is none.

Name who is on call and who is not. Ambiguity means everyone assumes they might be.

Cover for absence, properly. Most holiday-checking happens because nobody else can handle the thing.

Stop celebrating the weekend rescue. Praise it and you have specified the standard. Ask instead why the weekend was necessary.

Testing the reality

Look at message timestamps in aggregate, by team and by seniority. Not to police individuals — to see what the pattern is.

Ask whether people check messages on leave, anonymously. The answer is usually higher than leadership expects.

Ask whether anyone has ever been criticised for a slow reply outside hours, and whether people believe they would be. The second question is the one that matters, since the expectation is what governs behaviour.

On-call, done properly

Where genuine out-of-hours coverage is needed, it should be designed rather than assumed.

A named rota, with everyone else genuinely off.

Compensated, in time or money.

Frequency capped, with a floor on the gap between rotations.

Escalation criteria so that people are woken only for things that warrant it.

Recovery time after a disrupted night, as a rule rather than a favour.

Reviewed against actual call volume. A rota that fires every night is a staffing problem wearing an on-call costume.

The policy that does not work

A written statement that employees are not expected to work outside hours, with no change in behaviour above.

People read behaviour, not policy. The statement without the behaviour change adds cynicism to the original problem.

Auditing the timestamps

An aggregate look at when work actually happens, used to see the pattern rather than to police individuals.

Message and email volume by hour, across the organisation.

The same, split by level. Senior out-of-hours activity is what sets the norm.

The same, split by team, which shows where the expectation is strongest.

Volume during declared leave, in aggregate.

Do not identify individuals and say so before you start. The purpose is to see the shape of the working day.

Show the chart to the leadership team. A graph with a substantial evening peak makes an argument that no amount of survey commentary achieves.

Defining a response expectation

Ambiguity is what generates continuous checking, and a stated number removes it.

Say the actual expectation in hours, by channel. Email within a working day; chat within a few hours during working hours; nothing outside them.

Say what counts as urgent, and give a separate route for it.

Say who is on call and who is not, by name.

Say what happens if someone does not reply outside hours, which is nothing.

Then have senior people behave accordingly, which is the part that makes it true.