Corrections policy

Correct the fact. Preserve the forecast.

Prediction products need two different correction rules: factual and display errors should be fixed, while the pre-match probability must remain exactly what was published.

What can be corrected

  • A misspelled team, competition label or explanatory sentence.
  • A duplicate fixture, broken link, inaccessible interface or display calculation.
  • A settlement based on a provider result that was later officially corrected.
  • Documentation that inaccurately describes an active feature, model or data source.
  • Privacy or attribution information that is incomplete or incorrect.

What must not be rewritten

The locked pre-match record

Home, draw and away probabilities, original publication time, kick-off known at publication and model version must not be changed after the result to improve a hit rate or make a call look earlier.

If the underlying forecast payload itself was malformed, the record should be marked invalid with an explanation. It should not be replaced by a more favourable number and counted as though nothing happened.

How a correction is handled

  1. 01

    Identify

    Capture the affected URL, field, observed value and supporting source.

  2. 02

    Verify

    Compare the report with the source record, publication event and latest provider revision.

  3. 03

    Classify

    Separate a display correction, factual correction, settlement revision and invalid forecast.

  4. 04

    Publish

    Fix the current presentation and add a dated note when the change is material.

  5. 05

    Recalculate transparently

    If a settlement changes, recompute affected metrics from the corrected result without touching the original prediction.

Report an issue

The contact page shows whether a monitored inbox is available. Include the page URL, exact problem and a reliable source. A report does not guarantee a change; the evidence and audit trail determine the outcome.