Building a mistake log you will actually re-read

Every list of topper advice has "maintain an error notebook" on it, and almost every error notebook dies within three weeks. It dies because copying a wrong question into a book is slow, boring, and produces nothing you ever re-read. A mistake log is only worth keeping if it is quick to write and useful to read. Two rules get you there.

Rule 1: log the cause, not the question

Do not copy the question. Copy the line where you went wrong, and why. A dead entry is a fully transcribed projectile problem with the correct solution underneath. You will never read it again. A live entry looks like this:

Projectile on an incline. Took g perpendicular to the incline instead of resolving it. Cause: reused the flat-ground formula without checking the axes.

Twenty seconds to write, and it names a habit rather than an incident. Six weeks later it is still legible to you.

Rule 2: tag every entry with one of four causes

Almost every wrong answer in JEE is one of:

• Knowledge — you did not know, or could not recall, the result.
• Setup — wrong frame, wrong axes, wrong sign convention, wrong limits.
• Execution — right method, broken algebra or arithmetic.
• Reading — you answered a question that was not asked.

Tagging takes a second and turns the notebook into data. After fifty entries, count the tags. The distribution tells you what to do next, and it is usually not what you assumed. Mostly Knowledge means your revision is too passive. Go back to recall-first revision. Mostly Setup means you are pattern-matching to remembered solutions instead of reading the physical situation. Slow down on the first thirty seconds of each question and draw. Mostly Execution is the bucket students dismiss as silly mistakes. It is not silly — it is the largest single source of lost marks in JEE Main, and it responds to timed practice rather than to more theory. Mostly Reading means you are rushing the stem. Underline what is being asked before you start solving.

Reviewing it

Once a week, read only that week's entries and pick the two causes that repeat. Before a mock, read the Setup and Reading entries — those are the ones that recur under time pressure. Knowledge gaps you will catch anyway when you revise the chapter. The notebook should stay thin. If it is growing faster than you can re-read it, you have started transcribing questions again.