The monitoring question, answered properly
Screenshots, activity scores and keystroke counts are available to any manager who wants them. The question is what they cost.
Employee monitoring software is a mature market and it is easy to deploy. Screenshots at intervals, activity percentages, application usage, idle detection, continuous location for mobile staff.
The case for it is intuitive: you cannot see the team, so instrument the work. It is worth taking that case seriously and then looking at what actually happens. For broader context on privacy and workplace data, ICO employment guidance is a useful reference.
What monitoring measures
Activity metrics measure input signals — keyboard and mouse events, application focus, time at a screen. They do not measure output, and the correlation between the two is weak and frequently inverted.
Reading a specification carefully registers as idle. Thinking about an architecture on a walk registers as absent. Moving a mouse during a call registers as productive. The measurement systematically favours motion over thought, which in knowledge work is exactly backwards.
Within weeks of activity monitoring, people learn to generate activity. Mouse jigglers exist as a product category. What has been measured after that point is compliance, not work.
What it costs
Three costs, and the third is the one that lasts.
It changes behaviour toward the metric rather than the outcome. It damages the relationship in a way that is difficult to reverse — the message received is that the employer's default assumption is that people are not working. And it removes the manager's incentive to do the harder work of defining outputs, because a dashboard now provides a comfortable substitute.
It is also regulated
Employee monitoring is subject to law in most jurisdictions, and the requirements commonly include a lawful basis, prior notice, proportionality, an impact assessment where monitoring is systematic, and limits on retention. Covert monitoring is unlawful in many places outside narrow circumstances.
The rules differ sharply between countries, and a distributed team is usually subject to several at once — the position for an employee in one jurisdiction may be quite different from another, even under the same policy. This is an area for qualified advice rather than assumption.
Where measurement is legitimate
None of this makes time data illegitimate. There is a real distinction between measuring the work and watching the worker.
Recording hours against projects for planning and pricing is normal, useful and widely accepted. Verifying attendance for payroll is necessary. Knowing which client consumes disproportionate effort is a business question. All of these are answered by aggregate, task-level data — and none of them requires a screenshot.
The practical test is whether the capability answers a question you actually have. Tools in this space often bundle both: Monitask, like several competitors, offers straightforward time capture alongside optional monitoring features. Buying the first and leaving the second switched off is a coherent position, and it is usually the right one for a distributed knowledge team.
The reciprocity test
Before enabling anything, ask whether you would be comfortable showing the team exactly what is collected, who can see it, how long it is kept and what it will never be used for.
If yes, the measure is probably proportionate — and you should do the showing, because transparency is most of what makes any measurement tolerable. If no, the discomfort is the finding.
If the real problem is one person
Monitoring is often deployed across a team because of concerns about an individual. This is the least effective available response: it damages everyone's relationship with the employer and produces poor evidence about the person concerned.
A specific performance concern is a conversation, documented, with clear expectations and a review date. That is harder and it is the thing that actually works.