Contact and corrections — how to reach the desk

What to include in a correction

A useful correction includes four things: the URL of the page, the claim that is wrong, the correct fact, and the primary source that supports the correction. A correction that is missing any of those four things will take longer to process. A correction that includes all four will be reviewed within the hour during an active match window.

Examples of primary sources: circuit registration PDFs, developer release notes, broadcaster schedules, governing-body notices. Examples of sources that are not primary: community summaries, social rumours, outlet reporting that does not attribute a primary source.

What to include in a tip

A useful tip includes the claim, the source if known, and whether you are willing to be on record. Source-on-record tips are preferred. Anonymous tips are accepted. The desk protects source identity when requested and when the tip is not already public.

The desk does not publish tips as confirmed facts. The desk uses tips as a starting point for a primary-source check. If the primary source confirms the tip, the desk publishes a verified note. If the primary source does not confirm the tip, the desk does not publish it.

What happens after you write

Corrections during an active match window are reviewed within the hour. Corrections outside an active match window are reviewed within 24 hours. Tips are reviewed within 48 hours. General enquiries are reviewed within 7 days. Substantive corrections result in a public note and a timestamp on the affected page.

The desk does not guarantee a reply to every message. The desk prioritises corrections and tips over general enquiries. If your message is a correction and you do not see a public note within the response window, write again with the four required fields.

What the desk will not do with your message

The desk will not sell your email address. The desk will not add you to a marketing list. The desk will not share your tip identity when you have requested protection and the tip is not already public. The desk will not accept paid content disguised as a tip or a correction.

Worked example — a good correction

Subject: Correction — Helix captain on /teams/. Body: The /teams/ page lists Cassia as captain. The APAC circuit registration PDF filed 2026-07-28 lists Mira as captain under rule 4.2. Attached: link to the circuit page and the filing reference. That is a good correction. It has the URL, the claim, the correct fact and the primary source.

The desk opens the PDF, confirms the filing, updates the dossier, stamps the correction and publishes a public note. The previous claim is not silently rewritten.

Worked example — a tip that becomes a note

A tip arrives: Orbital roster freeze extended for Stage 2. The tipper is on record. The desk opens the AMER circuit site, confirms the freeze, re-verifies the dossier within the hour and publishes a wire note with the source and the timestamp. The tip was the starting point. The primary source was the confirmation.

A tip that cannot be confirmed is not published. The desk replies when possible and does not invent a filing to match the tip.

Worked example — a coverage concern

A reader flags that a mid-page CTA was written in a way that looked like an editorial recommendation. The desk reviews the copy, revises it to restore the sponsorship label and boundary language, stamps the revision and publishes a short note on the responsible-play chapter if the concern was substantive.

Coverage concerns are how the boundary stays honest. The desk welcomes them.

Languages and response expectations

The desk currently handles correspondence in English. Response times are as published: corrections within the hour during live windows, tips within 48 hours, general enquiries within 7 days. The desk does not guarantee a reply to every message but prioritises corrections and tips.

Routing table

Factual error in a chapter or wire note → corrections@. Tip about a possible roster, schedule, patch or viewing change → tips@. Coverage boundary concern → corrections@ with subject line starting Coverage. Privacy request → desk@. Terms question → desk@. General partnership pitch that asks for unlabelled content → declined.

Using the wrong route slows you down more than it slows the desk. The desk still tries to reroute, but the SLA clocks start when the message is in the right box with the right fields.

Attachments help when they are primary-source PDFs or screenshots of circuit pages. Attachments that are unrelated binaries are dropped.

Do not send malware. Do not send bulk spam. Do not scrape the contact addresses to build lists.

After a correction publishes

You may not always receive a personal reply, but a substantive correction should produce a public stamp on the affected page. If you do not see that stamp within the SLA, write again with the four fields and the date of your first message.

Disagreements about editorial scenarios are not corrections. If you disagree with a scenario, you can still write; the desk may revise the scenario or explain why it remains. That thread is editorial discussion, not a factual correction SLA.

Disagreements about illustrative labels are welcome when a label is missing. Missing labels are method bugs.

Thank-you notes are optional. Clear source links are better than thanks.

Safety and abuse

Threats, harassment and doxxing attempts against staff or players will be preserved as needed for safety and will not receive editorial attention beyond that. The desk is not a channel for targeting competitors.

If your tip involves a safety risk at a live event, contact event security and local authorities first. The desk is not emergency services.

Whistleblower-style tips about circuit integrity are read carefully. They still require primary-source confirmation before publication. The desk will not publish based on anonymous allegation alone.

These rules protect sources who are acting in good faith and protect the desk from becoming a vector for abuse.

Response SLA summary

Corrections in a live match window: within one hour. Corrections otherwise: within 24 hours. Tips: within 48 hours. General enquiries: within 7 days. Privacy requests: within a reasonable period under applicable law. Abuse and threats: preserved as needed for safety, not handled as editorial tips.

SLAs are operational targets for a static editorial desk, not contractual guarantees of personal replies to every message. Public stamps on corrected pages are the primary proof that a factual correction landed.