Match briefings separate operator-confirmed facts from open editorial questions

Two columns, one page. The desk splits the page down the middle. Confirmed on the left, open on the right. The desk will not invent a third column for “probable” or “likely.” Speculation is not a fact at any strength.

A third column creates a category the desk cannot source. Probable and likely are subjective; the desk reads from operator pages, publisher notes and the governing body. None of those sources publishes a probability column. Adding a probable column to the briefing would mean the desk is making a probability up, and a probability the desk made up is a fact error waiting to happen.

Two columns also keep the editorial copy honest. The copy uses the same vocabulary across the site: confirmed, announced, speculative. The two columns on the briefing map directly onto two of those three tiers. The third tier (speculative) appears on the dispatch stream as a flagged dispatch line, not as a row in the briefing column. The desk's pattern: speculative goes in the briefing queue, not on the briefing ledger.

Where a correction lands

If a row was placed in the confirmed column and the desk later finds it should have been in the open column, the desk posts a dated correction on the dispatch stream and updates the row in place. The desk does not silently move the row. The reader can see the before and after on the dispatch stream and decide whether to trust the desk going forward.

The desk treats every correction as a signal about a recurring gap. If three corrections in a row push back the same source, the desk considers whether the source is still Tier-1 and updates the evidence register accordingly. The register is a working document — the desk revises the tier labels when warranted, not because a reader complains.

The first habit is to read the operator match page before the trade press read. The operator match page names the stage, the format ruleset, the patch window, the listed casters and the time. Trade press may also name those facts but does not publish them first; reading the operator first means the desk is anchored on the source and only later enriched with interpretation. The desk does not paraphrase the trade press back as if it were the operator page because the desk does not read the trade press first.

The second habit is to write the confirmed column before the open column. A reader who reads the desk for the first time will notice that every briefing ledger has the confirmed facts on the left and the open questions on the right. The editorial reason for the split is that conflation is the most common source of corrections on other sites. A row in the wrong column reads as a fact; the desk wants to remove that risk. The editorial vocabulary on each side mirrors the discipline: confirmed on the left uses Tier-1 language, open on the right uses pending language.

The third habit is to keep the open column honest. The desk has three rates of questions on the open column: questions that two independent Tier-1 sources answer within 24 hours, questions one Tier-1 source answers and the other remains silent on, and questions no Tier-1 source has answered yet. The desk uses the second category only when the unanswered side is plausibly time-delayed. The desk uses the third category only when the question is operationally relevant to a reader making a viewing decision. The desk does not invent questions for the third category to make the column look fuller.

Where the desk diverges from coverage that mirrors trade-press reads is on the rate-the-column discipline. Trade press will sometimes promote a Tier-2 read into the confirmed column on the basis of one named source. The desk does not. The desk waits for two Tier-1 sources on the same fact, or one Tier-1 source that itself cites the operator record. Both conditions are required for confirmed. The discipline is sometimes slower; it is always more honest. Readers who want a higher read cadence can add operator pages to their own bookmarks.

The desk also treats the briefing ledger as a working document. Rows move up the confirmation ladder as sources confirm; rows that fall off the operator page get removed, not retained as a footnote. The ledger is rebuilt from 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. Readers who want a fuller view can add operator pages to their own bookmarks.

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