BuzbyTimeRead the requirements guide

The law, named by jurisdiction · 3.3

Consultation before deployment

Consultation before deployment. What decides it, what it costs, and what usually goes wrong. For a practical comparison point, see Monitask's work hour tracker.

In some countries you cannot simply deploy thisThe requirement

Several European jurisdictions give employee representative bodies a right to be consulted, and in some cases to agree, before technical systems capable of monitoring behaviour or performance are introduced.

German law is the strongest example: works councils have co-determination rights over the introduction of technical devices designed to monitor employees' behaviour or performance, and time recording systems fall within that. For additional context, European Commission is a useful reference.

The Netherlands, Austria and the Nordic countries have comparable arrangements in different forms, and French employers must inform and consult their social and economic committee.

Why this is a scheduling question, not just a legal one

Consultation takes months, not weeks. A works council will reasonably want to know what is collected, who sees it, what it will not be used for, and what happens to somebody whose data shows something unwelcome.

Those questions are answerable and answering them properly takes time. A rollout planned without that time in it will either slip or will be attempted without the agreement, and the second is not recoverable.

Deploying first is not recoverable

A system introduced without a required agreement can have to be switched off, and data collected in the interval may be unusable. The relationship cost is larger than the legal one: a body that discovers a monitoring system after the fact will scrutinise every subsequent proposal.

Which is a reason to involve them early enough that they can shape it, rather than late enough that they can only approve or refuse.

What a works council usually asks for

  • A written description of what is collected and why.
  • A commitment that it will not be used for performance comparison.
  • Access for individuals to their own data.
  • A retention period.
  • A review after some months.

Every item on that list is something this site argues for independently, which means an organisation that has read the rest of this blog arrives at the meeting with most of the answers already prepared.

What the person sees

There is no view in the product that compares individuals.

That is a design property rather than a configuration, which makes it a commitment a representative body can rely on rather than a setting somebody could change later.

Multinational deployments

The strictest requirement applies to that part of the workforce, not to the whole. A group rolling out across several countries frequently has one country requiring agreement, several requiring notice, and some requiring little.

Attempting one uniform process usually produces either over-compliance everywhere or a gap somewhere. Map it country by country before scheduling anything.

Working with them rather than around them

Representative bodies are not generally opposed to time recording. They are opposed to surveillance presented as time recording, and the distinction is the one this whole site is built on.

An employer who arrives with a clear statement of what is not collected has a different conversation from one who arrives with a feature list.

Not advice

Consultation and co-determination requirements differ by country and by the size and structure of the employer. This entry names the regimes and describes their shape; take advice in each jurisdiction before planning a deployment.

Getting the timing into the plan

Add the consultation period to the schedule as a dependency with a duration rather than as a step. Where a works council meets monthly, three rounds of questions is a quarter, and that is a normal rather than an obstructive pace.

What to bring to the first meeting

The notice from the entry above, a description of what is not collected, the retention schedule, and a statement of what the data will not be used for. Bringing those unprompted changes the character of the conversation entirely.

Agreements have terms

An agreement with a representative body typically specifies what may be collected and how it may be used, and those terms bind you afterwards. Read them as operating constraints rather than as a hurdle cleared, because a later feature request may sit outside them.

Where no council exists

Most employers in most countries have no such body, and the obligation does not arise. The practices this entry describes are still worth adopting: they are what a council would have asked for, and they produce the same result without one.

The review clause

Councils frequently ask for a review after six or twelve months, and it is worth agreeing to rather than resisting. It converts a permanent decision into a trial, which makes agreement easier, and the review is generally uneventful.

A short summary

Find out whether a body has rights before scheduling anything. Add months, not weeks. Arrive with the notice, the retention schedule and a statement of what the data will not be used for. Expect an agreement with terms that bind you afterwards.

The frame that works

Arrive proposing a monitoring boundary rather than a feature set: here is what we will collect, here is what we will never collect, and here is how you can hold us to it. Councils negotiate boundaries readily and resist open-ended capability.

The information rights that exist more widely

Even where no agreement is required, many jurisdictions give representatives a right to be informed about systems that process employee data. Informing costs nothing and it is a considerably better position than being asked why they were not told.

Also in the law, named by jurisdiction