Guide

How to use GTOWizard for live poker hand review

GTOWizard is powerful, but live poker players often get stuck before the solver: rebuilding a clean hand. Capture positions, stacks, action, board cards, and player reads first so review starts faster later.

• Know what information GTOWizard needs before study
• Lock in the minimum live-hand details to capture
• Connect session logging, sharing, and review text

Decide what GTOWizard needs before you study

Trying to build a perfect solver input at the table makes live logging heavy. Start by locking in the minimum details you need to rebuild the hand later.

• Positions, player count, stacks, blinds, and ante
• Action order from preflop through the river
• Board cards, showdown, and player tendency notes

Capture selected live spots, not every hand

Prioritize hands where the decision was unclear, the stack or profit changed materially, or the same opponent pattern repeated.

• All-in spots, 3-bet/4-bet pots, and big river bets first
• Do not lose stack depth or effective stack information
• Write down why the spot felt close

Separate share links from review text

A link for a friend or coach and a GTOWizard import text serve different jobs. Sharing needs readability; solver review needs structure and reproducibility.

• Keep private notes and labels out of public shares
• Use PokerStars-style text when the review tool expects that shape
• Attach the hand to the session result so the context is not lost

Tie review back to session results

If GTOWizard review lives outside your session log, it becomes hard to remember which leak cost money. Keeping profit, hourly rate, room, and hands in the same workflow connects the number to the decision.

See the GTOWizard review workflow