Your phone buzzes at 9pm. It's your manager. Again. The WRC Code of Practice on the Right to Disconnect has been in force since April 2021, and most employees have no idea it exists.

That needs fixing.

The code does not give you an absolute legal right to ignore all contact outside working hours. What it does is create a framework that employers are legally expected to follow, and that the WRC will examine if a complaint lands on their desk. Ireland has embedded this into the Organisation of Working Time Act 1997 landscape, sitting alongside existing rules on rest periods and maximum working hours. The code is not aspirational. It has teeth.

What the Code Actually Says

Three rights sit at the core of it.

The right not to routinely perform work outside your normal working hours. The right not to be penalised for refusing to attend to work matters outside those hours. The right to disconnect from work-related technology.

Each of those words matters. "Routinely" is doing a lot of work in the first one. Emergency contact once a year is different from a manager who treats every Sunday evening like a Monday morning. The pattern is what gets you.

"Penalised" in the second point covers more than sacking someone. Being passed over for promotion, being frozen out, being given the cold shoulder at the next team meeting. Retaliation does not need a P45 attached to it.

What Employers Must Do

The code requires employers to have a formal Right to Disconnect policy. Not a vague line buried in an employee handbook. A standalone document that covers what out-of-hours contact is acceptable, in what circumstances, and through what channels.

That policy has to cover:

  • Expected response times outside working hours
  • Whether employees are expected to have work email on personal devices
  • How on-call arrangements are defined and compensated
  • What escalation looks like in a genuine emergency

If an employer does not have this policy, they are not compliant. Full stop.

The code also says managers need training on how to model the right behaviour. Sending emails at midnight signals an expectation, whether a manager intends it or not. The code puts responsibility on leadership to stop creating that pressure by example.

The Messaging App Problem

WhatsApp groups, Teams channels, Slack. The code covers all of them.

Work communication tools are work, regardless of the platform. A manager adding you to a 20-person WhatsApp group called "Site Updates" and posting tasks at 11pm is not a grey area under the code. It is contact outside working hours through a work channel.

Employers cannot sidestep the code by using informal platforms. The nature of the communication matters, not the app it arrives on.

One practical implication: if your company uses messaging apps for shift scheduling or last-minute instructions, those systems need governance. Somebody needs to decide what hours they operate in, who can post to them, and what the expectation is around response times.

Exceptions That Actually Exist

The code is not absolutist. It acknowledges that some roles require genuine availability outside standard hours. Senior managers, on-call workers, roles with explicit out-of-hours responsibilities written into contracts.

The key word is explicit. If your contract does not mention out-of-hours availability, your employer cannot invent it informally through habit and expectation.

Genuine emergencies are also acknowledged. A serious incident at a facility, a system outage affecting customers, a safety situation. These are different from "the client wants something by morning and I need you to do it tonight."

What You Can Do If Your Employer Ignores This

First, raise it internally. The code encourages employees to use grievance procedures before escalating. Document everything. Dates, times, nature of contact, your response or lack thereof.

If internal routes fail, a complaint goes to the WRC. An adjudication officer can examine whether your employer has a compliant policy, whether the culture supports or undermines it, and whether you have suffered any detriment for trying to disconnect.

The WRC can award compensation. It can also direct that practices change. Neither outcome is what any employer wants on record.

The Burnout Connection

This is not just an administrative compliance issue. Burnout is a clinical condition, and the evidence is clear that always-on work culture accelerates it. When people cannot psychologically detach from work in the evening, they do not recover overnight. They arrive the next morning already depleted.

That has safety implications in physical roles and performance implications everywhere else. The code exists partly because the alternative has real costs, to workers and to organisations.

Employers who treat the right to disconnect as a soft HR issue are misreading it. The mental health at work obligations that sit alongside this code mean the whole picture is now a legal matter, not just a cultural preference.

The Practical Check for Monday Morning

Pull up your company's Right to Disconnect policy. If you cannot find one in under two minutes, your employer is not compliant.

If you can find it, check whether it covers messaging apps by name, sets clear response time expectations, and says anything specific about management behaviour. Vague policies that say "we respect work-life balance" are not policies. They are press releases.

The code puts the obligation on employers to build the structure. It puts the right to use that structure on employees. Neither side benefits from pretending the code is not there.

Your evenings are yours. That is not a soft suggestion from a government body. It is the framework your employer is legally expected to support.