The right to disconnect in India
Reviewed by Mellow Editorial Team, HR & payroll content team
Employees in India do not yet have a statutory right to disconnect from work outside office hours — no central law currently compels employers to limit after-hours contact. That said, the conversation is active, and employers who ignore it take on real risks.
Where India stands legally
No central legislation grants employees a formal right to disconnect. The four consolidated Labour Codes, which came into force in 2025, modernised large parts of Indian employment law — covering wages, industrial relations, social security and occupational safety — but they do not address after-hours communication or the expectation of constant availability.
A few states have moved ahead independently. Maharashtra introduced a Right to Disconnect Bill in 2018, though it has not been enacted into law. These state-level attempts signal growing political interest, but employers cannot yet treat any of them as binding obligations across India.
International context matters here. France, Portugal, Belgium and Australia have introduced statutory disconnect rights at various levels. India's employment law community watches these developments closely. It would be reasonable to expect Indian legislation to follow in the medium term, particularly as remote and hybrid work have become standard in sectors like IT, consulting and financial services.
What the existing law does say
While there is no explicit right to disconnect, existing law is not silent on working hours.
The Industrial Employment (Standing Orders) Act, and now the provisions folded into the Labour Codes, set out requirements around working hours, rest intervals and overtime for relevant categories of workers. The Occupational Safety, Health and Working Conditions Code includes provisions on daily and weekly working hour limits for certain industries and worker categories.
The practical problem is coverage. Many white-collar, managerial and supervisory employees fall outside the specific protections that cap hours for factory or shop-floor workers. For this category — which includes most of the workforce most likely to receive a late-night Slack message — statutory hour protections are limited or unenforced.
Separately, courts have in various contexts recognised an employer's duty of care toward employees. Persistent overwork that leads to documented harm could, in principle, form the basis of a dispute, though this remains an underdeveloped area.
The business case for a disconnect policy
Even without a legal requirement, there are practical reasons to act now.
Attrition cost. In sectors where talent is competitive — IT services, startups, professional services — burnout is a leading reason people leave. The cost of replacing an employee, accounting for recruitment, onboarding and lost productivity, is significant. A policy that protects rest time is cheaper than constant churn.
Manager behaviour. Most after-hours contact is not malicious. Managers send messages when they think of something, assuming the recipient will reply when ready. Without a written policy, employees often feel they have no legitimate basis to wait until morning. A policy gives them that basis and removes ambiguity for both sides.
Legal positioning. If India does introduce statutory disconnect rights — through central legislation or active state enforcement — employers who already have a functioning policy will be far better placed to demonstrate compliance than those starting from scratch.
Mental health and productivity. The evidence that sustained always-on availability reduces cognitive performance is well established. Employees who rest properly make fewer errors and produce better work. A disconnect policy is not a concession; it is sensible workforce management.
What a practical disconnect policy covers
A policy does not need to be complex. The core elements are:
Defined hours. State clearly what the expected working hours are for each role or band. Outside those hours, employees are not expected to read or respond to messages unless there is a genuine emergency.
Emergency definition. Specify what counts as an emergency requiring a response. This is important — without it, "urgent" becomes whatever the sender decides it is.
Manager obligations. Make it explicit that managers should not expect immediate responses to non-urgent messages sent outside hours. Some organisations use delayed-send features to reduce pressure even when a manager works late.
On-call arrangements. If certain roles require genuine availability outside normal hours — system administrators, support teams — document this separately with appropriate compensation, consistent with the wage and overtime provisions in the Labour Codes.
Escalation. Give employees a clear route to raise concerns if the policy is not being followed in their team, without fear of it being treated as a performance issue.
How to introduce it without disruption
Start with a conversation, not a memo. Teams that have operated with informal always-on expectations may find a hard cut-off jarring if it is imposed without context. Explain the rationale, address concerns about client-facing roles, and give managers time to adjust their own habits.
Review the policy after three to six months. What works for a software development team may not work for a client services team with overseas counterparts. Building in a review signals that this is genuine policy, not a gesture.
---
Run HR and payroll in India with Mellow
Mellow brings HR, payroll and 12 AI agents into one platform — built to handle India properly, with payroll included, from £4 per employee per month. The AI agents don't just answer questions; they generate contracts, run cost estimates and draft letters for you.
[Start a free trial →](/register)