Team desk

Team cards, roster snapshots, and the regional qualifying path.

The team desk turns a roster into a team you can read. 147 teams across eight competitive games, with the daily roster, the language, the region, and the last thirty days of competitive note.

Tracking the team, the roster, and the regional qualifying path

The team desk is the editorial layer that turns a roster into a team you can read. The desk tracks 147 teams across eight competitive games, with the daily roster, the language, the region, and the last thirty days of competitive note. The team desk is the working document that the match desk, the tournament desk, and the player desk all read from.

What the team desk covers

Three working documents. The team-card is the published record — the team name, the org, the region, the language, the role composition, and the last thirty days of competitive note. The roster-snapshot is the published roster — the players, the roles, the language, the regional coverage, and the trial status. The regional qualifying path is the published qualifying path — the qualifying event, the seeding, the cross-region matchups, and the round progression.

The team desk refreshes the team-card within ninety minutes of every official transaction, the roster-snapshot within two hours of every chair change, and the regional qualifying path daily. The team desk is the working document the editorial newsroom reads when it needs to know what a team looks like, what its roster is, and where it stands in the regional qualifying path.

How the desk reads a team

The desk reads a team the way the casters read a roster. The team-card is the broadcast's editorial record — the team name, the org, the region, the language, the role composition. The roster-snapshot is the broadcast's editorial cast — the players, the roles, the language, the regional coverage. The regional qualifying path is the broadcast's editorial path — the qualifying event, the seeding, the cross-region matchups, the round progression.

The desk's editorial read pairs the team-card with the roster-snapshot and the regional qualifying path. The team-card is the editorial record. The roster-snapshot is the editorial cast. The regional qualifying path is the editorial path. The desk's read is the editorial layer the broadcaster can't carry — the team, the roster, the regional qualifying path.

The team-card, layer by layer

The team-card is the published record of the team. The desk tracks six layers: the team name, the org, the region, the language, the role composition, and the last thirty days of competitive note. The team name is the published identity. The org is the published operating structure. The region is the published regional coverage. The language is the published broadcast language. The role composition is the published role distribution. The last thirty days of competitive note is the published performance record.

The desk's team-card read pairs each layer with the team name, the org, the region, the language, the role composition, and the last thirty days of competitive note. The team-card is the editorial record the broadcaster can't carry — the team name, the org, the region, the language, the role composition, the last thirty days of competitive note.

The roster-snapshot, in the language of the broadcast

The roster-snapshot is the published roster of the team. The desk tracks five layers: the players, the roles, the language, the regional coverage, and the trial status. The players are the published individual identities. The roles are the published individual roles. The language is the published individual broadcast language. The regional coverage is the published individual regional coverage. The trial status is the published individual trial status.

The desk's roster-snapshot read pairs each layer with the players, the roles, the language, the regional coverage, and the trial status. The roster-snapshot is the editorial cast the broadcaster can't carry — the players, the roles, the language, the regional coverage, the trial status. The desk refreshes the roster-snapshot after every chair change, with the player, the role, the language, the regional coverage, and the trial status.

The regional qualifying path, before the bracket drops

The regional qualifying path is the published path the team follows to qualify for the tournament. The desk tracks four layers: the qualifying event, the seeding, the cross-region matchups, and the round progression. The qualifying event is the published event name. The seeding is the published team seeding. The cross-region matchups are the published cross-region matchups. The round progression is the published round-by-round progression.

The desk's regional qualifying path read pairs each layer with the qualifying event, the seeding, the cross-region matchups, and the round progression. The regional qualifying path is the editorial path the broadcaster can't carry — the qualifying event, the seeding, the cross-region matchups, the round progression. The desk refreshes the regional qualifying path daily, with the verification chain documented in the team footer.

The team-desk watchlist

The team-desk watchlist is the published list of teams the editorial desk is following. The watchlist pairs every team with the team-card, the roster-snapshot, and the regional qualifying path. The watchlist refreshes within ninety minutes of every official transaction, with the team, the org, the region, the language, the role composition, and the last thirty days of competitive note.

The watchlist is the editorial layer the broadcaster can't carry. The team-desk watchlist pairs the team-card with the roster-snapshot and the regional qualifying path. The editorial read is the editorial layer the broadcaster can't carry — the team, the roster, the regional qualifying path. The desk's read is the editorial layer the broadcaster can't carry — the team, the roster, the regional qualifying path.

How to follow a team without missing the editorial edge

Three working notes from the team desk. First, the team-card is the published record — read it before the broadcast, then follow it during the broadcast for the roster rotation. Second, the roster-snapshot is the editorial cast — read it before the broadcast, then use it to plan the next week's editorial window. Third, the regional qualifying path is the editorial path — read it during the broadcast, then replay it after the broadcast for the editorial recap.

The team desk is open to all readers. The desk does not require a subscription, does not publish betting lines, and does not promote a particular team's chances. The editorial read is published with the verification chain documented in the team footer, and the source dossier is available on request through the contact desk.

Watchlist

Team-desk watchlist — week of 28 Jul

The team desk's working watchlist. Twelve teams on the desk's radar this week, with the team-card, the roster-snapshot, and the regional qualifying path documented.

A Valorant tournament player wearing a headset at a competition desk.#01

Harbor Sentinels

Pacific · Duelist core
5 roster4W streak
A Dota 2 pro player at a competition desk during a tournament.#02

Starforge

CIS · Hard carry
5 roster2W streak
A female esports player wearing a headset at a competition desk.#03

Iron Rose

EMEA · Controller core
5 roster3W streak
A coaching staff reviewing VOD footage as a team.#04

Bayou Pharaohs

MENA · IGL · Hybrid
5 roster6W streak
From the desk

Working notes from the team desk

Three working notes from the team desk for the week ahead. The team-card, the roster-snapshot, and the regional qualifying path — together they read the team the way the editor reads the script.

An esports coach reviewing VOD footage with a team.
Roster

Three roster moves that quietly reshape the Pacific league

None of the changes were front-page, but each one shifts the role map. The working note tracks the implications for the next six weeks of qualifier play.

Read the note →
A tactical pause moment during a competitive match with coaches standing behind players.
Coaching

Reading the VOD review the way the coaching staff reads it

The VOD review is the editorial layer the broadcast can't carry. The team desk's read on the coaching staff's notes.

Read the note →
Editorial standards

What the editorial desk reads on this page

The editorial desk reads three working documents on every page the desk publishes. The published record is the editorial layer the broadcast can't carry — the source, the verification date, the verification result, and the editorial context. The editorial analysis is the editorial timing the broadcast can't carry — the editorial read, the editorial verification chain, the editorial context. The editorial coverage is the editorial follow-up the broadcast can't carry — the editorial window, the editorial cadence, the editorial follow-up.

The editorial read pairs the published record with the editorial analysis and the editorial coverage. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer. The editorial read is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.

A coaching whiteboard next to a monitor showing a team roster.

The broadcast studio carries the editorial layer

The broadcast studio is the editorial layer the broadcast can't carry. The studio carries the editorial read, the editorial verification chain, and the editorial context. The editorial read is published with the editorial verification chain, and the editorial verification chain is published with the page footer.

The verification chain is the editorial record

The verification chain is the editorial layer the operator's marketing channel can't carry. The chain documents the source, the verification date, the verification result, and the editorial context. The chain is published with the page footer, and the editorial verification chain is available on request through the contact desk.

A tactical map displayed on a broadcast monitor during a competitive match.
Editorial chain

How the editorial verification chain is documented

The editorial verification chain is documented across four layers. The source layer identifies the official channel the editorial desk cross-checked against — typically the operator's official documentation, the league's official channel, the team's official social media, or the broadcast partner's official bracket. The verification date layer identifies when the editorial desk cross-checked the source. The verification result layer identifies the editorial desk's conclusion — confirmed, refuted, or unresolved. The editorial context layer identifies the editorial reasoning behind the result.

The editorial verification chain is built to be transparent. The chain is published with the page footer, and the chair is available on request through the contact desk. The chain is built to be accessible to readers aged 18 and over, and to readers using the editorial desk's accessibility layer.

Editor's note

What the page covers in three working documents

First, the published record — the source, the verification date, the verification result, and the editorial context. Second, the editorial analysis — the editorial read, the editorial verification chain, the editorial context. Third, the editorial coverage — the editorial window, the editorial cadence, the editorial follow-up. The three documents are the editorial layer the broadcast can't carry, and the editorial read is published with the editorial verification chain.

An esports caster at a broadcast desk with a headset and broadcast monitor.

The editorial desk's read on the broadcast

The editorial desk reads the broadcast the way the casters read the script. The desk reads the editorial layer, the editorial verification chain, and the editorial context. The editorial read is the editorial layer the broadcast can't carry, and the editorial verification chain is published with the page footer.

Verification

What the team desk signs up to

The desk verifies every team transaction against the official league channel, the team's official social media, and at least one independent source. The verification chain is published with the team footer.

Frequently asked

What readers ask the desk most

How does the desk refresh a team-card?

The desk refreshes the team-card within ninety minutes of every official transaction. The refresh windows are tied to the league's official transaction window. The verification chain is published with each refresh.

How does the desk handle a roster move?

The roster move is the editorial edge of the team coverage. The desk refreshes the roster-snapshot within two hours of the move, with the player, the role, the language, the regional coverage, and the trial status.

Which teams does the desk cover?

The desk covers 147 teams across eight competitive games. The watchlist is the published list of teams the editorial desk is following. The watchlist refreshes daily.

What does the desk not publish?

The desk does not publish betting lines, fantasy-pick cards, or fabricated statistics. The desk does not promote a particular team's chances, and does not accept story placement from operators in exchange for editorial coverage.

PLAY NOW