Tracking Without Surveillance
This is not legal advice. Rules on workplace monitoring vary by jurisdiction and several are strict.
Time tracking and employee monitoring arrive in the same products and answer different questions. Separating them is the whole of getting this right.
Two different needs
Recording hours. For billing a client, meeting a statutory duty, or knowing how long work actually takes. Requires a number per period and nothing else. For a related reference, see online timesheets.
Observing behaviour. Screenshots, application logs, activity scores, idle detection. Requires continuous capture of what a person is doing.
The first is administration. The second is surveillance, and products sell them as one because the same agent can do both.
What the narrow version needs
Somebody enters start, end and what it was for. Or a timer they start and stop.
Project or client attribution, if billing depends on it.
Approval, where somebody signs off.
And export, so the record leaves with you.
That is the entire feature set for the administrative need, and every capability beyond it is answering a different question.
Why the narrow version performs better
Because the numbers are more truthful.
Under observation, 24% take fewer breaks to avoid appearing idle, and the resulting data describes performance of work rather than work.
Self-entered hours are estimates and are frequently more accurate than an activity score, because the person knows what they were doing and the agent does not.
And people fill them in. An administrative tool people cooperate with beats a surveillance tool they route around.
Where the line is legally
In several jurisdictions the line is not a preference.
Systematic monitoring commonly triggers a data protection impact assessment; consent is a weak basis in employment; works council involvement is mandatory in some countries; and specific capabilities — continuous screen recording, keystroke logging — are treated as disproportionate in almost all circumstances by some regulators.
None of that applies to recording hours worked, which is why the distinction is worth keeping clean rather than buying a suite and disabling features.
Buying for the narrow need
Ask what is on by default. Default-on capture is how organisations cross the line without deciding to.
Ask whether the monitoring functions can be removed rather than hidden, and whether that can be evidenced to somebody who asks.
Ask what employees can see of their own data, since transparency is the difference between 77% acceptance and 54% considering leaving.
And ask what exports. Hours are a record you may need years later.
The uncomfortable question first
Before any of this: what is the number for?
If it is billing, capacity planning or a statutory duty, the narrow tool answers it.
If it is to find out whether people are working, that is a management question being answered with a measurement, and no tool resolves it.
The short version
- Recording hours and observing behaviour are different needs sold in the same products
- The administrative need requires start, end, purpose, attribution, approval and export — nothing more
- The narrow version produces more truthful numbers, because observation changes behaviour and self-entered estimates come from somebody who knows
- In several jurisdictions systematic monitoring triggers impact assessments, weak consent, works council involvement, and limits on specific capabilities
- Ask what is on by default, whether monitoring can be removed rather than hidden, what employees see of their own data, and what exports
- Ask first what the number is for: billing and planning have a narrow answer, and "are people working" is a management question
For additional context on this topic, see Xbox.