The Right to Disconnect Is Now Law — and MSPs Are the Most Affected Industry
Since 26 August 2024, Australian employees in non-small businesses have had the legal right to refuse work-related contact outside working hours. From 26 August 2025, that right extended to every employee in the country, including those at small businesses.
No industry is more affected than MSPs.
Managed services runs on after-hours work. Maintenance windows. Weekend patching. On-call rotations. "Just quickly check" emails that arrive at 9 PM. Slack messages about a client's printer that somehow became urgent at 10:30 on a Saturday night.
This article is your practical guide to what the right to disconnect actually means for MSP technicians, engineers, and account managers — and what your employer can and can't demand.
How the Right to Disconnect Works
The right to disconnect is part of the Fair Work Act. It gives employees the right to refuse to monitor, read, or respond to work-related communications outside their working hours, unless that refusal is unreasonable.
The law does not ban employers from contacting you after hours. It gives you the right to say no.
It Applies To
- Employees of all business sizes (small businesses since August 2025)
- All forms of contact: phone, email, messaging apps (Teams, Slack, WhatsApp), SMS
- All contexts: after hours, meal breaks, annual leave, sick leave, personal leave
- On-call arrangements where you're genuinely available (but you can refuse contact outside your agreed on-call hours)
It Does Not Apply To
- Independent contractors (though this is a grey area — see our Sham Contracting guide)
- Genuine emergencies where you're the only person who can resolve a critical issue
- Contact that's part of your agreed duties (e.g., scheduled maintenance windows you've accepted)
What This Means for MSP Workers
1. The "Quick Question" Culture Is Now Legally Questionable
Every MSP worker knows the pattern:
"Hey, sorry to bother you after hours — quick question about the Acme Corp firewall rules..." "Can you just check that backup job?" "Client XYZ is complaining about slow internet, can you log in and take a look?"
These aren't emergencies. They're convenience for managers and clients. And you now have a legal right to ignore them.
What you can say: "I'm not available after hours. Please log a ticket and I'll action it first thing tomorrow."
What they can't do: Penalise you, write you up, or hold it against your performance review.
2. On-Call Must Be Compensated (and Clearly Defined)
If your MSP requires you to be on call, the arrangement needs to be:
- In your employment contract (not implied or "everyone does it")
- Compensated — either through an on-call allowance, overtime pay, or clearly factored into your above-award salary
- Clearly defined — what hours, what responsibilities, what escalation process
If your MSP expects you to be available after hours but doesn't pay you for it, you have strong grounds to refuse contact under the right to disconnect.
3. Maintenance Windows and Scheduled After-Hours Work
Scheduled after-hours work that you've agreed to (e.g., "we run patching every Saturday 2-4 AM, you're rostered once a month") is not covered by the right to disconnect — it's part of your agreed duties.
However: - It must be in your contract or rostered in advance - You must be compensated (overtime, TOIL, or factored into salary) - Unreasonable rostering (e.g., every weekend, no notice) can be challenged
4. MSP Managers Are Also Protected
If you're a team lead or service desk manager, you're still an employee. Your boss can't contact you about operational issues at 11 PM and expect a response.
The "Emergency" Exception (and How MSPs Abuse It)
The right to disconnect includes an exception for genuine emergencies. If there's a critical security incident, a major outage affecting multiple clients, or a disaster scenario — it's reasonable to contact you.
But MSPs love to classify routine issues as emergencies:
| What they call it | What it actually is |
|---|---|
| "Critical client issue" | A client who won't wait until morning |
| "Urgent security concern" | A phishing email that's been around for hours |
| "Production down" | A single user can't access their email |
| "Emergency patch" | A patch that's been available for weeks |
The test: Would a reasonable person consider this an emergency? If the issue can wait until business hours without causing serious harm, it's not an emergency.
What to Do If Your MSP Violates Your Right to Disconnect
The right to disconnect is enforceable. If your employer takes adverse action against you for refusing after-hours contact, you may have a claim:
- Document everything. Save emails, take screenshots of messages, record dates and times of contact.
- Check your contract. Does it mention after-hours work, on-call, or out-of-hours contact?
- Raise it internally. Some MSPs genuinely don't realise they're overstepping.
- Contact Fair Work Ombudsman. They can investigate and mediate.
- General protections claim. If your employer penalises you, you may have a claim under the Fair Work Act for adverse action.
Key Contacts
- Fair Work Ombudsman: 13 13 94
- Fair Work Commission: 1300 799 668
- Your union (if you're a member of Professionals Australia, ASU, or similar)
Practical Scenarios for MSP Workers
Scenario 1: The 9 PM Slack Message
Your manager: "Hey, can you check the backup status for Client ABC? Client flagged an issue."
Your response: "I'm not available after hours. I'll check it first thing tomorrow and update the ticket."
Legal reality: This is textbook right to disconnect. Unless there's evidence backups actually failed and data is at risk, this is a routine query that can wait.
Scenario 2: The Saturday Morning "Urgent"
Your manager texts at 8 AM Saturday: "Client XYZ's server is down. Need you to log in and check."
Your response: If you're not on call or rostered, you can refuse. If it's a genuine outage affecting operations, it's reasonable to respond — but you should be compensated for the time.
Scenario 3: The "Everyone Answers" Culture
Your MSP says: "We don't have a formal on-call policy, but everyone chips in after hours when needed. It's part of the culture."
Your response: Culture is not a contract. Without a formal arrangement and compensation, you're not obligated to be available.
Scenario 4: Annual Leave Emergency
You're on leave and get called about a client issue.
Your response: You have the strongest possible protection here. Contact during approved leave is almost never reasonable unless you're literally the only person who can resolve a critical security incident.
What Smart MSPs Are Doing (vs What Bad Ones Do)
| Smart MSP | Bad MSP |
|---|---|
| Formal on-call roster with allowance | Expects everyone to be available "as needed" |
| Clear escalation paths (L1→L2→L3) | Calls the most senior person directly |
| Compensates after-hours work | "It's built into your salary" (without stating how much) |
| Respects leave boundaries | Contacts staff on annual leave |
| Uses managed alerts, not manual checking | Manual after-hours "checks" for reassurance |
| Pays overtime or offers TOIL | Offers "thank you" and pizza |
The Bottom Line
The right to disconnect is one of the most significant employment law changes in recent Australian history, and it directly targets the MSP industry's worst habits.
If you're an MSP employee:
- You can legally ignore non-urgent after-hours contact
- Your employer cannot penalise you for exercising this right
- On-call must be formalised and compensated
- "Culture" is not a legal justification for unpaid availability
If you're an MSP owner:
- Formalise your on-call arrangements
- Ensure after-hours work is compensated
- Build proper escalation and alerting systems
- Stop relying on "everyone chips in" — it's now legally risky
This article provides general information based on the Fair Work Act 2009 (Cth) as at June 2026. It does not constitute legal advice. For specific circumstances, consult an employment lawyer or the Fair Work Ombudsman.
Related: Fair Work and MSPs: Your Rights | Sham Contracting in IT | MSP Employee vs Contractor
Was this helpful?