Match coverage — live fixtures, broadcast schedules and editorial previews
The matches desk pairs verified scores with editorial previews 24 hours before every match day. Where two desk shifts run in parallel (APAC + EMEA on the same evening), coverage is split so the in-game end stamp lands within 60 seconds of the publisher stream.
Today's fixture list — verified and editorially framed
APAC Major · lower bracket round 1
Four BO3 fixtures spread across the APAC major stage. Publisher primary stream, EN + JA audio.
EMEA Championship · quarter-final 2
Northwind Hydra vs Ember Wolves. BO5 with map veto publishable in advance per the publisher's tournament rules.
APAC Major · upper bracket semi-final
Sakura Apex vs Coastline Foxes. The bracket's headline fixture this week.
Sakura Apex vs Coastline Foxes — preview snapshot
Verified + editorial · 19:00 UTC · BO5
PUBLISHED 02 AUG 02:14 UTC| Item | Detail | Source |
|---|---|---|
| Stage | Semi-final · APAC Major · BO5 | Publisher feed · A |
| Rosters | Sakura Apex: Akiyama, Hayate, Riko, Minato, Yuna | Editor verified · A |
| Map veto | Forge → Mirage → Apex-3 → Cascade → Tide | Coach interview · B |
| Patch | 7.42 · drops 31 July | Publisher feed · A |
| Opening tempo | Slower MAP-1 default — coach interview 31 July | Editor's read · C |
| Mid-round trigger | If Akiyama opens 1.0+, fast B execute round 7 | Editor's read · C |
Where to watch — by platform, region and accessibility
APAC Major — broadcast matrix
Refreshed 02:14 UTCSix things the matches desk checks on every fixture
Publisher feed lock
Publisher stream overlay + governing-body wire locked against the bracket position 24h before kickoff.
Roster check
Final rosters verified against the roster desk at kickoff − 30m.
Map veto
Veto published when both teams have locked it in; flagged PENDING until then.
Patch context
Patch number and the change log flagged on every preview that touches balance.
Live score
Score cross-checked against publisher overlay and governing body wire — 60s tolerance.
In-game notes
Optional analyst notes during commercial breaks only — never alongside verified scores.
Match coverage FAQ
How a verified score moves through the desk pipeline
A verified score is the desk's smallest editorial unit. The desk's pipeline from publisher stream overlay to a web-published score is six steps; the bracket row is updated within 60 seconds of the publisher's in-game end stamp; the article body lands within six hours. Below is the pipeline written out step-by-step, so readers can re-walk it themselves.
Six steps from in-game end to desk publication
The first step is the publisher stream overlay. The overlay is the publisher's authoritative score feed and is the desk's Tier-A citation. The desk reads the overlay at the same minute it appears. The desk does not write an article based on a verbal call, a chat message, or a community post; only the overlay counts as a verified score.
The second step is governing body cross-cite. Where the governing body publishes its own independent score feed — the tournament organiser's press wire, the publisher's partner press wire — the desk matches the overlay score against it. A disagreement of more than 60 seconds triggers a desk verification before any article body lands.
The third step is bracket row insertion. The bracket row on the affected tournament or matches page is updated the minute the publisher overlay and the governing body press agree. The row carries the verified score, the bracket position, the round number and the round-time-to-end in minutes. The row is stamped Tier-A and the editor's initials are recorded against it.
The fourth step is the app alert. Verified scores are pushed inside the companion app for readers who follow a single team or single tournament. The alert uses the same verified score and the same Tier-A stamp. The app alert lands before the web write-up; both surfaces keep the same stamp.
The fifth step is the article body. The article body is a short editorial piece with one verified lead and three or four contextual paragraphs. It runs after the app alert, generally within 30–90 minutes of the in-game end for daytime matches and 2–6 hours for late-night matches. The article body is where editorial scenario language appears — flagged with EDITOR'S READ or editorial scenario.
The sixth step is the post-match film note. A film-room note is filed within 24 hours for every bracket-stage match. The note logs the in-game end timestamps of two or three objective-control events, the round-by-round utility chain, and a one-line editorial read of the tempo. The note is part of the matches feed and links from the bracket row.
What the desk does not publish live
The desk does not publish mid-round commentary as a verified score. Mid-round notes are only filed under the live-blog tag during finals weekends, and only during commercial breaks; mid-round the score is held back to avoid issuing a stat against the publisher stream overlay that might later be corrected.
The desk does not publish a final score that disagrees with the publisher overlay by any margin. Where the governing body press wire disagrees, the desk holds the score for verification and stamps the row PENDING. PENDING rows are turned into verified rows within six hours of the disagreement, or the row is escalated to a Tier-A correction.
The desk does not publish reschedule announcements without the publisher's published schedule. A reschedule is a Tier-A item only when it appears in the publisher's official reschedule feed; verbal reschedule calls from the teams are Tier-B and live as REPORTED until the publisher feed catches up.
The 48-hour fixture timeline — what each column does and why the timeline recurs
The 48-hour fixture timeline is the matches page's signature device — a horizontal-strip rail that recurs across the home page, the matches page and the editorial colophon. It carries every fixture from the next 48 hours across all four regional series, with verified scores, map vetoes and editorial reads stacked row-by-row. The timeline helps be read on a phone in a single screen.
The four columns — fixture, time, stage, preview-link
The first column is the fixture: both team names with their current regional brackets in small italics below. The second column is the time: scheduled start time, time-to-kickoff and the projected round duration. The third column is the stage: group, lower bracket, upper bracket, semi, quarter, semi, final. The fourth column is the preview-link: the 24-hour match preview ledger for bracket-stage fixtures.
Why the timeline recurs
The timeline recurs across the home page, the matches page and the editorial colophon because the device — a horizontal-strip rail with verified scores on top and editorial reads below — is the desk's most readable mobile construct. A reader who follows a single team can scan the rail, see the team's next fixture, tap through to the preview ledger, and lock in their reading path before kickoff.
The recurrence is also deliberate. The home page's timeline is the season's headline; the matches page's timeline is the next 48 hours; the editorial colophon's timeline is the desk's last 24 hours. A reader who reads all three timelines gets the season's bracket state in three short scrolls.
How to read a fixture row
Each row opens with the team names. Then the scheduled start time, the broadcast platform, the language tracks available and the accessibility features. Then the stage and the round number. Then the map veto, if both teams have locked it in; otherwise, the row is stamped PENDING. Then the editorial read, if a preview ledger exists; otherwise, the row carries a link to the upcoming ledger.
What the timeline is not
The timeline is not a betting line. The desk does not publish or estimate betting lines on the timeline; the verified score appears only after the in-game end stamp. A row whose preview ledger carries an editorial scenario line is marked EDITOR'S READ; a row whose verified score is in dispute is marked PENDING until the desk resolves the dispute.
The timeline is not a projection. The desk does not project a team's next round on the timeline; the projection lives in the editorial scenario language, which is stamped and clipped to the verified facts above it.
The timeline is not a leaderboard. The desk does not rank teams across regions on the timeline; the ranking lives on the standings page, where it is a verified table.