WorkAuditor Blog

Employee monitoring raises the same questions in every company I work with. Here are the twenty I hear most often, answered directly. The usual caveat applies: this is practical guidance, not legal advice — your jurisdiction, your lawyer, and your context win.

1. Is employee monitoring legal? Yes, in most countries, when it is disclosed, proportionate, and applied to work. The conditions differ by jurisdiction — the EU requires a legal basis and a proportionality assessment, the US generally permits it with state-specific notice rules, and several countries mandate consultation with employee representatives. The common thread everywhere is disclosure and reasonable scope.

2. Do we have to tell employees they are being monitored? Yes. Notice is the floor of every credible legal framework and the foundation of any workable rollout. Tell employees what is tracked, why, and who sees it — before data collection starts. Silent monitoring is where legal problems and trust problems are born.

3. Do employees have to consent? Not in every jurisdiction. Some countries require explicit consent; others allow monitoring under legitimate interest with notice alone. In practice, consent is the safer design: a consent step in the policy acknowledgment protects you under most regimes and defuses the fairness objection.

4. Is it legal to take screenshots? In most places, yes, with conditions. Screenshots should be limited to work time, restricted to company devices, and saved where only authorized roles can access them. Several countries treat screenshots and keystroke logging as higher-risk practices requiring stronger justification. Avoid them where output metrics can do the job.

5. Is keystroke logging ever justified? Rarely. Keystroke logging captures passwords, personal messages, and content unrelated to work, which makes it hard to justify under proportionality tests in many jurisdictions. It is mainly defensible in regulated industries with data-handling requirements. For most companies, application and time tracking deliver the same value without the exposure.

6. Can we monitor employees on personal devices? Very carefully. Bring-your-own-device monitoring is legal in many places but sits in the highest-risk category, because personal devices contain personal data. The standard design: monitor only the work-related activity within the corporate app or browser container, and never claim the right to sweep the whole device.

7. Can we monitor employees outside working hours? Monitoring personal time is legally indefensible almost everywhere and destroys trust everywhere else. Configure the tool to exclude breaks, lunch, and off-hours by default. If a role genuinely requires on-call visibility, define the on-call window explicitly and track only within it.

8. Can we monitor employees during medical or parental leave? No. Activity tracking should stop when employment status changes to leave. Monitoring a person on medical leave is not just a trust violation; it can create legal exposure under health privacy and labor laws. Offboarding and leave triggers should be automated, not manual.

9. Can monitoring data be used in performance reviews? Yes, but with constraints. Activity data alone should never be the basis of a review — it is a signal, not a verdict. Pair it with output evidence and a human conversation, and state in the policy what the data may and may not be used for. Using months of silently collected data as a surprise gotcha is where monitoring programs turn into lawsuits.

10. Can we use monitoring to justify firing someone? Yes, if the termination reason is documented, the data is accurate, and the employee was informed of the policy. Courts have upheld terminations supported by monitoring data, and they have struck down ones where the collection was hidden or the data was the sole basis. The defensibility comes from process, not from the data itself.

11. What data should we never collect? Passwords and credentials, health information, religious or political activity, and personal content on personal devices. Also avoid location tracking of personal vehicles and any biometric data where it is not strictly required. If you would not want the data read aloud in a courtroom, do not collect it.

12. How long should we keep monitoring data? Short as possible. Thirty to ninety days serves most disputes, billing, and planning purposes. Longer retention only expands your breach surface and your exposure to access requests. If your industry mandates longer retention, automate deletion after the legal minimum instead of keeping everything forever.

13. Can employees see their own monitoring data? They should, and tools increasingly make it a default. Employee self-view catches classification errors, builds trust, and lets people correct the record before it reaches a manager. If your tool cannot show employees their own data, that is a red flag about the tool, not a feature to accept.

14. What should we do when an employee objects to monitoring? Listen first. Separate objections into the reasonable and the absolute: a request to keep personal time untracked is reasonable, while a demand for no tracking at all in a role where time is the deliverable may not be. Document the conversation, offer the alternative that fits the role, and make clear how the data will and will not be used. Most objections dissolve when the reasoning is real.

15. Does monitoring hurt trust? It can. Surveys consistently show trust drops when monitoring is silent, broad, or unexplained — and does not drop when the program is disclosed, scoped, and purpose-driven. Trust is a rollout variable, not a monitoring constant. Design the program as an agreement and the question mostly disappears.

16. How much does employee monitoring software cost? Per-user pricing typically runs from a few dollars to tens of dollars per month depending on features, deployment, and seat volume. The total cost includes implementation, management time, and compliance overhead, so budget the full picture, not the license line.

17. Can small companies afford employee monitoring software? Yes. Cloud-based tools removed the enterprise cost floor, and most vendors price for small teams. Small companies often get more value per dollar than enterprises, because accurate time data fixes payroll, billing, and staffing decisions that are proportionally larger in a small operation.

18. What is the difference between monitoring software and spyware? Disclosure, scope, and consent. Monitoring software is installed on company devices, announced in a policy, limited to work activity and time, and visible to the employee. Spyware hides, records indiscriminately, and operates without notice. The same product can be either, depending on how you configure it.

19. Do we need monitoring at all? Only if it changes a decision. If accurate time data, workload visibility, or security evidence would change how you staff, bill, or protect data, monitoring has a job. If nothing would change, you are paying for surveillance theater — cancel the tool and have a conversation instead.

20. What is the single most important rule? Monitor the work, not the person. Scope the data to decisions, tell people exactly what is collected and why, show them their own data, and review the program on a schedule. Every other answer in this FAQ follows from that rule.

If you have questions this list missed, the documentation at https://www.workauditor.com covers the practical side of rollout — WorkAuditor is cloud-based employee monitoring software for Windows and Mac built around employee-visible dashboards and configurable access. What question did you expect to see here that is not on the list?