Applies to: A recurring programme is being compared with an event specified as one fixed instant.
The useful distinctions
- A recurring local time can depend on timezone rules for each occurrence.
- A fixed UTC timestamp identifies one instant.
- Equal weekly clock labels do not imply a constant UTC offset.
Identify what the source intends to keep fixed
A source may intend a programme to recur at the same local wall-clock time, or it may announce a particular event as a fixed UTC instant. These are different scheduling promises. Preserve the wording and named location rather than converting the first occurrence and treating that UTC result as the permanent rule. A weekly local slot can keep its familiar hour while its UTC representation changes with the applicable seasonal rules.
Check an occurrence on each relevant date
For a recurring schedule, compare the actual dates involved and ask which clock the recurrence follows. For a one-off event, retain the announced instant and convert it for the viewer. Do not claim that either approach is universally correct for every broadcaster; the source’s intention decides the interpretation. If the source is unclear, ask before building a series of reminders that might be correct for one season and wrong for another.
Hypothetical worked example
A fictional programme is announced as “20:00 Europe/London every Wednesday”, while a separate fictional final is announced for a specific 20:00 UTC instant. The weekly programme’s summer and winter UTC representations can differ even though its intended local slot remains 20:00. Copying the first converted value into every future week would lose that intention. This example describes scheduling logic, not a verified broadcaster recurrence or an actual reminder feature in a player.
A focused way to proceed
- Ask whether the source intends a local recurring slot or a fixed instant.
- Keep the named location with each recurring occurrence.
- Compare each occurrence’s actual date instead of copying one conversion forever.
When to stop or ask for help
Confirm the source’s recurrence convention and retain date-specific conversions rather than a permanent copied offset.