For years, “being committed” at work has been confused with “being available”. A quick reply at 8pm becomes normal, then expected. A late-night Teams message turns into a culture of constant checking. Before long, you’re working two shifts: your contracted hours, plus the invisible one that happens in the gaps between dinner, family time and sleep.
It’s not sustainable. And it’s not actually good for performance.
That’s why the “right to disconnect” has become a modern workplace talking point. But even where employers make policy commitments, the real question is whether day-to-day behaviour changes — and whether people feel safe enough to switch off.
Why switching off has become harder
Most workplaces have more channels than ever: email, chat, project tools, shared docs, calls, group messages. The volume creates a tempting illusion: if we just stay responsive, we’ll stay on top of it.
In reality, constant connection usually does three things:
- it stretches the working day without reducing the workload
- it makes people feel “always behind”, even when they’re doing well
- it increases errors, because tired brains make worse decisions
The pressure isn’t always coming from a boss, either. It can come from clients, colleagues, or a team that’s been through restructures and is trying to prove it can cope with fewer people. When organisations are under strain, boundaries are often the first thing to go.
What the “right to disconnect” is really trying to fix
A policy is useful, but only if it’s solving the correct problem.
The right to disconnect isn’t just about banning messages after a certain time. It’s about reducing unreasonable expectation. Many people don’t mind the occasional out-of-hours issue. What causes stress is the sense that you must always be reachable, and that your reputation depends on it.
A strong approach usually includes:
- clear definitions of “urgent” versus “can wait”
- agreed response times (so silence doesn’t feel risky)
- leadership modelling (boundaries are taught by behaviour, not posters)
- practical defaults (delay-send, quiet hours, fewer “cc” chains)
If you want a simple way to tell whether your workplace is serious, ask: Does the policy change what managers praise and reward? If the heroes are still the people replying instantly at all hours, the policy will struggle.
Boundaries fail when performance expectations stay unrealistic
This is where employers and employees often talk past each other.
Employees hear: “You can switch off.”
But they also hear: “Targets stay the same, deadlines stay the same, headcount is down, and you’re being measured more closely.”
That mismatch is exactly how you end up with “quiet quitting” debates — people doing what they were hired to do, and opting out of the unspoken expectation to constantly go above and beyond.
A more honest conversation is this: if you genuinely want people to switch off, you may need to reset what “good performance” looks like. Not lower standards — but align standards with reality.
A practical boundary framework for teams
If you’re trying to make boundaries real (without turning work into a rigid clock-watching exercise), the easiest win is to agree a few team-level rules that remove ambiguity.
Here’s a workable framework:
1) Define “urgent” in plain English
Not “high priority”. Not “ASAP”. Actual examples.
Urgent might mean: safety, legal risk, payroll, critical client outage, or a deadline that expires within 24 hours.
2) Create two response windows
Core hours: normal responsiveness
Out of hours: respond only to urgent items, otherwise next working day
This reduces the “should I reply?” mental load. People stop guessing.
3) Shift from responsiveness to reliability
The goal isn’t instant replies. It’s predictable delivery.
Teams often perform better when they agree when work will be done, rather than when messages will be answered.
4) Put boundaries into the tools
Use delay-send, “quiet hours”, meeting-free blocks, and clear shared calendars. If your defaults encourage interruption, your culture will follow.
What managers can do tomorrow (even without a formal policy)
You don’t need a company-wide change to improve this. Managers can make a noticeable difference quickly, especially in teams under pressure.
Try these:
- Stop rewarding visibility. Praise outcomes, not late-night messages.
- Protect deep work. Fewer “quick calls”, more planned time.
- Fix the “everything is urgent” habit. If everything is urgent, nothing is.
- Be explicit about response time. “No need to reply tonight” is powerful when said consistently.
- Check workload properly. If switching off is impossible, that’s a workload issue, not a resilience issue.
One small but effective habit: when you send a message out of hours, add a line like, “For tomorrow — no need to respond tonight.” It’s not perfect, but it helps break the assumption cycle.
What employees can do without looking “difficult”
Boundaries are easier if you can set them without sounding defensive. The trick is to anchor your boundary in delivery.
Useful phrases include:
- “I’ll pick this up first thing tomorrow and confirm by 10am.”
- “If this is urgent for tonight, can you let me know what deadline we’re working to?”
- “I can do X by Friday, or Y by Wednesday — which matters more?”
- “I’m offline now, but I can respond during core hours.”
These responses do two things at once: they protect your time and show ownership. Most reasonable people respond well to clarity.
How to introduce a “right to disconnect” without making it feel like a crackdown
Some organisations worry that boundaries mean lower effort. In practice, the opposite is often true: when people can recover properly, they concentrate better, make fewer mistakes, and stay longer.
If you’re writing or refreshing a policy, focus on what helps work get done:
- make it a performance support policy, not a wellbeing slogan
- set expectations for leaders first (people watch managers)
- explain exceptions clearly (and keep them rare)
- review workload and resourcing alongside the policy
You can also run a simple pulse check after a few weeks: Do people feel safer not replying out of hours? If the answer is no, the issue is culture, not wording.
The bottom line
The modern workplace doesn’t need more availability. It needs better decisions about what matters, clearer expectations, and healthier recovery time so people can do their best work consistently.
A right to disconnect can help — but only when it’s paired with realistic performance expectations and leadership behaviour that backs it up.
