How to Review a Student Chess Game in 15 Minutes

Because the hour-long review does not survive contact with a real teaching week, and because students retain one well-worked moment better than ten covered in passing. A 15-minute review is something a working coach can run for every student, every week. An hour-long deep dive is something that happens once a term, for the keenest student, when nothing else goes wrong.

There is also a confidence cost to the long review that coaches underestimate. A student who sits through sixty minutes of their own errors leaves with a vague sense that they played badly everywhere. A student who works through one mistake, names the concept behind it, and leaves with a drill attached to it walks out with something they can actually fix by Thursday. What engine output means for coaching decisions more broadly is its own topic, and our pillar on engine analysis for chess coaching covers it; this post is only about the review meeting itself.

You run the entire engine pass before the student sits down, so that the 15 minutes of contact time contains zero waiting for analysis. Collect the game as a PGN file, the plain-text standard both major platforms export [3], run it through Stockfish [1], and mark the two or three biggest eval swings. That shortlist is your preparation; you do not need anything else.

Collection is the part most coaches do inefficiently. If your students play on Lichess, their games can be fetched in bulk through the free Lichess API [2] rather than asking each child to email a file. Chess.com games can be exported and imported the same way. Once the PGN is in front of an engine, a full student game analyses in well under the three minutes this step budgets, and a graph of the evaluation over the game makes the big swings visually obvious.

Resist the urge to prepare a lecture during the pre-scan. The marks are candidates, not a syllabus. A blunder that loses a queen to a one-move tactic produces the biggest swing on the graph, but it is often the least teachable moment in the game, because the student already knows exactly what went wrong. The pre-scan finds where the evaluation moved; the next step decides which of those moments is worth the lesson.

Pick the swing the student had the best chance of understanding and avoiding, not the swing with the biggest number next to it. The teachable moment is usually a decision the student made with time on the clock, in a position type they will meet again, where the mistake belongs to a pattern you have seen in their other games.

• Recurring over rare: a mistake you have seen in two or three of their games beats a one-off accident.
• Decision over oversight: a wrong plan teaches more than a missed two-move tactic, which is puzzle homework, not lesson material.
• Within reach: the correct idea should be one the student could plausibly have found at their level.
• Time on the clock: a mistake made with twenty minutes left reveals thinking; a mistake made on increment reveals only time trouble.
• Connected: prefer a moment that links to whatever theme the batch is currently training.

This selection step is also where rating context matters. A student stuck on a plateau tends to produce the same category of eval swing week after week, and picking that recurring category every time is how the plateau breaks; our post on the chess rating plateau goes deeper on reading those patterns across months rather than single games.

Set up the position one move before the chosen moment, ask "what did you see here?", and then stay quiet. The student's recall of their own thinking is the lesson. You are not presenting analysis; you are retrieving the thought process that produced the mistake, because that thought process, not the move itself, is the thing you are trying to change.

Recall-first works for a reason coaches feel intuitively even if they never name it: an explanation a student generates sticks far better than an explanation a student receives. When the child reconstructs what they considered, what they dismissed, and what they never saw at all, the gap in their thinking becomes visible to both of you at the same time. When the coach simply announces the gap, the student nods, agrees, and repeats the mistake a fortnight later. The seven minutes this step gets is mostly silence and short questions, and that is the design, not a failure of preparation.

The phrase to ban from this conversation is "the engine says". Stockfish did its job before the lesson [1]; quoting it during the lesson converts a thinking exercise into an appeal to authority, and students stop reasoning the moment an oracle enters the room. The engine evaluation is the coach's instrument for finding the moment. It is never the argument for why a move was wrong. If you cannot explain the problem with the move in chess terms a student can verify on the board, you picked the wrong moment.

1. 1"What did you see here?" Open with pure recall and let the silence do its work.
2. 2"What was your plan with this move?" Move from perception to intention.
3. 3"What did you think your opponent wanted?" Test whether the opponent's idea was ever considered.
4. 4"If you could take one move back in this area of the game, which one?" Let the student locate the mistake themselves.
5. 5"What would you look for next time you get this kind of position?" Convert the finding into a forward-looking habit.

Minutes 10 to 13 belong to the concept. Once the student has located the mistake, give it a name they can carry out of the room: loose pieces drop off, every check needs a question, the pawn structure decides where to attack. One concept, stated once, connected to where else it has appeared in their games. Naming matters because the student cannot watch for a pattern they cannot say; a named concept becomes a checklist item in their next game, while an unnamed one evaporates by the car park. If the moment you chose resists being named in one phrase, it was probably two ideas, and you should teach the simpler one and save the other.

One line with three parts: the concept, the position reference, and the drill. Something like "Concept: loose pieces. Game: vs Mehta, move 23. Drill: 20 undefended-piece puzzles before Thursday." That single line is the bridge between this review and the next one, and it is the input to the week's homework.

The format earns its keep at the next review, because checking last week's note takes thirty seconds and tells you whether the drill happened and whether the concept showed up in the new games. Turning the note into an actual set of exercises is its own playbook, covered in our guide to building chess homework from games. The free tooling is good here too: the key position can live in a Lichess study the student opens at home [4], and themed follow-up puzzles are available at no cost on the Lichess training pages [5].

A twelve-student batch is three hours of review contact time, which fits one evening, and the pre-scans are batched separately so the evening itself contains no analysis work at all. The method scales precisely because the expensive part, the engine pass and the moment selection, happens in one concentrated block the day before.

The batching workflow looks like this: collect every student's most recent serious game the day before, either through the Lichess API [2] or platform exports as PGN files [3], run the engine pass on all of them in one sitting, and mark candidate moments as you go. Twelve pre-scans take well under an hour once the collection is automatic, because you are reading evaluation graphs, not playing through games move by move. On the evening itself, students rotate through in 15-minute slots while the rest of the batch plays training games or works on puzzles.

Two things break the system at scale, and both are discipline failures rather than method failures. The first is skipping the note at minute 13 because the conversation was going well; without the note there is no homework and no continuity, and the review becomes a pleasant chat. The second is letting a review drift to 25 minutes because the game was interesting; every overrun is borrowed from the last student in the queue, who is usually the one who most needs the attention. The clock is part of the method.