With 72 hours to go, the real battle is not about playing more maps but about prioritizing the map pool into three tiers, simulating veto sequences, and writing timestamp-level prep notes that can be reviewed in a 30-second timeout.
Major's opening day is never the starting line. The real starting line is 72 hours before—map pool confirmation, opponent demo slicing, and veto order simulation all hit at once, yet training time is limited. I've seen too many teams spend this period "practicing more maps," only to find on match day that every map is just "playable," none is "worth betting on."
The map pool is not seven maps, but three priority bands
The Major map pool is fixed, but fixed doesn't mean equal. The first step in preparation is to divide it into three bands: must-win band (maps where we have the highest win rate and opponents know we're strong), trade band (maps where both sides are average, decided by veto order mind games), and sacrifice band (maps we actively give up to gain veto initiative).
The basis for this division is not scrim win rate but "reproducibility." If a map's winning formula relies on a player's on-the-fly brilliance, it shouldn't be in the must-win band; if a map's losing pattern is structural—e.g., we never get mid control in default—it should be in the sacrifice band. The harshest line in my prep notes: "Don't fool yourself with a 7:2 scrim score; 3 of those 7 rounds were the opponent testing new stuff."
Veto order simulation must be opponent-specific. Suppose they will ban our strong map; what do we ban first? My habit: first ban the map in the trade band that is hardest to patch up on short notice, pushing the pressure back. Veto is not about who has a deeper map pool; it's about who is forced into an unfamiliar rhythm first.
Granularity of prep notes: from "hit A" to "which smoke at which second"
Many teams' prep notes stop at "hit A fast, hit B slow," which is useless at a Major. What truly carries into the match are timestamp-level agreements: who throws which utility at second 15 of default, who takes which info at second 40, who has firepower rights in a 3v3 clutch.
My own notes have three columns: structure column (fixed setups and utility combos), trigger column (what info triggers what rotation), and fault-tolerance column (first reaction when the plan breaks). The fault-tolerance column is most overlooked, but under Major intensity, plans break routinely. For example, after a failed mid control plan, does the team fall back to default or force a fast pace? This decision must be written before the match, not left to five players voting on the fly.
Another point: notes must be short enough to flip through in a 30-second timeout. I've seen people write essays, then can't find the page during a timeout. Only notes that can be quickly retrieved are effective notes; the rest is self-comfort.
Information trade-offs under high-pressure schedule: less is more
Major's schedule is dense; you might play two matches in a day with only a few hours between. In that time, players shouldn't review everything but only the rounds where the decision chain broke. In close rounds, the outcome often hinges on a single misread—who gave false info, who didn't call, who called but no one listened.
My advice: split review into 15-minute blocks: first 5 minutes only on lost economy rounds, middle 5 only on opponent's force buys, last 5 only to confirm next match's veto order. The rest is for rest. Deep into a Major, it's not about who practiced an extra map but who can keep clear judgment on match day.
72 hours can only do so much, but enough to turn "we can play anything" into "we know what to play." That shift is the real output of preparation.