UGC NET Paper 1: Turn Mock Mistakes into Progress

Start with the decision you made

A mock-test score tells you where you finished; it does not explain why you lost marks. Before reading the explanation for a missed question, write down what you thought the question asked and why your chosen option seemed reasonable. This keeps review focused on your decision rather than recognition of the correct answer.

Include correct answers you guessed. A lucky choice can hide the same knowledge gap as an incorrect answer. Mark it as uncertain so your next study session does not treat it as a mastered topic.

Give each mistake a useful category

Separate a missing concept from a misread instruction. If you did not know the underlying idea, revise it and explain it in your own words. If you knew it but missed a qualifier such as “not” or “most appropriate”, practise checking the wording before selecting an option.

For a calculation or data question, identify the exact step that failed: choosing the base for a percentage, converting a unit, copying a value, or interpreting the result. “Careless mistake” is too broad to tell you what to do differently.

• Knowledge gap: the idea or method was unfamiliar.
• Interpretation error: the question, passage or chart was misunderstood.
• Execution error: the method was right but a step went wrong.
• Timing decision: too much time was spent on one uncertain item.

Re-solve before trusting the explanation

Cover the stored answer and work through the question again. For reasoning, check that the proposed rule fits every given condition. For a passage, locate the wording that supports the choice. For data interpretation, state what each number represents before doing arithmetic.

If the key and your solution disagree, examine assumptions and option wording. Disagreement alone does not prove an error. If the question appears ambiguous or an option seems absent, use the report control with a short explanation of the conflict. Keep that item out of your personal list of settled rules until the issue is resolved.

Choose the next session from your error log

Group mistakes by topic and cause. Repeated errors in the same method deserve focused work; one isolated slip may only need a checking habit. Choose one or two priorities rather than revising every topic after each mock.

Make an error-log entry short enough to revisit: topic, why you missed it, the corrected reasoning and one action for next time. For example: “Percentage change: used the final value as the base; label the starting value before calculating.” The action should describe a behaviour you can practise.

Test understanding on unfamiliar questions

A familiar question can feel easier because you remember its answer. When it reappears, explain the reasoning without looking at the options, then check whether you could apply the same idea to a different example. Do not use a higher score on a heavily repeated set as your only evidence of progress.

After focused revision, take another timed practice test and compare the causes of your mistakes. Fewer guessed answers, better completion and more reliable explanations matter alongside the total. Keep a steady review routine rather than taking several mocks in a row without learning from them.