PGN Analysis Checklist: What to Review After Every Game

Use a short game fragment when you practice the checklist. The example below is not meant to be opening theory; it is a compact review sample with a few common decision points: early development, a central break, and a tactical moment.

[Event "Training Review"]
[Site "ChessAnalysis.Pro"]
[Date "2026.07.17"]
[Round "-"]
[White "Review Student"]
[Black "Practice Opponent"]
[Result "*"]

1. d4 d5 2. c4 e6 3. Nc3 Nf6 4. Nf3 Be7
5. Bg5 O-O 6. e3 h6 7. Bh4 b6 8. cxd5 Nxd5
9. Bxe7 Qxe7 10. Nxd5 exd5 11. Rc1 Be6 12. Qa4 c5 *

Paste the PGN into the analyzer, step through the game without engine help once, then turn the engine on and review only the positions where the plan changed. This avoids turning a review session into passive engine watching.

Before turning on engine lines, write down the practical context: time control, color, opening, result, and one sentence about how the game felt. A blitz loss caused by time pressure should not be reviewed the same way as a slow classical game where you had time to calculate.

• • Where did you first feel uncomfortable?
• • Which move did you spend the most time on?
• • Did the result match your impression of the position?

Use the engine to find the biggest changes in evaluation, but do not stop at the number. For each swing, ask what type of decision caused it. Was it a missed tactic, a poor exchange, a pawn weakness, a king safety issue, or a move-order problem?

A useful note looks like this: "Move 18: I traded bishops because it looked simplifying, but after ...Qh4 my king became weak. Theme: check opponent threats before voluntary trades."

A PGN tells the whole story, but a FEN preserves the exact position you need to study. When you find the mistake, copy the FEN into your notes so you can revisit it later without replaying the entire game.

r1bq1rk1/p3bpp1/1p2pn1p/2pp4/Q2P4/2N1PN2/PP3PPP/2R1KB1R w K - 0 13

In this kind of isolated-queen position, ask three questions before checking the engine line:

• • Is the queen active or exposed?
• • Which central pawn break can change the position immediately?
• • Can either side gain time by attacking a piece or forcing a trade?

In the opening, the goal is not to memorize ten engine moves. First find the moment you left a position you understand. Then compare the engine suggestion to normal opening principles: development, center control, king safety, and piece activity.

Add one practical repertoire note, not a full database dump. For example: "Against this setup, develop the bishop before pushing the c-pawn because the knight needs the c3 square."

End each review with a short action list. Good training tasks are specific and testable:

• • Solve five back-rank tactic puzzles.
• • Review rook activity in rook-and-pawn endings.
• • Add one line to your opening notes after move 8.
• • Practice calculating forcing moves before quiet moves.

One position can produce a misleading lesson if you overfit it. After writing the note, compare it with a related position from another game or a training database. If the same idea appears again, the lesson is probably worth keeping.

For example, "develop faster" is too broad. "Do not move the queen twice while the center is unresolved and your king is still in the middle" is narrower and easier to apply.

For more detail on interpreting the score behind a critical position, read the guide on engine evaluations. If the mistake is tactical, continue with the guide on turning blunders into a training plan.

Use this five-line template after each game:

• • Opening note: one position to remember.
• • Biggest evaluation swing: move number and reason.
• • Missed tactic or plan: what you did not see.
• • Endgame note: technique, conversion, or defense.
• • Next training task: one concrete exercise.

This keeps analysis short enough to repeat, but detailed enough to improve future decisions.