How to Analyse Your Mock Test Results and Find Your Weak Areas

The short answer: look past the total. Compute attempts, accuracy and net score, see where the time went, sort every error by cause and topic and pick one or two changes for the next mock. A mock you analyse this way teaches more than three you only score.

Why the total score is not enough

A drop of ten marks could mean a weak topic, slow pacing, careless errors or a harder paper. Each needs a different fix. The total cannot tell them apart, so the analysis has to go one level deeper. For the review of individual questions see how to review incorrect questions; this guide is about the whole-paper picture.

The one-page results sheet

After each mock, fill a small table. An illustrative example for a 100-question paper with +1 and −0.25 marking:

Accuracy is correct ÷ attempted; net score is correct − 0.25 × wrong. Reading the table: quantitative has the lowest attempts (22 of 35) and took the most time (45 minutes), so the problem there is pacing, not only knowledge. Reasoning is the strongest section. English has decent attempts, but 8 wrong answers cost 2 marks of penalty plus the marks not earned. Ten minutes were left unused, which suggests that a few minutes could have gone to quantitative.

Accuracy and attempts tell different stories

• High accuracy, low attempts: you are too slow or too cautious. Raise attempts using a time ceiling.
• Low accuracy, high attempts: you are guessing or rushing. Tighten your guess policy.
• Both low: concept gaps; go back to the topics.

See accuracy vs attempts for how to find the break-even point for your marking scheme.

Read the time, not only the score

Most exam engines show time spent. Questions that took far longer than average, even if correct, cost marks elsewhere. List the five slowest questions and ask whether they were worth it. This is where a ceiling per question comes from: see section-wise time management.

Sort errors by topic and by cause

Group every wrong, guessed and unattempted question by topic and chapter, and tag each with a cause: concept gap, fact or formula not remembered, misreading, calculation slip, time pressure or bad guess. You will usually find that a small number of topics cause a large share of the losses. Fix those first. Incorrect and unattempted answers are different signals: incorrect suggests a concept error or a slip, while unattempted suggests a knowledge gap or a time problem.

Look for repeated mistakes

One mistake is noise; the same mistake in three tests is a pattern. Keep an error log and read it before each new mock.

Track the trend

Write one number per mock in a simple table: net score, accuracy, questions not reached or weak-topic count. The trend matters more than any single result. If three mocks pass with no change, see how to break a plateau.

Turn the analysis into a plan

1. Choose the biggest cause of lost marks (pacing, a topic or a habit).
2. Pick one change for the next mock and write it on your rough sheet.
3. Schedule a topic repair and a retest within a week. See how to revise after a mock test.
4. After the next mock, check whether the number you targeted moved.

Common mistakes

• Reading only the total.
• Analysing without acting.
• Changing many things at once.
• Comparing raw scores across tests of different difficulty.

Put the method to work on a practice test or a free mock test.