How to Keep an IMAT Mock Exam Error Log That Works

Most people review a mock exam, feel briefly bad about the questions they missed, and move on to the next one. That review teaches you something real, but only about that single sitting.

A mock exam error log is a running record, kept the same way after every mock, of what you got wrong and why. Four fields are enough: date, section, topic, and the actual reason (content gap, careless error, misread, or ran out of time). Kept consistently, it's what tells you whether a mistake is a one-off slip or the fourth appearance of a gap you keep not fixing - something a single review can never show you on its own.

A single review only shows you one data point

Reviewing one mock catches what happened that day: a topic you blanked on, a section where the clock beat you, a question you second-guessed into the wrong answer. All useful, but all isolated. Without a record that carries forward, every mock resets to zero. You relearn the same lesson about pacing or the same weak topic three or four times over, because nothing is tracking that it's the same lesson each time.

What actually belongs in the log

Skip the tally of right versus wrong, your score already tells you that. What's worth recording for each missed question is the topic, the section it fell under, and the actual reason you got it wrong: a content gap, a misread question, running low on time, or a careless slip you'd fix on a second look. That last column, the reason, is what turns a list of wrong answers into something you can actually act on.

The pattern that only shows up after three or four mocks

This is the same instinct behind tracking your IMAT progress over months rather than by feeling - a log just applies that same discipline at the level of individual wrong answers instead of section scores.

One mock might show two chemistry mistakes and one physics mistake, and that looks like noise. Log the same categories across four mocks and a topic that keeps resurfacing, titration calculations, say, or a specific type of data interpretation question, stops looking like bad luck. It starts looking like a gap that needs dedicated review, not just another round of general practice. That distinction only becomes visible once you have more than one data point to compare.

Keep it simple enough to actually maintain

A log with too many columns gets abandoned by the third mock, usually right when it would start becoming useful. Four fields are enough: date, section, topic, and reason. The value doesn't come from how detailed any single entry is, it comes from doing it the same way, every mock, without fail. A simple log you actually keep beats a detailed one you stop updating after two weeks. It pairs naturally with a proper mock review process - the log is just where that review's findings actually accumulate instead of disappearing after each mock.

A mock exam error log isn't extra work bolted onto your prep, it's what makes the prep you're already doing more precise. One review tells you what went wrong once. A log kept consistently across every mock tells you what's actually worth fixing.