Correction 2026-08-03 Dispatch · Tier-1

Regional qualification question remains open after governing-body note

A correction posted at 09:32 UTC supersedes a Tier-2 sports desk report from 02 August. The qualification question remains open; the desk does not extrapolate outcome.

The desk is posting a correction against a Tier-2 sports desk report from 02 August. The original report claimed the regional qualification question had been settled by a governing-body statement. The governing body has since clarified that the statement was a procedural note, not a qualification decision.

The desk verified the clarification against the governing-body page at 09:30 UTC and the operator's qualification page at 09:31 UTC. Both sources confirm the procedural-note reading. The qualification question remains open; the desk does not extrapolate outcome.

What this correction is not

This correction is not a retraction of the desk's editorial position on the qualification question. The desk has never published an editorial position on the question; the desk has only published the existence of the question and its procedural status. The correction is against the Tier-2 report, not against the desk.

What the desk is now reading

The desk is now reading the governing-body page daily until the qualification question is settled. The desk will publish a follow-up dispatch on the day the governing body publishes a qualification decision, with the date and source of the decision. Until then, the qualification question stays on the briefing queue as an open question.

The corrections policy on the dispatch stream applies: reader-filed corrections are verified against the desk's tier rules before publication. This correction was filed by the desk itself on the basis of a re-read of the governing-body page.

Source: Publisher patch-notes page · Verified 2026-08-03 by the desk · Tier-1 source on file

Return to the dispatch stream →

Reader depth

Reading a regional qualification question against the governing body

Three habits the desk follows when reading a regional qualification question.

The first habit is to verify the governing-body page on the same day as the question is filed. The desk verified the governing-body page at 09:30 UTC and the operator's qualification page at 09:31 UTC; both sources confirm the procedural-note reading. The editorial practice is to verify any source change on a Tier-1 page on the same day the change is filed, on the basis that immediate verification gives the desk enough certainty to publish a correction.

The second habit is to log the verification timestamps on the dispatch. The dispatch line names the source the desk consulted and the date the desk verified the source. The practice protects the reader from seeing a date-less dispatch line and protects the desk from a corrections cycle that is harder than the original publication. The verification timestamps are also useful internally when the desk re-reads the governing-body page on the next weekday morning.

The third habit is to publish the question, not the answer. The desk's editorial practice is to publish the existence of the question and its procedural status, not to extrapolate an outcome. The qualification question remains open; the desk does not extrapolate outcome. A reader who wants a wagering-analysis read should consult a dedicated publication; the desk's editorial scope does not extend to wagering analysis.

Where the desk diverges from coverage that mirrors trade-press reads is on the outcome-discipline policy. Trade press will sometimes extrapolate an outcome on the basis of one named source, or on the basis of a procedural note. The desk does not. The desk publishes the question, the source, and the procedural status; the desk does not extrapolate.

The desk also treats the qualification question as a working document. Rows move up the question-ladder as sources confirm; rows that fall off the publisher or operator page get removed, not retained as a footnote. The question is rebuilt from publisher and operator pages only. A row the desk kept for "tracking purposes" is a row the reader cannot verify, so the desk removes rather than retains. This is sometimes the slower choice; it is always the more honest choice.

Editorial cycle: weekday-morning source-scan, weekday-afternoon narrative-edit, weekly patch workshop. Verification timestamps on the dispatch stream.

Editorial working notes

How the desk reads this

A working description of the editorial cadence the desk follows on this route.

The regional qualification question is verified against both the governing-body page and the operator qualification page. The desk verified the governing-body page at 09:30 UTC and the operator qualification page at 09:31 UTC; both sources confirm the procedural-note reading. The two verifications give the desk enough certainty to publish a correction on the dispatch stream.

Where the regional qualification question covers the procedural-note reading. The governing-body note was a procedural note, not a qualification decision. The desk publishes the procedural-note reading on the dispatch stream rather than extrapolate a qualification outcome. The qualification question remains open; the desk does not extrapolate outcome.

Where the desk reads the next regional qualification update. The desk is reading the governing-body page daily until the qualification question is settled. The desk will publish a follow-up dispatch on the day the governing body publishes a qualification decision, with the date and source of the decision. Until then, the qualification question stays on the briefing queue as an open question.

Where the regional qualification question covers the publication cadence. The governing body publishes on weekday mornings in the relevant region. The desk reads the governing-body page on weekday mornings and notes any change against the prior day. The cadence is documented on /methods/ and reproduced in summary form on /about/.

What the desk will do if the governing body publishes a substantive change to the qualification question. The desk will publish a follow-up dispatch on the dispatch stream with the substantive change and the date the change was published. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier.

Worked example

How the cycle reads in practice

A worked trace of the editorial cycle on this page.

A worked example of the procedural-note reading in practice. The governing-body note was published at 09:30 UTC. The operator qualification page updated at 09:31 UTC. The desk verified both sources within 24 hours and confirmed the procedural-note reading. The desk published a correction on the dispatch stream with the verification timestamps logged.

Where the dispatch covers what the procedural-note reading is not. The procedural note is not a qualification decision. The desk publishes the procedural-note reading on the dispatch stream rather than extrapolate a qualification outcome. The qualification question remains open; the desk does not extrapolate outcome.

Where the dispatch covers the next governing-body publication cadence. The governing body publishes on weekday mornings in the relevant region. The desk reads the governing-body page on weekday mornings and notes any change against the prior day. The cadence is documented on /methods/ and reproduced in summary form on /about/.

Where the dispatch covers what the corrections register is. The corrections register is published on /about/#corrections. The register lists every correction the desk has published and the date of each. The audit-trail publication is documented on /methods/. The reader can audit the desk's editorial hygiene against the public register.

What the desk will do if the governing body publishes a qualification decision. The desk will publish a follow-up dispatch on the dispatch stream with the qualification decision and the date the decision was published. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier. The qualification question is closed on the briefing queue when the decision publishes.

Editorial practice

How the desk reads this in practice

A working description of the editorial cadence the desk follows on this page.

A worked example of the procedural-note reading cadence in practice. The governing body publishes procedural notes on weekday mornings in the relevant region. The desk reads the governing-body page on weekday mornings and notes any change against the prior day. The cadence is documented on /methods/ and reproduced in summary form on /about/.

Where the dispatch covers what the desk publishes as correction. The correction is dated, named against the entry being corrected and tied to the source that triggered the correction. The corrected entry remains in place; the dispatch stream shows the before and after in chronological order. The corrections register on /about/#corrections is the audit log for every correction the desk has published.

Where the dispatch covers what the desk does not publish. The desk does not publish the qualification outcome as a projection. The desk does not extrapolate a wagering-guidance read from the procedural note. The desk does not name a source the desk cannot verify. The dispatch stream is the desk's editorial scope as it relates to the regional qualification question.

Where the dispatch covers what the reader sees on the briefing queue. The briefing queue on the homepage lists the open question. The open question is published on the briefing queue until the governing body publishes a qualification decision. The desk will publish a follow-up dispatch on the day the governing body publishes a qualification decision.

What the desk will do if the governing body's procedural note is updated. The desk will publish a follow-up dispatch on the dispatch stream with the update and the date the update was published. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier. The procedural-note reading is logged on the dispatch stream and the briefing queue.