How to Analyze a JEE Mock Test (So Your Score Actually Improves)

Ask a topper how many mocks they took and you will get a number. Ask them how long they spent analyzing each mock and you will understand why they topped. A mock test is not practice — it is data. If you only look at the score, you throw away almost everything the test just told you.

Step 1: Sort every question into four buckets

Go question by question and label each one:

• Correct & confident — your banked strength. Move on.
• Correct but slow or unsure — a hidden risk. You got the marks this time; under pressure you might not. These need concept revision, not more questions.
• Wrong but you knew it — the most painful and most fixable bucket. Was it a calculation slip, a misread question, or a formula recalled wrongly?
• Wrong and no idea — a genuine gap. This is study material for next week, not something to brute-force with more mocks.

Step 2: Look at time, not just correctness

Two students score 60. One spent 40 minutes on 5 questions they never solved; the other never crossed 3 minutes on anything. The second student has a much higher ceiling — they just need better selection. Check where your minutes actually went: the questions that ate 5+ minutes and gave 0 marks are your biggest leaks. Selection discipline — knowing when to leave a question — is worth more marks than most chapters.

Step 3: Find the pattern behind the mistakes

One wrong answer is noise; the same kind of wrong answer across three mocks is a signal. Cluster your errors by concept, not by chapter: "sign errors in electrostatics potential", "limits involving logs", "SN1 vs SN2 confusion". A specific diagnosis turns two hours of vague revision into twenty minutes of targeted fixing.

Step 4: Convert the analysis into next week’s plan

End every analysis session by writing exactly three actions — e.g. "redo rotational motion torque problems", "practice 10 assertion-reason questions in inorganic", "attempt easy questions first next mock". Three, not ten. If your analysis does not change what you do next week, it was not analysis — it was mourning.

This is exactly the loop Mantrana automates: every attempt is broken down by concept, time, and behaviour, and turned into a priority list — so the thirty minutes you would spend building the spreadsheet go into fixing the gaps instead.