Accuracy and accountability

Corrections policy

How rule changes, factual errors and unclear labels are reviewed and corrected.

Report with evidence

Use the contact form and include the page URL, the exact statement, the date observed and an official source where possible. Do not include sensitive ticket data.

Review order

Safety-critical and money-related errors are prioritised, followed by live-data mapping, rule explanations, translations and presentation issues.

Visible corrections

Material editorial changes should update the page date or correction note. Provider outages are labelled as availability issues and are not replaced with invented data.

Report an error with enough context

Send the page URL, the wording or field that looks wrong, when you saw it and a supporting official source if you have one. A screenshot should hide the full PNR, passenger details and ticket QR code. A tool error and an outdated railway rule are different issues: describe which one you found. We do not promise a response time or claim that every page is continuously verified.

Corrections policy: how to use the result

Make the correction easy to reproduce

A useful report contains the exact page, the inaccurate sentence or result field, what you expected and an official source where relevant. For calculator problems, use made-up inputs that reproduce the issue. Avoid sending a real passenger record.

Separate a rule change from stale live data

A new railway circular, an untranslated label and a provider outage require different fixes. Tell us which you observed. Include a notice’s effective date as well as its publication date; they need not be the same.

Examples are illustrative. If you find an error, send the page address and a source for the correction. Corrections process

Accuracy and accountability: questions and corrections

Use the contact process without sharing sensitive ticket information.