Skip to content
policy

Corrections Policy & Log

How to report an error, and how we show the fixes we make.

Accuracy matters more to us than speed, even though speed is part of our name. When we make a mistake, we want readers to know what changed and why. This page explains our process and will hold the public log of corrections.

How to report an error

Email [email protected] with the headline of the story, the specific sentence or figure you believe is wrong, and any evidence or sources that support your view. You don’t need to be an expert, and you don’t need to give your name if you’d prefer not to, though a way to contact you helps if we have questions.

How we review it

An editor who did not write the story reviews every correction request. We check the original sources, contact the people involved where appropriate, and decide whether a correction, a clarification or no change is needed. We aim to respond within a few working days, and faster for errors that could cause harm.

How corrections appear

  • Corrections fix factual errors. We change the text and add a dated note at the end of the story explaining what was wrong.
  • Clarifications address wording that was accurate but could mislead. We add a dated note explaining the change.
  • Updates add new information to a developing story and are marked with a time stamp.

We don’t silently delete or rewrite published content. Minor typographical fixes that don’t change meaning may be made without a note.

The log

No corrections have been logged during the launch edition so far. Because launch stories are illustrative scenarios rather than reports of real events, corrections to them will mostly concern internal consistency, clarity or mislabelled figures. When we publish a correction to any story, it will be listed here with the date, the headline and a short description of the change.

When we disagree

If we review a request and decide not to change a story, we will explain why. If you still disagree, you can ask for the decision to be reviewed by a second editor. We keep a record of all requests, including those that do not lead to changes, so we can spot patterns and improve.

Last updated 2026-10-05