Define the problem before choosing the tool
Fraud prevention, network security, compliance with a specific legal obligation and performance management are different purposes. Write down the concern and the decision monitoring is meant to support. “Improving productivity” is usually too broad to tell a developer which data should be collected or a worker what is happening.
The ICO emphasises necessity, proportionality and the least intrusive means of achieving the aim. Our recommended procurement exercise is to compare the proposed tool with a simpler alternative. If ordinary task reviews or access logs answer the question, continuous screenshots may add intrusion without useful evidence. Record why the selected method is needed, what it will not collect and how you will judge whether it works.
A contract clause is not a universal permission slip
Choose a lawful basis appropriate to the particular monitoring. Inserting a monitoring clause into employment terms does not make all monitoring necessary to perform the employment contract. Consent is often unsuitable because workers may not have a genuine choice, given the power imbalance. A signed acknowledgement that someone received a policy is not necessarily valid consent to its contents.
Where legitimate interests is the proposed basis, assess the purpose, necessity and balance against workers’ interests and rights. Where a legal obligation is relied on, identify it specifically. Some monitoring may capture health, trade-union or other special-category information, requiring an additional condition. Avoid switching labels after a challenge without revisiting the substance of the assessment.
Assess the impact before the system becomes routine
Screen for a data protection impact assessment and complete one where the processing is likely to pose high risk. The assessment should address the effects on people, not simply whether the product has encryption. Consider how monitoring could influence behaviour, reveal private matters or produce unfair conclusions.
In practical terms, involve the people who understand the work. A manager may assume that low keyboard activity means low output; staff may spend substantial time on calls, reading or assisting colleagues. Consultation can reveal those blind spots before a metric becomes a management target. Record mitigations, decision owners and approval boundaries. Where high residual risks cannot be reduced, follow the requirement to consult the ICO before proceeding.
Tell workers what happens in language they can use
Transparency should explain what is monitored, why, when, by whom and how the results will be used. Include relevant suppliers, retention and rights information. A generic statement that “company equipment may be monitored” is unlikely to explain an extensive new behavioural analysis system adequately.
Our suggested briefing uses examples of the actual operation: whether message content is examined or only security events; whether location is recorded outside working hours; and who can see individual reports. Give workers a route to ask questions and challenge inaccurate information. Update the explanation before material expansion. Covert monitoring raises exceptional and tightly constrained issues and should not be treated as an ordinary management option.
Homeworking changes what the system may capture
A remote-working device may be used in a space shared with family or other household members. The ICO highlights heightened privacy expectations and the risk of capturing private life. Webcam, audio and screen recording can expose much more than an employee’s work activity.
A practical control is to define working-time boundaries and prevent unnecessary collection outside them. Review whether personal devices are involved and what the software can access. Do not assume a worker can reliably remember to disable an intrusive feature every evening. Prefer technical limits that implement the intended policy, and test those limits with fictional information before rollout.
Treat a score as evidence to examine, not a verdict
Monitoring information can be incomplete or misleading. A location signal may be inaccurate; an application may classify legitimate work as inactivity; a shared device may confuse identities. A dashboard’s numerical precision does not establish that its interpretation is sound.
Our recommendation is to document known limitations and require an appropriate human review before consequential action. Give the worker a meaningful opportunity to explain the context. Systems making significant decisions solely through automated processing require a separate assessment under the applicable automated-decision rules and safeguards. Do not assume that adding a nominal human approval button resolves that question.
Control access, retention and supplier behaviour
Restrict individual monitoring records to people who need them for the approved purpose. Decide how long raw information is necessary and whether a less detailed record would meet the continuing need. Review the supplier’s role, contract, overseas access and permitted use of the data.
Operationally, separate security investigations from routine performance reporting where possible. An administrator should not be able to browse private communications merely because they maintain the software. Keep access logs and an escalation process for suspected misuse. When the monitoring purpose ends, disable the collection rather than leaving it running because the licence remains active.
Review whether the original case still holds
After a defined trial, compare the benefits with the intrusion and administrative burden. Have findings led to better decisions, or mainly created more reports? Have workers raised concerns that change the risk assessment? A tool justified for a specific investigation should not automatically become permanent surveillance.
The practical standard is a defensible chain: a real purpose, a necessary method, accurate information, controlled access and proportionate use. Data protection is only part of the assessment; employment, confidentiality and other legal obligations may also matter. Seek specialist advice where the proposed monitoring is intrusive or could have serious consequences for individuals.
Sources and further reading
Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.
This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.