How to Analyse a CLAT Mock Test: The Error Log Method

The score from a CLAT mock tells you very little. What improves your next score is a written error log: for every wrong, skipped or lucky-correct question, you note the section, the cause, and the fix. Done properly this takes 60 to 90 minutes per mock, and it is worth more than taking a second mock the same day.

Step 1: Record the numbers before you look at explanations

Immediately after the mock, write down for each of the five sections: questions attempted, correct, wrong, left blank, and marks (correct minus 0.25 times wrong). Add the minutes you spent, if you tracked them. These numbers are the base for everything else.

Example row, using made-up figures: Legal Reasoning, attempted 26, correct 19, wrong 7, blank 4, marks 19 minus 1.75 equals 17.25.

Step 2: Classify every miss

Go through each wrong or blank question and assign exactly one cause code:

• K: Knowledge gap. I did not know the fact, rule or formula.
• M: Misread. I answered a different question than the one asked (for example, “which weakens” read as “which strengthens”).
• T: Time. I ran out of time or rushed.
• G: Guess that failed. I had no basis, or the elimination was poor.
• R: Reasoning trap. I knew everything but chose a tempting wrong option.
• L: Lucky. I got it right but could not explain why. Count these too.

Only after assigning a code should you read the explanation. If you read first, you will tell yourself you “knew” it.

Step 3: Write a one-line fix for each

A good fix is specific and testable:

• K: add the fact to a one-page notes list, or add the formula to a formula card.
• M: underline the question stem’s key word before looking at options.
• T: set a maximum of 90 seconds per question and skip beyond that.
• G: practise eliminating two options before choosing.
• R: write down why the tempting option fails, in one sentence.

Step 4: Count the codes

After three mocks, tally the codes by section. You will almost always see a pattern. Maybe 60 percent of your Logical Reasoning errors are M, or most of your Current Affairs errors are K from the same months. Your study hours should go where the biggest code cluster is, not where you feel least comfortable.

Step 5: Track attempts and accuracy together

For each section compute accuracy as correct divided by attempted. If accuracy is under about 60 percent, you are probably attempting too much in that section; the marks lost to negative marking are explained in our guide on how many questions to attempt. If accuracy is above 90 percent and many questions are blank, you may be too cautious, so lower your skip threshold.

Step 6: Redo, do not re-read

Two days later, attempt your wrong and blank questions again from scratch. A question you still miss goes onto a “stubborn list” that you revisit every few days. This is more effective than re-reading explanations, which feels productive but often is not.

Step 7: Review passage selection and timing

Passage-based papers let you choose where to spend time. Look at which passages you attempted first, which ones you skipped, and whether the skipped ones were actually harder. Often a “hard” passage had two quick questions you could have gained. Compare with the time plan in our guide on time management.

A simple template

1. Date, mock number, total marks.
2. Section table: attempted, correct, wrong, blank, marks, minutes.
3. List: question number, section, code, one-line fix.
4. Three habits to change before the next mock.

Keep it in a notebook or a spreadsheet, whichever you will actually use.

How many mocks do you need?

Quality of analysis matters more than quantity. In a five-week window, one full mock with full analysis every three to four days is enough for most people, supplemented by sectional practice. Our 5-week plan shows where they fit.

What your mock should provide

Choose papers with an answer key and a short explanation for each question, since the explanation is what lets you assign codes accurately. For example, Lexfolio’s four-paper pack (Rs 149) states an answer key, a section-wise analysis table and a short explanation for each question; the three-test online series (Rs 99) offers on-screen timed tests with explanations and instant scores. Neither is the only way to do this: the method works with any mock.

A worked example of one log entry

Suppose, in a mock, you got a Legal Reasoning question wrong. The passage said that a person is liable only for harms that a reasonable person would have foreseen, and the facts described a freak accident. You chose “liable” because the victim was badly hurt. Your code is R, a reasoning trap: you let sympathy decide instead of the rule in the passage. Your one-line fix is “State the rule first, then ask whether the facts meet it, before reading options.” That is a habit you can test in your next mock.

Mistakes people make when analysing

• Spending the whole time on questions they got wrong because of knowledge gaps and ignoring careless errors, which are cheaper to fix.
• Reading the explanation and nodding. If you cannot reconstruct the reasoning without looking, you have not learned it.
• Comparing scores between different mocks as though they are equally hard. Look at your accuracy and error codes instead.
• Skipping the lucky-correct category, which hides weak topics.