Time Theft and Remote Work

The phrase is applied most aggressively to people working from home, where it means something different and is measured worst.

What gets alleged

Not working during claimed hours.

Doing something else — another job, childcare, errands.

Being away from the keyboard.

None of these is observable without surveillance, which is why the products in this space are activity monitors rather than clocks.

What activity monitoring measures

Keystrokes and mouse movement.

Which correlate with typing, not with work. Reading, thinking, drawing, talking to a colleague, watching a build run — all score low and are all work.

And it is trivially gamed, with tools to do so freely available, which tells you how the workforce experiences it.

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

What the concern usually is

Output visibility rather than hours.

A manager who could previously read the room has lost the room, and the absence of incidental signal feels like absence of work.

Which is a management information problem, and installing observation answers a different question.

What addresses it

Visible work: shared plans, written updates, things that land.

Shorter cycles, so progress is observable weekly rather than quarterly.

Regular conversation, which is the actual replacement for the room.

These cost management attention rather than licence fees, which is why monitoring is attractive.

Where hours genuinely matter

Hourly-paid remote work is a real case: a start time is a legitimate record.

A plain clock-in serves it. No location check, no activity score — a tap.

Verifying that the tap happened at their home address adds nothing about whether they started work and puts a home address in the record for everyone.

The other direction, again

Remote workers commonly work more, not less, and take less of their leave.

Which means the unpaid-time question is larger here than the time-theft question, and the records that would show it are the same ones.

Look at both, or the analysis is not an analysis.

What this collection will not describe

How to configure screen capture, keystroke counting or activity scoring.

They appear here only to explain why they do not answer the question, and requests to help implement them are declined for the same reason.

Ask what would be done differently

The question that resolves most monitoring proposals.

If you knew someone was at their keyboard, what would change?

Usually nothing, which means the request is about reassurance rather than a decision.

Where a real action exists — reallocating work, addressing someone struggling — ask whether visible output provides it, which it generally does.

Ask it early and without hostility. It is a fair question and it usually answers itself.

Reproduce the workflow

For another way to make this requirement testable, consult employee activity tracking for remote work. Reproduce the case with real roles, codes, failures and recovery steps.

Independent reference

For a thematic point of reference, see the Information Commissioner's Office. Its current material provides useful context beyond product documentation.