0
Answered
How long should mock analysis take relative to the mock itself?
I take a 2-hour mock but barely spend 30 min analysing. People say analysis should take longer than the mock. How do you structure a deep analysis session?
1 Reply
0
✓ Accepted answer
Most people under-analyze because they don't have a structured process. A good analysis session is 3–4× the mock duration: for a 2-hour mock, plan 6–8 hours spread over 2 days.
Day 1 (~2 hours) — the attempted questions:
Go through every question you attempted, right and wrong. For wrong answers: identify the exact error — concept gap, calculation slip, misread, or time-panic guess? Tag each one. For right answers: flag any you solved by elimination or instinct rather than clean reasoning. These are 'lucky rights' — fragile under pressure. Don't look up explanations yet; try each wrong question again cold first.
Day 2 (~4 hours) — the unattempted questions:
Work through every question you skipped, untimed, with full solution focus. Compare your fresh-attempt time vs the time available in the mock: this tells you which skips were correct calls vs abandonment. Now read the official explanation for every wrong question, including the lucky rights.
What to log: not just 'got it wrong' but topic, question type, error category, and what you'll do differently. The log becomes your pre-exam revision sheet.
The meta-habit: spend 10 minutes at the end of each analysis session noting 2–3 specific changes to test in the next mock. Iterate explicitly, not by vibe. Improvement compounds faster when each mock has a stated hypothesis.