Daylight Saving Time 2026: Why Modern Time Tracking Shouldn’t Fear the Repeated Hour

On October 25, 2026, Germany will switch from daylight saving time back to standard time. For people, that means one extra hour of sleep. For professional time-tracking systems, however, the change should be little more than a change in how time is displayed. In fact, the annual clock change is an excellent test of how well software actually understands time. During the night of October 24-25, 2026, Central European Summer Time will end in Germany. At 3:00 a.m., the clocks will be set back to 2:00 a.m. As a result, the hour between 2:00 and 3:00 a.m. occurs twice. Germany's Physikalisch-Technische Bundesanstalt (PTB) even distinguishes the two periods as 2A and 2B to make them unambiguous. For most people, this simply means an extra hour in bed. From an IT perspective, however, it raises a surprisingly fundamental question: What does it actually mean to say that something happened at 2:30 a.m.? When 2:30 A.M. Happens Twice Imagine an employee starts working at 2:15 a.m. on October 25 and finishes at 2:45 a.m. At first glance, the calculation seems obvious: 30 minutes of work. But which 2:15 a.m. was it? Was it 2:15 before the clock was turned back, or 2:15 after the transition to standard time? The problem becomes even more obvious when an activity starts at 2:50 a.m. during daylight saving time and ends at 2:20 a.m. during standard time. If software simply subtracts the displayed local times, it could conclude that the employee somehow worked a negative amount of time. In reality, 30 minutes have passed. This is precisely why professional time-tracking systems cannot treat the displayed clock time as the complete representation of time. The underlying data needs to be based on an unambiguous timeline. Events should be associated with a unique timestamp and only converted into the user's local time zone for display. That way, a point in time remains identifiable regardless of whether the local clock is moving forward, moving backward, or being displayed according to another time-zone rule. Real Time Doesn't Stop When the Clock Changes Germany's legal time system distinguishes between Central European Time (CET) and Central European Summer Time (CEST). Under the current rules, daylight saving time ends on the last Sunday in October, when the clock moves from 3:00 a.m. CEST back to 2:00 a.m. CET. From the perspective of modern software, there is therefore no reason to suddenly "delete" an hour or artificially create one. The underlying timeline continues. What changes is the relationship between that timeline and the local clock displayed to the user. This may sound like a small technical distinction. For employee time tracking, project tracking, billing, and documentation, however, it can be extremely important. Time Tracking Is More Than a Clock on a Screen The distinction becomes particularly important for companies that track working hours, project time, billable activities, or tasks down to the minute or second. A modern time-tracking system needs to distinguish between three different concepts: - A point in time - A duration - A displayed local time When calculating how long an activity took, the system needs to know the amount of actual elapsed time between the beginning and the end of the activity. The local clock is primarily a representation of that information for the user. The same principle applies when employees travel between time zones. Imagine someone starts work in Germany in the morning, flies to New York, and records another activity after arriving. The displayed local time may suddenly shift by several hours. The underlying sequence of events, however, remains perfectly clear. A robust time-tracking system should preserve that sequence without forcing the user to think about time zones, offsets, or daylight saving rules. TimeSpin: Focus on the Activity, Not the Clock This is where the difference between a traditional punch clock and modern activity-based time tracking becomes particularly interesting. TimeSpin - Precision Time Tracking focuses on the activity rather than forcing employees to constantly interact with a running clock. With the physical TimeSpin cube, users simply rotate the device to the side representing the activity, project, or task they are working on. The system automatically records the corresponding time. The goal is simple: What did I spend my time on? The technical complexity behind that question should remain invisible to the user. Whether daylight saving time or standard time is in effect, whether a device changes its time zone, or whether an employee is working while traveling should not complicate the basic act of recording an activity. A professional time-tracking system should handle those conditions in the background. The Repeated Hour Is an Excellent Software Test The switch back to standard time is therefore a surprisingly useful test for the architecture of time-tracking software. A robust system should be able to handle situations such as: - An employee works across the daylight saving time transition. - An activity starts during the first 2 a.m. hour and ends during the second. - Multiple devices record or synchronize time information. - A mobile device temporarily operates offline. - Data is synchronized with a server at a later point. - Employees work simultaneously in different time zones. The key question is not what a particular device clock happens to display. The important questions are: When did the event actually happen? How much time actually elapsed? That turns what looks like a simple time-tracking feature into a classic distributed-systems problem. Offline Time Tracking Makes the Challenge Even More Interesting The issue becomes even more relevant for systems that do not require a permanent connection to a central server. TimeSpin's offline time tracking is designed so that tracked time can be stored locally and synchronized later. TimeSpin's documentation confirms that the cube can record time without a permanent internet connection and transfer the stored data during synchronization. That means correct time assignment cannot depend on having a permanent internet connection at the exact moment an activity is recorded. A professional data model needs to preserve enough information to reconstruct, even later, when an activity occurred and how long it lasted. Ideally, none of this complexity is visible to the employee. They simply turn the cube and continue working. The Clock Change Isn't Going Away - Yet Politically, Europe's twice-yearly clock change was supposed to have disappeared by now. The European Commission proposed ending seasonal clock changes in 2018. However, the proposal has not become final legislation. As of August 2026, the Council of the European Union states that no final decision has been taken and no timeline for such a decision has been defined. Until then, the current system remains in place. That means Germany will once again move its clocks back on Sunday, October 25, 2026, from 3:00 a.m. to 2:00 a.m. For people, the change can be noticeable. For software, it should be almost boring. And that is exactly the point. Good Software Hides Complexity From the User The annual clock change illustrates a fundamental principle of good business software: Complexity doesn't disappear when you ignore it. It has to be solved in the right place. Time zones, daylight saving rules, synchronization, offline operation, timestamps, and data consistency are technical concerns. Users should not have to understand them simply to record what they worked on. With time tracking, their attention should instead remain focused on the questions that actually matter to the business: - Which project consumed the most time? - How is workload distributed? - Which activities require more resources than expected? - Where are projects exceeding their budgets? - How does actual effort compare with planned effort? - Which tasks are creating bottlenecks? These are questions for employees, project managers, and business owners. Not: "Which of the two 2:30 a.m. timestamps did I just mean?" The Best Clock Change Is the One Nobody Notices The real test of modern time-tracking software is therefore not whether it can display the correct time after the clocks change. It is whether the user can continue working without thinking about the clock change at all. A well-designed system separates actual time, duration, local time, time zones, and synchronization at the technical level while presenting the user with a simple experience. That is the philosophy behind modern activity-based time tracking. And it is why the best time change in a modern time-tracking system is ultimately the one the user never notices. Top comments (0)