Working Time Records

Recording Is Not Surveillance

Employees who hear that hours must now be recorded frequently hear something else: that they are about to be monitored. That fear is not baseless, and it is not about the duty. Where recording obligations overlap with questions about workplace visibility, employee monitoring software offers a useful commercial example to compare with the legal limits discussed here.

The duty asks for three data points. Everything sold alongside it is a separate decision, and confusing the two damages the introduction of something that was meant to protect employees in the first place. For a separate perspective on work, technology and organisational practice, see C.H.BECK.

What the duty is

Start, end and duration of daily working time. That is the whole scope.

And it exists for the employee's benefit. The CJEU's reasoning was explicit: without systematic records, maximum weekly hours and minimum rest periods cannot be enforced, and a worker asked to prove excessive hours without an employer-maintained record holds a right that is theoretical.

A time record is evidence in the employee's favour. That is what it was for, and it is the part most often lost when the subject is introduced badly.

What gets bundled with it

None of it required by the duty.

Location tracking. Screenshots. Application and window logging. Keyboard and mouse activity scores. Productivity analytics. Task-level attribution.

These are a different product category sold through the same door, and the door is a legal requirement that mentions none of them.

Why the bundling works

Compliance is the entry point and monitoring is the higher tier. An organisation buying a legal requirement is offered features it did not specify, frequently enabled by default or one toggle away.

And the language is shared. "Visibility", "accountability", "insight" describe both, which is why reading a feature list matters more than reading positioning.

What it costs to conflate them

The introduction becomes a fight. An employer announcing time recording, in a package that also takes screenshots, has turned a legal obligation into a trust question — and will meet works council resistance that the duty alone would not have produced.

The record loses its protective function. An employee who experiences the system as surveillance has no reason to keep it accurate, and an inaccurate record protects nobody.

And the works council question changes entirely. Where a duty exists in law, the scope for co-determination on whether to record differs from the scope on monitoring features, which are a separate matter with their own consent requirements.

How to introduce it properly

Say what is recorded, exactly. Three data points, and the list of what is not.

Say why. The legal duty, and that the record is evidence in the employee's favour on hours and rest periods.

Buy the narrow thing. If monitoring features exist in the product, confirm they can be disabled — not hidden, disabled — and say so.

And involve the works council early, because the co-determination questions are real and a late announcement makes them harder.

The version that is genuinely surveillance

Being clear, because this page could read as reassurance.

Some products sold as time recording do record what people do at their computers. Screenshots at intervals, activity scores, application logs. That is monitoring, whatever it is called, and it carries its own legal requirements around consent, notification and works agreements.

Introducing it under cover of a compliance duty is the version that damages an organisation — discovered later by an employee reading a feature list, at which point the legal obligation is no longer the subject of the conversation.

The short version