Note-taking

Building an Error Log That Changes Practice

An error log is useful when it records a cause and a next action.

An error log is useful when it records a cause and a next action. A catalogue of wrong answers can become discouraging or repetitive if it never changes the way you practice.

Choose what to capture

Record the task, the first wrong step or missing idea, the correction, and a follow-up problem. Keep entries concise and group recurring causes. Distinguish conceptual misunderstanding, method selection, instruction reading, and execution. These categories help choose a repair, but they should remain flexible enough to describe what actually happened in the work.

Build notes you can use

If you repeatedly confuse percentage change with percentage points, add one comparison example and explain the denominator used in each calculation. Then solve a fresh item later. If the same error persists, revise the explanation or seek help rather than copying it again into the log. A successful entry eventually becomes less prominent because independent performance improves, not because the notebook has acquired a more elaborate color code or an impressive number of pages.

Turn capture into learning

Avoid logging every trivial slip with equal effort. Prioritize patterns and errors that reveal missing knowledge or affect important tasks. Do not label yourself careless when the specific problem can be identified. Return to a few entries regularly so the log functions as a practice plan rather than an archive you never reopen.

Put it into practice

Try it in your next study session

  1. Use a topic that matters to you and create three entries with cause, correction, and a follow-up item.
  2. Test the items after a delay and retire or redesign entries according to whether the correction transfers to new work.
  3. Return to the follow-up items before rereading their log entries. If the correction works, reduce attention to that entry and prioritize a persistent pattern. If it fails, inspect whether the stated cause was accurate. A more detailed log is not the solution when the original diagnosis targeted the wrong part of the task.
Take this with youMake each logged error lead to a specific repair and a later opportunity to demonstrate that the repair worked.

Sources & further reading

Practical examples and exercises are original StudyMaster learning activities. Read about our editorial approach.

Open your reading list →

Keep your curiosity going

A few more useful ideas.

More in note-taking →