Applies to: A viewer finds two different advertised start times for the same event.
The useful distinctions
- A time value needs its date and clock context.
- A later announcement can describe a different plan.
- Two clock numbers alone cannot establish the cause of disagreement.
Retain both announcements before choosing one
When a start time changes in a message or event page, preserve the publication context of both versions. The organiser may have revised the plan, or the two announcements may refer to different timezones, sessions or programme segments. A pair of clock numbers is not enough to distinguish those explanations. Keep the event’s complete name and edition with each record rather than silently replacing one time and losing the evidence of the change.
Ask a source question before a player question
Compare the stated date, timezone and session in each announcement. If those are the same but the newer source explicitly revises the start, the enquiry concerns the current event schedule. If the clock contexts differ, a date-aware conversion may explain the apparent change. Do not claim that refreshing an account will settle which announcement is authoritative. The source owner or organiser may need to confirm the intended start before the guide can be assessed meaningfully.
Hypothetical worked example
A fictional “Autumn Final” announcement published on 6 November gives 18:00 UTC for 8 November 2026. A later hypothetical announcement gives 18:30 UTC for the same session and date. The viewer records both publication contexts and asks whether the event was rescheduled. The example calls for a source-time confirmation, not an assumption that every programme in the guide has acquired a thirty-minute clock error.
A focused way to proceed
- Keep the original and revised announcements with their publication dates.
- Record each stated event date and timezone.
- Ask which announcement is current before changing a guide setting.
When to stop or ask for help
Confirm the current event announcement and preserve any genuine revision in the support record.