How to Review Missed AMC Problems

A full solution can make a hard problem look obvious after the fact. Before reading it, students should write down what they tried, where they got stuck, and what they thought the key obstacle was.

That short reflection preserves the learning signal. It shows whether the miss came from a missing concept, a weak setup, a bad assumption, or a computation issue.

Useful categories include careless error, reading error, concept gap, slow method, skipped case, and problem-selection mistake. One problem can have more than one label, but one primary cause should be chosen.

Patterns across labels matter more than any single problem. If careless errors dominate, the student needs checking routines. If concept gaps dominate, they need targeted topic practice.

After studying a solution, students should close it and write the shortest complete explanation they can. This forces them to reconstruct the idea instead of copying the surface steps.

The rewritten solution should include why the main move was reasonable. For example, not just that a variable was introduced, but what made that variable useful.

A missed problem is not finished when the solution makes sense. Students should retry it later without notes, usually after a few days.

If the retry fails in the same place, the issue was not fixed. That problem should become part of a small review queue until the method is genuinely repeatable.

The next practice session should respond to the review log. A student missing geometry diagram work should not jump randomly into number theory; they should practice related geometry moves while the lesson is fresh.

This is where adaptive practice helps: the review process identifies the next useful difficulty and topic instead of treating every missed problem equally.