Applies to: Two different channels show the same live event or programme at one point in time.
The useful distinctions
- Programme coincidence does not itself establish channel identity.
- Distinct services can have different surrounding schedules.
- A source reference needs its own context.
Separate programme agreement from service agreement
Two services may show one programme together without having identical schedules for the rest of the day. The shared event is useful evidence of that programme, but it cannot settle every surrounding listing. Preserve both service names and inspect a boundary before or after the common item. This is particularly important when a matching suggestion appears persuasive only because the current event looks right on both channels.
Choose a comparison that could disprove the assumption
Look for a programme that differs between the services rather than another shared segment of the same event. A local bulletin, studio introduction or following programme can provide a clearer identity test where a reliable dated schedule is available. If the surrounding evidence is unavailable, mark the association as unresolved. Do not turn one coincidence into a claim that one guide is universally suitable for both services or that the same commentary and edition are included.
Hypothetical worked example
Fictional Harbor Sports and Meadow Sports both list the “Autumn Final” at 18:00 on 8 November 2026. At 20:30, one schedule continues with “Harbor Review” and the other with “Meadow News”. A match tested only during the final could appear correct for either service. Comparing the distinct following items reveals which association actually needs investigation, without implying any real event carriage or broadcast rights.
A focused way to proceed
- Record the shared programme and its date.
- Compare the preceding or following distinct items on each service.
- Keep the services separate until their broader association is confirmed.
When to stop or ask for help
Request confirmation using a programme boundary outside the shared event before reusing a guide association.