How should candidates analyse VARC and quants in mocks to lift scores from 60s into the 90s?
Lifting mock scores from the 60s to the 90s requires a shift from answer-checking to method-auditing in Quants and from speed-chasing to comprehension-first diagnosis in VARC. Both sections need structured post-mock analysis, not just a tally of correct answers.
Quants: Method Over Outcome
Most candidates stop at "right or wrong," but 90+%ile scorers audit the method on every question. Even when you arrive at the correct answer, ask whether you used the fastest approach or brute-forced through algebra.
If a question on Time-Speed-Distance took four minutes because you set up simultaneous equations, note that a ratio shortcut would have saved two minutes for another attempt elsewhere.
Track three categories in your error log: conceptual gaps (you didn't know the formula), method inefficiency (correct answer, slow route), and silly mistakes (calculation errors under time pressure). The second category is invisible if you only check final answers.
From Reddit, we learnt that candidates who colour-code these three buckets in a spreadsheet often spot patterns within three mocks, like repeatedly missing percentage-to-fraction conversions or over-relying on algebra when ratios suffice.
VARC: Comprehension Before Speed
VARC improvement begins with untimed re-reads. After the mock, return to passages you answered and re-read them without the clock. Can you now articulate the author's main argument in one sentence? If not, speed was never the issue; comprehension was. Only when you can consistently grasp passage structure in an untimed setting should you layer on pace drills.
For Reading Comprehension, map each paragraph's role: is it introducing a counterargument, providing evidence, or offering a conclusion? Inference questions punish surface reading, so practice distinguishing what the passage states versus what it implies.
For Verbal Ability, track error types in a table
| Error Type | Count | Fix |
|---|---|---|
| Para-jumbles (transition words missed) | 5 | Drill connectors (however, thus, moreover) |
| Odd-one-out (theme drift unnoticed) | 3 | Underline topic sentence in each option |
| Summary questions (detail vs. big picture) | 4 | Write one-line passage gist before options |
The 30+ Per Section Benchmark
Competitive profiles for IIM Ahmedabad, IIM Bangalore, and IIM Calcutta typically require 30+ raw marks per section to clear sectional cutoffs at 99+%ile. That means 10-12 accurate attempts in Quants and 12-14 in VARC, assuming high accuracy.
Use the compare colleges tool to check whether your target schools weigh sectional balance heavily; some newer IIMs accept a 28-32 split, while older IIMs penalise lopsided scores.
Iterative Mock Cycles
Run mocks in three-test cycles: take Mock 1, analyse for two days using the method above, then apply fixes in Mock 2. If the same error type reappears, dedicate a full day to that topic before Mock 3.
This beats the common trap of taking seven mocks in seven days with no reflection. You can predict your percentile after each cycle to track whether method changes translate to score gains.
Pro Tip: After every mock, solve five questions you got wrong under no time limit the next morning; if you still can't crack them untimed, the gap is conceptual, not speed-related, and requires a topic reset before the next attempt.