A Complete Chess Game Analysis Checklist

This checklist is part of the chess tools collection. Use it during a focused game review session so that every conclusion becomes a reusable lesson rather than an engine score.

1. Save the complete game context

Record:

moves or PGN;
colors and result;
time control;
clock times at critical moments;
opening or starting position;
tournament or casual context; and
notes about thoughts, confidence, and distractions.

Context explains why a move happened. A difficult choice made with 20 seconds left requires different training from the same error made with 20 minutes.

2. Replay without an engine

Move through the game at a board and pause where you remember choosing between moves. Do not request an evaluation yet.

At each pause, write:

what the opponent threatened;
candidate moves considered;
the main line calculated;
expected evaluation; and
reason for the move played.

This preserves your decision process before the engine's answer changes your memory.

3. Mark the critical moments

Choose three to five positions where the game changed. Typical critical moments include:

first unfamiliar opening position;
tactical opportunity;
irreversible pawn move;
queen exchange;
change in king safety;
transition to an endgame;
large use of clock time; or
first serious error.

Do not give every move equal attention. The final blunder may be less instructive than the earlier decision that created the pressure.

4. Check tactical safety

For each critical position, scan both sides' forcing moves:

checks;
captures;
direct threats;
loose and pinned pieces;
overloaded defenders; and
intermediate moves.

If a tactic was missed, identify the motif and the search failure. “Missed fork because I never checked the knight's forcing squares” is more actionable than “do more puzzles.”

5. Compare candidate moves

Generate two or three serious alternatives. For each:

calculate the opponent's best reply;
reach a stable position;
compare material;
compare king safety;
compare piece activity;
inspect pawn structure; and
state a plain-language evaluation.

Give every candidate an equally strong opponent. Do not justify the played move with a cooperative line.

6. Review the opening by ideas

Answer:

Where did known preparation end?
Which pawn break did each side want?
Which piece was misplaced?
Did development match the center?
Was the king secured before lines opened?
Was a move-order difference ignored?

Add one position and plan to the repertoire. Avoid memorizing a long engine line that is unlikely to recur.

7. Review pawn structure and strategy

At the first quiet middlegame position, identify:

pawn chains and bases;
open and semi-open files;
weak pawns and squares;
good and bad minor pieces;
passed-pawn candidates;
each side's freeing break; and
the least active piece.

Then compare the plan played with the demands of the structure.

8. Review king safety

Track the moment each king became safe or vulnerable. Note:

castling decision;
pawn-shield changes;
open lines toward the king;
attacker and defender access;
flight squares; and
missed queen trades or defensive exchanges.

If an attack succeeded, find the first move where it could have been prevented.

9. Review time management

Mark:

long thinks on routine moves;
instant decisions in critical positions;
repeated calculation of the same branch;
time spent remembering theory;
opponent-time-pressure reactions; and
remaining time at the decisive error.

Create a specific rule, such as “generate candidates before every pawn break,” rather than “use time better.”

10. Review the endgame

If the game simplified, ask:

Was the transition favorable?
Which king should have activated first?
Were passed pawns pushed at the correct time?
Did rook placement follow the concrete position?
Was a theoretical technique known?
Did a trade enter a pawn ending with the correct move order?

Save reusable endgame positions as FEN for later practice.

11. Use the engine to verify

Now turn on an engine and test your candidates. For every major disagreement:

play the engine's best defense;
find the tactical or strategic reason;
compare it with your expected line; and
explain the lesson without an evaluation number.

Do not copy a sequence you cannot explain. Lower the depth or simplify the position until the reason is visible.

12. Classify the error

Use a small set of categories:

missed threat;
candidate-generation failure;
calculation or visualization error;
evaluation error;
opening understanding;
strategic plan;
endgame knowledge;
time management; or
emotional decision.

Patterns across games determine the training priority.

13. End with one action

Write:

one thing done well;
one critical position;
one recurring weakness;
one rule for the next game; and
one drill to complete this week.

The action should be measurable: “solve five positions where a defender is pinned and write the full line,” not “improve tactics.”

A compact post-game template

Use this after every serious game:

Result and time control.
First unfamiliar position.
Turning point.
Best decision.
First significant error.
Cause category.
One corrected line.
Next-game rule.
Weekly drill.

Common analysis mistakes

Opening the engine before reconstructing thoughts.
Reviewing only losses.
Treating every engine dip as equally important.
Saving variations without explanations.
Blaming the final blunder instead of the first cause.
Ignoring clock context.
Ending with too many training tasks.

Frequently asked questions

How long should game analysis take?

A rapid game may need 20–45 focused minutes; a serious classical game may need longer. Stop when you have explained the key decisions and selected an action.

Should beginners analyze without an engine?

Yes, first. Then use an engine to verify tactics and challenge conclusions.

How many critical moments should be saved?

Usually three to five. Choose positions with reusable lessons rather than every small evaluation change.

Use FEN to save one position, PGN to preserve the whole game, and a weekly practice plan to schedule the resulting drill.