Tagging Poker Study Material by Situation, Not by Source Name
Most poker players collect material faster than they can use it. Articles, videos, forum threads, saved hand histories, and half-finished notes pile up in folders named after whoever wrote them or where they were found. That structure feels tidy at first, but it breaks down the moment you sit down to solve a real problem at the table or during a review. You remember that a particular idea was useful, but not which page it lived on. This article looks at a different organizing principle: sorting your study material by the situation it addresses. The approach is general and does not depend on any single source, and it works regardless of which resources you already use.
Why source-based folders fail under pressure
When material is filed by source, your retrieval depends on remembering where you first encountered an idea. That is a weak memory cue. Ideas travel: a concept you first read in one place may be discussed more clearly in another, and by the time you need it, you are searching across five folders to find one paragraph.
Source-based filing also hides overlap. Three different resources may all address how to think about bet sizing on wet boards, but they sit in three separate places, and you never notice that you have redundant or conflicting guidance. Organizing by situation forces those overlaps into the open.
Choosing situation categories that match real decisions
Start from the decisions you actually face. Good category names describe a moment in play: preflop opening ranges from different positions, facing a raise out of position, multiway pots, river decisions when the action is checked through, or bankroll and session-length choices. Avoid abstract buckets like 'theory' or 'strategy' that are too broad to search quickly.
Keep the number of top-level categories small, perhaps six to ten, and allow subcategories only where your play generates many notes. If a category grows beyond about thirty items, split it by one more dimension such as stack depth or table format.
Each note should carry two or three tags beyond its primary category, such as the street, the position, or the type of mistake it addresses. Tags let one piece of material serve several situations without being duplicated.
Writing notes that survive being filed
A filed note should be readable without the context that produced it. Begin with a one-sentence statement of the situation and the question it answers. Follow with the reasoning you want to remember, not a copied quotation. If a point came from a specific resource, record the source inside the note as a reference, so you can return to it, but do not let the source name become the organizing key.
Record when you last reviewed a note and whether you still agree with it. Ideas that were useful at one stage of your development may need revision after you have played more hands. A simple date and a one-word status such as current, revisit, or retired keeps the library honest.
Auditing the system you already have
You do not need to rebuild everything at once. Pick one recent review session and list the three decisions you found hardest to think about. For each, ask whether your existing material contains anything relevant, and where you would have looked for it. If you cannot find it within a minute, that is a signal the category for that situation is missing or poorly named.
Repeat this audit monthly for a short while. Over time, the categories that match your real questions will become clear, and the ones that never get used can be merged or removed.
A short checklist for testing your organization
Confirm that every category name describes a situation you actually encounter at the table or in review. Check that a note can be found by asking the question it answers, without remembering its origin. Verify that no note has been filed in two places at once; use tags for cross-references instead. Make sure each note has a date and a status. Finally, try retrieving three recent decisions from memory and time how long it takes to find supporting material. If the times are consistently long, adjust category names before adding more material.
An organizing system is only useful if it reduces the effort between a question and an answer. Judge yours by that standard, and revise it as your game and your questions change.