The review is where the score actually moves, and a full mock deserves at least as much review time as the test took, sometimes more. Here's how I'd run it.
First, don't review while you're fried. A full Focus mock runs over two hours, and you won't think clearly right after it. Rest, then come back to the review with a fresh head.
Second, review your correct answers, not just the wrong ones. This is the step almost everyone skips. Flag every question you got right but felt unsure about, guessed on, or took too long to solve. A correct answer built on a shaky reason is a wrong answer waiting to happen on a slightly different version of the question, so treat those the same as outright misses.
Third, for each question you missed, redo it yourself from scratch before you read any explanation. Cover the answer, give yourself unlimited time, and try to solve it cleanly. What happens next tells you a lot. If you can now get it, the issue was likely pressure, a misread, or a careless slip. If you still can't, you've found a real content gap. You learn far more from wrestling with the question yourself than from passively reading someone else's solution.
Fourth, diagnose the actual reason you missed it. Put every wrong answer into one of these buckets:
- Concept or formula gap: you didn't know the underlying content.
- Misread or misunderstanding: you knew the content but misread the question or set it up wrong.
- Careless error: you knew it and the approach, but slipped on execution.
- Trap answer: you got lured into a choice the test engineered to look right.
- Process or timing: your method was inefficient, or you rushed because you were behind pace.
Be honest in this step. The most common self-deception is labeling a miss "careless" when it was really a gap. If you truly understood it, you'd have gotten it. Careless means you'd reliably get it right nine times out of ten and just slipped once.
Fifth, log it. Keep a simple
error log recording each missed question's topic and the reason you missed it. One test tells you a little. The log across several tests tells you everything, because when the same topic or the same error type keeps showing up, that's your priority list handed to you.
Sixth, close the loop on the content, not just the question. A missed question is one instance of a weakness. Go back to that whole topic, relearn it properly, and drill it until your untimed accuracy is high. Then, a few days later, redo the original question from scratch to confirm the fix actually stuck.
One more layer worth tracking is your timing and focus. Note where your time drained, where your attention slipped, and which sections felt shakiest. Those patterns shape your test-day strategy as much as the content review does.
Do this consistently after every mock and the tests stop being just scores. They become the engine of your improvement.
This article covers how to build and use an
error log, which is the backbone of this whole process:
GMAT Error Log: Do I Need One?PurvaG
Best way to review wrong answers on GMAT Focus mocks?" "I've been just re-reading the explanation but not sure if that's enough. Do people redo the question from scratch after a few days or just move on?"Best way to review wrong answers on GMAT Focus mocks?" "I've been just re-reading the explanation but not sure if that's enough. Do people redo the question from scratch after a few days or just move on?""I've been just re-reading the explanation but not sure if that's enough. Do people redo the question from scratch after a few days or just move on?"