How to Analyse an MHT CET Mock Test: A Copyable Review Template

A mock-test score tells you what happened in one attempt. A review helps you decide what to do in the next study session. You do not need an elaborate spreadsheet: a notebook and a consistent way to describe mistakes are enough.

If you need a baseline, start with one of MHTCET Simu's two free PCM papers. Full reports are included for both free papers.

Start with the questions, not a target percentile

Record the paper, date, score and whether the attempt was timed and uninterrupted. Also note whether you had seen the solutions before. Comparing a fresh attempt with a familiar paper can make progress look larger than it is.

Review wrong answers, unanswered questions and correct answers that were guesses. Do not treat all unanswered questions as the same problem: a chapter you have never studied requires a different next step from a familiar question you never reached.

Keep raw marks separate from percentile estimates. This review method does not convert a mock score into an official percentile or predict a college seat.

Give each mistake one main cause

Use these five labels as a starting point:

• Concept: You could not explain why the method works, or chose the wrong principle.
• Recall: You understood the idea but could not retrieve a required formula, fact or reaction.
• Calculation: Your setup was sound, but arithmetic, algebra or a unit conversion went wrong.
• Reading: You missed a condition, sign, unit or part of the question.
• Time: You knew a viable method but did not complete it within the attempt.

Add “not studied yet” separately when appropriate. When more than one label fits, choose the earliest failure in your reasoning. If the setup was wrong before the arithmetic began, start with the concept rather than blaming the calculation.

These are suggested manual labels. They are not a claim that the simulator automatically diagnoses every cause.

Copy this review template

Use one entry per question worth revisiting:

• Paper and attempt date:
• Question number:
• Subject and chapter:
• Outcome: wrong / unanswered / correct guess / correct but slow:
• Main cause:
• The exact step where I went wrong:
• Correct method in my own words:
• One repair task:
• Date for a fresh check:
• Fresh-check result:

For example, a fictional entry might read: “Physics; Current Electricity; wrong; concept; I added parallel resistances directly; redraw the circuit and explain which voltage is shared; solve three new parallel-circuit questions tomorrow.”

The valuable part is the exact failed step. “Revise Current Electricity” is too broad to tell you whether the repair is complete.

Choose the next task from the error

For a concept gap, return to the explanation and work through an example without copying each step. Then try a fresh question that tests the same idea.

For recall, write a short prompt rather than another page of notes. Try retrieving the answer later before looking it up.

For calculation, redo the original working line by line and identify the specific operation. Practise that operation in another question; simply rereading the final solution may not expose the habit.

For reading errors, underline the condition you missed and write what it changes. For time pressure, try a fresh question with the same method and a timer, while keeping accuracy visible.

Use your textbook, class material or another reliable practice source for these checks. MHTCET Simu's targeted practice modes are an optional paid route, not a requirement for using this template.

Pick a small number of priorities

Choose two or three repair tasks you can complete before your next full paper. Give priority to repeated errors in chapters you have already studied, while reserving separate time for unfinished syllabus coverage.

Do not rank a chapter as “fixed” after one correct answer or as “hopeless” after one mistake. A few fresh questions provide a better check than rereading one familiar solution.

Our chapter pages can help you explore the available subject and chapter breakdowns. Historical question patterns are context, not a guarantee of what a future paper will contain.

Close the loop with a fresh check

After completing a repair task, attempt fresh questions before looking at the solutions. Record whether the same error recurred and whether your method was clearer.

If you retake an identical question, mark it as a repeat. Remembering the answer can be useful for revision, but it is weaker evidence of transfer to an unfamiliar question.

When you take another full paper, compare your review notes as well as the score. Fewer reading errors, a correct circuit setup or fewer unfinished familiar questions can tell you what changed even when paper difficulty differs.

A practical review session

Here is a suggested session structure, not an exam rule:

1. Spend a few minutes recording the attempt conditions and overall result.
2. Review a manageable batch of wrong, unanswered and guessed questions.
3. Write the exact failure and one repair task for each.
4. Select two or three tasks for your next study sessions.
5. Set a fresh-check date before closing the report.

If the paper contains too many errors to review carefully in one sitting, split the review across sessions. Do not replace understanding with copying a long list of solutions.

Take a free baseline paper or read how to use previous-year questions.