How to use EvoDecks

EvoDecks separates a deck’s plan from the physical copies in your collection. A list can require four copies of a card even when you own only two. That distinction lets you preserve the list you intend to play while the Completion page tells you exactly what can be moved from storage and what still needs to be acquired.

1. Find the right printing.Use catalog search and card details to identify cards and check format information.
2. Record what you own.Collection counts provide the inventory used by deck completion.
3. Build the intended list.Import a decklist or add cards from search, then set required and assigned copies separately.
4. Resolve missing copies.Move owned cards from collection locations into the deck and isolate the remaining buy-or-trade list.
5. Write down results.Record event matchups, starting position, wins, losses, notes, and misplays.
6. Preserve meaningful versions.Save builds before changes so tournament results stay connected to the version that produced them.

Collection tracking answers a different question than the decklist: “Where are my actual copies?” An unassigned copy is owned and free to use. An in-deck copy is owned but already committed to a deck. Copies can also be organized in binders or bulk boxes. EvoDecks uses those locations when it explains which missing deck cards can move immediately.

Do not increase ownership just to make a deck look complete. Keep the intended quantity in the deck and the true physical quantity in the collection. The resulting gap is useful: it becomes a focused acquisition list instead of a hidden shortage.

On the Create Deck page, choose a name and format, then optionally paste a deck list. Imports understand section headings such as Pokémon, Trainer, and Energy. Verify Deck List checks matches inline without leaving the page, so you can fix unmatched names or ambiguous printings before creating the deck. After creation, use the workspace search to add or test more cards.

Required and assigned are intentionally separate

Needed (the required quantity) describes the deck you want. Assigned describes physical copies currently committed to it. That is why the sample Charizard ex row can need three while only two are assigned. Side notes, card sections, a testing queue, and potential cards help preserve the reasoning behind changes instead of reducing the deck to a bare list of names.

The Completion page combines deck requirements with collection ownership. It distinguishes cards already assigned to the deck, matching copies available elsewhere in your collection, and truly uncovered copies. The distinction prevents a copy sitting in a binder from being mistaken for a card you still need to buy.

Move available copies only when you are ready to commit them to this deck. After movable copies are assigned, copy the remaining missing-card list for shopping or trading. A deck becomes ready when every required copy is covered; format legality is a separate check, so review both before an event.

Tournament tracking is most valuable when notes are specific enough to change a future decision. Create an event record, identify the deck version used, then add matchup rows with wins, losses, whether you started first or second, and concise observations. Separate fields for your misplays and the opponent’s misplays help distinguish a list problem from a piloting error.

After the event, translate repeated observations into the Testing queue: cards to try, cards to cut, and unresolved slots. A single loss does not automatically justify a change, but a clear note makes it possible to compare the same question across several events.

Save a build before a tournament or before replacing several cards at once. Give it a label that will still make sense later, such as an event name, date, or testing goal. Saved builds can be compared with the current list and can be linked to tournament records, so results remain attached to the cards that were actually played.