Most organisations run one monitoring configuration and apply it to everyone with a laptop. For contractors specifically, that is a decision with a tail risk nobody prices.
The problem is not primarily data protection, though that applies too. It is that detailed monitoring of how and when someone works is documentary evidence that you control how and when they work — and control is close to the centre of every employment-status test there is.
Why this is a status question
Across jurisdictions the tests differ in detail and converge in substance. Whether someone is genuinely in business on their own account turns on things like who controls the manner of work, whether they can send a substitute, whether they bear financial risk, whether they can work for others, and how integrated they are into your organisation.
Control does a lot of the work in that list. And an activity monitoring record is, by design, a detailed account of control: when the person started, how long they were active, which applications they used, whether they were working during hours you specified.
If a tax authority or tribunal later examines the relationship, that record is available and it reads badly. "We required them to be online 9 to 5 and monitored their activity levels" is not a sentence that supports contractor status, whatever the contract says — and in most of these tests the written contract loses to the practical reality it describes.
The exposure is not theoretical. Reclassification brings back-dated tax, social contributions, holiday and sometimes pension entitlement, plus penalties. It dwarfs anything monitoring was going to save.
What you can legitimately require
The distinction that holds up is between output and method.
Deliverables, deadlines and acceptance criteria are entirely proper — that is what you contracted for. Progress reporting is proper. Time records are proper where the engagement is billed hourly, because the client is purchasing hours and both parties accept evidence of them; this is the one place screenshot-based time tracking has a genuinely defensible home, and it is why tools built for that model exist.
Security controls over your data and systems are proper, and are a different thing again — access logging, DLP on your repositories, device requirements for handling your data. These attach to the data, not the person, and do not imply control over how they work.
What sits uncomfortably is specifying working hours for someone paid for a result, requiring presence or availability signals, and activity monitoring aimed at establishing diligence rather than supporting a bill. Each of those is a control indicator, and together they are a pattern.
Why one system for everyone is the wrong default
Beyond status risk, there are three practical reasons to separate.
The lawful basis differs. For employees in Europe the usual route is legitimate interests with a documented balancing test. For a contractor the relationship is contractual, which changes the analysis — and in both cases the proportionality question gets asked separately. Data protection law follows the personal data rather than the employment status, so the obligations in our GDPR and UK/ICO guides apply to contractors too; it is the basis and the necessity argument that shift.
The device is usually theirs. Contractors frequently work on their own hardware, which takes you straight into BYOD territory where broad monitoring is both legally difficult and practically poor.
And offboarding is different. Engagements end, often abruptly, and the data and access questions are sharper than for employees. The offboarding checklist applies with less warning and usually no device recovery.
A configuration that works
If you engage contractors regularly, the arrangement that holds up is roughly this.
Keep them out of the employee monitoring deployment entirely where you can. Different tenant, different tool, or no tool.
Where the engagement is hourly, use a time tracker scoped to billed hours, with collection limited to what substantiates the invoice. Agree it in the contract rather than imposing it afterwards.
Where the engagement is deliverable-based, do not monitor activity at all. Manage it through milestones and review. If you cannot judge whether a deliverable-based contractor is performing without activity data, the specification was the problem.
Put your security controls on your systems and data rather than on their machine. Access logs, repository controls, VPN and SSO give you most of what you actually need to know about risk, and none of it is a control indicator.
And write down which population is in which arrangement, and why. If status is ever questioned, the existence of a deliberate distinction is itself helpful evidence.
The soft version of the problem
Separate from the legal exposure, there is a practical one. Contractors notice how they are treated relative to staff, and monitoring is one of the more visible signals.
A contractor subjected to employee-grade activity monitoring while being denied employee benefits is being asked to accept the costs of both arrangements and the advantages of neither. In tight markets for specialist skills, good contractors decline that, and you end up selecting for the ones who cannot.
Where ProdView fits
ProdView is built for company-managed devices and salaried desk teams, which is to say: employees. That is the honest scope.
When not to pick us: for contractors specifically. If you bill or pay hourly, a time tracker built around timesheets fits the contractual reality better than analytics does. If the engagement is deliverable-based, the right answer is usually no monitoring at all, and we would rather say so than sell you a seat that increases your misclassification exposure. Where contractors work on your managed hardware alongside staff and must be in the same tool, keep them in a separate group with collection scoped to the engagement — and record why.
Try before you commit
Three seats are free forever if the question is about your employed team's capacity. For a contractor population, the more valuable exercise is reading your engagement terms against how the work is actually managed, which costs nothing and finds more.
General information as of October 2026, not legal or tax advice. Employment-status tests vary significantly by jurisdiction and the consequences of misclassification are substantial; take local advice before deciding how to monitor a contractor population.