Applies to: A live programme continues beyond the scheduled start of the following item.
The useful distinctions
- A programme guide describes a schedule.
- An observed live transition and a planned boundary are different records.
- One overrun does not establish a permanent offset.
Describe the disagreement precisely
A guide may show the next programme while the current live event is still on screen. Record that specific discrepancy instead of immediately calling the clock wrong. The planned start and the observed transition are different pieces of evidence. Keep the service name and date, and avoid guessing how long the live event was supposed to last. A single overrun cannot establish that all future programmes should move by the same amount.
Look for evidence outside the live boundary
Check a known earlier item or an unrelated service against its own dated schedule. If those align, a global offset is less helpful than a report about the live event’s actual finish. If the guide later catches up with the programme sequence, preserve that observation too. The viewer does not need to promise a revised broadcast time or identify an organiser’s decision; the useful task is to show when the published sequence and actual picture diverged.
Hypothetical worked example
On 8 November 2026, fictional Harbor Sports lists “Evening Review” at 20:00. The live final continues until 20:14, after which the review begins. Earlier programme boundaries and an unrelated news channel were aligned. This case supports a report of a fourteen-minute live overrun. It does not support setting a permanent fourteen-minute offset that would also move tomorrow’s unrelated listings.
A focused way to proceed
- Record the scheduled boundary and the observed transition.
- Check whether other services and earlier items align.
- Report the specific overrun rather than shifting the whole guide.
When to stop or ask for help
Send the planned boundary and observed transition as a dated schedule discrepancy, without promising a revised event duration.