How to Analyse a Mock Test: A 30-Minute Review That Actually Raises Your Score
Taking mocks does not raise scores; reviewing them does. A step-by-step 30-minute review for SSC, bank and railway mocks, with a simple error log.
Updated 27 October 2026· 7 min read
Most aspirants take a mock, look at the score, feel good or bad, and take the next one. Scores rise slowly that way, if at all. The marks are hidden in the review. A good review takes about 30 minutes and should happen the same day.
Step 1: Look at the score last
Start with the sections, not the total. For each section, write down three numbers: attempts, accuracy and time spent. A total score of 140 can hide a section that is costing you 20 marks.
Step 2: Sort every wrong answer into one of four types
| Type | What it looks like | What fixes it |
|---|---|---|
| Concept gap | You did not know how to solve it | Study the topic, then 20 practice questions |
| Silly mistake | You knew it, but misread or miscalculated | Slow down on the last step; underline what is asked |
| Rushed guess | Answered in a few seconds without real elimination | Follow a guessing rule (see our negative marking guide) |
| Time pressure | Answered in the last minute of the section | Better question selection earlier in the section |
Count each type. If silly mistakes are your biggest group, more study will not help; slower checking will.
Step 3: Find your time sinks
List the five questions that took you longest. For each one, ask: was it worth it? A question that took 3 minutes and was answered correctly still cost you about four other questions' worth of time in a 15-minute SSC section.
Step 4: Re-solve the skipped questions without a timer
Some skipped questions will turn out to be easy. These are the cheapest marks you have: you already know how to get them, you just did not see it in the exam. Note the question types, so you attempt them next time.
Step 5: Pick just two fixes
Do not try to fix everything. Pick the two changes worth the most marks, write them down, and focus on them before the next mock. Examples:
- "Do the reading passage last in IBPS English."
- "Practise 15 percentage questions a day this week."
- "In Quant, skip any question I cannot start within 15 seconds."
Step 6: Keep an error log
A notebook or a sheet with five columns is enough: date, exam, topic, error type, and the fix. After five mocks, the log shows your patterns: the topics you keep missing and the mistakes you keep repeating.
How many mocks, and how often?
Quality beats quantity. Two or three full mocks a week, each followed by a proper review, is better than one every day with no review. In the last month before the exam, take mocks at the same time as your exam shift.
Let the report do the counting
RankVyuh does Steps 1 to 3 for you. Every mock report shows section-wise attempts, accuracy and time, flags rushed answers and time sinks, and lists the fixes worth the most marks. After five full mocks, it shows the patterns across tests. Your part is the thinking: Steps 4 to 6.
Take a free SSC CGL mock, or try IBPS PO or RRB NTPC.
Frequently asked questions
How long should I spend analysing a mock test?
About 30 minutes for a full mock, on the same day. Focus on sections, error types and time sinks, then pick two fixes for the next mock.
How many mock tests should I take before the exam?
Two or three full mocks a week with a proper review is a good pace. In the final month, take them at the same time as your exam shift.