Twenty-eight active series across five game chapters, each row carrying a region chip, a format tag, a prize tier band, and a source badge. The desk refreshes the ledger every Monday and on every Tier 1 release.
Region, format, prize tier and source confidence are independent filters. Each row's badge tells you which column to trust first.
The desk builds the ledger around four filters. Pick any combination and the rows re-order so the most recent verification lands at the top.
The region chip on the left tells you where the qualifier is hosted. Cross-region events carry a multi-region tag and a single primary region.
Format tags follow the league's official wording. Where the desk disagrees with the league's format tag, the row carries a footnote.
Prize tiers are bands, not exact figures. The desk uses S · $1M+, A · $100K–$1M, B · $25K–$100K, C · below $25K. Where the prize is unknown, the cell reads TBD.
Read the rows in the order that fits your week. The right-most column is the source badge; trust the row before you trust the cell.
| Event | Window | Region | Format | Prize tier | Source |
|---|---|---|---|---|---|
| Counter-Strike Major · Stage 28 qualified, 2 advance | Aug 04–10 | EU | DE | S · $1M+ | Tier 1 — League/Official |
| Hextech Open · Group B8-team groups, top 2 advance | Aug 04–06 | APAC | RR | A · $100K–$1M | Tier 2 — Verified org |
| Apex Predator Cup · Stage 220-team match point | Aug 04–07 | NA | MP | A · $100K–$1M | Tier 1 — League/Official |
| Fighting Games Cup · Top 8Double elimination | Aug 05–08 | Global | DE | B · $25K–$100K | Tier 1 — League/Official |
| Sim Racing Continental · Rd 9Three-race round | Aug 06 | EU | RR | C · <$25K | Tier 3 — Established media |
| Battle Royale Open · Mid-seasonSolo + duo pools | Aug 09–11 | SA | GSL | B · $25K–$100K | Tier 2 — Verified org |
| Underground Series · Closed qualifier4 spots to LAN | Aug 09–11 | SA | GSL | B · $25K–$100K | Tier 4 — Community |
| MOBA Winter Invitational · Group stage12 teams, 4 advance | Aug 12–16 | APAC | Swiss | A · $100K–$1M | Tier 1 — League/Official |
Every ledger row carries one source tier. The desk does not promote a Tier 4 row to a Tier 1 row by editorial decision; the badge is the source, not the desk's confidence.
League announcements and qualifier windows. The desk treats the date as fixed when the league's channel carries it. Tier 1 does not extend to bracket projection or roster commentary.
Where the org posts a roster, the desk logs it on the same day. Where a Tier 2 source conflicts with a Tier 1 source, the Tier 1 source wins and the row is annotated.
Used where the desk needs a meta reading or a broadcast schedule. Tier 3 readings carry a named reporter and a date stamp on the methodology page.
Useful for shape of the bracket. Never used to anchor a Tier 1 dossier. Tier 4 rows carry a rumor badge and are not promoted to a higher tier without independent confirmation.
Where to go next once you've picked a tournament to watch this week.
The desk's match ledger pairs the schedule with the platform, format and source tier for each row.
Open the match desk
Each roster the ledger lists has a dossier on the teams page, with the change log and verification date.
Read the dossiers
The matrix tells you which platform carries the broadcast by region, plus replay and caption support.
Open the matrixThe calendar ledger is the desk's primary surface. It is dense on purpose: a reader who opens the ledger is looking for a verification date, a region chip, a format tag, and a prize tier band. The four fields answer the four questions a competitive gaming reader brings to a tournament listing — where, when, what shape, and what the source is.
The format is not editorial decoration. The desk tested the four-field column against three alternatives — a calendar widget, a featured card row, and a map-driven layout — and found that the ledger table answered the most common questions in the shortest number of screen pixels. The map-driven layout added visual richness at the cost of clarity; the calendar widget compressed the prize tier band out of the row.
Two design choices follow from that test. First, the ledger is the same shape on every page that uses it; the calendar widget would have forced a per-page redesign. Second, the source badge sits at the right edge of every row, so a reader scanning the ledger reads the source last and trusts the row before they trust the cell.
The calendar ledger is the desk's primary surface. It is dense on purpose: a reader who opens the ledger is looking for a verification date, a region chip, a format tag, and a prize tier band. The four fields answer the four questions a competitive gaming reader brings to a tournament listing — where, when, what shape, and what the source is.
The format is not editorial decoration. The desk tested the four-field column against three alternatives — a calendar widget, a featured card row, and a map-driven layout — and found that the ledger table answered the most common questions in the shortest number of screen pixels. The map-driven layout added visual richness at the cost of clarity; the calendar widget compressed the prize tier band out of the row.
Two design choices follow from that test. First, the ledger is the same shape on every page that uses it; the calendar widget would have forced a per-page redesign. Second, the source badge sits at the right edge of every row, so a reader scanning the ledger reads the source last and trusts the row before they trust the cell.
The calendar ledger links to the match desk, the team dossier, the player atlas and the patch workshop. The links are independent — a reader who knows the tournament can open the dossier without re-reading the calendar.
Where the ledger's row changes, the change is recorded on the change log with the previous row, the new row and the date. The desk's case for the explicit row change is that a ledger without a change log reads as static.
The desk does not promote a calendar ledger row's tier by editorial decision. A Tier 4 row carries a rumor badge and stays Tier 4 until a Tier 1 or Tier 2 source confirms it. The desk's case for the no-promotion rule is that an editorial promotion would conflate the desk's confidence with the source's confirmation.
The desk answers the most common reader questions about this surface in editorial voice. The FAQ is editorial — the desk does not invent answers; the answers cite the surface that already carries the answer.
Region, format, prize tier band and source badge. The desk refreshes the ledger every Monday and on every Tier 1 release.
The four-field column answers the most common questions in the shortest number of screen pixels. The calendar widget compressed the prize tier band out of the row.
The badge tells you what the desk trusts about the row. A reader scanning the ledger reads the source last and trusts the row before they trust the cell.
The desk's source hierarchy lives on the methodology page. Every dossier, ledger row and match note carries one of four tiers: Tier 1 (League/Official), Tier 2 (Verified org), Tier 3 (Established media), Tier 4 (Community).
The source badge tells you what the desk trusts about the row. A Tier 1 source is a league announcement; a Tier 2 source is an org confirmation; a Tier 3 source is a named reporter; a Tier 4 source is a community post the desk has not yet verified.
The desk does not promote a row's tier by editorial decision. A Tier 4 row carries a rumor badge and stays Tier 4 until a Tier 1 or Tier 2 source confirms it. The desk's case for the no-promotion rule is that an editorial promotion would conflate the desk's confidence with the source's confirmation.
The surface refreshes weekly on Monday and on every Tier 1 release. The refresh date is published in the methodology block at the foot of every route.
The desk's RSS feed at /feed.xml carries every news desk story. The LLMs manifest at /llms.txt carries the editorial surface as a single document.
Corrections are routed through the corrections email at corrections at esportswagerin dot com. The desk verifies the correction against a Tier 1 or Tier 2 source and updates the row within 48 hours.