A useful guide correction record identifies the station edition, programme title, date, displayed time and expected time in a named timezone. It should describe the schedule error without exposing the guide URL’s credentials. That small amount of precise evidence is more actionable than a long unstructured conversation.
Capture the mismatch at the right moment
Include the date and local timezone with a screenshot or written note. A screenshot of a clock without a date becomes ambiguous later, especially across midnight or daylight-saving changes. Keep the relevant programme title visible.
State what still works
Say whether the channel plays and whether neighboring stations have accurate guides. This helps separate a source schedule correction from an account or import failure. Do not combine every unrelated app issue into the same report.
Redact private values
Mask account names, device keys, full playlist links and tokens before sharing evidence. Support can request a nonsecret account reference through the verified private channel. Public forums do not need live credentials to understand a timing mismatch.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
“City One East, 27 October, 20:00 local: guide shows a film, live station shows the news; other channels are correct” is a useful correction description.
Questions about this topic
Should I send the password with the screenshot?
No. Redact secrets and use the verified support route.
Is “EPG wrong” enough detail?
It rarely identifies the station, date or type of error needed for a correction.
