When Australia’s right-to-disconnect law finally covered small employers in August 2025, I heard the same refrain from global ops leaders: “Our Australian team is now unreachable after 6 p.m.” That’s not what the law says. It’s the myth to kill.
The law isn't a curfew
Australia’s rules don’t ban after-hours contact. They give employees the right to refuse to monitor, read, or respond outside working hours—unless that refusal is unreasonable. The law itself lists factors: why the contact was made, how it was made, whether the employee is paid for availability, their role, and their personal circumstances. A customer-down emergency still gets a call. A routine status update on a Sunday doesn’t require an answer. That’s not a ban; it’s a forcing function for clarity.
The real exposure is ambiguity
Most managers don’t actually want to interrupt dinner. They want plausible deniability: no explicit on-call duty, but an unspoken expectation that good people reply. That ambiguity was already a retention problem. Australia just made it a legal one. If after-hours responsiveness matters to the job, write it into the role, pay for it, and schedule it. If it doesn’t, stop measuring it.
What I tell leaders
Treat the law as documentation of what should already be operating practice. Define escalation paths. Distinguish urgent from convenient. Train managers that “I didn’t see it” is a legitimate answer when no one defined the interval. The payoff is better handoffs, not less access.
The countries that adopt right-to-disconnect laws are telling executives something important: if your operating model depends on voluntary always-on behavior, you don’t have a flexibility strategy—you have an unmanaged overload problem. Fix the model, and the legal risk disappears.