Stack
Your stack is the chips you have at the table at any moment. Stack depth, measured in big blinds, shapes correct strategy.
In short: The chips in front of you.
- Category
- Game
- Best use
- Session review and bankroll decisions
- Related page
- Effective stack
Why Stack matters
Your stack is the chips you have at the table at any moment. Stack depth, measured in big blinds, shapes correct strategy. Game terms matter because they describe the conditions that make a result meaningful. The same £300 win says different things at different stakes, stack depths, formats and table line-ups. Without the game context, the number is detached from the decision.
Worked example
Sitting with £1,000 at 2/5 NL is a 200 big-blind, deep stack. The useful part is not the label itself; it is the decision it changes. If the example changes your stake, stop-loss, review queue or next study block, write it cleanly in the log.
How to apply it
Record the table facts before the memory softens: stake, format, stack depth, position, relevant reads and any hand context worth reviewing. Then use the term as a label for the spot, not as a story about whether the session felt good. For Stack, the practical question is whether the label changes a bankroll, session or study decision. If it does not change a decision, it belongs in a note, not in the headline read.
In Overshove, game context belongs in the session fields, hand notes and player notebook. Tag it plainly, then review by cluster: all 3-bet pots, all deep-stack spots, all hands against the same player type, not one isolated memory. Use the same spelling every time, then link it back to effective stack so the page, calculator or guide beside the term does useful work.
Common mistakes
- +Logging only the result and leaving out the game texture.
- +Using a term loosely enough that it stops being searchable.
- +Reviewing a hand without the stack, position or opponent context that made the decision real.
Questions players actually ask
How should I use Stack in a session log?
Use Stack as a decision label, not decoration. Log the raw session first, then attach the term only where it explains a stake, bankroll, variance or study choice you can review later.
What is the common mistake with Stack?
The common mistake is reading the term without the sample and context behind it. In live cash, a clean label still needs stake, hours, stack depth, cost and result data before it tells you anything reliable.