Texas Hold'em Hand Analysis with Software: Five-Phase Review Workflow
June 2, 2026

Structured hand review: export, priority filter, blind replay, street-by-street verdict, one leak patch. Tracker + replayer + calculator stack. Process over outcome; verify pot odds on every borderline spot.
- hand analysis
- poker review
- hand history
- replayer
- PokerTracker
- GTO review
- poker software workflow
- session review
The river result tells you who won the pot—not whether your line was correct. Professional review uses street-by-street logs: positions, stack depths, pot sizes, and action sequence. Software (trackers, replayers, equity calculators) supplies that data so you can judge decisions independent of outcome.
RiverOdds and Check Replay both recommend 5–10 key hands per session, reviewed while table context is fresh, instead of marathon database scrolls with no filter.
This guide is a five-phase review protocol: export and load, priority filtering, blind replay, street verdict worksheet, one patch rule, tool stack by function, one verified arithmetic example, and leak log maintenance. Works with PT4, HM3, Check Replay, or any import-capable replayer.
What Data You Need Before Review
| Data point | Why it matters |
|---|---|
| Positions + stacks | Same action, different SPR = different line |
| Pot size each street | Pot odds and bet sizing context |
| Action sequence | Range construction depends on line |
| Showdown (optional last) | Hide until verdict to avoid outcome bias |
Export hand histories from PokerStars, GGPoker, ACR, etc., or log live hands into mobile trackers. DeepFold and similar tools parse replay links for apps without standard export—the same protocol applies once data is imported.
Five-Phase Review (30–40 Minutes)
Phase 1 — Export & Load (5 min)
End session → export HH file → import to tracker or upload to browser replayer (Check Replay, etc.). Check Replay supports drag-drop from major rooms without install.
Do not filter yet. Load the complete session. Missing hands = missing decision points.
Phase 2 — Priority Filter (5 min)
Apply priority codes, not "biggest losses first":
| Code | Filter | Why |
|---|---|---|
| P1 | Time-bank or noted "???" hands | Highest learning signal |
| P2 | 3-bet/4-bet pots | Structural mistakes repeat |
| P3 | Pots > 30bb, any result | SPR decisions matter |
| P4 | Showdown surprises | Range calibration |
| P5 | Biggest $ loss only | Lowest priority—coolers hide leaks |
Pull 5–8 hands total. Reviewing five focused hands beats reviewing twenty without structure.
Tracker filters (PT4/HM3): position, pot size, hand strength, street of all-in, note tags. Tag uncertain hands during play when possible—P1 hands are pre-marked for review.
Phase 3 — Blind Replay (10 min)
Watch each hand without looking at the result first:
- Pause before your first decision point
- State aloud: "Villain range is ___; default action is ___"
- Play forward one street
- Repeat until river or fold
Check Replay and built-in tracker replayers both support street pauses. Cover the winner icon if your tool shows it early.
RiverOdds' core rule: Would you make the same decision 100 times in this spot? If yes, correct—even if it lost today.
Phase 4 — Street Verdict (10 min)
For each hand, one verdict row per street where you acted:
| Street | Your action | Verdict (✓ / ✗ / ~) | One-line reason |
|---|---|---|---|
| Preflop | 3-bet AQo | ✓ | Standard vs CO open |
| Flop | c-bet 33% | ✗ | Wet board—too small/frequent |
| Turn | Check | ~ | OK given flop mistake |
| River | Call $45 | ✗ | Needed 43%, had ~28% |
Verdict on process, not outcome. Use free equity + pot odds calculators for borderline spots:
Facing $45 into $60 → need 45/105 ≈ 43% equity to call.
Phase 5 — Patch Log (5 min)
Extract one rule per session into a leak log (spreadsheet, notes app, tracker notepad):
2026-06-02 | Wet flop OOP | Check or bet 66%+, never 33% auto | P2 hand #3
Next session: one sticky note with that rule. Repeat fixes compound because the same mistake gets flagged before the next session, not after another costly pot.
Tool Stack by Function
| Role | Job | Options |
|---|---|---|
| Import + storage | Capture + store HH | PT4 ( |
| Replay | Visual street replay | Check Replay (browser), tracker replayer |
| Math | Equity, pot odds, ICM | HoldemInside, PokerPro, ThinkGTO (free) |
| Deep analysis | Solver comparison | GTO Wizard free tier, Flopzilla (paid) |
You do not need all four on day one. Minimum viable stack: browser replayer + free equity calculator + notes app. Add a tracker when volume justifies the cost.
PokerStars/GGPoker: export tutorials vary by client version—use platform-specific guides rather than guessing file paths.
Worked Review: One Hand Through All Phases
Setup: $1/$2, 100bb. CO opens $6, you BTN 3-bet to $20 with A♣J♣, CO calls. Flop Q♠ 8♦ 3♣. Pot $41.50. You c-bet $14 (~34%). CO calls. Turn 2♥. Pot $69.50. You bet $35 (~50%). CO calls. River 5♠. Pot $139.50. CO shoves $141 (all-in). You call with AJ.
Phase 3 blind read: Flop—CO range has many Qx, 88, 33, some floats. AJ has two overs + backdoor. C-bet small is OK on dry-ish flop. Turn 2—still ahead of floats, behind Qx. Bet for value/protection reasonable. River 5—CO shove represents Q+, sets, maybe turned floats that got there.
Phase 4 verdict:
- Flop c-bet: ✓ (dry texture, range advantage)
- Turn bet: ~ (thin but defensible)
- River call: ✗ — Pot $139.50, villain shoves $141, you call $141 → total pot $421.50 → need 141/421.50 ≈ 33.4% equity.
AJ vs tight shove range (QQ+, AQ, KQ, sets, few bluffs) often sits below 33%—and even when close, reverse implied odds vs QQ+ hurt. Process error: hero call without range read supporting it.
Phase 5 patch: "River vs CO 3-bet pot caller: fold one-pair below top pair to pot-size shove on brick runout."
No solver required—just range logic and pot math.
Outcome Bias Controls
Three mechanical rules:
- Hide result until Phase 4 complete
- Verdict before showdown card on replay
- Log decision quality in leak tracker, not $ won/lost
Pausing before showdown reveal is the most effective anti-bias tool in browser replayers.
Group Review vs Solo
| Mode | Best for | Tool |
|---|---|---|
| Solo | Volume, private leaks | Tracker + notes |
| Group | Line validation, live feedback | Shareable replay link (Check Replay, etc.) |
| Coach | Systematic leak plans | Export P1 hands weekly |
Same five phases—group adds external verdict on Phase 4.
Maintenance Schedule
| When | Action |
|---|---|
| After session | Phase 1–2 (export + filter), 5 min |
| 2× weekly | Full review Phases 3–5, 30 min |
| Monthly | Re-read leak log; retire fixed rules |
| Quarterly | Audit tool stack—still using what you paid for? |
Three Common Review Mistakes
Highlight-only review — Only watching hands you won big or lost big. P1 uncertain hands matter more.
Spreadsheet without replay — Stats without street context. Numbers need action sequence.
Solver before hypothesis — Running Pio before stating your own range read. Solvers confirm; they do not replace Phase 3 thinking.
Summary
Software hand analysis is structured decision review, not reliving the biggest pots. Export, filter by priority, replay blind, verdict street by street, patch one rule. The players who improve are not the ones with the most tools—they are the ones who run the same five-phase checklist after every session.
PokerJudge bundles import, replayer, calculators, and AI street notes in one stack—but the five phases work with any tracker or browser replayer.