#01Reading the player, the role, and the recent competitive note
The player desk is the most granular layer of the editorial newsroom. 1,408 players profiled across eight competitive games, with the daily role, the language, the regional coverage, and the last thirty days of competitive note. The player desk is the working document the team desk reads from when it builds a team-card, and the match desk reads from when it builds a talent rotation.
What the player desk covers
Three working documents. The player profile is the published record — the player name, the org, the region, the language, the role, the role history, and the last thirty days of competitive note. The role note is the published role analysis — the role the player plays, the role history, the role transitions, and the role impact. The interview log is the published interview record — the interviews the player has given, the language, the regional coverage, and the editorial context.
The player desk refreshes the player profile within ninety minutes of every official transaction, the role note within two hours of every role change, and the interview log within four hours of every interview. The player desk is the working document the editorial newsroom reads when it needs to know who a player is, what role they play, and what they have said in the recent interview rotation.
How the desk reads a player
The desk reads a player the way the casters read a roster. The player profile is the broadcast's editorial record — the player name, the org, the region, the language, the role. The role note is the broadcast's editorial analysis — the role, the role history, the role transitions, the role impact. The interview log is the broadcast's editorial voice — the interviews, the language, the regional coverage, the editorial context.
The desk's editorial read pairs the player profile with the role note and the interview log. The player profile is the editorial record. The role note is the editorial analysis. The interview log is the editorial voice. The desk's read is the editorial layer the broadcaster can't carry — the player, the role, the interview.
The player profile, layer by layer
The player profile is the published record of the player. The desk tracks seven layers: the player name, the org, the region, the language, the role, the role history, and the last thirty days of competitive note. The player 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 is the published role. The role history is the published role history. The last thirty days of competitive note is the published performance record.
The desk's player profile read pairs each layer with the player name, the org, the region, the language, the role, the role history, and the last thirty days of competitive note. The player profile is the editorial record the broadcaster can't carry — the player name, the org, the region, the language, the role, the role history, the last thirty days of competitive note.
The role note, in the language of the broadcast
The role note is the published role analysis of the player. The desk tracks four layers: the role, the role history, the role transitions, and the role impact. The role is the published role. The role history is the published role history. The role transitions are the published role transitions. The role impact is the published role impact in the competitive cycle.
The desk's role note read pairs each layer with the role, the role history, the role transitions, and the role impact. The role note is the editorial analysis the broadcaster can't carry — the role, the role history, the role transitions, the role impact. The desk refreshes the role note after every role change, with the role, the role history, the role transitions, and the role impact.
The interview log, before the broadcast window
The interview log is the published interview record of the player. The desk tracks four layers: the interviews, the language, the regional coverage, and the editorial context. The interviews are the published individual interviews. The language is the published interview language. The regional coverage is the published interview regional coverage. The editorial context is the published editorial context.
The desk's interview log read pairs each layer with the interviews, the language, the regional coverage, and the editorial context. The interview log is the editorial voice the broadcaster can't carry — the interviews, the language, the regional coverage, the editorial context. The desk refreshes the interview log within four hours of every interview, with the interview, the language, the regional coverage, and the editorial context.
How to follow a player without missing the editorial edge
Three working notes from the player desk. First, the player profile is the published record — read it before the broadcast, then follow it during the broadcast for the role rotation. Second, the role note is the editorial analysis — read it before the broadcast, then use it to plan the next week's editorial window. Third, the interview log is the editorial voice — read it during the broadcast, then replay it after the broadcast for the editorial recap.
The player desk is open to all readers. The desk does not require a subscription, does not publish betting lines, and does not promote a particular player's chances. The editorial read is published with the verification chain documented in the player footer, and the source dossier is available on request through the contact desk.
Four players on the desk's watchlist
The player desk's working watchlist. Four players on the desk's radar this week, with the player profile, the role note, and the interview log documented.
#01
#02A. Kovács
Duelist · 6y
#03M. Soto
Controller · 3y
#04R. Karim
IGL · Hybrid · 5yWorking notes from the player desk
Three working notes from the player desk for the week ahead. The player profile, the role note, and the interview log — together they read the player the way the editor reads the script.

Reading the player profile the way a coach reads it
The player profile is the editorial layer the broadcast can't carry. The player desk's read on the coaching staff's profile note.
Read the guide →
Reading the role note the way the broadcast reads it
The role note is the editorial layer the broadcast can't carry. The player desk's read on the role analysis.
Read the note →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.
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.
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.
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.
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.
What the player desk signs up to
The desk verifies every player profile against the official league channel, the team's official social media, and at least one independent source. The verification chain is published with the player footer.
What readers ask the desk most
How does the desk refresh a player profile?
The desk refreshes the player profile 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 role change?
The role change is the editorial edge of the player coverage. The desk refreshes the role note within two hours of the role change, with the role, the role history, the role transitions, and the role impact.
Which players does the desk cover?
The desk covers 1,408 players across eight competitive games. The watchlist is the published list of players 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 player's chances, and does not accept story placement from operators in exchange for editorial coverage.