Right to Disconnect in Remote Work: What Teams Need

Right to disconnect legislation is expanding. France had it in 2017. Ontario added it in 2022. The EU has been pushing for it. A growing number of countries and companies have formal policies that employees have a right not to respond to work communications outside business hours.

These policies are well-intentioned. Most of them do not work. Not because the intent is wrong — disconnecting from work after hours is genuinely important for sustained performance and basic human health — but because they treat a structural problem as a policy problem. And structural problems do not respond to policy mandates without the structure to back them up.

Why people actually check Slack at 11pm

The reason people check messages after hours is not that they are bad at setting boundaries or that their employer is explicitly demanding it. The reason is anxiety about information asymmetry.

They check because they are afraid that something happened while they were offline that will create a blocker tomorrow morning — and they will be the last to know. They check because in a synchronous work culture, the person who is absent when a decision is made often ends up re-litigating the decision, or worse, executing against it without knowing it was made. They check because the cost of being offline is often higher than the cost of a quick check.

A policy that says "you have the right not to check" does not change that calculus. It just adds guilt to the equation — now they feel bad for checking while also feeling anxious about not checking.

The structural problem underneath this pattern is the absence of declared state. Teams where people constantly check after hours are teams where the current state of work is opaque unless you are actively monitoring the communication channels. Nobody can safely disconnect because disconnecting means accepting information blindness.

Declared state is the actual fix

The right to disconnect becomes real when disconnecting does not mean becoming blind to what matters. That requires a different infrastructure than most teams have.

Specifically: if every team member's current work state, decisions made, and open blockers are explicitly declared and accessible without monitoring a stream of messages — then disconnecting is safe. You can check the declared state in two minutes tomorrow morning and be fully current. The compulsive after-hours check disappears because the information anxiety that drove it has been eliminated.

This is not a new idea. It is how good asynchronous teams have always operated. The discipline of declaring your state — what you shipped today, what decisions you made, what is blocked and why, what you need from whom — is the discipline that makes genuine disconnection possible.

What the infrastructure of disconnection looks like

Teams that have successfully built genuine disconnection culture share several structural properties that have nothing to do with policies:

End-of-day wrap declarations. Team members declare their state at end of day in a structured format — not a narrative status update, but a machine-readable declaration of current work state. What was completed. What decisions were made. What is blocked. What is needed. This takes five minutes and eliminates the information asymmetry that drives after-hours checking.

Explicit urgency protocols. When something is genuinely urgent — the kind of thing that actually warrants interrupting someone's evening — there is an explicit, high-friction escalation path that both parties understand. Slack DMs are not that path. The high friction is the feature: it forces the person escalating to actually ask "is this urgent enough to use the escalation path?" Most things are not.

Decision trails that survive absence. If a decision is made while someone is offline, there must be a record of it that is findable without monitoring the message stream. Not just "the decision was made in Slack" — an explicit declaration that a decision was made, what it was, who made it, and what context informed it. Coming back from offline should mean reviewing declarations, not scrolling message history.

No implied urgency in async messages. A Slack message sent at 10pm is not an urgent request. But in cultures where the default response to any message is "respond as fast as possible," sending a message at 10pm effectively pages the recipient. Fixing this is cultural — the sender has to normalize "I sent this for when you're next working, not now" — but it can be reinforced structurally by systems that hold messages for delivery within declared working hours.

The manager's responsibility

Most right-to-disconnect initiatives put the responsibility on employees to enforce their own boundaries. That is backwards.

If managers message team members after hours, respond quickly to evening messages, or implicitly expect responsiveness outside working hours — no policy will change the incentive structure for employees. The manager is the model. If the manager disconnects genuinely and makes it structurally easy for the team to do the same, most people will follow.

The manager's job is not to tell people they can disconnect. It is to build the infrastructure — declared state, explicit urgency protocols, decision trails — that makes disconnecting safe. When that infrastructure exists, the policy becomes redundant. When it does not exist, the policy is theater.

Frequently asked questions

Do right-to-disconnect laws actually work?

Evidence is mixed. Laws raise awareness and create legal protection for employees who choose to enforce the right. They do not change the underlying structural conditions that make disconnecting feel risky. Organizations that pair the legal framework with structural changes — declared state infrastructure, explicit urgency protocols, manager modeling — see real behavior change. Organizations that treat the law as a compliance checkbox see minimal change in actual behavior.

What is the difference between async culture and right to disconnect?

Async culture is the practice that makes right to disconnect possible. Right to disconnect is the policy. You can have the policy without the practice — which is what most organizations have, and it does not work well. You can also have the practice without the policy — many fully async teams have genuine disconnection without ever articulating it as a right. The practice is the foundation. The policy formalizes and protects it.

How do you handle time-zone overlap in global distributed teams?

The time-zone question is where declared state matters most. If your only overlap window is two hours in the middle of your day, every piece of information that needs to be available across time zones must be in declared, accessible form — not stuck in a conversation that happened during the overlap window. Global teams that do this well treat async documentation not as a courtesy but as a structural requirement for their time-zone spread.