We were recently asked a question by an MSP customer that comes up often, in one form or another: “How do we actually tell our clients’ teams this is coming, without it causing a wave of upset?”
It is a fair question, and an understandable worry. Announcing monitoring software feels, to many IT teams and business owners, like inviting a difficult conversation they would rather avoid. The instinct that follows is usually to say as little as possible: a short notice that new software is being installed, and nothing more.
Here is what we told that customer, and why the answer matters more than it might first appear.
The Honest Answer: It Goes Better Than Expected, Even Done Minimally
In practice, we see very few objections, even where a rollout has been communicated briefly, along the lines of “we are installing new software, here is what you will see.” Staff generally accept a short, plain notice from IT without significant pushback.
This is a useful and reassuring pattern. It does not, however, mean that a brief notice represents the right approach, and there is a more significant reason to do this properly than simply avoiding a few awkward questions.
The Real Reason Transparency Matters: It Protects the Business, Not Just Staff Morale
UK employment law does not treat monitoring as a purely operational decision. Several tribunal cases illustrate a consistent pattern: where an employer has monitored staff without adequate transparency, or used monitoring data beyond its stated purpose, tribunals have found the resulting dismissal unfair, even where the underlying misconduct was genuine.
Two examples illustrate this well. In one case, an employer accessed personal emails sent from a work account without prior notice; the tribunal found this breached the employee’s right to privacy and rendered the subsequent dismissal unfair. In another, CCTV originally installed for security purposes was later used to assess staff performance without staff being told the purpose had changed; the tribunal held this shift, without notification, was itself unfair and contributed to an unlawful dismissal.
In both cases, the issue was not whether misconduct had occurred. It was whether the business could show it had acted fairly and transparently in how the evidence was gathered. A business that skips proper disclosure is not simply risking a few uncomfortable emails. It is risking the very protection it hoped monitoring would provide in the first place.
What This Means in Practice
A monitoring rollout that follows a proper, documented process, confirming a lawful basis, completing a DPIA, and clearly informing staff in advance of what is collected and why, puts a business in a genuinely stronger position if that data is ever needed. Not because the data itself becomes untouchable, but because the process behind it is one a tribunal is far more likely to view as fair.
This is precisely why our full deployment process is structured as it is. Each step is designed to leave a business with a defensible position, not simply a completed rollout.
See the full process: How to Deploy mi.team: The Complete Rollout Process. For guidance on the staff communication itself, including a ready-to-use template, see How Do I Tell My Team About mi.team Without It Sounding Like Surveillance?
The Takeaway
Doing this properly is not extra caution for its own sake. It is what distinguishes a monitoring process a business can genuinely rely on from one that could unravel the very outcome it was trying to protect. The short answer we gave our customer stands: the upset most businesses anticipate is smaller than expected, and doing this properly is worth considerably more than avoiding it.
This is a general overview of a complex area of employment law, not legal advice for your specific circumstances. For anything genuinely high-risk or contested, we would recommend seeking advice from a solicitor.
