Time Tracking Shows When We Work—Not What We Do
Working hours are relatively easy to measure. An employee starts at 8 a.m., takes a break, and finishes at 5 p.m. The time record shows eight hours. But an important question remains: What actually happened during those eight hours?
A pilot project in Bremen, Germany, brings this question into focus. During the 2026–2027 school year, teachers at nine schools are recording not only their working hours but also the activities that fill them. These include lesson preparation, grading, supervising breaks, advising parents, attending conferences, organizing class trips, and resolving conflicts—all essential tasks that can remain invisible when workload is measured mainly by teaching hours.
The lesson extends far beyond education: Is time tracking enough to understand how work gets done today? In many workplaces, it is not.
Time Tracking vs. Activity Tracking
In industrial settings, time was once a useful indicator of work. Today’s knowledge work is more complex. A software developer may spend a day coding, investigating bugs, attending meetings, documenting systems, helping colleagues, and responding to messages. A patent attorney may review files, advise clients, check deadlines, draft legal documents, and handle administrative communication.
Both employees might record eight hours, yet their days—and the implications for planning and productivity—could be very different.
Time tracking records when work starts and ends and how long it lasts. Activity tracking adds context by showing how that time is spent. Combining the two creates a clearer picture of workloads, processes, and how work is distributed.
The Bremen Teachers’ Pilot Shows Why Context Matters
For teachers, the distinction is particularly clear. Teaching hours are only one part of the job; preparation, grading, administration, parent communication, and conflict resolution also take time.
Bremen’s education senator, Mark Rackles, has argued in connection with the pilot that the focus should move beyond scheduled teaching hours toward total working time. But total hours are only the starting point. If a teacher works 50 hours in a week, it also matters how those hours are divided among teaching, preparation, grading, administration, and communication.
One teacher involved in the pilot reportedly found that the workload reached around 50 hours a week at the start of the school year. Recording activities also encouraged a more deliberate approach to organizing the working day. This illustrates an important effect of activity transparency: measurement can change awareness. Patterns that were previously only a vague impression become visible.
Transparency Should Improve Work—not Become Surveillance
Detailed activity tracking can raise concerns about employee surveillance. That is why the purpose of collecting data must be clear from the start.
Activity records should not become a tool for continuously ranking individuals or comparing how many minutes different employees need for the same task. That approach can undermine trust rather than improve work.
The real value lies in understanding how work is distributed, which processes consume disproportionate time, how often interruptions occur, and which tasks take up more of the day than expected. The useful question is not, “What did this employee do for eight hours?” but “Which activities shape our working day, and does that distribution support our goals?”
Activity Transparency Helps Explain Overload
Knowing that someone regularly works ten hours a day signals a problem, but it does not explain its cause. The workload may come from too many operational tasks, excessive meetings, growing documentation requirements, administrative work, or repetitive manual processes.
Without insight into activities, conversations about overload remain abstract. With it, organizations can identify where pressure originates and decide whether to add staff, redistribute tasks, redesign workflows, automate repetitive steps, or stop doing work that no longer adds value.
Why Activity Data Matters for AI and Automation
As organizations invest in artificial intelligence, activity transparency becomes even more important. Businesses want to know whether AI tools are improving productivity—but that is difficult to assess without understanding how employees spend their time.
Imagine that an AI tool reduces the time needed to produce a document from two hours to 30 minutes. That appears to save 90 minutes. But are those minutes genuinely freed up, redirected to higher-value work, or absorbed by other tasks? Time records alone cannot answer that question. Activity data can help organizations evaluate where the time goes and whether the expected productivity gains materialize.
From Compliance to Better Organizational Decisions
Working-time recording has also gained legal importance in Germany. In 2022, the Federal Labour Court (Bundesarbeitsgericht) held that employers are generally required to establish a system for recording the beginning and end of daily working time. Organizations should not treat time recording solely as a compliance exercise, however.
Existing records can become more useful when time is also categorized by activity. This does not necessarily require minute-by-minute project accounting. Even broad categories can reveal patterns—for example, how much time a manager spends on strategy, people leadership, customer contact, administration, and operational problem-solving.
Developers might distinguish between development, debugging, meetings, support, and documentation. Law firms could track client work, communication, deadline management, research, and internal administration.
Tools such as TimeSpin follow this principle: the goal is not simply to count hours, but to understand the activities to which those hours are allocated. Instead of seeing only a 45-hour workweek, an organization can build a clearer picture of what that week actually involved.
The Key Metric Is How Time Is Used
Debates about whether a 35-, 38-, or 40-hour workweek is ideal are legitimate, but hours alone tell only part of the story. Two people can each work 40 hours and experience very different workloads. Two companies can invest the same number of working hours and achieve very different results.
Organizations need to understand how much time goes to core work, coordination, administration, tasks created by inefficient processes, and activities that could be automated or organized differently. That insight supports better decisions than knowing only that employees worked an average of 8.2 hours a day.
Conclusion: Move from Time Tracking to Activity Transparency
The Bremen teachers’ pilot may offer lessons that reach well beyond education. Organizations need to look at working time as more than a number. They understand work more fully when they can see which activities fill that time.
Time tracking answers: How long did we work?
Activity transparency answers: What did we work on—and was that the best use of our time?
Top comments (0)