The real battle at a Major starts long before match day. This piece breaks down how teams approach map pool selection, the psychological warfare of the veto, and what players actually jot down in their prep notes.
At a Major, the real contest often begins before the first pistol round. Every hesitation on the veto screen, every map crossed off in the practice room—these are bullets fired in advance. This article isn't about aim; it's about what a team is actually preparing in the 48 hours before the event.
1. A Map Pool Isn't About Quantity—It's About Clarity
Many teams fall into the trap of thinking a wider map pool makes them harder to target in BP. The opposite is true. The cost of breadth is depth: default setups, utility combinations, clutch protocols—all require time to hone. The Major schedule doesn't allow you to polish all seven maps to the same level.
A more sensible structure is "three mains, two counters, one sacrifice": three maps you can play against anyone, two maps for specific opponents, and one map you've effectively given up but keep a minimal "don't get blown out" plan for. The key is that this structure must be explainable—the coaching staff can justify why these three, and players can quickly read the opponent's intent during BP.
Take Anubis. Mid control on this map hinges heavily on the rhythm of utility trades. If a team's utility execution is naturally slow, grinding Anubis has low ROI. Conversely, Ancient's default lines rely more on individual holds and clutch reading, suiting lineups with reliable clutch players. Map pool selection is essentially translating a team's capability structure into map language.
2. BP Is an Information War, Not a Lottery
The veto is hard because opponents are studying you too. Your last three matches on each map, where you won, where you lost—it's all public. The mind game is to make opponents believe there's a gap between your perceived and actual map pool.
A common tactic is "sandbagging"—deliberately running incomplete tactics on a map during the group stage to mislead opponents about your readiness. Then in the playoffs, you unveil the full execution chain on that same map. The risk is that every group stage match affects advancement, so sandbagging is costly. A safer approach is "partial sandbagging": holding back one or two tactical nodes in non-critical rounds without revealing the full utility sequence.
Another detail is the psychology of veto order. The team that bans first often signals what they fear; the team that bans second responds. If a team hesitates more than ten seconds on a ban, the opposing coaches will note it immediately—it usually means that map is a backup, not a primary. The time pressure on the veto screen is itself a leak.
3. Prep Notes: What Players Actually Write Down
Player notes are different from the coach's tactical board. The board holds macro defaults and utility timings; player notes are more like "fragments of opponent habits": a certain player likes to peek half a second early in gun rounds, a certain AWPer tends to hold a specific angle in clutches, a certain team uses utility at an unusually high rate in eco rounds.
The value of these fragments is that they help players build expectations quickly during matches. In CS2, expectation beats reaction—if you know where the opponent is likely to come from, your crosshair will be half a notch ahead. The thickness of prep notes doesn't equal quality; what matters is the entries players can actually recall mid-match. Good notes are short, specific, and actionable—not a list of abstract principles.
In the final 48 hours, training volume should drop, leaving time for review and communication. Over a long Major, stamina and focus are hidden variables; many teams lose not on tactics but on attention decay after the third map. The last page of a prep notebook often just says: "Don't rush."
Map pools and BP at a Major are never a simple reflection of paper strength—they are a team's clear-eyed assessment of its own limits. The team that wins the veto often wins those seemingly even matches.