Roster brief · source: team channel

Standing roster continuity flags enter pre-match briefings

The desk now publishes a roster continuity flag for every pre-match brief. The flag lists stand-ins, travel injuries and academy promotions. The flag is verified against the team channel and the organizer feed before the brief goes live. The flag stays attached to the brief until the next public roster confirmation.

Read the match desk Team dossier index

What changed

From ad-hoc verification to a standing flag

Before the standing flag, the desk verified roster continuity on a per-brief basis. Each brief opened with the public lineup, scanned the team channel for stand-ins, scanned the organizer feed for late substitutions, and applied a single-source label. The process was sound but slow. The desk could not always confirm a substitution before the match window opened. The brief went live with a placeholder note.

The standing flag changes that. The desk now maintains a roster continuity register per team per cycle. The register is populated from the team channel and the organizer feed as soon as the source publishes. The flag is then attached to every pre-match brief for the team until the next public roster confirmation. The reader can see at a glance which teams are running with a stand-in, which teams are carrying a travel injury into a series, and which teams have promoted an academy player into the active roster.

Source class

The desk reads the team channel and the organizer feed. Stand-ins and travel injuries are labelled as "team channel confirmed". Academy promotions are labelled as "team channel confirmed, organizer feed pending" until the organizer feed is published.

Verification window

The desk verifies the flag at the moment the source publishes. The flag sticks to the brief for the rest of the cycle unless a stronger source contradicts it. A correction is published as a stand-alone note if the flag is reversed.

Stand-in label

A stand-in is labelled with the player's name, the team's name and the source class. The label does not infer role fit. The label only states the substitution. The competitive impact is left to the analyst.

Travel injury label

A travel injury is labelled with the affected map pool and the source class. The label does not infer map availability. The label only states the injury. The competitive impact is left to the analyst.

Competitive impact

What the standing flag means for the read

The standing flag changes two things for the reader. First, the reader can compare a team's flag against the prior cycle's flag without re-reading the brief. Second, the reader can weigh a roster move against the public lineup on match day without waiting for a follow-up brief. The flag is a small structural change with a meaningful read benefit.

The flag is not a prediction. The flag is a verification artefact. The desk still labels the brief with a source class and a competitive impact note. The flag is an additional label, not a replacement. A brief with a flag is read the same way as a brief without a flag — the analyst weighs the impact, the schedule and the source. The flag only tells the reader that a continuity event has been logged for the team.

The flag's value is in the cumulative read. A team that carries a stand-in across three cycles is in a different competitive posture than a team that runs a stable roster. The flag makes that visible without forcing the reader to compare three briefs side by side. The desk has always published the underlying facts; the flag is a presentation layer that makes the facts easier to compare.

The flag is also a discipline for the desk. A flag that is not verified is a flag that does not get published. The desk would rather publish a brief without a flag than publish a brief with an unverified flag. The standing flag inherits the desk's editorial standard: the strongest source class wins, and the brief is updated in place when a correction lands.

Teams and players touched

The first cycle under the standing flag

The first cycle under the standing flag covers the three teams on the active match desk roster. The flag is verified against the team channel and the organizer feed. The flag is updated in place. A correction is published as a stand-alone note if the flag is reversed.

Team Nova Echo

Carrying a travel injury into the next series. The affected map pool is published on the team channel. The flag is labelled "team channel confirmed". The next public roster confirmation is expected before the series window opens.

Team Iron Circuit

Promoted an academy player into the active roster for the next series. The promotion is labelled "team channel confirmed, organizer feed pending". The flag will move to "organizer feed confirmed" once the organizer feed publishes.

Team Glacier

Running with a stand-in for the next two cycles. The stand-in is labelled "team channel confirmed". The competitive impact is left to the analyst. The desk does not infer role fit.

Schedule implications

What the flag changes for the schedule desk

The schedule desk does not move series on the basis of a flag. The schedule desk moves series on the basis of an organizer-issued reschedule notice. The flag is a label, not a scheduling input. A team with a stand-in still plays its scheduled series unless the organizer publishes a reschedule.

Where the flag does affect the schedule desk is in the pre-match brief window. A team with a travel injury and a team with a stand-in both play the same scheduled series; the brief window just gets a clearer picture of the lineup. The pre-match brief is published earlier in the window for teams with a confirmed flag, because the desk does not need to wait for the public lineup to confirm the substitution.

The post-match brief is also affected. A team that played under a flag gets a post-match brief with a continuity note that compares the on-stage lineup to the flag. The desk does not score the lineup. The desk records the comparison and labels it with the source class. The reader gets a verified record of how the flag held up on stage.

What to watch next

One thing to verify before the next cycle

01Verify the organizer feed for the academy promotion

02Verify the travel injury map pool against the team channel

03Verify the stand-in identity against the on-stage lineup

04Publish the next roster continuity flag update

FAQ

Roster continuity flag, plain answers

What is a roster continuity flag?

A roster continuity flag is a verified label that is attached to a pre-match brief when a team is running with a stand-in, a travel injury or an academy promotion. The flag is verified against the team channel and the organizer feed.

How long does a flag stay attached?

A flag stays attached to the brief until the next public roster confirmation. A correction is published as a stand-alone note if the flag is reversed.

Does the flag predict competitive impact?

No. The flag is a verification artefact, not a prediction. The desk labels the flag with a source class and a competitive impact note. The reader weighs the read.

What happens if the organizer feed contradicts the team channel?

The desk publishes a correction as a stand-alone note. The brief is updated in place with a visible "corrected" flag and a link to the correction. The flag is reversed if the organizer feed is the stronger source.

The flag and the brief

How the flag and the brief fit together

The flag and the brief are two parts of the same read. The flag is the at-a-glance label on the pre-match brief. The brief is the underlying signal stack. The desk publishes both. A reader who only has time for the at-a-glance read can read the flag. A reader who wants the signal stack can read the brief.

The flag and the brief are not duplicates. The flag is a single label. The brief is three signals — source class, competitive impact, what to watch next. The reader who reads the flag without the brief gets a verified label but not the underlying signals. The reader who reads the brief without the flag gets the signals but not the at-a-glance label. The desk recommends both reads.

The flag is published at the same cadence as the team channel. The brief is published at the same cadence as the pre-match window. The two cadences are not the same. The flag is updated in place when the team channel publishes a revised roster. The brief is updated in place when the organizer feed publishes a revised lineup.

The desk publishes a stand-alone correction when the flag and the brief disagree. The correction lists the flag, the brief, the source classes and the verification timestamps. The reader can compare two corrections without re-reading the underlying flag or brief. The desk does not silently rewrite either the flag or the brief.

The two-part read is the desk's commitment to the reader. The desk does not endorse a single read. The desk publishes the flag for the at-a-glance reader and the brief for the signal-stack reader. The reader decides which read matches the moment.