France pioneered the legal right to disconnect in 2017 through the El Khomri law, which requires companies with 50 or more employees to negotiate disconnect policies with staff representatives. Australia's Fair Work Act now gives employees an enforceable right to ignore out-of-hours contact from their employer unless refusing would be unreasonable. Spain, Italy, Belgium, Portugal, and Ireland have all adopted some version of the same idea over the years since, each with its own scope and enforcement mechanism. The US, notably, has nothing at the federal level, and most American workers are left negotiating this boundary informally, one manager at a time, with no legal backstop if the negotiation doesn't go their way.
What These Laws Actually Do, and Don't Do
It's worth being precise about what "right to disconnect" means legally, because the popular framing oversells it a little. None of these laws ban employers from sending a message after hours. What they generally do is remove the obligation to respond, and prohibit retaliation against someone for not responding — France's law, for instance, requires companies to negotiate the boundaries of that right with employee representatives rather than dictating a single national cutoff time. Australia's version is similarly conditional: an employee can refuse out-of-hours contact unless that refusal would be unreasonable, with "unreasonable" weighed against factors like the person's role, how they're compensated for availability, and the nature of the contact. That's a meaningfully different thing from an absolute ban on after-hours messages, and it's worth understanding the actual mechanism rather than assuming these laws work like an on/off switch.
The genuine emergencies carve-out matters too, and it's present in every version of this law I'm aware of. A real safety issue, a security breach, or a scheduled, pre-agreed deadline during an unusual crunch period isn't what these laws are trying to stop. What they target is the routine, non-urgent message sent at 9 PM because it happened to occur to someone then, with an implicit expectation of a same-evening reply — the pattern that turns "flexible work" into "work that never actually stops."
The Corporate Examples Worth Knowing
A couple of well-known corporate responses predate the legal wave and are worth understanding on their own terms, separate from any law. Volkswagen's German operations became known for configuring email servers to stop routing messages to certain groups of employees' phones outside shift hours — a technical solution to a cultural problem, applied to the workers it covered rather than as a blanket company-wide policy. Daimler drew similar attention for an opt-in feature that let employees have incoming email during vacation auto-deleted, with the sender notified and given an alternative contact for anything urgent — a clever inversion of the usual expectation, since it protected the vacationing employee without requiring them to do anything once they'd turned it on. Both are frequently cited as early proof that a large, traditional company can meaningfully reduce after-hours contact through configuration and policy rather than relying purely on employees enforcing their own boundaries — worth knowing about, even without pretending to know the exact compliance numbers each company reported internally.
Where I'd Push Back on the Common Objections
"Our industry needs 24/7 responsiveness" is the objection I hear most, and it deserves a real answer rather than a dismissal. For genuinely client-facing, time-sensitive roles, the honest solution isn't pretending disconnection is universally possible — it's a compensated, rotating on-call structure, where the people covering after-hours availability are explicitly paid for it and know in advance when their turn comes, rather than an ambient expectation that everyone is reachable, always, for free. That's a real accommodation, not a workaround that quietly reintroduces the always-on problem under a different name.
"Global teams across time zones make this impossible" is a real operational challenge, not a dismissible complaint — but the fix is more often async-first communication and rotating meeting times across the team, so the burden of an inconvenient hour doesn't land on the same people every single time, rather than concluding that disconnection simply doesn't apply to distributed teams.
The objection I'd push back on hardest is "good employees want to be available." In my experience managing a team, availability and dedication aren't the same trait, and treating them as interchangeable rewards the wrong thing — a person who answers messages at 11 PM isn't necessarily doing better work than one who's fully present during work hours and fully disconnected afterward; they might just be worse at managing their own time, or worse at saying no. Rewarding visible availability over actual output is a values choice a company is making, not a neutral read of who the good employees are.
What This Actually Means for You, Practically
If you're in a country with a real legal right to disconnect, know the specifics of your protection rather than assuming it's absolute — understand what counts as an emergency exception under your specific law, and understand that the obligation removed is to respond, not the ability of your employer to send a message in the first place. If you're not covered by any such law, the practical tools are the same ones that predate the legislation entirely: turning off notifications for work apps outside your own defined hours, using a scheduled-send feature so your own late-night work doesn't create an expectation of availability in the person receiving it, and having a direct, calm conversation with your manager about what response time is actually reasonable for your role, rather than assuming silence on the topic means the expectation is unlimited.
The clearest signal I'd watch for, regardless of what the law in your country says: does your manager or leadership actually model disconnecting themselves? A written policy that says nobody has to respond after hours, sitting next to a culture where the CEO sends messages at midnight and everyone scrambles to reply, tells you which one is the real policy. Culture eats a written disconnect policy just as reliably as it eats any other stated value that isn't backed up by what leadership actually does.
The broader shift underneath all of this isn't really about specific hours or specific laws — it's a slow correction of the assumption, which crept in over the smartphone era largely without anyone deciding it deliberately, that being reachable at all times is simply part of having a job. It wasn't always assumed, and the fact that a growing number of countries are now writing it back out of the default expectation says something about how far that assumption drifted from anything workers actually agreed to.