A preview names what the team and the organiser have signed for; the editorial scenario below it is the desk's reading, not a forecast. Reviews are written from the broadcast tape and any gap in footage is flagged in the byline.
Each preview is written against the same nine-block template: confirmed rosters, announced map pool or patch, broadcast window, venue note, regulatory note (region-locked if applicable) and an editorial scenario reading.
Both teams are confirmed and dated in the organiser filing. Patch 7.4 has been referenced in published post-patch notes. The desk's reading: Quill's tempo in the early-game jungle contest is the single biggest variable.
Source: league filing 06 Aug · patch notes 31 Jul · broadcast cast note 02 Aug
Map pool restricted to six and announced 04 Aug. Kestrel's roster is on the partner clip. The desk's reading: Kestrel needs coordinated utility or Aurora's retake playbook claims the round.
Source: broadcast partner clip 05 Aug · player social 31 Jul
Both players are seeded and signed. Patch 9.0 is in scope (defensive meter gain reduced). The desk's reading: this is the more cautious round-one of the day and probably a slower first game.
Source: player interview 02 Aug · stream VOD 03 Aug · patch notes 28 Jul
Reviews are written from the broadcast tape after the round or match closes. Where the broadcast covered a different match or where audio was unclear, the desk publishes a shorter piece and flags the limit.
Team roster · the press-lineup wall the desk reads as the booked comp for the next preview.
A review answers one question — what changed the game. It does not give the round count or a K-D line unless the broadcast cut is reproducible on the partner's VOD. When the broadcast missed a frame, the review says so.
A second review answers what the next opponent should expect. We do not extend that section into a prediction; we list the variables we know and the variables still missing.
Below is the public archive of every preview the desk has published in the last thirty days. Each entry links to the broadcast tape it was built from.
Reader questions the desk answers weekly. Where a question belongs in the calendar, the desk deflects there; where it is unique to a match preview, it lives here.
A confirmed fact can be re-checked against a public source. An editorial scenario is the desk's read of the same facts, and we want the two to be visibly different on the page.
The desk updates the team ledger with the social note, then emails the organiser for confirmation. The preview carries the latest confirmed roster as of the day it was published.
Round counts inside a preview are filler; they imply a forecast. The desk only publishes round counts after the match closes, when they appear in the review, not the preview.