Practice knowledge base
Right-to-Disconnect (Quiet Hours)
The Right to Disconnect establishes quiet hours and rules for urgent communications, allowing people to recover without constantly expecting work messages.
Documentation sections
What it is
This is an organizational policy on non-working time: when the team is not expected to respond, which channels are considered urgent, and what requests should not be sent in the evenings, on weekends, or during vacation. It addresses the issue of "hidden availability," where work messages are formally optional but people still feel pressure to respond. This practice works best when the company already has clear priorities and escalation rules.
When it helps
- Employees respond to work messages in the evening, even though it is not part of their agreement.
- People return from weekends or vacations without feeling fully recovered.
- Managers send non-urgent tasks outside working hours and expect a quick response.
- Teams on different schedules do not differentiate between urgent incidents and routine inquiries.
- Reports show complaints about work-life balance.
How to start
- 1 Define quiet hours for the entire organization or specific work schedules.
- 2 Document which topics are considered urgent and who is authorized to initiate escalation.
- 3 Set up delayed message sending for non-urgent requests outside working hours.
- 4 Ask managers to communicate the rule: not responding during quiet hours is not an issue.
- 5 After a month, review which exceptions arose and which rules need to be clarified.
Expected effect
The team gains a clear boundary between work and recovery: less background expectation of messages, easier to plan personal time and vacations. Managers find it easier to distinguish truly urgent cases from tasks that can be addressed during working hours.
Common pitfalls
- The rule is announced, but managers continue to send messages in the evening and thank employees for quick responses.
- All exceptions are labeled as urgent, so quiet hours quickly lose their meaning.
- The policy is introduced without on-call rules for roles where genuine incidents can occur outside regular hours.
- Teams in different time zones do not agree on whose working hours are considered baseline.
- The practice is used as a substitute for workload management, even though the volume of work remains unchanged.
Further reading
- Report: Eurofound, Right to disconnect: implementation and impact at company level
- Research: Sonnentag and Fritz, Recovery from job stress: the stressor-detachment model
- Book: Cal Newport, A World Without Email
FAQ
Who should own this policy?
Typically, the policy is initiated by leadership together with HR, but its daily enforcement is supported by managers. If a manager sends non-urgent messages at night themselves, the team will view this as the actual norm.
Can you start without a comprehensive policy?
Yes. Start with a simple agreement: hours without expectation of response, a list of urgent cases, and an escalation channel. After the first few contentious situations, refine the wording.
What to do about truly urgent matters?
Outline a separate procedure: who is on call, which channel is used, and what topics are considered incidents. Routine tasks should not be routed through this channel.
How can you tell if the practice is working?
Observe recurring indicators: fewer non-urgent messages outside scheduled hours, fewer complaints about inability to disconnect, and clearer reasons for exceptions to the rule.