How to Analyse a JEE Mock Test (Error Log)

A mock test gives you a number, but the number is the least useful part. The real value is in the two or three hours after the test, when you work out why you lost marks. Students who improve steadily usually spend as long analysing a test as they spent taking it.

Step 1: Check the score, then put it away

Note your total, your score in each subject and how many questions you attempted. Then stop looking at it. Comparing raw scores across tests of different difficulty is misleading; the patterns in your mistakes are what matter.

Step 2: Sort every lost mark into a bucket

Go through every question you got wrong and every question you skipped. Put each into one bucket:

Didn’t know the concept. You couldn’t have solved it without studying something new.
Knew it, couldn’t apply it. You recognised the topic but got stuck setting it up.
Silly mistake. Misread the question, sign error, unit slip, wrong option bubbled.
Time ran out / skipped wisely. You didn’t reach it, or chose to leave it.

Count the buckets. If most losses are silly mistakes, more theory won’t help; slower reading and a final check will. If most are concept gaps, the test is pointing you to chapters to revisit.

Step 3: Re-attempt before you read the solution

For each “knew it, couldn’t apply it” question, try again with no time limit and no solution. Only after a genuine attempt should you check the explanation. This step converts a mistake into learning; reading the solution first converts it into a feeling of understanding that fades by next week.

Step 4: Audit your question selection

With JEE Main marking (+4 / −1), choosing which questions to attempt is a skill. Look at:

Questions you attempted and got wrong: were they guesses? Four wrong guesses cancel one correct answer.
Questions you skipped but could solve easily during the review: that is lost time management, not lost knowledge.
The order you attempted subjects in, and where you spent too long on a single question.

A simple rule many students find useful: if you have no clear approach after a minute or so, mark the question and move on. Come back only if time remains.

Step 5: Update your error log and your plan

Write the important mistakes into your error log with the reason and the fix. Then change next week’s plan: add a revision session for the weakest chapter, or practise 20 questions on the topic where application keeps failing.

Step 6: Re-test the same weakness

A week later, take a set of fresh questions on the chapters you flagged. If the same mistakes appear, the fix didn’t work; try a different approach (another explanation, more worked examples, or a doubt session).

How often should you take full mocks?

Early in your preparation, chapter-level tests are more useful than full papers. As the exam gets closer, increase full-length mocks, but never so often that you have no time left to analyse them. One analysed mock is worth more than three that you only scored.

Doing this on Nit Bro

After each Mock Test, the result screen shows your subject-wise score and lets you filter the review to Incorrect or Skipped questions. Re-attempt those in Practice (filter by the same chapter), ask Ask BRO for hints only when you’re stuck, and watch your accuracy trend on your Profile.