Make an error notebook that leads to action

Record the reason, not the whole question

An error log is an organizational tool. For each useful mistake, keep the topic, the decision you made, the correct reasoning and one action to take next. You do not need to copy every line of a question or maintain a perfect notebook.

Separate different kinds of mistakes

Use categories that tell you what to change. These are practical labels, not a diagnosis of ability.

• Knowledge gap: learn or revisit the underlying concept.
• Reading error: identify the condition or instruction you missed.
• Method error: compare your setup with a worked solution.
• Execution error: check units, signs, arithmetic or answer transcription.

Retest the idea in a new form

After correcting the reasoning, try a related question or create a small example. Return to the topic in a later session. A familiar answer on the exact same item is useful feedback, but a new example gives you another way to check understanding. This workflow applies the broader idea of practice with feedback; it is not a validated scoring system.

Sources & further reading