Use these pages as prompts for calmer hand review, not as certainty claims. The aim is a repeatable note habit, clearer table thinking, and safer study boundaries.
The template I can actually finish
My one-hand template is built around one idea: capture enough detail to review the decision, but not so much that the note becomes a chore. I have tried long forms with dozens of fields, and they usually fail after a few sessions. The shorter version lasts because it respects attention. A finished simple note beats an unfinished perfect form.
The entry begins with table context. I write date, format, position, stack depth in rough terms, number of players in the hand, and any read that truly mattered. I do not add every tiny observation. If a player had shown several loose calls, that belongs. If a player wore a funny avatar, it probably does not. The point is to preserve decision context, not decorate the entry.
Then I write the action street by street. I keep it neutral. No excuses, no story, no verdict. The hand history should read like a camera: action before me, my action, response, next card, next action. When I stay neutral in this section, the later analysis becomes cleaner.
Field one: the decision point
Every note needs one main decision point. If I try to review the whole hand at once, I often drift. The decision point might be a preflop call, a flop raise, a turn barrel, a river bluff catch, or a missed value bet. I mark it with a question: what was I trying to accomplish here? That question slows me down and turns the entry from a replay into a study task.
A good decision point includes alternatives. I write the option I chose and at least two options I considered. If I only write the choice I made, I will usually defend it. When I write the alternatives, I can compare them honestly. Check behind, bet small, bet large, fold, call, raise, delay, or choose a different sizing: each option reveals a plan.
I also note what information I used. Was I reacting to board texture, position, stack depth, blocker effects, previous action, timing, or a player tendency? If I cannot name the information, the decision may have been autopilot. That is not a disaster; it is exactly the kind of thing a journal should reveal.
Field two: range thoughts
Range notes do not need to be exact. I start with broad categories: strong made hands, medium showdown hands, draws, missed draws, traps, floats, and hands that may fold to pressure. The purpose is not to produce a solver output. The purpose is to check whether my table thought was coherent. Did my action target worse hands? Did it fold out enough better hands? Did I ignore a category that should have mattered?
I write my range assumption in present tense from the table: I think villain has many top-pair hands, I think the check-raise is value-heavy, I think the river completes enough draws to reduce bluff frequency. Later, I can challenge that assumption. Writing it in the original frame helps me see how I reasoned when time was short.
If the range section feels too hard, I use a simple sentence: the hands I expected to continue were blank, and the hands I expected to fold were blank. That one sentence exposes many weak plans. If I cannot fill it out, my bet or call may not have had a clear purpose.
Field three: emotion and tempo
I include a small emotion and tempo field because many mistakes are not technical at first. They start as hurry, irritation, boredom, fear of being bluffed, or desire to recover from an earlier spot. I do not need a diary entry. I need one honest note about state. Calm, rushed, tilted, distracted, tired, too confident, or curious is enough.
Tempo matters because autopilot often hides inside speed. If I clicked within seconds on a close river spot, I mark fast decision. If I tanked but never formed a range, I mark long but unclear. Both are useful. The problem is not speed by itself; the problem is acting without a plan.
This field also stops me from pretending that every leak is a knowledge gap. Sometimes I know the better process but fail to use it. The journal then gives me a behavioral target: pause on paired rivers, write ranges before big calls, or stop adding tables when note quality collapses.
Field four: one next-session cue
The final field is the most important: one next-session cue. It must be concrete. Watch cutoff opens versus button calls. Pause before river bluff catches. Do not fire turn barrels on bad cards without naming target folds. Look for thin value against sticky pairs. These cues translate review into table behavior.
I avoid giant goals. Play better from position is too vague. Review every river is too large. A cue should fit on a sticky note. If I can read it before opening a table and remember it during a hand, it is the right size.
After the next session, I check whether the cue appeared. If it did, I write what happened. If it did not, I keep it for one more session or replace it with a more relevant theme. The cycle stays small, which is why it survives.