How do I actually analyse a mock test so that the next one improves?
Everyone says "analyse your mock" and nobody shows how. What does a useful analysis look like, and how long should it take?
Commons Community Team
1 Oct 2026 Β· 1 min read
Many of you take a mock, check the score, feel something, and move on to the next one. A few of you ask what analysis actually looks like, because "analyse your mock" is advice everyone gives and nobody explains. The difference between a mock that teaches you and one that merely measures you is what you do in the day or two afterwards. What do you look at? A subject-wise score? Every wrong question? How long do you spend on it, and what do you write down? Tell us what has worked for you.
6 answers & replies
Sign in to join the conversation.
[+][β]Commons Mock & PYQ DeskTeamΒ· 19d ago
Think of analysis as sorting every question into a box, because the score hides what happened.
First pass: label each question correct and sure, correct but guessed, or wrong. The middle box matters: it is a lucky mark that may not repeat.
Second pass: for each wrong or guessed item, name the cause.
Cause Fix Concept gap Re-study, then re-solve Recall slip (knew it, forgot it) Add to the revision system Calculation or unit error Slow down, check units Misread the question (NOT, INCORRECT) Underline the keyword Ran out of time Pacing practice Changed a right answer Change only with a reason Count the causes, not the score. The biggest tally is your next priority. Do this while you still remember your thinking, ideally within a day or two.
[+][β]Commons Strategy DeskTeamΒ· 18d ago
If you log in a spreadsheet, one row per question is enough: subject, chapter, result (sure, guess, wrong), cause, time spent. After four or five mocks, sort by chapter and the weak units appear on their own. That is a better revision plan than your gut.
[+][β]Commons Physics DeskTeamΒ· 18d ago
For Physics, add a re-solve step. For each wrong question, close the solution and solve it again from a blank page. Then compare your path with the printed one. The aim is to find the first line where you went wrong: wrong formula, wrong concept, a sign error, or arithmetic.
Make the unit check a habit, because it catches many slips. If your answer for a pendulum came out as , the units inside the root would be , which gives , a frequency and not a time. The correct form is .
Keep one "Physics slips" page of the error types that keep recurring. Reading it before the next mock is more useful than another formula list.
[+][β]Commons Chemistry DeskTeamΒ· 18d ago
Chemistry mistakes split into two types that need different cures: fact misses and reasoning misses. A fact miss is an NCERT line you did not know. A reasoning miss is when you knew the facts but chose the wrong option, often on statement-based or "which is NOT correct" items.
Keep a trap log with a line per mistake: "read INCORRECT as CORRECT", "mixed up oxidising and reducing agent", "forgot the exception". After a few mocks you will see two or three traps that account for most of your losses.
For Organic, take any missed reaction and write the full mechanism or conversion chain on paper. If you cannot, the issue is in the basics, such as electronegativity effects and the stability of intermediates, and not in the question.
[+][β]Commons Biology DeskTeamΒ· 18d ago
For each wrong Biology question, find the exact NCERT line and ask which of three things happened.
- Never read it. Read that section again and mark it.
- Read it but forgot. Put it on the spaced-revision list.
- Read it but confused it with something similar. Make a comparison table.
The third group is a very common source of avoidable losses: Sertoli vs Leydig cells, mitosis vs meiosis phases, cyclic vs non-cyclic photophosphorylation. Tables fix that class of error better than rereading.
Also look at the time cost. Biology is the section where you should be quick. If a few questions swallowed minutes, note what kind they were.
[+][β]Commons Dropper DeskTeamΒ· 18d ago
A trap we see in repeat attempts: analysis that takes longer than the mock. A page of notes per mock is plenty. End every analysis with three actions for the next test, in plain words: "check units on every Physics numerical", "build a comparison table for the cell cycle", "attempt Biology first". At the next mock, check whether you did them.
Without that step, analysis becomes a ritual of self-criticism that changes nothing. Keep the tone neutral. A mock samples one day's performance; it is not a verdict on you.
How do you analyse your mocks? Tell us your format, spreadsheet or notebook, and what you changed after it.
