How to Build a JEE Mistake Log That Actually Stops Repeat Errors
Part of How to Analyse JEE Mock Tests: The Complete Guide to Using Tests Properly.
Every JEE student makes mistakes. The students who improve are the ones who stop making the same ones. That difference is almost entirely a habit: writing mistakes down and looking at them again.
This post is part of our guide to analysing JEE mock tests. It covers what goes into a mistake log, how I handle a question I cannot solve, and how often to review.
Short answer
- Record every wrong question and every calculation error. Circle it, store it, and note why it went wrong.
- Cap your attempt on a hard question at 5 to 10 minutes. Then learn from a well-explained solution.
- Re-attempt after one week, then after one month.
- Review old mistakes daily or regularly. A log you never open is decoration.
- Aim to be the student who does not repeat the same mistake, not the one who never makes any.
Why a log beats “I will remember”
You will not remember. Mistakes feel memorable in the moment, but a week later you only recall the ones that hurt most. A written log shows patterns you cannot see from memory: the same sign error in kinematics, the same misread in permutation questions, the same organic step you keep skipping.
I mention this in one of my short videos on first-attempt errors. Not maintaining a revision booklet of your mistakes is one of the five that I list, along with too few mocks and over-relying on only important chapters by weightage.
What to record
Keep each entry short. Four fields are enough.
| Field | Example prompt |
|---|---|
| Question source | Test name, book, or PYQ year |
| What went wrong | Concept gap, execution, silly error, or time |
| Correct approach | A few lines, not a full solution copy |
| Re-attempt dates | One week, one month, ticked when done |
You can add a fifth field, “trigger”, meaning what in the question should have told you the right method. That is the field that builds real pattern recognition.
The method for a question you cannot solve
This is the sequence I follow and recommend.
- Analyse the question. Which chapter, which topic.
- List the formulas you associate with that topic, mentally.
- Note the key given data. For example, a value of electric field or magnetic field in a physics problem.
- Decide which concept fits and solve step by step. Give it five to seven minutes of fully focused effort.
- If it is still unsolved, study the solution and absorb it. Do not just read, memorise the approach.
- Log it, then re-attempt after a week and after a month.
In another video I frame the time cap slightly differently: give a stuck question at most 5 to 10 minutes, not one or two hours. Use the first 2 or 3 minutes to recall concepts and formulas. If nothing clicks, go to a clear solution and note how the author approached it. Solved examples in a good book are the best teacher at this point. If you use a heavy book for this, see how to use Cengage for JEE Advanced for how to structure it, and consider whether a very hard book like Irodov belongs in your plan with is Irodov worth it.
Review schedule
A log works only if you return to it. A simple schedule:
- Daily: skim yesterday’s new entries and ask why each happened.
- One week later: re-attempt the question from scratch, without looking at the solution.
- One month later: attempt it again. If it still fails, it stays in the log.
- Before each test: read the top repeating mistakes, not everything.
If you want to connect this to your wider revision routine, how to revise for JEE shows where it fits.
Group mistakes by type
After a few weeks, sort your entries into types. You will usually find three or four patterns that cause most losses.
- Concept gaps: fix with theory and solved examples.
- Execution errors: fix with more questions of that type.
- Silly mistakes: fix with checks. See silly mistakes in JEE.
- Time losses: fix with skipping rules and timed practice.
This is the same cause-tagging I use in test analysis. It stops you from fixing the wrong problem.
Plug one leak at a time
I use a metaphor for this. Your score is a pot of marks, and each subject is a thief stealing from it. Electromagnetism takes some, organic chemistry takes some. You do not tackle all of them at once. You build a defence against one, then the next. The mistake log is your list of thefts. Look at which chapter shows up most, and build a defence there first. If your total feels stuck, why mock scores stop improving explains the wider picture.
What the log can do for your marks
In one video I said that if you stop repeating mistakes, a very high Advanced score becomes possible, enough, in my words, for a good branch in a top IIT. That is my claim, not a rule, and I also said it is simple advice that is hard to implement. The log is how you implement it. Be disciplined. Do not aim to never make errors, aim to never make the same one twice.
Connect it to PYQs
Previous-year questions are a rich source of log entries because they reflect the real exam. When one goes wrong, log it with the year and the reason. See how to solve JEE PYQs for how to use them without wasting them.
Common mistakes with the log itself
- Copying full solutions. Keep entries short or you will stop writing.
- Logging only big errors and ignoring small ones.
- Never reviewing it.
- Logging without a cause tag.
- Skipping the re-attempt, which is the part that proves you learned it.
FAQ
Should the log be digital or a notebook? Whichever you will actually open. I would not tell you one is better without knowing your habits.
How many mistakes should I log per test? All the wrong and skipped ones that matter. If that is too many, log the ones that repeat or cost the most marks.
What if I fail the one-week re-attempt? Study the solution again and re-attempt in a week. Keep it in the log until you solve it cleanly.
Do I log right answers? Log the ones you got right by guessing or with a shaky method.
How does the log help in the last weeks before the exam? It becomes your most personal revision material. Read your top repeating mistakes before each test.
Related reading
- Complete guide to analysing JEE mock tests
- Why mock test scores are not improving
- How to solve JEE PYQs
- Silly mistakes in JEE
- How to revise for JEE
- Is Irodov worth it?
Need help with your own plan?
If you feel you are drifting off track and want an IIT student to review your mistake patterns with you, check our mentorship page. Explore JEEcompass mentorship
Want a plan built around your own gaps? Join the next webinar.