Out-of-hours messages and the right to disconnect

These are listed in the order worth acting on, which with out-of-hours contact is not the order they are usually presented in.

Why a two-minute message is not two minutes

The cost of an out-of-hours message is not the reply but the attention it occupies for the rest of the evening. Knowing that messages may arrive changes behaviour even when none do, because the phone has to be monitored.

That monitoring is a mild form of being on call, and it is entirely unpaid and entirely uncounted. Where it is frequent, the effective working day extends well beyond anything on the contract. The distinction that matters is between occasional genuine urgency and a routine expectation of availability.

Where the rules are moving

Several countries have introduced or debated a right to disconnect, requiring employers to define when contact is expected. The approaches vary from statutory obligations, to a requirement to negotiate a policy, to non-binding guidance.

Elsewhere the question is handled through working time rules, which cover on-call arrangements rather than messaging specifically. Because the position differs so much by country and continues to develop, checking your own jurisdiction is essential. This is general information rather than legal advice, and a union or labour authority will know the current position where you work.

Culture beats policy every time

A written policy discouraging evening contact has little effect where senior people send messages at night. Junior staff read the timestamp rather than the policy, and they respond because they can see who is watching.

Delayed sending is the simplest fix available, since it lets people work when they want without setting an expectation for others. Making response time expectations explicit, by channel, removes most of the ambiguity that causes the problem. Where genuine urgency exists, a defined escalation route stops everything else being treated as urgent by default.

Remote work made it worse

Removing the commute removed the boundary that used to end the working day physically as well as formally. Working in the same room where you rest makes the equipment always present and the shutdown always optional. Time zones across distributed teams create genuine overlap problems that get solved by individuals stretching their days.

Put simply, where a team spans several regions, rotating the inconvenient meeting time is the fair solution and is rarely the default one. Asking for core hours to be defined is a reasonable request that helps everyone, including the people making the requests.

Setting a boundary without damage

State your availability plainly rather than apologising for it, since a stated norm is easier to respect than an implied one. Agree with your manager what genuinely constitutes an emergency and how it will be communicated. Use the tools rather than willpower: notification schedules, separate work profiles and delayed sending do more than intentions.

Respond within your stated hours consistently, because inconsistency teaches people to keep trying outside them. Where the role genuinely requires availability, that is an on-call arrangement and should be recognised and paid as one.

When it is really on-call work

If you must remain reachable and able to respond, the arrangement resembles standby regardless of what it is called. Many systems treat constrained availability differently from free time, particularly where response is required quickly. The relevant test is usually how much the requirement restricts what you can do, rather than how often you are actually contacted.

Where availability is a real requirement of the role, it belongs in the contract with a payment attached. Raising it as a request to formalise the arrangement is more productive than raising it as a complaint about messages.

Everything above, in order of what to do first

1. Why a two-minute message is not two minutes. The cost of an out-of-hours message is not the reply but the attention it occupies for the rest of the evening.
2. Where the rules are moving. Several countries have introduced or debated a right to disconnect, requiring employers to define when contact is expected.
3. Culture beats policy every time. A written policy discouraging evening contact has little effect where senior people send messages at night.
4. Remote work made it worse. Removing the commute removed the boundary that used to end the working day physically as well as formally.
5. Setting a boundary without damage. State your availability plainly rather than apologising for it, since a stated norm is easier to respect than an implied one.
6. When it is really on-call work. If you must remain reachable and able to respond, the arrangement resembles standby regardless of what it is called.

The takeaway

Define availability and what counts as urgent, in writing; if reachability is required, it is on-call and should be paid.

Small and repeatable beats ambitious and abandoned, almost every time.