Employee Monitoring vs Surveillance: Where the Line Is

Every employer who has ever run a time clock is monitoring employees. The punch card is monitoring. Nobody quits over a punch card.

So the objection people raise to “employee monitoring” is not really about data collection. It is about something more specific, and if you can name it you can build a system that gets you the information you need without triggering it.

The test

Here is the cleanest version I know:

Monitoring measures the work. Surveillance measures the worker.

A time clock records when work started and stopped — a fact about the job. A tool that scores an employee’s attention minute by minute and ranks them against their colleagues is making claims about the person.

A second test, more practical: would you be comfortable showing the employee the exact screen you are looking at? If yes, you are monitoring. If the honest answer is “they’d be upset if they knew I could see this,” you have crossed over — and you will find out when they do.

What separates them in practice

	Monitoring	Surveillance
Scope	Bounded — on the clock, company equipment	Unbounded — whatever can be captured
Purpose	A specific question: payroll, billing, staffing	General suspicion
Disclosure	Told in advance, in detail	Discovered, or buried in a handbook
Access	Employee sees their own record	One-way mirror
Retention	Deleted on a schedule	Kept indefinitely
Granularity	The least that answers the question	The most the software can collect

The pattern: monitoring starts from a question and collects the minimum to answer it. Surveillance starts from a capability and collects whatever it can, in case it turns out to be useful.

Why the distinction is worth money

This is not only an ethics argument.

Data you collect is data you must protect. Screenshots are indiscriminate. Turn them on company-wide and you will eventually hold images of a bank login, a medical portal, and a private message about someone’s divorce. That is a breach liability you created for no operational benefit.

Surveillance data is usually bad data. Activity percentage cannot distinguish a developer reading documentation from a developer reading the news. Rank people on it and you will promote the wrong ones — you are measuring input frequency, not value.

It changes behavior in the wrong direction. People optimize for whatever you measure. Measure mouse movement and you get mouse movement. Availability theatre replaces deep work, and the metrics look great while the output declines.

Your best people leave first. Strong performers have options. They are also the ones most insulted by the implication, because they know their output speaks for itself.

Four questions before you turn anything on

1. What specific decision will this data inform? If you cannot name the decision, you do not need the data.
2. What is the least I could collect and still make that decision? Usually much less than the default configuration.
3. Would I be comfortable if this were public? Not the data — the practice.
4. What happens if I am wrong about someone? Data that “proves” someone is slacking, when they were actually caring for a sick parent, will still be in your system.

Where Klees Desk draws the line

Klees Desk exists because remote staff need their hours recorded like everyone else, and because most tools that do this go far past what an employer legitimately needs. The limits are built in rather than left to configuration:

It records nothing while clocked out or on break. There is no setting that changes this.

It never logs keystrokes. Not the contents, not a count of what was typed. Camera, microphone, and clipboard are never touched.

Screenshots are off by default, and when enabled they are blurred on the employee’s own machine before upload — the unblurred image never leaves their computer. You can limit them to the primary display and cap them at a few per interval, taken at random rather than predictable moments.

Excluded applications are never captured. List your banking, health, and HR tools and an excluded app in the foreground suppresses the screenshot too.

URL tracking defaults to the domain, not the full path.

Everyone acknowledges a plain-language notice first, generated from your live settings, and the exact text is stored with the acknowledgment.

Employees see their own data in the same view their manager uses, and can delete their own screenshots when you allow it.

Monitoring that an employee cannot inspect is the kind that becomes a dispute. Making it mutual is not a concession — it is what keeps the record credible when you actually need it.

Related reading

• Is employee monitoring legal?
• How to write a remote work monitoring policy
• Klees Desk documentation