THE REFERENCE SHELF / ORIGINAL EXPLAINER
How release corrections appear in Premiere Notes
A correction should explain what changed, who changed it and which dates it affects.
Published 30 October 2026 · Source examples checked 30 October 2026 · Slot Premieres editorial desk
Preserve the difference between an update and an error
A provider can revise a planned date, publish more detail or confirm that a game has launched. Those are source developments. We can also misread a date or attach the wrong source. Those are editorial errors. The correction note should name the kind of change instead of hiding both behind “updated”.
Our records contain a place for dated change notes. At launch of this edition there are no verified changes or delays logged. That is a statement about this publication’s review history, not a guarantee that a provider has never changed a schedule. We do not invent a corrections feed to make the site appear older than it is.
What a material note should contain
A useful note identifies the affected title, the field changed and the evidence supporting the new value. If a date changes, it should preserve the old value when that helps explain a saved item. If status changes from announced to released, link the release confirmation rather than merely changing the badge.
The date of the correction is the day we made that correction. It does not become the source publication date or the original release date. Keeping all three visible gives the reader enough information to judge freshness without an artificial “today” stamp on every page.
How the newsletter fits
Premiere Notes is the optional weekly editorial roundup described in the signup terms. A material correction should be stated in the next relevant edition when delivery is operating, with a link to the corrected record. We do not promise an immediate notification or an automated alert for every saved calendar entry.
All release records and corrections remain readable without signup. Newsletter subscription does not change the quality or amount of evidence shown on the site. During testing, delivery remains on hold; a form receipt does not mean that a newsletter has already been sent.
Report a problem with enough context
Use the contact page and include the release URL, the field that appears wrong and a direct source if you have one. An exact quote can help locate the issue, but please do not send copied article bodies or account documents. We do not need your gambling history to investigate a release date.
We review the evidence before changing the record. If the source is unavailable, we retain the previously reviewed record with its last check date and explain the access problem. A failed feed request must never erase the catalogue or silently replace it with unreviewed discovery results.