The Error Log: Turning Every Mistake Into a Fixed Weakness

A wrong answer, marked and moved past, teaches you almost nothing on its own. The value in a mistake only appears when you look at it closely enough to understand why it happened — and it multiplies further when you can see it sitting next to five other mistakes that share the same root cause. Most students never get that second view, because the wrong answers from last month's test are gone, forgotten, replaced by this month's new set.

An error log is simply a single running record of every mistake you make across practice questions, mock tests and homework, written down in enough detail to spot the pattern. It turns your own mistakes — usually the most wasted resource in a student's preparation — into the most personalised study material you will ever have.

What actually goes in the log

Every entry should capture four things briefly: the topic, a short description of the question, what went wrong, and the specific fix. Skip questions you got right, and skip trivial slips you immediately recognise and will not repeat — the log is for mistakes worth remembering, not a record of every pen stroke.

• Topic and sub-topic — precise enough to find it again quickly.
• What the question actually asked, in a line or two.
• The specific cause: knowledge gap, misread question, wrong formula, slow method, calculation slip.
• The exact fix: what you will do differently next time.

Sorting mistakes by cause, not by subject

Most students file mistakes only by subject — "Chemistry mistakes", "Maths mistakes" — which hides the deeper pattern. The more useful sort is by cause: knowledge gaps across all subjects in one section, careless misreads in another, timing pressure in a third. Looked at this way, you often discover that your real weakness is not any one topic but one recurring habit, like rushing the first line of a question.

How often to review the log

A log that is written but never re-read has almost no value beyond the moment it was written. Set a fixed, recurring time — for instance, every Sunday evening — to read through the whole log so far, and specifically look for any cause that keeps reappearing across different topics or tests.

1. Add new entries the same day you make the mistake, while the reason is still fresh.
2. Review the whole log weekly, scanning for repeated causes.
3. Before every mock test and the real exam, do a final full read-through.

A worked example of a log entry

A well-written entry looks something like this: "Topic: Organic Chemistry, nomenclature. Question asked for the IUPAC name of a branched compound. Mistake: numbered the longest chain from the wrong end, missing the lowest-locant rule. Cause: knowledge gap in the numbering rule, not a careless error. Fix: re-read the numbering rules section, then do ten practice nomenclature questions specifically testing chain-numbering direction."

Notice how specific the fix is — not "study organic chemistry more" but a named rule and a named number of targeted practice questions. That specificity is what makes the log actionable rather than just a list of regrets.

Using the log to plan revision, not just record it

As the log grows, let it directly shape your revision schedule. If three of your last ten entries all trace back to one particular topic or one particular habit, that topic or habit earns a dedicated revision slot before anything else — the log has effectively told you exactly where your remaining preparation time will pay off the most.

Frequently asked questions