Quick answer
A mock is useful only if you analyse it. Within 24 hours, go through every wrong, skipped and slow question, label why it went wrong (concept, calculation, misreading, time, guess), re-solve it without the solution, and write the fix in an error log. Use the free tracker below: it stays in your browser, shows your score trend and tells you your most common mistake.
Mock test tracker and error log
1. Log a mock test
2. Log every mistake
Everything stays in this browser on this device. Nothing is sent to us. Download the CSV to keep a copy.
The 5-step analysis method
- Score by subject and accuracy. Note correct, wrong and unattempted for each subject. Accuracy below about 80% means you are guessing or rushing.
- Label every wrong question. Concept gap, calculation error, misread question, ran out of time, wrong guess or silly mistake.
- Re-solve without the solution. Only look at the solution if you are stuck after a real attempt.
- Check the questions you skipped. Could you have solved them? If yes, your problem is selection or time, not knowledge.
- Write one fix per mistake (for example “redo 15 rotational motion PYQs”) and do it before the next mock.
What your mistake pattern means
| Most common reason | What to change |
|---|---|
| Concept gap | Go back to theory and NCERT for those chapters, then PYQs. Do not take more mocks until fixed. |
| Calculation error | Daily timed calculation sets; write steps neatly; check signs and units at the end. |
| Misread question | Underline what is asked and the units before solving; reread the last line. |
| Ran out of time | Do a first pass of easy questions in every subject; cap time per question (about 2–3 minutes). |
| Wrong guess | Answer only when you can eliminate options. Every wrong answer costs a mark. |
| Silly mistake | Slow down on easy questions; a 10-second recheck of the final step saves marks. |
How often to take mocks
One full mock a week from about four months before the exam, two a week in the last two months, and three a week in the final month, always at your exam shift time. If you cannot analyse a mock properly, skip the next one: analysis is where the marks come from. See the 30, 60 and 90-day plans.
How do I analyse a JEE mock test?
Within a day, go through every wrong, skipped and slow question, label why it went wrong, re-solve it without the solution, and write a specific fix in an error log. Track which reason is most common and work on that first.
Why are my mock scores not improving?
Usually because mocks are taken without analysis, or the same type of mistake repeats. Log your mistakes for three mocks; the most common reason tells you what to change.
Is my data saved on this website?
No. The tracker keeps everything in your own browser on this device. Use the CSV download to keep a copy.