TestGuru
Mock Tests

How to analyse a mock test so the next one goes better

A mock test only improves your score if you learn something from it. This is a simple, repeatable way to review one: sort every lost mark by its cause, log it, and check later that the fix held.

TestGuru editorial team Updated 9 October 2026 6 min read

In shortReview every question you got wrong, skipped or guessed, and sort each into one of four causes: careless slip, concept error, time or strategy, or didn’t know. Log each one with the specific fix. Spend at least as long reviewing as you spent taking the test, and re-test the same ideas a few weeks later to see whether the fix held.

Most students check their score, glance at the solutions for a few questions and move on to the next mock. That wastes most of the test. The score tells you where you stand. The review tells you what to change, and that is the part that moves the next score.

Here is a review method that works for JEE, NEET or any other objective exam. It needs a notebook or a spreadsheet and some honesty.

When should you review a mock test?

Start the same day, or the next day at the latest. You need to remember what you were thinking during the paper: why you skipped a question, why you picked one option over another, where you felt rushed. That memory fades within a day or two.

Block time for it. A good rule is to spend at least as long reviewing as you spent taking the test. For a 3-hour paper, that is three hours of review, which you can split over two sittings.

Which questions should you review?

Not just the wrong ones. Go through four groups:

  1. Wrong answers. Each one cost you marks; in JEE Main and NEET, a wrong answer costs −1 on top of the +4 you missed.
  2. Skipped questions. Was skipping the right call, or did you skip something you could have done?
  3. Correct guesses. A lucky correct answer hides a gap just as well as a wrong one.
  4. Correct but slow. If a question took twice as long as it should have, it cost you time you needed elsewhere.

How do you sort your mistakes?

This is the core of the method. For every question in those four groups, decide why you lost marks or time. Use four categories.

1. Careless

You knew how to do it and slipped. A sign error, a dropped factor, a misread unit, picking (b) when you meant (c), not reading “NOT” in the question.

Test: if you redo the question now without help and get it right in a reasonable time, it was probably careless.

2. Concept

You had the wrong idea, or an incomplete one. You applied a formula outside the conditions where it holds, mixed up two similar ideas, or reasoned confidently towards a wrong answer.

Test: if you redo it and get the same wrong answer, or you cannot explain why the correct answer is correct, it is a concept error.

3. Time or strategy

You could have done it, but the paper got in the way. You ran out of time, spent eight minutes on one question, attempted questions in a bad order, or left an easy question for the end and never reached it.

Test: if you can solve it comfortably now with no pressure, and the problem was when or how long, it belongs here.

4. Didn’t know

You had not covered the topic, or you had forgotten it completely.

Test: if you would need to go back to the textbook or notes to even start, it is a didn’t-know.

Some questions sit in two groups. Pick the one that, if fixed, would have saved the marks.

What should an error log look like?

Keep one running log for all your tests. A simple table is enough:

DateTestQSubject and topicCauseWhat exactly went wrongFixRe-test date

The two columns that matter most are “what exactly went wrong” and “fix”. Be specific.

  • Weak: “Rotational motion, concept.”
  • Useful: “Used the moment of inertia about the centre when the axis was at the edge. Fix: always check which axis before choosing I.”

The specific version is something you can act on and check later. The vague version is not.

What do you do with each category?

Each cause needs a different fix. Treating them all the same is why many students keep losing marks in the same places.

CauseWhat it usually needs
CarelessA process change: write units, re-read the question stem before marking, check signs at one fixed step
ConceptGo back to the specific idea, rebuild it, then do a few fresh questions on exactly that idea
Time or strategyChange how you run the paper: rounds, skip rules, subject order. Then practise that plan
Didn’t knowAdd the topic to your study plan, sized by how often it appears in the syllabus and past papers

Count how many marks each category cost you. The biggest category is where your next week should go.

Why re-test the same ideas later?

Fixing an error once is not the same as fixing it for good. It is common to “understand” a correction on the day and make the same mistake three weeks later under time pressure.

So, for each concept error in your log, set a re-test date a few weeks out. On that date, do a fresh question on the same idea, ideally without looking at your notes first. If you get it right, mark it as fixed. If not, it goes back into the log with a note.

Spacing practice out over time, rather than cramming it into one session, is one of the better-supported ideas in learning research, and this is a simple way to build it into your week.

What patterns should you look for across tests?

After four or five reviewed mocks, read your error log from the top. Look for:

  • The same topic turning up more than once
  • The same cause dominating, for example most errors being careless
  • The same kind of slip, for example sign errors in a particular type of calculation
  • Time trouble in the same subject or section

A single error is noise. The same error three times is a pattern, and patterns are worth far more of your time. Our guide to why you make the same mistake twice goes deeper into telling a recurring misunderstanding from a one-off slip.

Can software do some of this for you?

Partly. Sorting errors by cause by hand is slow, and the “why” is the hardest part to judge on your own. TestGuru’s mock test report names the likely idea behind each wrong answer for you, so you can spend your review time on the fixes instead. You still need to do the fixing.

Putting it together

  1. Take the mock under real conditions: full time, no breaks, no phone.
  2. Review the same or next day, for at least as long as the test took.
  3. Go through wrong, skipped, guessed and slow questions.
  4. Sort each into careless, concept, time or didn’t-know.
  5. Log the specific error and the specific fix.
  6. Act on the biggest category first.
  7. Re-test concept errors a few weeks later.

If you are preparing for JEE Main, our JEE Main exam pattern page and JEE Main preparation strategy cover the paper you are reviewing against. If you are preparing for NEET, start with the NEET UG exam pattern.

Sources

TestGuru editorial team. We build mock tests that diagnose every wrong answer, for Indian entrance exams. Facts about an exam are checked against the official notice and dated; if something here is out of date, write to support@testguru.co.

Keep reading

Common questions

How long should I spend analysing a mock test?
At least as long as the test itself. For a 3-hour paper, that means about three hours of review, which can be split across a day or two.
What is an error log?
A running record of every mark you lose in tests and practice, with the topic, the cause and the specific fix. Its value comes from reading it back and spotting the same entry turning up again.
Should I review questions I got right?
Review the ones you got right by guessing or with low confidence. A lucky correct answer hides a gap just as much as a wrong one does.
Is it better to take more mocks or review fewer mocks properly?
Reviewing fewer mocks properly is usually better. Taking a test shows you where you stand; the review is where you find out what to change.

Practise in the real exam pattern

Take a free test. Twenty minutes, no card, and the full report at the end — not a teaser.

Free test · ₹1,199 once for the 2027 Pass · 7-day refund