Major format debates usually focus on qualification slots and seeding, but for players, the real game-changer is the weight of the map pool in the pick/ban phase. The difference between BO1 and BO3 isn't just one more map—it turns 'preparation depth' from optional to mandatory.
Major format discussions often stop at qualification slots and seeding, but for players, what truly alters preparation rhythm is the weight of the map pool in the pick/ban phase. The difference between BO1 and BO3 isn't just playing an extra map—it's turning 'preparation depth' from optional into hard currency.
1. Pick/Ban Is Not a Draw; It's Resource Pre-commitment
In BO1, the first-ban side gets a 'veto vote,' while the second-ban side gets a 'targeted vote.' Many teams only write 'what we ban' in their pre-match notes, but fail to write 'what remains after we accept the opponent's ban.' This is the most common structural gap in prep notes: making single-point decisions without building a branch tree.
A team with complete tactical packages for only two maps might seem sufficient in BO1, because bans can always push opponents into familiar territory. But in BO3, the third map often becomes a forced 'semi-familiar zone'—default positions exist, but utility lines don't; utility lines exist, but clutch role assignments don't. The format won't tell you this; only the score will.
So the first page of prep notes shouldn't be a tactical map, but a three-branch table: opponent bans first, we ban first, and neither bans our 'semi-familiar map.' Under each branch, specify: who carries the bomb, who takes first contact, and who calls the default rotate before 0:00.
2. The 'Version Velocity' of the Map Pool Is More Worth Recording Than Patch Notes
Map pool changes have two layers: official adjustments and teams shifting their focus within the pool. The latter is more subtle and affects on-the-fly decisions more. For example, if a map is repeatedly picked by opponents in the last three weeks, it indicates it's treated as a 'low-risk high-reward' option in the current matchup circle; then your prep notes should record not 'we've practiced this map,' but 'who has beaten us on this map recently and with what rhythm.'
Velocity judgment can be based on three observable items: average engagement time in default rounds, first utility placement, and the trigger condition for the attackers' first rotate. These don't require official data—just VOD review. After five matches, you'll get a map profile closer to actual combat than patch notes.
3. The Fifteen-Minute Pre-Match Checklist
The value of player prep notes lies not in thickness but in executability. It's recommended to split the fifteen minutes before the match into three segments:
First five minutes: confirm the pick/ban branch tree and default positions for 'semi-familiar maps'—just run through once, no debate. Second five minutes: confirm the first round of utility placement order, focusing on smoke and flash relay points—who flashes first, whose smoke lands later, written as names plus seconds. Third five minutes: confirm clutch communication vocabulary: who reports player count, who reports bomb site, who calls the rotate. The shorter the vocabulary, the better; more than six words will fail in clutches.
This checklist won't guarantee a win, but it guarantees one thing: when the score reaches 12:12, the team won't lose an extra round because 'we weren't prepared for this map.' The Major format pushes the map pool to the forefront; prep notes should bring the spotlight back to the players' hands.