When fixture times disagree, build a short source hierarchy based on who owns each fact. The organizer defines the sporting schedule; a broadcaster defines its programme window; a calendar displays a converted version that may be stale.
Resolve event identity and time zones before choosing a winner between two clock values. Different labels can describe the same instant or different stages of coverage.
Confirm that the sources describe the same event
Match the competition edition, teams or participants, round, venue and date. A replay, another leg or a different session can share much of the title. A familiar thumbnail does not establish equivalence.
Then read what each time labels. A broadcaster's pregame start can precede scheduled play, and a venue-local listing can differ numerically from a browser-localized one. Neither is a conflict until the subject and reference zone match.
Use the primary owner for the relevant field
Start with the competition's current fixture or official change notice for scheduled play. Use the participating club or event organizer's official update as supporting context. The Premier League's fixture FAQ explicitly directs supporters to official changes and club communications.
Use the broadcaster for its own studio start, channel placement and presentation. Do not ask a calendar import to settle a fresh postponement when its source may not have refreshed. Third-party summaries can help discovery but should not override a newer relevant primary notice.
| Question | First source to inspect |
|---|---|
| When is scheduled play? | Competition or event organizer |
| When does this programme begin? | Named broadcaster |
| What does my local clock show? | Date-aware conversion of the confirmed instant |
| Why does my calendar differ? | Import/subscription source and refresh state |
Normalize the time before comparing
Record the original date, time and named zone from each relevant source. Convert them to one common reference, such as UTC, using current zone data. Check the local date and any repeated clock interval near a seasonal transition.
If both become the same instant, the disagreement was presentation. If they remain different, compare publication context and the latest official update. Do not manually split the difference or choose the result that best fits your evening.
- Match the complete event identity.
- Label play versus coverage.
- Read each source’s zone and update context.
- Convert confirmed times to one reference.
- Reconcile stale calendar entries and retain the official source.
Keep an unresolved conflict visible
If the organizer has not confirmed a time or two primary notices remain inconsistent, leave the entry tentative and seek the official clarification. A guessed timestamp can spread quickly once shared as a confident reminder.
A useful outcome is one supported event instant with the source retained, or a precise unresolved field. It does not establish broadcast access or IPTV USA carriage. Timing and availability require their own evidence.
Useful answers
Should I always trust my calendar over a new official notice?
No. An import can be a snapshot and a subscription can lag. Reconcile it with the current organizer update.
Can two different local clock values describe the same fixture time?
Yes. Convert the complete dates and named zones to one reference before treating them as a conflict.