A roster move is the most over-announced event on a competitive desk and the least measured. Teams post the swap on a Tuesday, the broadcast talks about it through Wednesday, and by Friday the form table still says the same thing it said on Monday. The reader who waits for the form table to confirm the move waits too long. The reader who watches the pick-ban reads the move on day one.
Why the veto order moves before the win rate does
Pick-ban is a call sheet. The IGL or the head coach picks the first map for a reason, and the order in which a team presents (or removes) maps from the pool is the most direct window into what the room is trying to do that series. A new IGL almost always re-orders the veto on the very first map she or he calls. A new entry-fragger almost always shifts the comfort pick one slot higher. A new coach almost always protects the slow map differently. None of those shifts are visible in the win rate on the day of the move. All of them are visible in the pick-ban of the first completed series on the new credit.
The form table, by contrast, is a lagging measure. It only updates with completed series on the new credit, and the first such series rarely arrives within the same week. Even when it does, one completed series is one data point. A win rate based on one map is a coin flip with branding. A pick-ban based on one map is a documented choice. The desk treats the pick-ban as the primary read on day one and the form table as the read that earns its place by the third weekend.
What a new in-game leader actually changes
An IGL change is the cleanest test. The old IGL built the veto order around one read of the map pool: which map the team wanted to start on, which map they wanted to ban away, which map they wanted as the decider. The new IGL inherits the same five players but builds a different veto around a different read. The same five players, on the same patch, in the same bracket, can produce a different veto order on the very first series, because the new IGL sees the pool differently.
The pattern repeats at a smaller scale with a flex swap. When a team moves a veteran into the flex slot, the comfort map tends to move up one slot in the veto. When a team promotes an academy player into the starting six, the slow map tends to drop one slot, because the rookie has not yet built a slow-map call sheet. None of those shifts is visible in the form table on day one. All of them are visible in the first completed pick-ban on the new credit.
Reading the first three veto windows after a move
The desk tracks the first three completed series after any roster move, and the read is sequenced. Series one answers the question: did the veto order change at all. Series two answers the question: did the change hold, or did the team revert to the old veto under pressure. Series three answers the question: is the new veto producing the map it was designed to produce. If the answer to all three is yes, the move has landed in voice, and the form table will start to mean something by the fourth or fifth series.
If the answer to series one is no (the veto order did not change), the move is almost certainly cosmetic. A cosmetic move produces a cosmetic pick-ban and a form table that does not move. If the answer to series one is yes but series two is no, the move was a press-conference move: the team tried the new veto, did not trust it under match pressure, and reverted. That kind of move produces a noisier form table than a cosmetic one, because the read is split between two call sheets.
The third window, the third completed series, is where the desk starts to write a verdict. The third series is the first series where the team has had time to settle on the new veto and has a small sample of map outcomes to compare against the old credit. By the third series the desk can say whether the move produced the map it was designed to produce. The form verdict follows when the data earns it.
Why the second weekend matters more than the first
The first weekend after a move is a sample of one. The second weekend is a sample of two or three. Most roster moves produce one completed series on the announcing weekend and two or three on the following weekend. The second weekend is when the pick-ban starts to look like a pattern instead of a single series. It is also the weekend when the broadcast analyst desk catches up to the move and starts talking about it in production, which means the second-weekend read is the read the team itself is most likely to react to.
On the team and roster index the desk publishes the veto order from publicly reported series results and flags any roster move that has not yet produced a re-tested series on the new credit. That flag is what keeps the read honest. A 30-day win rate pinned at 71 percent after a coaching hire says almost nothing about whether the coach was a good hire. A 30-day win rate pinned at 71 percent after a player swap says almost nothing about the swap. The veto order on the first three completed series says the most, and the form table catches up by the third weekend.
What the next move is worth watching for
Treat the announcement as a hypothesis, not a result. Read the pick-ban before the form table, and ask what specific map or slot the move is designed to change. Track the first completed series on the new veto, the second weekend's veto pattern, and the form table only after the third weekend of completed series. If all three readings line up, the move held. If any one of them does not, that is the line the desk will update first.
The next move worth watching is whichever one happens in the upper half of the form table in the next seven days. The desk will publish the announcement on the news index the morning it lands, the pick-ban read on this coverage within the same week, and the form verdict when the data earns it.
