Poker Hand History Review Template: Find Leaks and Improve Your Decisions
A useful poker hand history review is less about proving whether a hand was won or lost and more about finding repeatable decision patterns. This guide gives you a practical template for marking hands, reviewing every street, separating strategic errors from normal variance, and tracking whether a suspected leak is improving over time.
Overview
Hand history review is the process of returning to recorded hands after a session and examining the decisions with more time and information than you had at the table. It can be used for cash games, sit-and-gos, and multi-table tournaments, but the questions should match the format. A tournament decision may depend on stack preservation, payout pressure, or the stage of the event, while a cash-game decision is usually evaluated more directly through chip or money expectation.
The most productive reviews focus on decisions rather than results. Winning with a questionable line does not automatically make the play good, and losing after making a sound decision does not prove that the decision was wrong. A review should ask whether your assumptions about ranges, position, bet sizes, stack depth, and incentives were reasonable at the time.
Use this basic workflow after each session:
- Mark hands during play without trying to solve them immediately.
- Record the context before looking at the result.
- Reconstruct the action street by street.
- Write your first conclusion before consulting a calculator, database, coach, or solver.
- Compare the decision with a reasonable alternative and record the lesson in a searchable log.
For foundational probability terms, a quick reference such as the Poker Hand Odds Guide can help you check assumptions without turning every review into a complicated calculation.
What to track
1. Context before the hand
Begin with facts that influence the decision. Record the game format, stakes or buy-in level, table size, blind level if applicable, and whether the hand came from a cash game or tournament. Then note your position, the positions of relevant opponents, effective stack size, and any unusual table conditions.
For tournaments, include the approximate stage, remaining players, pay-jump considerations, and whether the hand occurred near a bubble or final table. You do not need to assign an exact monetary value to every chip during an initial review, but you should flag situations where payout pressure may change the preferred risk level. The guide to poker tournament payout structures is useful when a review involves ICM or bubble decisions.
2. The action and sizing
Copy the complete action in order. Include preflop positions, opening size, calls, folds, 3-bets, 4-bets, and the effective stack after each action. On later streets, record board cards, pot size, bet sizes, and remaining stacks. Avoid summarising a hand as raised, called, and lost; that removes the details that usually explain the decision.
Also note whether the action was taken online, in a live game, or while playing multiple tables. Time pressure and incomplete information can be relevant to a study plan, even though they do not change the underlying strategic question.
3. Your decision and the alternatives
For each important decision, record:
- Your available options, such as fold, call, check, or one of several bet sizes.
- The range you assigned to each opponent before acting.
- The information supporting that range.
- Your estimate of how often worse hands continue and better hands fold.
- The hands or draws you expected to improve on future streets.
- The alternative line you now want to investigate.
Write this before checking the showdown whenever possible. Seeing the opponent's cards can create hindsight bias and make a narrow result appear more obvious than it was.
4. Tags for recurring leaks
Tags make a hand history database useful. Start with a small, consistent list rather than creating a new label for every hand. Helpful categories include position, stack depth, street, pot type, and mistake type.
| Tag group | Examples | What it can reveal |
|---|---|---|
| Position | UTG, cutoff, button, small blind, big blind | Whether your preflop ranges or postflop plans change by seat |
| Stack depth | Short, medium, deep | Whether you use the same strategy when implied odds or commitment thresholds change |
| Street | Preflop, flop, turn, river | Where decisions become unclear or overly passive |
| Action type | Open, defend, 3-bet pot, continuation bet, bluff-catch | Specific situations that deserve focused study |
| Mistake type | Range error, sizing error, equity error, timing error, tilt | Whether the problem is technical, procedural, or emotional |
| Confidence | Low, medium, high | Which hands need outside verification first |
Do not tag every losing hand as a leak. A leak is more credible when a similar decision appears repeatedly and the underlying reasoning is consistently weak or incomplete.
Cadence and checkpoints
A review system works best when it is regular but limited. Trying to analyse every hand can produce fatigue and shallow conclusions. Instead, mark hands during play and choose a manageable group after the session.
After each session
Review the hands that caused uncertainty, emotional discomfort, or a large pot swing. Include a few routine hands as a control sample, because only reviewing dramatic pots can distort your view of your game. For each selected hand, write one sentence describing the decision you found hardest.
Weekly checkpoint
Group hands by tag and look for repetition. If three or more hands involve defending the big blind, turn play, or river bluff-catching, review them together rather than treating them as unrelated problems. Compare the assumptions you made in each hand and identify one common question to study.
A good weekly output is a short action list: one concept to learn, one decision rule to test, and one behaviour to monitor in the next session. For example, you might commit to recording turn bet sizes more carefully or pausing before calling large river bets.
Monthly or quarterly checkpoint
At a longer interval, compare your tags across a larger sample. Track how often a category appears, how often you identified a possible error, and whether your confidence in those decisions changed after study. Do not treat these counts as proof of your win rate or skill level; they are study signals, not a substitute for a complete database review.
Revisit the tags themselves at this point. Merge labels that mean the same thing, remove categories that never help you make a decision, and add a label only when a recurring situation needs separate attention.
How to interpret changes
The central distinction in a poker leak finder is between decision quality and outcome. Results are noisy over short samples, especially in all-in situations. A better review asks whether your process improved: Did you assign a more realistic range? Did you account for position? Did you choose a sizing that matched your objective? Did you recognise when tournament conditions changed the value of taking a marginal risk?
Use the following comparison when reviewing a tagged pattern:
| Observation | Possible interpretation | Next step |
|---|---|---|
| The same error appears in several similar hands | A repeatable technical or process leak is plausible | Study the spot as a group and create a simple decision checklist |
| The hands have different contexts but the same result | Outcome bias may be connecting unrelated decisions | Separate the hands by position, ranges, and stack depth |
| Your decisions improve but results do not | Variance may be masking progress | Continue tracking process quality over a longer sample |
| Your results improve but reasoning remains unclear | A temporary result may be hiding a fragile strategy | Review assumptions and test the line in comparable spots |
| Confidence changes sharply after seeing the showdown | Hindsight bias may be influencing the review | Write your range and plan before checking revealed cards |
Use tools proportionately. Pot-odds calculations can clarify a call, while range analysis can help with close decisions. Solver outputs are most useful when you understand the assumptions behind the model, including positions, stack sizes, bet sizes, and allowed actions. A tool result should prompt a question, not replace your explanation of why the decision works.
When the hand involves a serious emotional mistake, record the state of mind separately. Fatigue, frustration, distraction, and fear of losing can influence otherwise familiar decisions. This is not a reason to label yourself; it is a way to distinguish a strategy leak from a session-management problem.
When to revisit
Revisit your poker session review checklist after every session, but do a deeper review weekly and a broader audit monthly or quarterly. Return sooner when you change formats, move to a different stack depth, enter a new tournament structure, or notice that a previously stable decision has become uncomfortable.
Update the template when your games change. A cash-game log may need more detail about table dynamics and player tendencies, while a tournament log may need blind levels, antes, payout pressure, and late-registration context. The poker tournament blind structure guide can help you identify which tournament details are worth recording.
Use this five-minute action plan at the end of your next session:
- Mark three hands: one uncertain hand, one emotionally difficult hand, and one routine hand.
- Write the context, effective stack, action, and your range assumptions for each.
- Choose the single decision that deserves deeper analysis.
- Tag it by position, stack depth, action type, street, and suspected mistake.
- Schedule a weekly review and compare the tag with hands from earlier sessions.
- At the end of the month, keep one recurring leak to study and one improved habit to maintain.
The goal is not to eliminate every difficult decision. It is to make your reasoning more visible, identify patterns before they become expensive habits, and build a review record that becomes more useful each time you return to it.