Right to Disconnect Is a Policy. Coverage Is a System.

The right to disconnect sounds like the answer to being always on. Give people the legal right to ignore work after hours and the problem is solved. But a policy that protects your evening does nothing about the work that still needs answering. Those are two different problems, and only one of them is being solved.

What the policy actually does

A right to disconnect is a rule that says your employer cannot punish you for not responding outside working hours. Several countries have some version of it. France is the best known. Australia has more recent rules. The idea is to draw a line: after this hour, your time is yours, and silence is not insubordination.

In the United States, it is worth being precise, because the picture is often overstated. There is no enacted federal right to disconnect law. Some states have floated bills. California's Assembly Bill 2751, introduced in 2024, would have created such a right, but it did not pass. It died in committee. So for now, a US right to disconnect is a live conversation and a set of proposals, not a law on the books. Any team planning around it should treat it as a direction things may move, not a rule that binds them today.

The policy protects the person, not the work

Here is the gap. A right to disconnect gives a person permission to be offline. It says nothing about what happens to the work while they are.

Picture a teammate who logs off, fully protected by policy, and can ignore every message until morning. Good. Now picture the person in another time zone who needs an answer that only the first person has. The policy did its job for one of them and left the other one stuck. The question does not disappear because someone earned the right to ignore it. It just waits. On a distributed team, someone is always at the start of their day while someone else is protected and offline.

So the policy solves the human problem, which is real and worth solving, and leaves the work problem untouched. People deserve to be off. The work still needs to move. A rule about the first does not address the second.

Why "just wait until they are back" does not scale

The unspoken assumption behind a disconnect policy is that the work can wait. Sometimes it can. Often it cannot, not without cost.

When an answer waits twelve hours for someone to come back online, the person who needed it is blocked for those twelve hours. Multiply that across a team spread over many time zones and the waiting compounds. Each protected evening on one side of the world is a stalled morning on the other. The policy did not remove the delay. It just moved it onto whoever is awake and blocked. Protecting everyone's off hours, one by one, can quietly add up to a team that is always waiting on someone.

Coverage is the part that has to be built

The real fix is not only a rule about when people can be offline. It is a system for what happens to their work while they are. That is coverage, and coverage is not a policy you write. It is something you build.

Coverage means that when a person is off, the things they know are still reachable. Not the person, the knowledge. A teammate should be able to get what they need from the work that was already done, without waking anyone and without violating anyone's right to be offline. When that exists, the policy and the work stop being in conflict. People can be genuinely off, because their absence no longer strands anyone.

Without coverage, a disconnect policy forces a bad choice. Either people quietly break the policy to keep things moving, which makes the right hollow, or they honor it and the team eats the delay. A right that only holds when nothing urgent is happening is not much of a right.

Build the system so the policy can be real

The lesson is that the two problems need two solutions. A right to disconnect handles the human side, whether it arrives by law, as it may in time in more places, or as a norm your team adopts on its own. Coverage handles the work side, and no law will build it for you. You have to.

This is the narrow thing StandIn is for. Each person writes a short brief at the end of their day, and while they are off, it answers their teammates from what they actually wrote down, with a source under each answer. When the answer is not in the record, it says so instead of guessing. It does not ask anyone to be reachable after hours. It makes the work reachable instead of the person, so being offline stops meaning being a blocker. A policy can give people the right to disconnect. A system is what lets them actually take it.