At a Major, map picks are tied to bracket position and scrim hours—not a flat list of comfort maps. Seeds, BO1 chains, and a deliberately kept “tail” map decide where teams spend their prep time before elimination BO3s.
During a Major cycle, the active map pool is not a checklist of maps you might play. It is a labor ledger locked to your Swiss seed. Higher seeds often see softer early-round pairings; teams spend pick priority protecting staple maps and steering rivals toward the tail. Lower seeds flip the script—every strong map can become a must-win grind, so scrim blocks get split by BO1 versus BO3 likelihood instead of spreading hours evenly across every name in the pool.
Seeding and Pairings: Maps Before Names
Swiss is about crossing the advancement line in a fixed number of rounds. Most staffs run two spreadsheets: map strengths and pick/ban habits by opponent, and how your slot moves after each W or L. Top teams rarely spam their best map in round one. On BO1s they take mid-tier preferences to harvest defaults and test reactions, saving the hammer for matches that actually end a run. Weaker sides lean on single-map spikes because a long BO1 streak exposes thin pools, and if you reach BO3, tail maps—Anubis, Ancient, and other rotation slots—often lack full default depth. First bans must ask whether you can drag opponents into a narrow lane you have scrimmed for hundreds of rounds.
Middle seeds hurt the most. One win can pair you with another middle team; if your pool is shallow, back-to-back BO1s reveal a “three-map team” fast. Prep notes spell out whether default sites, mid handoffs, and utility economy on each map can be reviewed inside forty-five minutes. If not, that map is either a must-pick early in the veto chain or a decoy played only with off-meta looks.
The Pool Tail and BO3 Deciders
Most squads do not improvise a decider on the day. They reserve a low-ban-rate, high-rep slot that looks like a concession but concentrates hours. Scrim logs usually track three layers: CT first-contact timing (who eats the first flash, who holds the trade window); T-side switches between slow defaults and fast execs (numbers advantage, utility left); and post-timeout resets (second variant on the same site in one half). If you are still rebuilding macro on that map two weeks out, either your veto forecast was wrong or opponents compressed your bans.
After a map rotation, last season’s auto-ban sheet is stale. New or returning maps change more than geometry—sound radius, smoke gradients, cross timing—which rewires default lines and hold order. Serious teams archive “week-one demos after the patch” as pure POV timeline alignment: the same default can miss first contact by half a beat under different tick feel, and in Swiss that snowballs into full-round economy collapses. That work has nothing to do with skin markets; it is in-server rhythm only.
Player Discipline Across the Cycle
Three rules show up in every notebook. Physical blocks: daily BO1s drain focus before aim; mark the round where new defaults are banned. Comms compression: with few pauses, calls stay economy, site, rotate—no stack overload. Mental seeding: do not BO3-grind deciders while winning; do not swap three defaults within twenty-four hours while losing. The tail exists to catch you, not to hide from prep.
Seeding, veto, and the map-pool tail are the same prep budget repriced each round. What belongs in the Major notebook is which map is worth revealing at which seed, not a vanity list of “our strong maps.”