You lose a league game in 40 moves, shake hands, and spend the drive home replaying one position. You know roughly where it went wrong. The question is whether you do anything useful with that knowledge. Most club players either skip the post-mortem altogether or switch on an engine, watch the evaluation bar swing about, and close the laptop having learned nothing they can apply. A proper review is less glamorous and far more effective: half an hour, the same four steps, every time.
Reconstruct what you were thinking. Play through the moves on a real board using your scoresheet, and stop at every position where you spent more than a couple of minutes. Write one line about each: what you wanted to do, what you were afraid of, how much time you had left.
Do this within a day or two of the game, while the memory is still fresh. The point is not accuracy. Your reasoning at the board was probably flawed — that is exactly why it is worth capturing. If you believed your opponent's knight on d5 was pinned when it was not, that false belief is the thing you need to see written down in your own handwriting.
The engine is a fact-checker, not a coach. It comes later.
You cannot analyse forty moves properly, and you do not need to. Look for the moments where the game genuinely changed direction.
Two or three turning points is plenty. Mark fifteen and you will analyse none of them properly.
A single blunder is not a lesson. Once you have your turning points, describe each mistake in plain words, without using the word "blunder". Then put it in a category:
Now do the arithmetic. Go through your last ten long games and tally the categories. If five of them involve a time-trouble error, your training plan is not "study more openings" — it is clock management. If three come from the same opening line, you have found your next study topic without anyone telling you.
The engine can tell you that a move was a mistake. Only your notes can tell you why you played it.
Open the engine once your own notes are written. Start with your turning points rather than clicking to the first moment the evaluation bar moved — that usually just reflects a quiet positional difference you could not have calculated anyway. Ask two questions of each key position: what did the engine prefer, and what idea makes that move work? If the answer is a tactic, solve it yourself before reading the line.
"Stop blundering" is not a goal. It is a wish. A usable goal sounds like this: "Before every capture, I check whether the piece is defended and whether my opponent has a zwischenzug." Or: "Three times a week, fifteen minutes of rook-ending drills."
Give it a deadline of four to six weeks, and keep a single page of notes where you log each game in two or three lines: result, opening, turning point, category. That log becomes the most honest description of your chess you will ever read, and it takes about ninety seconds per game.
Here is how it looks in practice. You lose as White in a Queen's Gambit. Your turning point is move 22, where you played a natural rook move and allowed a knight to land on e4 and win a pawn. Your note says you assumed the pawn was defended. Category: tactical oversight caused by a lazy assumption. Two more games that month show the same habit — you check your own pieces but not your opponent's replies. The goal writes itself.
You do not need to review everything. Blitz is for playing, not for study — the lessons there are thin and the noise is high. Ten long games reviewed properly will teach you more about your own chess than a hundred engine-checked five-minute games. If you work with a coach, bring the log to the lesson; it turns a vague "I keep losing the middlegame" into a specific, fixable problem. Start with your most recent serious game and give it half an hour this week.
Photo: Ri_Ya / Pixabay