The Line Between Timekeeping and Surveillance

Products in this market are sold as one category. They are two, and the difference determines what you are legally obliged to do, what happens to trust, and whether the data you collect is worth anything.

Rules on workplace monitoring differ substantially by country, and within some countries by state or province. What follows describes the distinction and the questions to ask; the specific obligations where your people are located need checking there.

For a vendor-side example of this category, see employee monitoring software from Monitask; treat vendor descriptions as product information rather than independent evidence.

What each one is

Timekeeping records what work was done and for how long. Which project, which task, start and stop. It is production data, it is what payroll and invoicing rest on, and it is expected.

Monitoring records how the person behaved. Screenshots, keystroke counts, mouse movement, application and website use, idle detection, activity scores, webcam capture, location.

The test: is the subject the work, or the person? A record saying "four hours on the Henderson project" is timekeeping. A record saying "62% active, 14 minutes idle, three visits to a news site" is monitoring.

Why the distinction is not academic

The legal position differs

Timekeeping is generally expected and in many places required — records of hours worked are employment records with retention and access obligations.

Monitoring frequently carries additional requirements: notice, sometimes consent, sometimes consultation with employee representatives, sometimes an impact assessment. Several jurisdictions restrict specific techniques outright.

Data protection obligations apply to both and bite harder on monitoring, because it collects more, about the person rather than the work, and frequently without a clear necessity argument.

Check what applies where your people are, not where the company is registered. This is the part organisations most often get wrong with distributed teams.

They measure different things

Monitoring measures presence and motion.

Someone thinking is idle by these measures. Someone reading a long document is idle. Someone on a phone call away from the keyboard is idle. Someone moving a mouse while achieving nothing is productive.

Which means the metric rewards the appearance of work — and people, being rational, produce what the metric rewards.

Mixing them destroys the timekeeping data

The practical consequence and the one most often overlooked.

Once the timesheet lives in the same system as the screenshots, the timesheet is a surveillance instrument. People record defensively, waiting time disappears, and the operational data you actually needed becomes fiction.

You cannot have honest production data and behavioural monitoring in the same system. Choose. See tracking time against measuring people.

Where the line genuinely blurs

Not everything is clear-cut, and pretending otherwise is unhelpful.

Automatic time capture from calendar entries and application use. Reduces friction genuinely, and captures behaviour. The question is what is recorded and who sees it — a suggestion to the individual which they confirm is different from a log sent to a manager. See automatic tracking.

Location on a mobile timesheet, for field workers. Defensible where the job requires proof of attendance at a site; not defensible as continuous tracking.

Screen recording for compliance in regulated environments — trading floors, some financial and healthcare contexts. Genuinely required in specific settings and frequently over-applied by analogy.

Activity data used in aggregate to find where a whole team loses time. Weaker objection, and it remains monitoring if the underlying records identify individuals.

The question for each: is this the minimum needed for a stated purpose, and would you be comfortable explaining it to the people affected?

If you are considering monitoring software

Questions worth answering before buying, not after.

What specific problem is this solving? "We do not know if remote people are working" is usually a management problem being addressed with software.

What will you do with the output? If the answer involves conversations about individuals, you are building an evaluation system.

What are the legal requirements where your people are? Notice, consent, consultation, assessment.

What happens to trust? Predictably: the monitored team behaves like a monitored team, the best people leave first, and the data starts describing performance for the metric.

Is there a narrower option? Outcomes, deliverables, regular conversation. These are harder to administer and they measure the thing you actually care about.

And what does it do to your existing time data? See above. For broader independent background, see ICO guidance on monitoring workers.

Doing timekeeping well without crossing over

Record work and duration. Nothing about behaviour.

Report at the level of work. Project, client, task type — not individual leaderboards.

State the purpose and hold to it.

Make non-productive time safe to record, which is the single strongest signal that this is not an evaluation system.

Give people access to their own data.

Set a retention period and configure it, because these are personal data. See time records as employment records.

And if someone asks whether this is monitoring, have a clear answer. If the answer is uncomfortable, that is information.

For small teams and solo workers

The distinction still matters when it is you and two other people, and the informality makes it easier to drift.

A shared spreadsheet of hours by project is timekeeping. A group chat where people report what they are doing hourly is monitoring with extra steps.

And tracking yourself: logging what you worked on is useful. Scoring your own activity percentage is the same trap aimed inward.

The short version

Timekeeping records the work; monitoring records the person. That is the whole test.

The legal obligations differ, and they follow the location of the people, not the company.

Monitoring measures presence and motion — thinking registers as idle, and the metric rewards the appearance of work.

Mixing them in one system destroys the timekeeping data, permanently.

And if you cannot comfortably explain a measure to the people affected, that is the answer.