TLDR: Use this mtg limited set analysis checklist to create a one-page reference covering mechanics, archetypes, build-arounds, removal, combat tricks, fixing, curve requirements, and matchup cards. Record patterns that affect decisions rather than trying to memorize every card. Treat your first conclusions as hypotheses, then revise them after drafts and matches.
Good set preparation is not a test of whether you can recite every common from memory. The useful skill is recognizing what matters when a pick, build, or combat decision appears: which archetypes have enough support, what removal misses, which tricks you must respect, how ambitious the mana can be, and what a functional curve looks like.
Your set audit should therefore be compact enough to consult between packs or rounds. It is a working document, not a permanent tier list and certainly not a sacred tablet declaring that every green five-drop is a B-minus.
Start with the event and product context
Write down the set, event type, match structure, and product being opened. Draft and Sealed use the same card pool differently, while Best-of-One and Best-of-Three play place different emphasis on matchup cards and sideboarding. Product configuration also matters; Wizards introduced Play Boosters as a Limited-capable replacement for the former Draft and Set Booster model, so avoid assuming every product follows an older booster structure.
- Set and release date
- Draft or Sealed
- Best-of-One or Best-of-Three
- Paper or digital event
- Booster or product configuration
- Any event-specific deck construction rules
This context prevents a technically detailed analysis of the wrong environment. Before studying individual cards, confirm what players will actually open and how they will play it.
Translate mechanics into gameplay consequences
Do not copy reminder text into your notes. For each mechanic, record the decision it changes. Ask what resources it consumes, what board state enables it, whether it rewards attacking or waiting, and whether it creates unusual deckbuilding constraints.
| Question | Useful note |
|---|---|
| What enables the mechanic? | Creatures, spells, graveyard cards, artifacts, tokens, or a specific permanent type |
| What does it reward? | Attacking, trading, going wide, casting multiple spells, or extending the game |
| What can disrupt it? | Removal timing, graveyard interaction, bounce, blockers, or denying a setup turn |
| What does it demand in deckbuilding? | Enabler density, payoff density, cheap spells, fixing, or a particular curve |
| What wording needs verification? | Timing, targeting, replacement effects, triggers, or card-specific exceptions |
Use the current set’s official release notes for mechanic explanations and card-specific rulings. The supplied Mystery Booster Commander Edition notes illustrate the type of set-specific document to find, but they are not a substitute for the notes belonging to the set you are preparing for. For broader corner cases, consult Wizards’ official Magic rules resources, which present the Comprehensive Rules as a reference for specific rules questions.
Build an archetype map, not just a signpost list
Gold multicolor uncommons often advertise intended themes, but one appealing signpost does not prove that its deck is deep or reliable. Build a small map for every apparent color pair or supported strategy.
- Plan: How does the deck expect to get ahead or win?
- Enablers: Which commons make the plan function?
- Payoffs: Which cards become meaningfully better in this shell?
- Baseline: Can the deck play acceptable Limited Magic without drawing its synergy pieces?
- Overlap: Which enablers and payoffs belong in other decks?
- Warning signs: What would tell you the lane is shallow, overdrafted, or too dependent on uncommons?
A genuinely supported archetype usually has playable commons that establish its plan, not merely a powerful uncommon that describes the dream. If the enablers are weak outside one narrow combination, committing carries a higher opportunity cost.
For a systematic way to scan the card file by role rather than rarity, use the workflow in browsing a new MTG set with a Draft plan. It turns card browsing into a search for patterns, gaps, and questions worth testing.
Audit build-arounds by support density
For each build-around, count the playable support rather than every card containing the relevant word. A nominal enabler that you would rather leave in the sideboard does not suddenly become premium because an uncommon asks nicely.
Record the number and quality of enablers, how early you must commit, which pieces other drafters want, and whether the deck still functions when its centerpiece never appears. Also identify a pivot: if the dedicated plan dries up, can the early picks become part of a normal aggressive, controlling, or value-oriented deck?
The deeper process in evaluating build-around uncommons can help separate supported engines from attractive traps. Your one-page reference only needs the conclusion: low, medium, or high support, plus the most important enablers.
Make a provisional format-speed and board-texture forecast
Before playing, you can form a useful forecast—but not a verdict. Inspect the density of early creatures, cheap interaction, efficient evasion, fixing, defensive bodies, card advantage, and late-game mana sinks.
- If early creatures attack through common blockers, missing turn two may be costly.
- If defensive creatures line up well against common attackers, boards may stall more often.
- If removal is expensive or conditional, tempo and combat tricks may gain value.
- If fixing is plentiful but slow, multicolor decks may be possible without being safe against fast starts.
- If common threats generate value immediately, one-for-one removal may not fully stabilize the game.
- If evasive threats are scarce, identify the cards that can break a ground stall.
Finish this section with three to five provisional statements, such as “two-drops appear important” or “large ground creatures may demand unconditional answers.” The wording matters: these are questions to test during practice, not facts smuggled in before anyone has shuffled up.
Create an interaction map
Group interaction by function instead of making one undifferentiated removal ranking. For each color, record premium answers, conditional removal, expensive catch-all answers, tempo interaction, combat tricks, and narrow matchup tools.
| Interaction class | What to record |
|---|---|
| Premium | Targets answered, mana efficiency, speed, and important restrictions |
| Conditional | Power, toughness, card type, tapped-state, or combat requirements |
| Expensive | Whether it is reliable enough to justify the tempo cost |
| Tempo | Bounce, tapping, stun effects, or temporary exile and which decks exploit them |
| Combat trick | Mana value, stat change, granted ability, and blowout potential |
| Matchup card | The threat or strategy that makes the narrow effect worthwhile |
Then reverse the map. Which threats strain the available answers? Large toughness, ward-like costs, recursive threats, tokens, death triggers, and immediate value can all change how effective removal is in practice. “It kills a creature” is only the first line of the evaluation.
Record combat breakpoints and trick signals
You do not need every creature’s exact statistics in your compact reference. Note recurring power and toughness breakpoints instead: the size of common early attackers, the toughness that survives damage-based removal, the bodies that stop ground attacks, and the evasive threats that end stalled games.
For combat tricks, record visible clues rather than trying to memorize the whole file. Group tricks by their mana value and color, then note the unusual outcomes: first strike, indestructible, trample, untapping, protection, or multiple targets. During a match, this lets you ask a manageable question—“What can two open white mana represent?”—instead of searching your memory for dozens of cards.
Audit fixing, splashes, and casting demands
List the fixing available at common and uncommon, how much tempo it costs, and which decks naturally want it. Separate true color fixing from cards that merely draw or filter without helping you cast the spell in question.
- Untapped or tapped fixing lands
- Mana creatures and artifacts
- Treasure or other one-shot fixing
- Land search and basic-land cycling
- Cards that reward additional colors
- Double- and triple-pip spells that resist splashing
A splash should pay for its inconsistency. Bombs and efficient late-game removal are more plausible splash candidates than early creatures, combat tricks, or synergy cards needed on curve. Record both the splash target and the fixing package it requires; “I have three colors of cards” is not, by itself, a mana base.
Tag main-deck and matchup cards
Mark narrow cards during the initial review so they remain available when a matchup calls for them. Useful categories include anti-flyer interaction, graveyard hate, artifact or enchantment removal, specialized blockers, narrow removal, and slow card advantage for attrition games.
Wizards’ Limited sideboarding guidance notes that unused cards form the Limited sideboard and explains that a card’s value can change after seeing the opponent’s deck; creature size matchups are one example. The official Limited sideboarding discussion also distinguishes the practical sideboarding considerations of Draft and Sealed. Your notes should therefore describe the matchup that activates a card, not simply label it “bad.”
Adjust the checklist for Draft and Sealed
The underlying audit remains the same, but the emphasis changes.
| Draft emphasis | Sealed emphasis |
|---|---|
| Signals and which colors appear open | Pool depth and where the playable cards are concentrated |
| Opportunity cost of speculative picks | Alternate builds using the same pool |
| Common support for archetypes | Fixing and splashable power |
| When to commit or pivot | How the curve changes across configurations |
| Drafting matchup cards at low cost | Rebuilding or sideboarding for a known opponent |
In Draft, ask whether the cards arriving support your archetype map and whether your lane has enough playable depth. In Sealed, compare complete configurations: a consistent two-color deck, a stronger but slower splash build, or a different plan for a specific matchup.
Turn the audit into a practice loop
Once the one-page reference exists, test it. Practice picks with a Draft simulator while stating why each choice fits your archetype, curve, or interaction map. The goal is not to produce a pretend trophy; it is to find assumptions that fail under actual pick pressure. The 30-minute Draft simulator training plan provides a focused structure for those repetitions.
After a practice draft or event, build the final deck and inspect its curve, colors, land count, and card-role balance. MTG App promotes Draft Simulator and Deck Builder tools, while its Deck Builder describes checks involving curve, colors, lands, and ratios. These tools can expose construction questions, but they cannot decide whether your format assumptions or synergy package are correct.
For a clearer division of labor between list management and curve diagnosis, see when to use a deck builder versus a mana curve analyzer. A healthy curve is evidence that spells are distributed sensibly, not proof that the spells belong together.
The reusable one-page MTG Limited set analysis checklist
- Confirm the set, event type, match structure, and product configuration.
- Summarize each mechanic by what it enables, rewards, demands, and changes in play.
- Map each archetype’s plan, enablers, payoffs, baseline, overlap, and warning signs.
- Rate build-arounds by playable support density, commitment cost, and pivot options.
- Forecast speed and board texture using early plays, blockers, evasion, removal, fixing, and inevitability.
- Classify interaction as premium, conditional, expensive, tempo-based, or matchup-specific.
- Record common combat breakpoints and the mana values of tricks worth respecting.
- List fixing by availability, speed, and suitability for splashes.
- Tag narrow cards with the matchup that makes them useful.
- Write three to five provisional format truths and revise them after every event.
Common questions
Do I need a tier list before drafting?
No. A tier list can provide another opinion, but your compact audit is more useful for understanding relationships among cards. Knowing that a card is strong matters less than knowing what supports it, what competes with it, and when its value changes.
Should I memorize every common?
Learn recurring patterns first: key removal restrictions, trick mana, archetype enablers, fixing, and combat breakpoints. Exact card familiarity will grow through practice. Trying to memorize everything at once often hides the decisions you actually need to make.
Can one checklist serve both Draft and Sealed?
Yes. Keep one shared set audit, then add a small Draft column for signals and opportunity cost and a Sealed column for pool depth, splashes, alternate builds, and matchup reconfiguration.
Are curve and color tools enough to validate a deck?
No. They can reveal expensive curves, awkward color demands, or suspicious ratios. They cannot determine whether your threats match your plan, your synergy has enough support, or your interaction answers the format’s important threats.
Keep the reference short and revisable
The best set audit gets smaller as your understanding improves. Replace long card summaries with sharper observations, cross out predictions that failed, and promote repeated match lessons into concise format truths. Your next step is simple: open the card pool, create the ten checklist sections above, and limit the first draft to one page. Learn the environment’s decision patterns first; card-by-card memory can follow.