Screenshots and Keystroke Counts

Several widely sold time tracking products capture periodic screenshots, keystroke counts, mouse activity and application logs. None of this is needed to record how long someone worked.

What they capture

Screenshots at intervals, sometimes every few minutes, sometimes blurred, sometimes not.

Keystroke and mouse event counts, presented as an activity percentage.

Application and website logs.

Webcam images, in a small number of products.

Idle detection used to subtract time automatically.

What they are actually for

Worth being direct.

They are not for measuring duration, which a clock or a timer does.

They are for demonstrating effort to a third party — a client paying for hours, or a manager who does not trust the record.

Which is a trust problem being solved with observation, and observation does not solve it: it produces the appearance of effort rather than effort.

Why activity percentages are meaningless

Keystroke and mouse counts measure input, not work.

Reading, thinking, drawing on paper, talking to a colleague, watching a build run all produce low activity and are all work.

Typing rapidly in a document produces high activity regardless of whether the document is any good.

The measure is trivially gamed, and tools to game it exist and are widely used, which tells you how the workforce experiences it.

A measure that is both invalid and gamed produces a number that is worse than no number, because decisions get made on it.

The specific harms

Screenshots capture whatever was on screen: a colleague's message, a medical result, a bank balance, another person's confidential document.

For anyone handling client or patient information, screenshots are a confidentiality breach by construction, and in regulated professions that is a serious matter independent of employment law.

Automatic time deduction from idle detection is unpaid working time where the person was working, which is the wage-and-hour exposure described elsewhere.

And the reputational position is poor: these features are widely reported and widely disliked, and their presence shapes how every other part of the system is received.

The legal position

General orientation, not legal advice.

Continuous screen capture of employees engages data protection obligations — notice, proportionality, assessment — and proportionality is the hard test, because a less intrusive method for recording duration plainly exists.

Regulators have found such monitoring disproportionate in several cases where the stated purpose was time recording.

Consent is not a sound basis in employment.

Works council or employee representative agreement is required in a number of jurisdictions before such systems can be introduced.

What to do

Check whether these features are on. In several products they are enabled by default when an account is created.

Turn them off, and record that you did.

If a client contract demands screenshot evidence, negotiate. A contemporaneous time record with a narrative is the normal professional standard, and offering it is usually accepted.

If the underlying concern is trust in the hours recorded, address that: shorter recording intervals, timers, review of outputs. Observation of screens is not a measure of work and everyone involved knows it.

Where you are asked to enable it anyway, the note on declining applies.

The confidentiality problem

An objection that is independent of employment law and frequently decisive.

Screenshots capture whatever was on screen, including another client's matter, a patient record, a colleague's message.

For regulated professions that is a breach regardless of the employment analysis.

It also captures the employee's own private content: health, finances, family.

And it creates a store of other people's confidential data with its own breach exposure.

Raise this first with a professional-services audience, because it lands where the employment argument sometimes does not.

Checking whether it is already on

Several products enable capture features by default, and organisations discover it afterwards.

Create a test account and look.

Check the admin settings for screenshot intervals, activity scoring and application logging.

Check what an individual user sees about themselves, which sometimes differs from what is collected.

Document the finding, because if it was ever on you will need to say so.

Disable at account level and confirm it cannot be re-enabled without a logged administrative action.

A useful implementation prompt

During configuration, stealth monitoring software can be used as a prompt for questions about fields, ownership and output. Confirm current capabilities with the provider and document any plan, integration or policy assumption behind the decision.