Data tracking done right

How offices can make good use of time and process data – and where the limits are

DataLegal & compliance
Thursday, October 15, 2026

“I couldn't tell you off the top of my head how many open reviews we have.” We heard this sentence in one of our conversations, and it's typical for many offices: there are hardly any reliable numbers about their own work.

The other extreme is familiar from the headlines: software that counts mouse movements, takes screenshots and logs every minute of the working day. Between these two poles lies a sensible path. It starts with a simple distinction: we measure processes, not people.

The question first, then the data

Collecting data just because you can is a common mistake. It's better to work the other way around: start with the question you want to answer. Which cases take the longest? Where do we wait, and for what? What comes up so often that it's worth simplifying? Only then do you work out which data you need for that – and which you don't.

That isn't just sensible, it's also a legal requirement. Article 5 of the EU General Data Protection Regulation requires that personal data be collected only for specified purposes and limited to what is necessary.

Along the way, not on top

Good data is created where the work happens anyway. When every step of a case runs as a task in the system, timestamps appear on their own: when a task was created and when it was completed. Nobody has to keep a list. That makes the data not only cheaper but also more honest, because what's created along the way doesn't get polished.

Process before person

The most important insights almost always lie in the totals. How long does a contract review take on average? Which chain has the longest waiting time? In which week do requests pile up? Questions like these don't call for evaluating individuals, but for averages, trends and teams. If you set up your reports this way, you answer your questions and avoid the impression that anyone is being watched.

The legal framework

When it comes to working time, the matter is clear: employers have to record it. The European Court of Justice ruled on this in principle in 2019 (Case C-55/18), and on September 13, 2022, Germany's Federal Labor Court held that the obligation already applies in Germany under the Occupational Safety and Health Act (1 ABR 22/21). The German Ministry of Labor has also presented a draft that would explicitly write electronic recording into the Working Hours Act. In early October 2026, it was still being coordinated within the federal government.

Co-determination matters, too. Under Section 87(1) no. 6 of the German Works Constitution Act, the works council has a say whenever technical systems are introduced that are designed to monitor employees' behavior or performance. According to case law, it's enough that a piece of software is objectively capable of doing so. Talking to the works council early saves a lot of trouble later.

This section is not legal advice. But it shows one thing: whoever records data should know why, and say so openly.

Data quality: no numbers without shared definitions

Numbers are only as good as the terms behind them. If one colleague marks a review as “done” as soon as the draft has been sent, and another only after the signature, every report compares apples with oranges. So agree together on when a step starts and when it ends. And make sure requests arrive in a structured way, for example through forms instead of free text. Otherwise, every report starts with a cleanup.

Trust built in: the example of WTAux

Our time tracking module WTAux shows how these principles translate into software. Employees see their own hours first and at any time: overtime, hours still to make up, the overview by day, week or month. Team leads see their team, HR sees everyone. An audit log records every change, so it's always clear who corrected what and when. And there are two kinds of entries: clock-in entries are created in real time and stay exactly as they were recorded. Manual entries rest on trust, the way many offices work anyway.

The result is a system both sides can trust: management, because the data is reliable, and employees, because they know who sees what.

Checklist: data tracking without surveillance

  1. Write down the questions you want to answer.
  2. Only collect the data that answers these questions.
  3. Let data be created as part of the work, not on top of it.
  4. Evaluate processes and teams, not individuals.
  5. Decide who sees which data, and tell everyone.
  6. Involve the works council early, where there is one.
  7. Agree on shared definitions for when a step starts and ends.
  8. Show employees their own data first.

Data doesn't make an office colder when you collect it the right way. It shows where work gets stuck, and so provides exactly the arguments you need to improve your processes. Find out more on the pages for WTAux and TaskAux. How to make workflows visible without setting up a project is the subject of our article Thinking in processes.

Sources