Editorial desk / news

Dated reports, visible corrections

The news desk reads official operator channels first, then licensed broadcast partners, then team channels. Anything that is not on a tier-one or tier-two source is labelled as awaiting verification and held until the source lands.

Dated reportsVisible correctionsRSS feed
Editorial photograph of a contemporary esports newsroom desk with two monitors and a microphone on a boom
Editorial photograph of a contemporary esports newsroom desk with two monitors and a microphone on a boom

01 / latest reports

Latest reports
Dated rail

The latest reports are listed in reverse-chronological order. Each report carries a date, a status pill and a brief description. The status pill is verified, in review, or archived.

2026-07-28

Patch 14.10 published across competitive tracks

Verified
2026-07-25

North Atlantic Open group draw released

Verified
2026-07-22

Roster window closes for the August qualifier

In review
2026-07-19

Pacific Major statement on regional seeding

Verified
2026-07-15

Endurance 12 Hours sweetens the support slots

In review
2026-07-12

Continental Fighting Series opens August registration

Verified
2026-07-09

Last-Zone Royale regional mirror added

Verified
2026-07-02

Mid-season community tier notes published

Archived
2026-01-12

2025 season register published

Archived

02 / correction status

Correction status
Public register

Every change is recorded on the public corrections register. The register lists the date, the original claim, the source of the correction and the updated description. The desk never silently rewrites a claim.

2026-07-22

Roster window clarification

The original draft referred to the August qualifier window. The corrected draft refers to the regional qualifier window. The source of the correction is the operator channel.

2026-07-15

Endurance 12 Hours slot update

The original draft referred to the support roster. The corrected draft refers to the support category. The source of the correction is the licensed broadcast partner.

03 / source discipline

Source-date discipline
Editorial rule

The news desk reads the operator channel first, the licensed broadcast partner second, and the team channel third. Anything that is not on a tier-one or tier-two source is labelled as awaiting verification and held until the source lands.

What the desk publishes

The desk publishes dated reports, visible corrections, and a public feed. The feed is RSS-ready. The desktop sitemap is XML; the human sitemap is a footer link.

What the desk does not publish

The desk does not publish live tickers, prediction markets, or live odds feeds. The desk does not publish unverified social-media posts or fan-vote rankings.

04 / how play12 covers

How play12 covers the news
Editorial rule

The news desk reads the calendar every morning. The first read is the operator channel for each active tournament. The second read is the licensed broadcast partner. The third read is the team channel. Any report that lands on a tier-one or tier-two source is recorded; any report that does not is held.

05 / regional buckets

Regional news buckets
Geographic split

Reports are tagged by region. Where the report is multi-region, the desk tags the row as global. The regional bucket is the editorial ask; the report is the source.

EU

European reports

Multi-language mirrors, English-language primary.

NA

North American reports

English-language primary, regional mirror on broadcast partner.

APAC

Asia-Pacific reports

Multi-language, English-language primary.

Global

Global reports

Multi-region operator, regional mirror per channel.

06 / evidence

Evidence register
Source tier

The news desk is sourced from the operator channel first, the licensed broadcast partner second, and the team channel third. The tier-one source is the only source for a confirmed report.

07 / related

Related hubs
Editorial links

The news desk is one of three interconnected desks. The tournament horizon reads the same fixture and adds the calendar story. The match preview desk reads the same fixture and adds the reasoning layer.

08 / desk notes

How the desk reads the calendar
Editorial cadence

The desk reads the calendar every morning. The first read is the operator channel for each active tournament. The second read is the licensed broadcast partner. The third read is the team channel. The cascade is the editorial cadence.

Morning

The morning read is the daily check. The horizon table is refreshed, the gate dates are verified, the source rule is run. The desk publishes the daily note every weekday at 09:00 UTC.

Midday

The midday read is the patch check. The developer patch portal is checked, the editorial reading is written, the workshop is updated. The desk publishes the midday note every weekday at 12:00 UTC.

Afternoon

The afternoon read is the team check. The team corridor is refreshed, the player role gallery is verified, the source register is updated. The desk publishes the afternoon note every weekday at 15:00 UTC.

09 / news mechanics

News mechanics
How the row is built

The news desk publishes one row per report. Each row carries the report title, the date, the status pill, the brief description. The mechanics are simple and public: the reader is invited to verify the source and judge the editorial reading.

Status pill

Three status pills are used. Verified means the operator channel is the source and the date is on the row. In review means the broadcast partner is the source and the operator channel is pending. Archived means the row is closed and the source register holds the historical record.

Date

The date column lists the publication date. The date is read as the editorial ask; the operator channel is the source. Where the date is missing, the row is held until the source lands.

Title

The title column lists the report. The title is read as the editorial ask; the operator channel is the source. Where the title is unclear, the row is held until the source lands.

Description

The description column lists the brief. The description is read as the editorial ask; the operator channel is the source. Where the description is long, the row links to the full report.

10 / cadence

Reporting cadence
Editorial rhythm

The news desk publishes on a three-pass cadence. The morning pass runs the operator channel; the midday pass runs the broadcast partner; the afternoon pass runs the team channel. Three passes a day, every weekday, every season.

Morning

The morning pass is the daily check. The horizon table is refreshed, the gate dates are verified, the source rule is run. The desk publishes the daily note every weekday at 09:00 UTC.

Midday

The midday pass is the patch check. The developer patch portal is checked, the editorial reading is written, the workshop is updated. The desk publishes the midday note every weekday at 12:00 UTC.

Afternoon

The afternoon pass is the team check. The team corridor is refreshed, the player role gallery is verified, the source register is updated. The desk publishes the afternoon note every weekday at 15:00 UTC.

11 / reporting rules

Reporting rules
Three rules

The news desk runs on three reporting rules. Rule one: a report is published when the source is dated. Rule two: a correction is published within 24 hours. Rule three: the editorial ask is the source register, not the opinion.

Rule one

A report is published when the source is dated. The reader is invited to read the source date, then read the report. The source date is the rule; the report is the editorial ask.

Rule two

A correction is published within 24 hours. The reader is invited to read the correction, then read the original report. The correction is the rule; the original report is the editorial ask.

Rule three

The editorial ask is the source register, not the opinion. The reader is invited to read the source register, then read the editorial ask. The source register is the rule; the editorial ask is the ask.

Past editions

The past-edition register holds the historical record. The reader is invited to read the register, then read the editorial ask. The register is the source; the editorial ask is the rule.

12 / weekly reading

Weekly reading
Editorial cadence

The news desk reads the calendar weekly. The first read is the operator channel for each active tournament. The second read is the licensed broadcast partner. The third read is the team channel. The cascade is the editorial cadence.

Monday

Monday is the desk's reading day. The horizon table is refreshed, the gate dates are verified, the source rule is run. The desk publishes the weekly horizon note every Monday at 10:00 UTC.

Wednesday

Wednesday is the desk's patch day. The patch notes are read, the editorial reading is written, the workshop is updated. The desk publishes the weekly patch note every Wednesday at 11:00 UTC.

Friday

Friday is the desk's film day. The post-match film room is updated, the draft reasoning is refreshed, the editorial reading is closed. The desk publishes the weekly film note every Friday at 15:00 UTC.

Daily

The daily pass runs the operator channel in the morning, the broadcast partner at midday, the team channel in the afternoon. Three passes a day, every weekday.

FAQ

Reader questions
Plain answers

Reader questions, answered plainly

How do you decide what to publish?

The desk reads the operator channel first, the licensed broadcast partner second, and the team channel third. Anything that is not on a tier-one or tier-two source is labelled as awaiting verification.

How are corrections handled?

When a report is updated, the original draft is left visible and the correction is appended with a date. The desk never silently rewrites a claim.

What does the desk not publish?

The desk does not publish live tickers, prediction markets, or live odds feeds. The desk does not publish unverified social-media posts or fan-vote rankings.

How often is the desk updated?

The desk is updated as soon as a tier-one or tier-two source changes. The desk publishes a daily update note on weekdays.