Team identity dossiers: rosters, verification dates, change logs
Six rosters the desk is tracking this cycle. Each dossier carries the org-snapshot, the most recent verification date, and the change log since the desk last refreshed the file.
Editorial independence
Sources cited · Updated 2026-08-04 · No invented fixtures · No fabricated rosters
Team identity dossiers
Six rosters the desk is tracking this cycle
Each dossier carries the org-snapshot, the most recent verification date, and the change log since the desk last refreshed the file.
EUFPS · CSVerified 2026-08-03
Iron Wolves
Stable EU field carrying its practice partner from last cycle. Two-trial roster swap confirmed Tuesday.
- Active roster
- 5
- Open trial slot
- 1
APACMOBA · HextechVerified 2026-08-01
Saffron Royals
APAC dark-horse run on a fresh patch. Two substitute slots open. Reading tracks the qualify math.
- Active roster
- 6
- Open trial slot
- 2
NABR · ApexVerified 2026-08-02
Pacific Vortex
Twenty-team match point bracket. Carry-over from Stage 1; one flex-sub rotation in week two.
- Active roster
- 4
- Open trial slot
- 0
EUFighting · FG CupVerified 2026-07-31
Northwind FGC
Three-pool rotation through Top 8; anchor role is the longest-tenured player on the EU circuit.
- Active roster
- 3
- Open trial slot
- 1
EURacing · ContinentalVerified 2026-08-02
Helix Simworks
Round 9 is a fixed-setup triple-header. The desk is tracking the tyre-cliff window across the three races.
- Active roster
- 2
- Open trial slot
- 0
SABR · UndergroundVerified 2026-08-01
Tropico Storm
SA Underground qualifier run; the dossier is light on confirmed sources and the desk is awaiting org confirmation.
- Active roster
- 4
- Open trial slot
- 2
Change log
What the desk moved this week
Roster movements, trial windows and org statements land on the change log with a Tier 1 or Tier 2 source badge.
2026-08-03 · Tier 2
Iron Wolves confirm two-trial roster swap
Org posts roster confirmation; the desk logs the swap on the dossier and the change log.
2026-08-02 · Tier 1
Pacific Vortex flex-sub rotation locked
League posts rotation confirmation; the desk notes the rotation on the dossier.
2026-08-01 · Tier 2
Saffron Royals open two substitute slots
Org posts trial window; the desk logs the trial window and re-states the active roster.
How the desk writes a dossier
Four checks before a roster line ships
Every roster entry passes four checks before it lands on the desk. Where any check fails, the dossier carries a footnote.
- The org's own channel has posted the roster or the change.
- A second source (Tier 1 league, Tier 2 verified org, or Tier 3 established media) confirms the change.
- The verification date is recorded and surfaced on the dossier.
- The change log entry names the source badge and the date.
Roster reading
How the desk reads a roster move
The desk reads a roster move in three steps. First, the desk verifies the move against the org's own channel. Second, the desk cross-checks the move against a Tier 1 or Tier 2 source. Third, the desk records the move on the change log with a named date.
Where the move is a trial window, the desk reads the trial as a trial. The desk does not promote a trial to an active roster line on the basis of the org's teaser; the desk waits for the org's confirmation.
Where a move is reported by community sources first, the desk reads the row as Tier 4 until the org's confirmation lands. Tier 4 rows carry a rumor badge in the calendar ledger and are not promoted to a higher tier by editorial decision.
Team identity
What the desk puts on a team identity dossier
A team identity dossier carries four fields. The org-snapshot is the org's name, region, and primary stage. The verification date is the most recent date the desk refreshed the dossier. The change log is the named list of moves since the dossier was last refreshed. The roster line is the active roster and any open trial slots.
The desk does not include a form band on the dossier. Form bands belong on the player atlas; the team dossier carries the roster shape, not the recent form. The split is a discipline: the team page answers "who is on the team", not "how is the team playing".
Roster reading
How the desk reads a roster move
The desk reads a roster move in three steps. First, the desk verifies the move against the org's own channel. Second, the desk cross-checks the move against a Tier 1 or Tier 2 source. Third, the desk records the move on the change log with a named date.
Where the move is a trial window, the desk reads the trial as a trial. The desk does not promote a trial to an active roster line on the basis of the org's teaser; the desk waits for the org's confirmation.
Where a move is reported by community sources first, the desk reads the row as Tier 4 until the org's confirmation lands. Tier 4 rows carry a rumor badge in the calendar ledger and are not promoted to a higher tier by editorial decision.
Team identity
What the desk puts on a team identity dossier
A team identity dossier carries four fields. The org-snapshot is the org's name, region, and primary stage. The verification date is the most recent date the desk refreshed the dossier. The change log is the named list of moves since the dossier was last refreshed. The roster line is the active roster and any open trial slots.
The desk does not include a form band on the dossier. Form bands belong on the player atlas; the team dossier carries the roster shape, not the recent form. The split is a discipline: the team page answers "who is on the team", not "how is the team playing".
Cross-references
What the team dossier links to
The team dossier links to the player atlas, the change log, the patch workshop, and the calendar ledger. The links are independent — a reader who knows the team can open the dossier without re-reading the calendar.
Where the dossier's roster line changes, the change is recorded on the change log with the previous line, the new line and the date. The desk's case for the explicit roster change is that a roster without a change log reads as static.
Qualifier read
How the desk reads a qualifier roster
The desk reads a qualifier roster by tying the roster to the patch reading that currently governs the qualifier lane. The roster is the team line; the patch reading is the named beat reporter's interpretation of the patch text.
Where the desk has filed a qualifier roster on the dossier, the dossier carries the verification date and the named beat reporter. The desk's case for the explicit qualifier read is that a roster without a reading is a list; a roster with a reading is an analysis.
FAQ · teams
Frequently asked questions, in editorial voice
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.
What does a team dossier carry?
Org-snapshot, verification date, change log and roster line. The desk does not include a form band on the dossier.
How does the desk read a roster move?
The desk verifies the move against the org's own channel, cross-checks against a Tier 1 or Tier 2 source, and records the move on the change log with a named date.
What does the change log carry?
Previous wording, new wording and date. The desk does not silently edit history.
Where do I find the source hierarchy?
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).
What does the source badge tell me?
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.
How does the desk promote a row's tier?
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.
How often does the surface refresh?
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.
How do I subscribe to updates?
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.
How do I file a correction?
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.