How to analyse a JEE mock test
A score tells you how a mock went. It does not tell you why. The marks you can still win are in the analysis, and most students spend too little time on it, or spend it on the wrong thing.
Why the score is not the analysis
Two students can both score 140 in a mock. One lost marks because three chapters are weak. The other knew the chapters, then rushed the last twenty questions. They need opposite advice, and the score cannot tell them apart. Analysis is the work of finding out which student you are, and it is worth doing carefully on one mock rather than quickly on five.
Step 1: List every question that cost you marks
Do not stop at the wrong answers. Make one list with four kinds of entry:
- Wrong answers, because they cost marks directly.
- Skipped questions, because skipping is a decision and sometimes a mistake.
- Right answers you guessed, because you got lucky and the gap is still there.
- Right answers that took far too long, because the time they used came out of other questions.
Step 2: Ask what you were thinking, before you look at the solution
This is the step most people skip. Reading the solution first makes it feel as if you would have got it, and you lose the evidence of what actually happened. For each question on your list, try to recall or reconstruct your own reasoning: what you took the question to be asking, which method you reached for, and where you stopped being sure. Write one honest line. “I assumed the acceleration was constant” is useful. “Silly mistake” is not.
Step 3: Name the cause
A wrong answer can have very different causes, and each one is fixed in a different way. A useful set to sort into:
| Cause | What it sounds like | What helps |
|---|---|---|
| Conceptual gap | “I didn’t know how this works.” | Go back to the idea, then try fresh problems on it. |
| Wrong assumption | “I assumed something that wasn’t true here.” | Write the condition a method needs before using it. |
| Misread question | “I answered a slightly different question.” | Underline what is asked and the key condition before solving. |
| Weak strategy | “I should have skipped it, or started elsewhere.” | Practise choosing and ordering questions, not only solving. |
| Careless calculation | “I knew it, then dropped a sign or a factor.” | A calculation routine, covered in our guide to silly mistakes. |
| Poor time management | “I ran out of time or rushed the end.” | Time targets per section, and a rule for when to move on. |
Sometimes more than one cause applies. Pick the one that, if it had not happened, would have given you the marks.
Step 4: Look across mocks, not inside one
One mock gives you a guess. Several give you a pattern. After three or four mocks, put your causes side by side. A single chapter that keeps appearing is a conceptual gap you have not closed. The same cause across different chapters, for example misreading or rushing, is a habit, and no amount of extra revision of content will fix a habit. This is where most of the value is, and it is the part that is hard to do by memory alone, because every mock feels like a fresh story.
Step 5: Choose one thing to do next
Finish with a single, specific action for the coming week, not a long list. “Rotational motion: rebuild the idea of friction on rolling bodies, then do ten problems” is something you can do. “Revise Physics” is not. At the next mock, check first whether that one thing moved.
Don’t forget the time analysis
Look at how long you spent per section and where the time went. Marks lost to the last fifteen minutes usually started in the first hour: a few questions that took three times as long as they should have. Note the questions where you were stuck for a long time and what you did about it.
How often, and how long
Give a mock a proper review while it is fresh, ideally within a day. A careful review takes real time, and a rushed review of several mocks tells you less than a careful review of one. Keep your notes in one place so the pattern across mocks stays visible.
Where JEE AI Mentor fits
JEE AI Mentor does Steps 2 to 5 with you. After you submit a mock it asks what you were thinking, helps you name the cause, and keeps that record, so the pattern across mocks is built for you instead of from memory. It can be wrong, so check important points against your books and teachers. You can do this method with a notebook; the tool just makes it easier to keep up.
Common questions
How many mocks should I analyse?
Analyse every mock you take, but do each one properly. A careful review of one mock is worth more than a quick look at several. Patterns become reliable after three or four mocks.
Should I analyse questions I got right?
Only the ones you guessed or that took far too long. Those show gaps that the score hides.
What if I do not remember what I was thinking?
Reconstruct it as best you can before reading the solution. If you cannot, note that too, because not being able to explain your own answer is itself useful information.
See the pattern across your own mocks
JEE AI Mentor reads each mock you submit, asks what you were thinking, and keeps a record of the causes behind your mistakes so the pattern shows up over time. It is a study aid, not a promise of any rank or score.
Create a free account