Pokemon: How to Write Matchup Notes That Actually Win Best-of-3

Best-of-3 in the Pokemon TCG punishes vague preparation. It is not enough to know that a matchup is “slightly favored” or that a deck “needs to go first.” Tournament wins usually come from smaller, repeatable decisions: which attacker matters first, which Prize cards can be ignored, when to bench a liability, which search card should stay in hand for Iono recovery, and what changes after side information appears in Game 1.

Useful matchup notes are not long theory documents. They are short, test-backed instructions that can be applied between games and between rounds without re-learning the matchup from scratch. For players preparing for Regional Championships, League Cups, or long online events, the goal is to convert testing into decision rules that survive fatigue and time pressure.

This guide lays out a practical note-writing system built specifically for the real Pokemon TCG tournament ecosystem: Standard best-of-3 rounds, open decklist and closed decklist contexts, and current deck families built around familiar engines such as Rare Candy evolution shells, Lost Zone engines, and Item-heavy setup decks. If broader tournament prep is still in progress, it helps to pair matchup notes with a full event routine like the one outlined in Deck Insider’s tournament coverage and prep pieces, including the Deck Insider home hub and the site’s Pokemon category.

What matchup notes are actually for, and when they are not the right tool

What to do: Write matchup notes to answer three tournament questions fast: what matters in the first two turns, what causes losses after setup, and what changes after Game 1 information. Every note should support one of those jobs.

For whom: This is most valuable for players on one deck for multiple events, players testing with a stable group, and anyone expecting nine or more Swiss rounds where memory quality drops late in the day.

When not to use: Do not rely on matchup notes as a substitute for reps. If the deck is still changing by 8 to 10 cards every session, notes will become obsolete faster than they become useful. The same is true if the player does not yet recognize common opposing lists. Notes cannot fix missing format literacy.

Bad notes are broad labels like “play carefully around Iono” or “take two-Prize KOs when possible.” Good notes are specific, testable, and attached to board states. For example: “Against Charizard ex, avoid benching a low-HP two-Prize support Pokemon before they commit their first attacker unless it directly secures turn-two pressure.” That sentence changes real in-game behavior.

The best way to judge whether a note deserves space is simple: if it cannot change an opening hand keep, a benching decision, a search target, an attack sequence, or a late-game resource line, it probably does not belong in the final sheet.

Build notes around matchup triggers, not around long summaries

What to do: Organize notes under triggers that appear during games. This makes them scannable and usable under round pressure. A strong structure is:

Opening priority: what matters before the first attack
Must-protect resources: cards or pieces that cannot be wasted
Bench rules: what not to expose
Prize map: most common winning route
Disruption points: when Iono, Counter Catcher, Roxanne effects in older formats, or hand pressure matter most
Game 2/3 adjustment: what changes after seeing their exact counts and techs

For whom: Ideal for competitive players who already know card text and deck functions, but need a system that speeds up recall.

When not to use: If the player is still learning a deck’s basic sequencing, trigger-based notes can feel too compressed. In that case, use a longer testing log first, then condense later.

Example skeleton for a current Standard matchup note:

Example framework: Raging Bolt ex against Charizard ex

Opening priority: establish Energy acceleration without over-benching two-Prizers
Must-protect resources: gust effects needed for support Pokemon and damaged threats; Energy recovery counts if the list is lean
Bench rules: do not give away easy multi-Prize sequencing by exposing unnecessary support ex Pokemon
Prize map: decide early whether the game is a 2-2-2 race or a 2-1-2-1 route through support pieces
Disruption points: if expecting Iono to low hand sizes, preserve one searchable setup out in deck or on board
Game 2/3 adjustment: if they show heavy gust and multiple switching outs, passive bench protection matters less than speed

This is already more useful than a paragraph saying the matchup is “tempo-based and close.”

Record only the information that changes decisions in best-of-3

What to do: Cut anything that does not alter Game 2 or Game 3 play. Best-of-3 notes should emphasize hidden information becoming known, adaptation to pacing, and the role of who won Game 1.

For whom: Especially useful for Regional-level play, where many matches involve known archetypes with small but critical list differences.

When not to use: In single-game local events with relaxed enforcement and highly casual deck diversity, granular Game 2/3 adjustment notes matter less than general fundamentals.

The most valuable best-of-3 note categories are:

Revealed techs: Manaphy, Jirachi, Lost Vacuum, additional gust, enhanced switching counts, stadium counts, unusual attackers
Pacing change: whether the opponent becomes slower or more conservative after winning Game 1
Response to your deck: whether they hold disruption for one exact turn window or aggressively chase support Pokemon
Clock implications: whether the matchup trends toward one full game plus a compressed Game 2, or reliably finishes three games

One practical note might read: “If Gardevoir ex shows only one heavy alternate attacker in Game 1, preserve gust for Kirlia line instead of holding for the bigger threat. Win by reducing engine, not by planning for a long boss chain.” That note creates a different target priority than the default assumption.

Another might read: “If Lost Zone Box reveals both Manaphy and Jirachi in Game 1, stop assuming spread or snipe pressure will carry the Prize map. Shift to direct knockout planning in Game 2.” Again, this is not theory; it is a changed line.

Use a one-page note format that can survive tournament stress

What to do: Compress the final version so each matchup fits in five to eight lines. The best notes are readable in under 20 seconds between games.

For whom: Players attending long official events, where over-detailed prep becomes dead weight by round six.

When not to use: Do not start with the one-page version during early testing. Compression only works after dozens of actual games or high-quality group review.

A practical final format looks like this:

Recommended layout

Matchup name
Go first / go second preference
Turn 1-2 priority
Bench rule
Prize route
Lose condition to avoid
Game 2/3 reveal adjustment

Sample compressed entry:

Charizard ex
Prefer: depends on list; default test result required, do not guess
T1-2: stabilize setup without exposing free gust target
Bench: no extra two-Prize support unless it changes damage math immediately
Prize route: usually support piece + two main attackers, not pure 2-2-2 if they can trade back cleanly
Lose condition: over-benching into gust chain after first KO
G2/3: if they show high switch/gust density, stop overplaying around a single stuck active line

That is enough to trigger memory without creating a second textbook.

How to test for notes that are real, not imagined

What to do: Tie every final note to observed games. A note should come from repeated outcomes, not from one memorable blowout.

For whom: Testing groups, coaches, and players who use online events or local Cups as data collection before larger tournaments.

When not to use: If sample size is extremely small, mark the note as tentative instead of presenting it as a rule.

A reliable process:

Play 8 to 12 post-board-equivalent best-of-3 sets against a serious pilot on the opposing deck.
Track why games were lost in one sentence each.
Circle causes that repeat at least three times.
Turn those repeated causes into positive instructions.
Retest after list changes of three or more meaningful cards.

The key step is converting losses into actions. “Lost because of dead hand after Iono” is not a note. “Against control-leaning disruption turns, keep one setup out in deck and one live draw/search line in hand rather than emptying all redundancy early” is a note.

For players balancing deck selection with note creation, it is useful to keep archetype-level summaries separate from deck-choice work. The broader metagame discussion belongs in resources like Deck Insider’s Pokemon strategy hub, while the note sheet should remain focused on in-round execution.

Write matchup notes by role: aggressor, stabilizer, or denial deck

What to do: Label your role in each matchup before writing any detailed note. In Pokemon TCG, many mistakes come from using the wrong role template. A deck can be the beatdown in one pairing and the stabilizer in another.

For whom: Essential for players piloting flexible decks like Lost Zone variants, Gardevoir builds, and toolbox lists that can switch attack plans.

When not to use: Very linear decks with one obvious plan in almost every pairing may not need a formal role label, though even those decks benefit from checking it.

Three useful role labels:

Aggressor: force the Prize race quickly; tempo matters more than perfect efficiency
Stabilizer: survive the first major swing, then win through stronger mid-game resource conversion
Denial/pivot: trade speed for a narrow choke point like energy access, bench space, or engine attrition

Example: against an explosive setup deck, Gardevoir ex may need notes centered on stabilization first: preserve evolving pieces, manage self-damage thresholds carefully, and only pivot into a high-damage closer after engine density is secure. Against a slower stage-based deck, the same list may become the aggressor, and the note shifts toward taking an early two-Prize lead before their main attacker chain is online.

This role-first framing prevents contradictory notes like “play slower and preserve everything” next to “pressure immediately and race,” both of which may be true in different pairings but cannot be true at the same time in the same matchup.

Practical scenario notes for common Pokemon TCG tournament situations

What to do: Use scenario notes when a matchup repeatedly turns on one narrow decision window. These are often more useful than general matchup summaries.

For whom: Strong for experienced players who already know the broad matchup but still drop percentage points in recurring spots.

When not to use: If the issue is broad inconsistency or poor mulligan/opening discipline, scenario notes may be too advanced to solve the real problem.

Scenario 1: Opponent reveals a thin switching count in Game 1

Note to write: “In Game 2, a trapping line becomes real. Value gust not only as a finisher, but as a tempo turn if they bench a high-retreat support Pokemon without protection.”

Practical effect: Changes gust timing from Prize-taking only to board-lock pressure.

Scenario 2: Opponent over-respects bench damage protection

Note to write: “If they bench Manaphy early in a matchup where bench damage is not the primary win route, their board may be less efficient. Punish reduced attacker density rather than chasing the protection piece.”

Practical effect: Prevents wasting resources on the wrong target.

Scenario 3: Game 1 shows heavy gust aggression

Note to write: “Do not bench support ex unless the immediate value exceeds expected gust punishment within two turns.”

Practical effect: Tightens bench discipline in Games 2 and 3.

Scenario 4: Opponent’s list is slower than expected

Note to write: “Shift from conservative setup to proactive Prize pressure. A slower list should be punished before it reaches full engine.”

Practical effect: Avoids playing scared against a list that cannot actually force the feared line on time.

Scenario 5: Match is likely to go to time

Note to write: “If Game 1 runs long, prioritize lines that preserve a win or tie structure rather than resource-maximizing lines that need three extra turns.”

Practical effect: Aligns decisions with best-of-3 tournament policy realities instead of idealized full-length games.

How to handle open decklist versus closed decklist note writing

What to do: Separate notes for open and closed information events. These are not the same skill.

For whom: Players moving between major unofficial events, online tournaments, and official circuits with different information environments.

When not to use: If the event structure is confirmed and fixed, keep only the relevant version to reduce clutter.

Closed decklist notes

Focus on default assumptions, scouting through revealed cards, and how to update priorities mid-match. These notes should include phrases like “if they show X, switch to Y plan.”

Open decklist notes

Focus on exact counts and inevitability questions. If the list has only one stadium, one heavy attacker, or no bench protection, that should already shape the opening plan before Game 1 begins.

In open decklist events, matchup notes become more exact. “Preserve Lost Vacuum in case of tool lock” is weaker than “their single Forest Seal Stone is their cleanest setup stabilizer; pressure before it converts.” Exact counts matter more because there is less uncertainty.

Limitations: where matchup notes stop helping

What to do: Recognize the ceiling. Notes are a memory and decision aid, not an autopilot system.

For whom: Everyone, especially players who tend to over-prepare on paper and under-prepare on board states.

When not to use: During active gameplay if consulting notes would violate tournament policy. Notes are a between-round and between-game preparation tool; always follow official event rules and judge guidance.

Main limitations:

Format churn: A new set, one major Regional result, or one card-count shift can invalidate old assumptions quickly.
Pilot variance: Some matchups feel different depending on opponent skill, sequencing discipline, and tech familiarity.
List-specific edges: A note that is perfect for one Charizard ex build may be wrong against another with different gust, stadium, or recovery counts.
Overcompression: Very short notes can hide why a rule exists, which makes adaptation harder when the game departs from the script.

The solution is maintenance. Update notes after every serious event, delete anything not supported by current games, and tag uncertain claims as tentative instead of treating them as law.

FAQ

How many matchups should be on a note sheet?

Usually six to ten, covering the decks most likely to appear at the event. Do not spend equal space on fringe archetypes if the top metagame decks still lack clear notes.

How long should each matchup note be?

For tournament use, five to eight short lines is enough. Longer versions belong in testing documents, not in the final event sheet.

Should matchup notes include exact card names?

Yes, when the card changes decisions. If Manaphy, Jirachi, Counter Catcher, Lost Vacuum, Rare Candy counts, or specific attackers alter sequencing, name them directly.

Do matchup notes matter more for control and toolbox decks?

Usually yes, because these decks have more branching decisions. Linear decks still benefit, but often from simpler notes focused on bench discipline, Prize mapping, and disruption timing.

How often should notes be updated?

After meaningful list changes, after a major event shifts the metagame, or after testing reveals that a previous “rule” is no longer winning games. In active formats, weekly review before a major event is reasonable.

What is the biggest mistake players make when writing notes?

Writing observations instead of instructions. “They can gust aggressively” is an observation. “Do not bench support ex before extracting immediate value because they showed aggressive gust lines in Game 1” is an instruction.

Conclusion

Matchup notes win best-of-3 rounds when they are short, specific, and tied to repeat decisions: opening priorities, bench rules, Prize routes, disruption windows, and Game 2/3 adjustments after real information appears. The strongest note sheets do not try to summarize an entire matchup. They tell the player what to do, for whom the plan works, and when that rule should be abandoned because the list, role, or event context is different.

In the Pokemon TCG, where small sequencing errors often decide otherwise even matchups, that level of clarity matters more than elegant theory. A one-page sheet built from tested triggers, role labels, and exact adjustment points will usually outperform pages of broad matchup commentary. The target is simple: less remembering, faster adaptation, and more rounds where Game 2 starts with a plan instead of a guess.