EDITION · Sat, 01 Aug 2026 · 13:21 UTC
Source-verified ledger · editorial corrections desk open
DESK · 01 · TOURNAMENTS

Tournament coverage — brackets, regional majors and the global finals calendar

The tournaments desk tracks four ongoing series: APAC Major, EMEA Championship, Americas Open and the Global Finals circuit. Each series has its own verified publisher feed, its own editorial stamp and its own corrections channel.

BRACKET FRAGMENT · APAC MAJOR

The current upper bracket, annotated

Below is the upper bracket of the APAC Major as of 02 August 06:00 UTC. Each seed is sourced from the publisher qualifier feed; the projected semi-finals are bracket-mechanical, not editorial.

APAC Major — upper bracket · 02 Aug 06:00 UTC snapshot

VERIFIED
A1Sakura Apex2
A4Phoenix Tigers1
A2Coastline Foxes2
A3Lattice Sentinels0
B1Northwind Hydra
B4Ember Wolves
B2Cobalt Regiment
B3Iron Mirage

Next · Sakura Apex v Coastline Foxes · 19:00 UTC · 02 Aug · BO5

FIXTURE TIMELINE

Next 48 hours across all four tournament series

02 AUG · 11:00 UTC

APAC Major · lower bracket Rd 1

Four BO3 fixtures. Publisher primary stream, EN + JA audio tracks.

BO3 · 4 matchesTier A
02 AUG · 15:30 UTC

EMEA Champ · quarter-final

Hydra vs Wolves BO5. Editor's read above with the broadcast map veto.

BO5 · 1 matchTier A
02 AUG · 19:00 UTC

APAC Major · upper bracket semi

Sakura Apex v Coastline Foxes — the bracket's headline fixture this week.

BO5 · 1 matchTier A
02 AUG · 22:45 UTC

Global Finals · stage double

Cobalt Regiment vs Iron Mirage, then Americas Open cross-over match.

BO5 · 2 matchesTier A
HOW WE COVER A TOURNAMENT

The tournament desk's working method

A tournament is treated as a six-week project — three weeks of build-up (qualifier feeds, map pool reviews) and three weeks of active coverage (group stage, bracket, finals weekend). The desk keeps its own correction log per series and a Tier-A citation trail for every score it publishes.

01

Build-up

Seeds, map vetoes, qualifier results. Editor reviews the publisher's published bracket in the first 48 hours and locks the seeds.

02

Group stage

Live scores cross-checked against the publisher stream overlay + governing-body press. 60-second tolerance before flag.

03

Bracket stage

Every match gets a match preview ledger 24 hours before fixture; verified scores within 60 seconds of in-game end.

04

Finals weekend

Six-hour desk shifts through the entire weekend; verified scores are also delivered via the in-app alert before the web write-up.

05

Correction

Any bracket revision post-publish is logged at /corrections/ within six hours. Mean turnaround across the year: 14h.

06

Archive

The whole desk feed is filed under the tournament archive with the cross-tournament similarity audit signed in the editorial standing order.

EVIDENCE STANDARDS

How a tournament series is verified

Tier A

Publisher stream overlay

The authoritative score feed, anchored to the publisher's primary broadcast stream.

STAMP A
Tier A

Governing-body press wire

Independent press wires published by the tournament organizer. Required for any bracket motion outside the publisher flow.

STAMP A
Tier B

Independent tournament press

Verified independent press cited where publisher feed is unavailable.

STAMP B
Tier C

Coach interview reads

Coach and analyst read-throughs are always flagged EDITOR'S READ — never published as fact.

STAMP C
READER Q&A

Eight tournament questions the desk actually gets

How do you decide which tournament series to cover?
Coverage follows reader signal, publisher-published regional series, and the global finals calendar. APAC, EMEA, Americas and Global Finals are always covered; smaller series are covered if a publisher feed and an independent press feed are both verifiable.
When does the APAC Major bracket actually finish?
Finals weekend is 08–10 August. The grand final is BO5 and broadcast globally with EN + JA commentary.
Who decides the map veto?
The map veto is set by the publisher's tournament rules and executed by the teams in the broadcast. Lvlup reports what was vetoed, with timestamp.
Does the desk use betting odds as a citation?
Never. The desk uses publisher feeds, governing-body press and independent tournament press. Betting odds are out of scope.
Can I subscribe to a single series?
Yes. The Lvlup app lets you follow a single series and gets alerts 24h before each match day.
When does the next big patch drop?
The publisher's public patch cadence is roughly 4–6 weeks. The patch desk reads the publisher's roadmap and posts one editorial read of every patch.
Where can I watch?
The full broadcast matrix — by platform, by region, by language and accessibility — is at the viewing guide.
Does the desk republish its own archived coverage?
Yes — the editorial archive is open. Old coverage is preserved with the same citations it carried on day one.
BRACKET MECHANICS · DEEP READ

How the desk reads a bracket — and where editorial scenario is intentionally kept out

The desk treats a tournament bracket as a mechanical document, not a leaderboard. Every seed is locked from the publisher qualifier feed; every score is verified against the publisher stream overlay and the governing body press wire; editorial interpretation appears only on rows flagged EDITOR'S READ or editorial scenario. This page is the working method, written for readers who want to re-walk it themselves before a finals weekend.

Step-by-step — what happens between group stage kickoff and a grand final

The first three days after the publisher publishes the qualifier output are build-up. The desk reviews the bracket line by line, cross-checks every seed against the regional press wire, and flags any seed that disagrees by more than one tier with the editor's own re-walk. Where two of three sources disagree, the seed is left open and the panel is stamped PENDING until the publisher re-issues the seed or the regional press catches up.

Group stage coverage is the bracket's first living layer. The desk reads every match as a fresh score; nothing carries from previous splits except the editorial scenario language. When the desk writes a coach interview read for round 7 of an APAC Major group A match, the read is published alongside the verified score, with a clear fork between the two: a row starting with a check mark is verified; a row starting with a diamond is editorial scenario.

Bracket stage changes the desk's cadence. Every match now carries a 24-hour preview ledger in addition to the verified bracket row, and the bracket updates the morning after each round. Where a bracket revision crosses a previous publish, the revision is logged on the corrections page within six hours and the bracket section on the affected page is updated first, the article body second.

Finals weekend is the desk's largest continuous run. Six-hour desk shifts run through all three days. Verified scores are delivered inside the app before the web write-up so readers who follow a single team get the in-game end stamp within minutes of the publisher stream overlay. Post-match press is filed under the same headline, with the verified result fixed and the editorial reaction separated as the writer's perspective.

Where the desk stays out — and why

The desk does not publish or estimate betting lines, projected final scores, or any pro-team resourcing language that is not in the publisher's own published form. We do not republish messages from the publisher's internal chat or screenshot lobbies. We do not name-share player departure rumours from community forums without an independent press wire to anchor them. Editorial framing is reserved for the language we can publish verbatim — coaches, players, governing bodies — and for the language the desk itself produces in interviews conducted or transcribed by the newsroom.

Throughout the bracket, the desk keeps a correction count visible to readers. The corrections page carries every public revision with a timestamp and re-citation. Mean turnaround is 14h, but the desk commits to a faster 6h turn for bracket and score changes, and a 24h turn for story-tip-based corrections.

Region by region — what each series' bracket looks like

The APAC Major bracket uses a group stage into a single-elim top-8. The single-elim structure is publisher-determined and stays constant across splits. The desk follows the bracket top through quarters into semi-finals into the BO5 grand final. Map vetoes are set on a per-stage basis; the publisher releases a stage-specific ban pool in the build-up week.

The EMEA Championship bracket uses a double-elim structure through the bracket stage and a BO5 grand final. Double-elim means the desk tracks both winners' and losers' branches independently; an L-bracket run from lower bracket round 1 to the grand final is six rounds of coverage per team. The desk files the L-bracket matches in their own newsroom sub-categories so a reader searching for one team's full run lands on a single date-stamped feed.

The Americas Open bracket uses a round-robin group stage followed by a single-elim bracket. Round-robin scoring gives the desk a different verification challenge: a win count plus map differential has to be re-summed at the end of each round. The desk keeps a per-group tally table in the newsroom wiki and updates it after every round. The Americas Open bracket typically finishes across two weekends in late August.

The Global Finals bracket is the season's capstone. Four regional winners advance to a single bracket in Tokyo. The Global Finals bracket is small but high-stakes; the desk opens a dedicated Tokyo desk nine days before the bracket and runs a continuous feed through finals weekend. The bracket uses BO5 for every series including the grand final; the grand final carries the season's closing bracket prize pool.

18+ · RESPONSIBLE PLAY

Tournament coverage is open to all readers. Where wagering routes connect, age and jurisdiction apply.

The Lvlup newsroom covers tournaments independently of any wagering or fantasy product. Where a brand SERP page (download app, bonus, refer) is referenced, the publisher’s age and jurisdiction controls apply.

READER WORKFLOW · APAC MAJOR

A reader's Monday-morning re-walk of the past weekend's APAC Major bracket

The reader workflow below is the one the desk itself uses between shifts. It runs from a fresh page open on a Monday morning through to the editor's correction log. Use it as a starting point for a weekend's bracket; replace each link with the bracket you are following.

Step one — open the matches page and the bracket page in two tabs

The matches page carries every fixture that landed in the bracket this weekend. The bracket page carries the verified scores and the editorial scenario language. Open both: the matches page is the structural view, the bracket page is the editorial view. The two tabs let you walk the bracket left to right while reading the editorial read across the matches.

Step two — read the verified scores, mark the PENDING rows

The matches page's match-list shows verified scores next to fixtures where the publisher overlay and the governing body press agreed. The bracket page marks PENDING rows where the two feeds disagreed. Mark the PENDING rows in your own notes; the desk will turn them into verified rows or escalate to a correction within six hours.

Step three — read the editorial reads in order

The bracket page's editorial reads appear under the verified rows. Each editorial read is stamped Tier-C and is flagged EDITOR'S READ or editorial scenario. Read the editorial reads in order — they are written in chronological editorial order, not in bracket-order. The first editorial read is the most recent editorial from the desk's last shift.

Step four — read the post-match film-room notes

The film-room notes for the weekend's bracket-stage matches are filed under the matches feed within 24 hours of the in-game end. Open each film's mid-round trigger and turning point rows; the editorial scenario language is flagged. The notes are designed to be re-walked against the broadcast footage.

Step five — check the corrections log

The corrections log carries every public revision. Read the corrections published after your last open. A correction that affects a row you marked PENDING will be turned into a Tier-A row; a correction that affects a row you marked verified will be stamped with the corrected score and the original timestamp.

Step six — re-mark the matches page once a week

The desk commits to a six-hour refresh cadence. The matches page also carries an edition masthead at the top, timestamped at the start of each shift. Re-mark the matches page when a new edition masthead opens, or when a Tier-A correction lands; both events usually land at the top of a six-hour cycle.

FINAL

Subscribe to a single series — alerts 24h before every match day

The Lvlup app sends a single alert per match day for the series you follow. Coverage is editorial.