How to analyse a NEET mock test in 30 minutes: a protocol and an error log

To analyse a NEET mock test properly in 30 minutes, do four things in order: mark your uncertain answers before checking the key, classify every lost mark by cause, log each fixable error as a specific concept with a re-test date, and convert the tallies into no more than three actions for the coming week. The protocol below fits that into half an hour so you can do it after every single mock, which matters more than doing it perfectly once.

This is the fast, weekly version. For the thinking behind it, including why a raw score is an outcome rather than a diagnosis, read the companion article on reading your NEET mock score. That piece explains what the number means. This one is the routine you run on the paper.

Before you check the key: mark your confidence

The most useful data in a mock is created while you are sitting it. Next to each answer, put a small mark: a tick if you are sure, a question mark if you are unsure, and a cross if you guessed. It takes a second per question and it is the only way to separate real knowledge from luck afterwards.

Without it, a lucky correct guess looks exactly like mastery and the topic never reaches your error log. With it, every question-marked answer gets reviewed whether it was right or wrong.

Minutes 0 to 10: score, then sort every lost mark

Check the key and put every wrong, unattempted and question-marked question into one of five buckets. Be strict. The point of the buckets is that each has a different fix, so a wrong label means a wrong week.

• Concept gap: you did not know the idea, rule or fact. Fix: learn it.
• Recall failure: you had learned it and could not retrieve it. Fix: spaced review, not relearning.
• Careless error: you knew it and slipped, such as a sign, a unit or a misread 'NOT'. Fix: a process check.
• Time loss: you could have solved it but ran out of time or skipped it in a panic. Fix: pacing and question selection.
• Bad guess: you guessed without eliminating options. Fix: a guessing rule.

Minutes 10 to 22: write the error log

An error log is only useful if every entry is specific enough to act on. Write one line per concept gap, recall failure and careless error. Time losses and bad guesses get tallied, not logged individually, because their fix is behavioural.

Use these columns. You can keep them in a notebook or a spreadsheet; the format matters less than the discipline.

• Date and mock name.
• Subject and chapter.
• Concept, as narrowly as possible: 'sign convention for a concave mirror', not 'Ray Optics'.
• Bucket: gap, recall or careless.
• What went wrong, in one sentence, in your own words.
• The correct reasoning, in one or two sentences, written from memory after checking.
• Re-test dates: roughly 3 days and 14 days from today.
• Result of each re-test: pass or fail.

Minutes 22 to 27: count the buckets and find the big one

Add up the marks lost in each bucket, counting 4 marks for an unattempted question and 5 for a wrong one, since a wrong answer also costs the −1 penalty on top of the 4 you missed. This single table tells you where your score is leaking.

Most students expect the concept gap bucket to be the biggest. Often it is not. If careless errors and time losses together cost more than concept gaps, then more content study cannot move your score much, and your week should be spent on process. If recall failures dominate, you are learning but not reviewing.

After five or six mocks, add the tallies together. One mock is noisy. A pattern across six is a diagnosis.

Minutes 27 to 30: choose three actions, no more

Convert the biggest bucket into at most three concrete actions for the week. More than three and none of them will happen. Each action should be something you can tick off.

• Good: 'Relearn electrochemical series applications and do 20 fresh questions on it by Thursday.'
• Good: 'Before marking any Physics answer, check units and sign. Track slips in the next mock.'
• Good: 'Leave any question I cannot narrow to two options. Count guesses in the next mock.'
• Not useful: 'Revise Chemistry.' 'Be more careful.' 'Do more questions.'

The re-test is where the fixing happens

Logging an error does not fix it. Answering it correctly again, cold, days later, does. On each re-test date, cover the answer, redo the question or a fresh one on the same concept, and mark pass or fail. A fail goes back into the log with a new date.

This is spaced retrieval, one of the two learning techniques rated high utility in the most cited review of study methods (Dunlosky et al., 2013, https://doi.org/10.1177/1529100612453266). The spacing matters: a re-test the same evening mostly measures short-term memory. Fresh questions on the concept are better than the same question again, because you may remember the answer rather than the reasoning. The free chapter-wise NEET question bank at lumineet.com/questions has explained distractors for each option, which is useful here: if you chose a wrong option, you can read why that specific option was tempting.

What a good error log looks like after a month

After four weekly mocks, a healthy log has a few dozen entries, most of them re-tested at least once, with the pass rate on second re-tests clearly higher than on first ones. The bucket tallies should also be shifting. If careless errors were your biggest bucket in week one and they are still the biggest in week four, your process fix is not working and needs to change.

This is also the point where tools help. Lumi schedules reviews of individual concepts with the FSRS algorithm, so the re-test dates in your log are handled for you rather than tracked by hand. But the protocol works on paper, and it works only if you run it every time.

Common ways students waste mock analysis

The most common waste is spending the whole review re-solving the hardest question on the paper. It feels productive, and it usually addresses one question worth 4 marks while a pattern costing 30 marks goes unnoticed. Count before you solve.

The second is writing solutions out in full for questions you got wrong through carelessness. You already know how to solve them. What you need is a note of the slip and a check that would have caught it, which takes one line, not a page.

Related on Lumi

• Your NEET mock score is lying to you. Here's how to read it
• What your wrong answers actually reveal about your prep
• Why you score 600 in mocks and 500 in the real NEET
• Silly mistakes in NEET Physics: a taxonomy, and a fix for each