Daylight saving time is a seasonal change to civil clock rules used in some regions. It affects the numerical offset between local time and UTC for particular dates, while other regions keep a consistent offset. For a programme guide, the important task is converting each scheduled instant using the correct regional rules for that date. A fixed offset is not a substitute for those rules. Schedule sources and device timezone data must remain suitable for the region, and a one-hour error near a clock change should be investigated before applying a permanent guide shift.
Daylight saving time and UTC
UTC does not observe seasonal clock changes; local civil time can change its offset from UTC.
Clock changes create unusual local times
When clocks move forward, some local times do not occur. When clocks move back, a range of wall-clock times occurs twice. Explicit offsets distinguish the two occurrences of an otherwise identical time. A guide that stores only an ambiguous local clock reading can place programmes incorrectly around the transition even if ordinary days appeared correct before it.
Source and viewer regions can differ
A channel’s production region and the viewer’s region need not change clocks on the same date, or at all. Converting through a correctly identified instant handles that difference. Manually assuming a constant time gap between regions can fail during the weeks when their seasonal rules differ. The guide should follow date-aware conversion rather than a memorised year-round difference.
Review before making a correction
Check the affected dates, source offsets and selected device region. Compare channels from different guide sources to see whether the problem is widespread. If a previous manual correction was added during another season, test without it. Timezone rules can change through public policy, so device software and timezone data may matter when a region’s current rules differ from older assumptions.
An illustrative example
During a backward clock change, a region can have two local 01:30 times with different UTC offsets. A programme carrying the correct offset remains distinguishable from another scheduled at the repeated clock time. Treating both as the same unqualified wall-clock value can put one entry in the wrong position.
Practical actions
- Check source offsets on both sides of the clock change.
- Use a regional timezone rather than a fixed seasonal offset.
- Review old manual corrections after a seasonal transition.