43 Database Review, Note-Taking & Leak-Finding
Most players believe they improve by playing more hands. They do not. They improve by playing hands, recording them, and then sitting in a quiet room afterward and forcing themselves to look honestly at what the record says. The table is where you earn or lose money; the database is where you find out why. A serious modern player treats the two as a single loop — play, capture, review, adjust — and the engine that drives the second half of that loop is the tracking software sitting on your hard drive and the notes you keep on every opponent you meet.
This chapter is about that engine. We will cover how to mine a hand-history database for your own leaks using the major trackers, which filters and reports actually carry signal, how to read the famous red line without scaring yourself off good aggression, how to keep opponent notes that are still useful three months later, and — the part nobody enjoys — how to convert a pile of damning evidence into a focused study plan and the self-discipline to follow it. Earlier chapters taught you to read a HUD live and to read opponents at the table; this one is about the cold, unhurried analysis you do away from the felt.
A word of honesty before we start. A database is a sample, and a sample lies in proportion to how small it is and how badly you slice it. Everything below comes with an implicit warning label: check your sample size before you believe the number. A leak you “found” in 800 hands is a coin flip wearing a lab coat.
43.1 Why review at all
Live reads are vivid and memorable; that is exactly what makes them treacherous. You remember the river bluff that got snapped off and the cooler that busted you, because they hurt. You do not remember the four hundred small pots where you folded the turn one street too early and bled a third of a big blind each time. Memory is a highlight reel weighted toward pain and drama. The database is the full footage, unweighted, and it is the only honest witness you have to your own game.
Your biggest leaks are almost never the spectacular hands you replay in the shower. They are small, repeated, boring errors — folding the big blind too much, c-betting a touch too often, calling river too wide — that each cost a fraction of a big blind but happen thousands of times. Reviewing is the act of making the boring leaks visible.
43.2 The tools
Three categories of software matter for off-table work, and most pros run more than one.
- Trackers — PokerTracker 4 (PT4) and Hold’em Manager 3 (HM3) are the two dominant hand-history databases. They import the histories your client writes to disk, store millions of hands, drive your live HUD, and — the focus of this chapter — let you filter and report on your own play. Their feature sets are broadly equivalent; pick one and learn it deeply rather than dabbling in both.
- Solvers and trainers — GTO Wizard, PioSolver, and similar tools answer the question “what should I have done here?” once a review has told you where to look. GTO Wizard in particular bridges the two worlds: it has its own analysis mode and, increasingly, can ingest your hand histories to score them against equilibrium and flag your largest mistakes by EV.
- Equity calculators — Flopzilla, Equilab, and the equity tools built into the above, for hand-by-hand range work when you want to understand a single spot in depth.
The workflow is: the tracker tells you where you are leaking, and the solver tells you what the leak is and how to fix it. Running a solver with no idea what to study is how people spend two hours confirming they play the button fine while the big blind quietly hemorrhages money.
43.3 Reading your own winrate: the two lines
Every tracker can draw a graph of your results over time. The single most instructive version of that graph splits your winnings into two lines.
- The green line (or “showdown winnings”) is the money won and lost in pots that reached showdown.
- The red line (or “non-showdown winnings”) is the money won and lost in pots that ended before showdown — i.e., pots decided by someone folding.
Your total winnings are the sum. The shape of each line is diagnostic.
A red line that slopes steadily downward is the classic signature of a winning-but-leaky player: you make money at showdown with strong hands (green line up) but bleed it back in all the pots where you give up — you check-fold too much, you fold the big blind too often, you fail to fight for pots nobody wants. Most small-stakes regulars have a sharply negative red line. This is not automatically a disease. Some red-line loss is structurally correct: you post blinds you cannot always defend, and a value-heavy style legitimately wins more at showdown than away from it. The red line becomes a leak when it is steeper than your style warrants — when you are folding equity you should be contesting.
“My red line is negative, so I must be too passive — I need to bluff more.” This is how losing players talk themselves into spewing. A negative red line caused by too much folding is fixed by contesting more pots; a negative red line is not a license to fire three barrels with air into calling stations. Diagnose the cause before you prescribe aggression. Plenty of solid players have a moderately negative red line and a fat, healthy green line and are doing absolutely fine.
The healthiest profile for most players is a strongly rising green line and a red line that is flat-to-gently-falling. If your red line is plunging while your green line barely climbs, you are a “showdown merchant” who only wins when you hit — predictable, exploitable, and leaving money in every pot you concede.
43.4 The filters that find leaks
A tracker’s power is in filtering: carving your millions of hands into subsets and asking what your winrate is inside each one. A leak is simply a subset where you lose money (or win far less than you should) at a meaningful sample size. Here are the slices that pay rent. Winrate is conventionally measured in bb/100 (big blinds won per 100 hands).
Positional winrate
Filter your winrate by your seat. This is the first report you should ever run, and it is brutally clarifying.
| Position | Healthy 6-max winrate (bb/100) | Reading |
|---|---|---|
| BTN | strongly positive (e.g., +20 to +40) | Your money-printing seat; should be your best |
| CO | clearly positive | Second-best |
| MP / LJ | around break-even to modestly positive | Fine |
| SB | meaningfully negative (e.g., −20 to −40) | Negative is normal — you post and act first |
| BB | negative (e.g., −10 to −30) | Negative is normal; how negative is the question |
The blinds lose money for everyone — you are forced to invest with no choice of hand and you are out of position. The diagnostic question is not “is my big blind negative” (it is, for everyone) but “is it more negative than it should be?” A big blind running worse than roughly −30 to −40 bb/100 usually means you are over-folding preflop, giving walks and easy steals, or folding too much to c-bets. If your button winrate is mediocre, you are leaving the single largest edge in the game on the table — that is an emergency, not a tweak.
Showdown vs non-showdown by line
Combine the red/green concept with line filters. Filter for hands where you were the preflop aggressor, then look at your c-bet flop winrate. Filter for hands where you called a 3-bet out of position and see the carnage. Filter fold-to-c-bet by position — a frequent culprit is folding far too much to flop c-bets in the big blind, where the population badly over-folds and the solver wants you defending a wide, sticky range.
Specific high-frequency, high-stakes spots
The pots that move your winrate most are the common ones. Prioritize by frequency times severity:
- C-bet / fold-to-c-bet — happens almost every hand you raise. A small percentage error here, multiplied by its enormous frequency, dwarfs a big error in some rare spot.
- Big blind defense — you face a raise here constantly; over-folding is the most common single leak in poker.
- Turn play after c-betting flop — the “second barrel or give up” decision, where a lot of red-line money lives.
- River bet/call/fold — biggest pots, so even modest frequency errors are expensive in raw bb.
Rank your study targets by frequency × cost-per-error, not by how painful the hand felt. A 0.05 bb leak that occurs 30% of hands is worth more than a 2 bb leak that occurs once every 500 hands. Trackers let you sort spots by total bb lost — let the arithmetic, not your emotions, set the agenda.
Filters for tournament and ICM players
Cash winrate is one number; tournament play needs slicing by stack depth and stage. Filter your push/fold spots when effective stacks are under ~15 bb, and review whether your shoving and calling ranges match the equilibrium charts from the short-stack chapter. Filter hands played near the money bubble and at the final table, where, as the ICM chapter explained, correct ranges tighten dramatically and a cash-game reflex to “get it in with the best of it” can be a real, expensive leak. Note that bb/100 is a noisier yardstick in tournaments — small samples and the all-or-nothing payout structure mean you lean harder on hand-by-hand review and solver checks than on raw winrate graphs.
43.5 A worked review
Let me walk through a realistic session of self-review the way I would actually do it, so the abstractions become concrete.
I import last week’s 9,400 hands of 6-max cash into PT4 and pull up the positional winrate report. Everything looks normal except one number: my big blind winrate is −44 bb/100 over a 1,600-hand BB sample. That is worse than the −25 to −30 I would expect for my style. The sample is modest but the gap is large, so it earns a closer look.
I filter to big blind, facing a single raise, hand reached the flop, and split the result by what happened on the flop. The c-bet-faced subset is where the loss concentrates. I add a filter: big blind, faced a flop c-bet, folded. My fold-to-flop-c-bet from the BB is 58%. Population and solver baselines for a defended big blind sit much lower — a single-raised pot wants the big blind continuing on the large majority of flops because of the great pot odds and the preflop investment already made. Fifty-eight percent is a flashing red light: I am folding the flop far too often after defending preflop.
Now I switch from the tracker to the solver to find out which flops I am misplaying. I pull a BB-vs-BTN single-raised-pot spot in GTO Wizard and look at the big blind’s flop response. The solver defends low and middling boards aggressively — it floats and check-raises connected and paired textures, folding only the genuine air. I scroll through my actual folded hands in the tracker and the pattern jumps out: I am open-folding hands like 9 8 on 7-5-2 and K T on T-6-3 — backdoor-laden, gutshot-equipped holdings that the solver wants to peel or raise. I have been treating “I missed the flop” as “I fold,” ignoring backdoor equity and the price I am being laid.
The leak, stated precisely: I over-fold the flop in the big blind in single-raised pots, specifically surrendering hands with backdoor straight/flush equity and overcards that should continue. That is a sentence I can study against and measure next month.
43.6 From data to a study plan
A leak you have named but not scheduled is a leak you will have again next week. The bridge from review to improvement is a written plan, and it should be ruthlessly short.
After every review session, write down exactly one leak — the largest by frequency × cost — as a single sentence, plus one concrete corrective action and one measurable check. For the example above:
- Leak: I over-fold flop in the BB vs a single raise, especially with backdoor equity.
- Action: Drill 50 BB-defense flop spots in the solver this week; build a simple heuristic (“defend any backdoor flush draw, any gutshot, any overcard pair-outs”).
- Check: Re-pull fold-to-flop-c-bet from the BB next month; target is bringing 58% down toward the low-to-mid 40s.
One leak. Not seven. You will actually fix one.
The reason for the brutal focus is that leak lists are demoralizing and motivating in inverse proportion to their length. A player who tries to fix nine things fixes zero and quits. A player who fixes one leak per week fixes fifty per year. The database will still be there; the leaks are not going anywhere. Work the biggest one, re-measure, and only then move to the next.
A sustainable rhythm for a serious player looks like: a quick session review after each session (mark 3–5 hands you were unsure of with the client’s flag/tag feature for later), a deeper database review weekly (positional winrates, red/green line, one named leak), and a solver study block between sessions targeting that week’s leak. The point of tagging hands live is that you cannot review what you did not capture — flag the spot the moment it confuses you, because by tomorrow you will have forgotten the runout.
43.7 Note-taking on opponents
The database tracks you; notes track them. Stats describe frequencies; notes capture the things a number never will — why he did something, what he showed down, the texture of his decision.
Online. Use the client’s color-coding plus short text notes; the trackers attach notes to a player that follow them across sessions. Two principles make notes useful months later:
- Record showdowns, not impressions. “Bad player” is worthless. “Showed down 8 5o after calling 3 streets from the BB, river was a brick” is gold — it is evidence of a calling range, timeless and unambiguous.
- Record deviations from baseline, not the baseline itself. Your HUD already tells you he c-bets 65%. Your note should capture what the HUD cannot: “min-3-bets only QQ+/AK,” “open-limps then 3-bet-shoves over a raise = AA/KK twice,” “tanks then jams river = always the nuts.” Capture the exploitable pattern.
A clean color scheme — say red for aggressive regs to avoid, green for recreational players to target, yellow for nits, blue for stations — lets you orient at a fresh table in one glance before any stats populate.
Tilt-notes. Typing “donkey, runner-runner, can’t fold” after a bad beat records your emotional state, not his strategy, and it actively misleads the future you who reads it and sits down expecting a fish. Notes must be falsifiable, behavioral, and written in a neutral voice. If you cannot write it as something he did and showed, do not write it.
Live. You cannot type at the table and a tracker is not running, so the channel is memory plus a discreet phone note after the session. Live notes lean on stable identifiers — the player’s appearance, seat habits, a verbal tell, a betting-size pattern (“bets pot only with the nuts, half-pot with everything else”). Encode the things from the live-tells chapter you actually confirmed at showdown, and jot them down in the bathroom or the car, because by the next session they are gone. The same falsifiability rule applies: “older gentleman, seat 4, open-limps then calls raises with any ace, never bluffs the river” is a strategy you can exploit next Tuesday.
43.8 The discipline of self-review
All of this fails without the one ingredient no software supplies: the honesty to look at a losing graph and ask “what am I doing wrong?” instead of “how unlucky was I?” Variance, as the variance chapter detailed, gives the rationalizing mind infinite cover — any stretch of bad results can be blamed on the cards, and any leak can be hidden behind “I just ran bad.” The database is the antidote precisely because it does not care about your feelings, but only if you let it speak.
Review your winning sessions as hard as your losing ones. Wins hide leaks beautifully — you ran a flush into a set, got there, and never asked whether the call was correct, because the result absolved you. The disciplined player audits the decision, not the outcome. A bad call that won is still a bad call, and the database is where you catch the ones the scoreboard let you get away with.
Three habits separate players who genuinely improve from players who merely accumulate hands:
- Separate decision quality from result. When you review a hand, evaluate the choice given the information you had at the time, with the river card covered. If the decision was good and it lost, log it and move on; if the decision was bad and it won, that is the hand to study.
- Quantify, then prioritize. Sort your leaks by total bb bled, not by how much each one stung. Let the arithmetic pick your homework.
- Close the loop. A review that does not change what you do next session was entertainment, not study. Every review ends with one named leak, one action, and one future measurement — and next month you check whether the number moved.
Do this and the play-capture-review-adjust loop becomes a flywheel: each session feeds the database, the database surfaces a leak, the solver fixes it, and the next session’s numbers tell you whether it worked. That loop, run patiently for a year, will move you further than any amount of raw volume. The felt is where you find out who is winning. The database is where you find out who is learning.