Most employers now have tools that can watch their staff far more closely than the law comfortably allows: productivity dashboards, keystroke and screenshot capture, location tracking, call and message analysis, and a growing layer of AI that scores, ranks, and flags workers automatically. The technology has run ahead of the question that decides whether any of it is lawful: is this necessary, proportionate, and fair?
UK law does not ban workplace monitoring. It conditions it. This article sets out where the line sits in 2026, what changes when AI does the watching, and the one form of AI monitoring that is now banned outright next door in the EU.
Article 88 and where the rules actually live
Article 88 of the UK GDPR is the provision that allows a country to set more specific rules for processing employee data. The UK has not enacted a comprehensive set of those rules, so workplace monitoring runs on the general UK GDPR principles, the Data Protection Act 2018, and the ICO's guidance on monitoring workers, published in October 2023 to replace the old Employment Practices Code.
So there is no single "surveillance statute" to point to. The lawfulness of monitoring is decided by applying the ordinary data protection principles to the employment relationship: a lawful basis, necessity, proportionality, transparency, and a documented assessment of the risk to workers.
The lawful basis: legitimate interest, almost never consent
Every monitoring activity needs a lawful basis under Article 6. For most monitoring the right one is legitimate interest under Article 6(1)(f).
Consent is usually the wrong answer. The ICO's position is that consent is unlikely to be valid in the employment context, because the imbalance of power means a worker cannot freely refuse without fear of consequence. An employer who builds a monitoring programme on consent and is later told that consent was not freely given is left with no lawful basis at all.
Legitimate interest is not a free pass. It requires a Legitimate Interest Assessment on file: the legitimate aim (security, safety, regulatory obligation, protecting assets), the necessity (monitoring is genuinely needed to achieve it), and a balancing test weighing the intrusion against the worker's rights and reasonable expectations. The assessment is the document a regulator asks for first.
Necessity, proportionality, and transparency
Three tests decide most cases.
Necessity. Monitoring has to be genuinely needed for a real aim, and it has to be the least intrusive way of achieving it. If a narrower measure would do the job, the broader one is unlawful.
Proportionality. Continuous, blanket monitoring of everyone, all the time, rarely survives. The more intrusive the method, the stronger the justification has to be, and the narrower the scope should be.
Transparency. Workers generally have to know what is monitored, why, and how. Secret monitoring is the exception, not the default. Covert monitoring is lawful only in narrow circumstances, where there is a genuine suspicion of serious wrongdoing and telling people first would defeat the purpose, and it is almost never lawful in places with a heightened expectation of privacy such as toilets, changing areas, or break rooms.
When monitoring is high-risk: the DPIA
Systematic monitoring of workers is one of the clearest triggers for a Data Protection Impact Assessment under Article 35. Large-scale monitoring, monitoring using new technology, and monitoring that evaluates workers all push the processing into the high-risk category that makes a DPIA mandatory. Our guide to when a DPIA is needed for an AI system covers the threshold. For AI monitoring it is hard to argue a DPIA is not required.
What changes when the watcher is AI
AI monitoring adds a distinct layer of risk on top of the ordinary rules: bias in how the system scores different groups, opacity in how it reaches a score, and function creep as a tool bought for one purpose drifts into others. Two issues bite in law specifically.
It can trigger the automated-decision regime. If the monitoring output drives a significant decision about a worker by solely automated means, for example an AI productivity score that feeds performance management, pay, or dismissal without meaningful human involvement, the decision falls under the new Articles 22A to 22D of the UK GDPR, in force since 5 February 2026. The worker is then owed the four safeguards: information about the decision, the ability to make representations, human intervention, and the ability to contest it. The full regime is set out in our reference on automated decisions under Article 22A to 22D. A manager who rubber-stamps the AI's score does not take the decision out of scope.
It often involves special category data. Monitoring that infers health, emotional state, trade union activity, or similar is processing special category data under Article 9, which needs a separate condition and far stronger justification. Inferring these things by accident, through behavioural or sentiment analytics, does not avoid the rule.
The line the EU has already drawn: emotion recognition
The sharpest current development sits across the Channel. The EU AI Act prohibits AI systems used to infer the emotions of a person in the workplace, outside narrow medical or safety uses. This is one of the Act's prohibited practices, and the ban has applied since 2 February 2025.
The UK has no equivalent outright ban. But workplace emotion recognition is high-risk under the UK GDPR for the reasons above: it usually processes special category data, it rarely passes the necessity and proportionality test, and it would need a DPIA and a strong justification to stand up. The practical position on both sides of the Channel is that AI reading workers' emotions is very hard to do lawfully, and in the EU it is simply off the table.
What workers can do
If you are monitored and want to understand or challenge it:
- Make a subject access request. You are entitled to the personal data held about you, which includes monitoring data, and meaningful information about any automated decision-making.
- Ask for the lawful basis and the assessment. If monitoring relies on legitimate interest, there should be a Legitimate Interest Assessment behind it.
- Object. You have the right to object to processing based on legitimate interest, and the employer then has to show compelling grounds to continue.
- Use the automated-decision safeguards. Where a significant decision about you was made by an automated monitoring system, you can ask for human intervention and contest the outcome.
If you are the employer
The same rules read as a checklist:
- Lawful basis chosen per monitoring activity, with a Legitimate Interest Assessment where you rely on Article 6(1)(f).
- A DPIA for systematic or AI-driven monitoring, completed before it goes live.
- A clear, accessible notice telling workers what is monitored and why.
- The least intrusive method that achieves the aim, scoped as narrowly as possible.
- Genuine human involvement in any consequential decision the monitoring feeds, with records that show it was real.
- Extra care, and a separate Article 9 condition, wherever monitoring could infer special category data. Treat emotion recognition as a line not to cross.
When to take advice
Monitoring becomes a legal problem at the point it feeds a decision that affects someone's job, or strays into private space or special category data.
Instruct a specialist when:
- Monitoring data is being used in a disciplinary, capability, or dismissal process
- You are deploying AI scoring or analytics that rank or flag workers
- The system could infer health, emotion, or other special category data
- A worker has objected, made a subject access request, or challenged an automated outcome
- You are rolling out monitoring across the workforce and need the DPIA and the assessment to stand up
Current as at 18 June 2026. This is educational. For your specific situation, instruct a qualified data protection or employment adviser.
Part of the Janus Compliance AI and your rights theme and the Employment Law cluster. See also: Automated Decisions Under UK Law: Article 22A-22D, AI Rejected Your Job Application, Do I need a DPIA for my AI system?.
Frequently Asked Questions
Is it legal to monitor employees in the UK?
Yes, within limits. UK law does not ban workplace monitoring, but it has to be lawful, necessary, proportionate, and transparent under the UK GDPR and the Data Protection Act 2018, interpreted through the ICO's 2023 guidance on monitoring workers. You need a lawful basis (usually legitimate interest, supported by a documented assessment), you generally have to tell workers what you monitor and why, and the monitoring has to be the least intrusive way of achieving a real business aim. Blanket, continuous, or secret monitoring usually fails that test.
What is Article 88 of the UK GDPR?
Article 88 is the provision that lets a country set more specific rules for processing personal data in the employment context. The UK has not enacted a comprehensive set of Article 88 employment rules, so workplace monitoring is governed by the general UK GDPR principles, the Data Protection Act 2018, and the ICO's guidance rather than a single bespoke statute. Article 88 is the hook; the operative rules are the general ones applied to the employment relationship.
Do I need consent to monitor staff?
Usually not, and consent is usually the wrong basis. The ICO treats consent as unlikely to be valid in employment because the power imbalance means a worker cannot freely refuse. For most monitoring, the appropriate lawful basis is legitimate interest under Article 6(1)(f), which requires a Legitimate Interest Assessment: the legitimate aim, the necessity, and a balancing test against the worker's rights and reasonable expectations. Relying on consent and getting it wrong leaves the whole monitoring programme without a lawful basis.
What changes when AI does the monitoring?
AI monitoring (productivity scoring, keystroke and behavioural analytics, sentiment analysis) adds risks of bias, opacity, and function creep on top of the ordinary monitoring rules. Two things bite specifically. If the monitoring output drives a significant decision about the worker (performance management, pay, dismissal) made by solely automated means, the automated-decision regime in Articles 22A to 22D applies and the worker gets the four safeguards. And monitoring that infers health, emotion, or other special category data triggers the stricter Article 9 conditions.
Can employers use AI to read employees' emotions?
Not in the EU. The EU AI Act prohibits AI systems used to infer emotions of a person in the workplace, outside narrow medical or safety uses, and that ban has applied since 2 February 2025 as one of the Act's prohibited practices. In the UK there is no outright ban, but workplace emotion recognition is high-risk processing under the UK GDPR: it usually involves special category data, rarely passes the necessity and proportionality test, and would need a DPIA and a very strong justification. In practice it is hard to do lawfully on either side of the Channel.
Start with a £500 scoping review
If you need GDPR documentation, AI Act work, or a compliant AI build, the first step is a written scoping review. You get a real report, not a generic discovery call.
Related Articles
AI Governance
Automated Decisions Under UK Law (2026): The New Article 22A-22D Safeguards Regime
The Data (Use and Access) Act 2025 replaced Article 22 of the UK GDPR with Articles 22A to 22D, flipping automated decision-making from a near-ban to a permitted-with-safeguards regime. What changed, the four safeguards you must now evidence, the special-category restriction, the 'meaningful human involvement' test, and what deployers of AI that decides about people have to do in 2026.
AI Governance
AI Governance Consulting for UK Businesses: What You Actually Need
What AI governance consulting involves, who needs it, and why the best approach for most UK businesses is building AI systems with governance baked in from day one.
GDPR
Is the Claude API GDPR Compliant? The 2026 Setup, Step by Step
Yes, the Claude (Anthropic) API can be run GDPR compliant, and the defaults start in a stronger place than most. The DPA is built into the Commercial Terms, API data is not used for training, and retention defaults to seven days. Here is exactly what to check and configure: the DPA, retention and zero-data-retention, data minimisation, the DPIA, international transfers, the Microsoft Copilot caveat, and where the EU AI Act lands.