Right to Disconnect Laws Are Spreading. Your After-Hours Messages Need to Catch Up

You send a message at 9 p.m. because that happened to be the moment you finished the thought, not because anyone needs to act on it tonight. The person receiving it cannot tell the difference. A notification carries no context about why it arrived when it did, only that it arrived, and for a lot of people that alone reads as an expectation.

That gap between intent and reception used to be purely a matter of team culture. In a growing number of countries it is now a matter of law. Australia’s Fair Work Ombudsman confirms that the right to disconnect extended to small business employees on 26 August 2025, a year after the same protection took effect for larger employers. France, Portugal, Spain, Belgium, Italy, and Ireland already have some version of a right to disconnect on the books too, though the form varies from an enforceable statute to a non-binding code of practice, so the practical protection differs by country.

None of these laws stop you from sending the message. What they change is who bears the cost of an unclear one. An employee in a covered jurisdiction can now ignore an after-hours ping without it counting against them. The ambiguity you used to leave in the message, the one that let the reader guess whether “when you get a chance” meant tonight or next week, is no longer a minor stylistic tic. It is a cost you are now handing to someone with a legal basis to push back on it.

The Law Protects The Receiver, Not Your Habits

Right to disconnect legislation is written from the recipient’s side. It gives an employee the standing to decline to monitor, read, or respond outside working hours, and it protects them from being penalized for that refusal.

It says nothing about when you are allowed to write or send. You can still work at whatever hour suits you. What the law removes is the assumption that your timing automatically becomes their obligation. That assumption was doing a lot of quiet work in most workplace messaging, and it is worth noticing how often a message relied on it without saying so.

Say When You Do Not Need A Reply

The fix is not to stop sending messages outside working hours. It is to stop letting the timestamp do the talking.

Before:

Can you take a look at the Peterson deck tonight? I want to have it ready first thing.

After:

Sending you the Peterson deck now while it is fresh in my head. No need to open it tonight, tomorrow morning works fine, and if you see this after your working hours, it can sit until you are back online.

The second version separates two facts the first one had merged into one timestamp: when the sender did the work, and when a response is actually needed. Once those are stated separately, the reader does not have to infer either one.

Time The Message, Not Just The Wording

Most mail and chat clients now have a scheduled or delayed send option, and it costs nothing to use it. If the content does not need to land at 9 p.m., set it to arrive at 8 a.m. instead. A message that never appears cannot be seen, ignored, or worried about, which does more for the recipient than any amount of careful phrasing.

Phrasing still matters when timing the send is not practical, an urgent shift handoff, say, or a message to someone in a timezone with no good hour to wait for. A Wrivio Context for this situation could say:

Rewrite this as a calm, low-pressure message. State explicitly that no reply is expected outside normal working hours. Keep every name, date, figure, and commitment exactly as written. Do not add urgency language, and do not soften “no reply needed” into something vaguer like “whenever you get a chance.”

Press Ctrl+Shift+Space, paste the draft, and check the diff for that last part specifically. “Whenever you get a chance” still reads as a soft deadline to a lot of people, and a rewrite that trades an explicit non-urgency line for it has made the message worse, not better, even though it sounds friendlier.

Distributed Teams Make Every Hour Someone’s After Hours

On a team spread across three or more timezones, no send time falls inside everyone’s working day. The default framing you build into your own messages matters more than any individual judgment call, because you will not always remember to make that call, and your teammates cannot tell whether you did.

This connects to the timing problems in cross-cultural email etiquette for global teams: the same words carry different implied urgency depending on the reader’s convention, on top of whatever the send time already implies. A professional out-of-office message solves this for planned absences. Right to disconnect phrasing is the version for an ordinary Tuesday evening, when nobody is away and the ambiguity is just an unbroken habit.

What Good Phrasing Does Not Fix

Being explicit about urgency removes the excuse for treating a message as a deadline. It does not remove the notification, or the moment of seeing a work message light up your phone at dinner. Right to disconnect laws address that moment directly, by making it acceptable to leave the notification unread until morning regardless of how it was worded.

Writing and policy solve different halves of the same problem. A team that fixes its message defaults but leaves after-hours notifications on for everyone has only done half the work. The other half is a settings change, not a writing habit, and it deserves its own conversation rather than an assumption that better phrasing will quietly cover for it.

Common Questions

Does the right to disconnect mean I cannot send work emails after 6 p.m.?

No. The laws in effect in Australia, France, and other countries restrict the obligation to respond, not the ability to send. You can write and send whenever you want; the recipient gains the standing to leave it until their next working hour without penalty.

Is there a right to disconnect law in the United States?

Not currently at the federal level, and no US state had one in force as of this writing. Several states have proposed similar bills in recent legislative sessions, but proposals have stalled or been withdrawn rather than enacted, so treat any claim that a specific US state has passed one with caution until you can confirm it against that state’s own legislature.

What if my job genuinely requires after-hours availability?

Most right to disconnect frameworks, including Australia’s, allow for reasonable exceptions tied to role, seniority, and how the refusal is judged, not a blanket ban on out-of-hours contact. If availability is a real part of the role, say so directly in the message rather than leaving it to be assumed, since the assumption is exactly what the law now lets people decline.

Does marking a message “low priority” actually help?

It helps less than a plain sentence stating when a reply is needed, because priority flags are inconsistently supported across email and chat clients and are easy to miss entirely in a busy inbox. A sentence in the body of the message survives every client and every notification setting.

Download Wrivio for Windows and build an after-hours context once so every late message states its own urgency correctly, without you having to type the disclaimer by hand each time.