How to keep an error log for NEET PG, and what to do with it

An error log is a running list of questions you got wrong, with one line on why, one line on the fix and a tag for the cause. Keep it short enough that you will actually write it, and review it on a schedule, because the review is where the value is. Done well, the log becomes your personal syllabus: the specific things you, and not the average candidate, keep missing.

Why bother with an error log at all?

Right answers mostly confirm what you know. Wrong answers are the only part of a practice set that tells you something new, and they are cheap to find now and expensive to find in the exam. Without a record, the same slip returns three weeks later and feels like a surprise each time.

There is also a plain logistical reason. By the third month of preparation you will have attempted thousands of questions. You cannot reread them all, but you can reread a few hundred lines about the ones that went wrong. If the idea is new to you, our post your wrong answers are the real syllabus makes the case in more detail. This post is the practical version: the format, the habit and the review.

What should one entry contain?

Four things, in a line or two:

• The topic. Specific enough to find again: "nerve supply, muscles of mastication", not "anatomy".
• What happened. Not the full question text, but the trap. "Picked the common cause, the stem pointed to the rarer one."
• The fix. The fact or rule, in your own words, small enough to say aloud in ten seconds.
• The cause tag. One of a short list, below.

That is all. If an entry takes more than a minute, it will not survive a tired Thursday night after a ward shift. You can write it on paper, in a notes app or in a spreadsheet; what matters is that it is in one place and that you can search or sort it.

What cause tags should I use?

Tags are what turn a list into a diagnosis. Keep them few and keep them honest. A set many candidates find workable:

Tag guesses even when you got them right. A lucky guess is a gap that has not cost you yet.

Be strict about the first two. Most people over-tag "slip" because it is flattering. If you keep repeating a "slip" on the same topic, it is a gap.

When should I write the entries?

Write them while the explanation is fresh, at the end of each set, not at the end of the week. A reasonable routine: attempt a set, then spend about as long on the review as on the questions. For each wrong answer, read the explanation for every option, including the ones you rejected correctly, then write the entry.

You will also need a rule for what counts. Log every wrong answer, every guess and every question you got right for a wrong reason. Do not log everything you feel lukewarm about; that is how logs bloat and get abandoned. If a set produces more entries than you can write in the time you have, log the first ones and tag the rest in bulk as "not logged". Honest incompleteness beats a perfect habit you quit in week two.

NextPrep's question bank gives an explanation for every option, and tells you why each wrong choice is wrong, which makes the "what happened" line easier to write. Our questions are original, and review by named faculty is still being built, so if an explanation seems wrong to you, report it from the question and cross-check with your standard textbook.

How should I organise the log?

Two layouts work, and you can use both.

By date. Simple and fast. Each set ends with entries at the bottom of a running list. This is the capture layer.

By subject and topic. Once a week, copy or tag entries so you can see them grouped. This is the review layer, and it is where patterns show up. If your tool allows filters, you only need one list and a tag column for subject.

Add one more column: next review date. When you add an entry, set it to a few days ahead. When you review, move it further out if you got it right and bring it closer if you did not. That is a hand-made spaced schedule, and it is the same idea that spaced repetition explained for NEET PG describes.

What do I do with the log each week?

This is the part people skip. Block thirty to sixty minutes at a fixed time, and do four things:

1. Count by tag. How many gaps, slips, two-ways, traps? The proportion tells you what to fix. Mostly gaps means you need more content passes. Mostly slips and two-ways means your knowledge is fine but your reading and discrimination need work.
2. Count by subject. Which subject and which topic recur? Small counts mislead, so look for the same topic appearing three or four times, not one stray miss.
3. Convert entries into cards. Anything you could not say aloud becomes a flashcard. Our guide to making flashcards for NEET PG shows what a good card looks like, and the flashcards page has decks you can review on a schedule.
4. Retest. Pull a handful of questions on the recurring topics from the question bank and see whether the fix held.

At the end of the session, cross out entries that have been correct on two retests. They are finished. A log that only grows is a list of worries; a log that also shrinks is a map of progress.

How do I spot patterns that cost marks?

Patterns are easier to see once you have fifty or so entries, though there is no magic number. Look for:

• Same-topic repeats. The strongest signal. Make a short note or one-page table for that topic and revise it before the next set.
• Qualifier misses. Words like "most likely", "next best step", "except" and "not" cause slips. If these keep appearing, change how you read: read the last line of the stem first, then the whole stem.
• Look-alike pairs. Two conditions, two drugs or two organisms you keep swapping. Write the single discriminating feature and put it where you will see it.
• Subject-specific style problems. Calculation errors in PSM, image misreads in anatomy or pathology, dose and interaction confusion in pharmacology. Each needs its own drill.
• Late-set errors. If your error rate rises in the second half of a long set, that is a stamina or time problem, not a knowledge problem. How to sit a long paper addresses it.

Resist concluding too much from a small number of questions. A single bad day produces a cluster that looks like a weakness and is not one. Look again the following week before you rearrange your plan.

How does the log fit with mock tests?

A mock is just a big set, and the log handles it the same way, with one addition: tag the questions you left for later and the ones you changed your answer on. After the test, ask whether changed answers helped or hurt you. Do this over several mocks before drawing a conclusion, as one test proves little. For the review routine after a disappointing score, see after a bad mock, and for how many mocks to take, how many mock tests for NEET PG. The timed tests page shows what is available for practising under the clock.

What mistakes do people make with error logs?

• Copying the question and explanation. It takes five minutes, produces a textbook-sized pile and teaches nothing. Write the trap and the fix.
• Never reviewing. A log nobody reads is a diary.
• Logging only the topic. "Pharmacology, anti-epileptics" tells you nothing. Log what went wrong.
• Tagging everything as a slip. Be honest about gaps.
• Starting a beautiful system and quitting. Start with a plain page and one rule: every wrong answer gets one line.
• Using recalled exam questions as a source. They are unofficial and unreliable, and NextPrep does not use them. Learn from questions with explanations you can trust and verify, and see previous year papers: what they are.

Common questions

How many entries should I write per day?

As many as your wrong answers produce, within the time you have for review. If that is too many, the real issue is usually that you are attempting more questions than you can digest. Cut the volume of questions a little and keep the quality of review; our post on how many MCQs a day discusses the trade-off.

Paper, spreadsheet or app?

Whichever you will actually open. Paper is fast and tactile but hard to sort. A spreadsheet is easy to filter and count. A notes app is fine if you tag consistently. Pick one and keep it for the whole preparation so you never have to merge two systems.

Should I log questions I got right?

Only when you got them right for the wrong reason: a guess, a hunch, or elimination you could not justify. Those are gaps that have not cost you yet. Do not log every correct answer or the log will drown.

How long does the weekly review take?

Thirty to sixty minutes is a reasonable range for most people, though it depends on how many entries you have. The smaller the log is kept, the more likely you are to do it. If review runs long every week, tighten your entries and retire the ones you have retested successfully.

Can the log replace my notes?

It can replace a lot of them, since it holds exactly the points that need attention. You will still want your skeleton notes for subjects you are learning for the first time. Think of the log as the layer that sits on top: it records where your notes failed to stick. See notes you will actually reopen.

What should I do next?

Start today with a plain page. After your next set of questions, write one line for each wrong answer: topic, trap, fix, cause tag. Set a fixed weekly slot for review and convert the recurring entries into cards. If you want a starting set to practise on, take the free assessment and log what it surfaces. Exam details change, so confirm the current pattern in the official NBEMS bulletin.