Corrections Policy
Predictions are, by definition, sometimes going to be wrong. Here's what happens when a publisher proves one wrong, or when we simply get something wrong ourselves.
When an official announcement lands
The moment a publisher, developer, or platform holder confirms something we'd previously labeled Estimated, we replace that content with the confirmed version and switch its status pill from Estimated to Confirmed. We don't leave a superseded prediction live next to the real answer.
When we simply get something wrong
Factual errors happen, a wrong date, a mislabeled spec, an outdated price. When one is reported (see Contact) or caught internally, we fix it directly rather than issuing a visible retraction notice, since most errors here are small factual details, not editorial stances. Corrections to factual errors are prioritized and typically actioned within a few days of being reported.
How to report an error
Email hello@gamereadycheck.com with the page URL and a description of what's wrong. Include a source if you have one (an official announcement, a patch note, a store listing), it speeds up verification.
How updates are tracked
Most content pages display a "Last updated" date, generated automatically from the page file's own modification time rather than typed in by hand, so it can't silently go stale. For predictions where a real historical record adds value, such as GTA 6's requirement predictions, we maintain a dated changelog on the relevant page rather than a single overall timestamp.