The Error Log Habit That Separates 700 Scorers From Everyone Else

What an Error Log Is (and What It Isn't)

An error log is not a list of questions you got wrong. Anyone can make that list. An error log is a structured post-mortem on every mistake — what the question asked, what you were thinking, why you got it wrong, and what the correct approach was.

The distinction matters enormously. A list of wrong questions is inert data. An error log is a learning system.

Here's what a proper error log entry contains:

The "what you were thinking" field is the one most people skip. It's also the most important. If you only write down the correct approach, you're studying the answer. If you write down your wrong reasoning first, you're studying your actual mistake — which is the thing you need to fix.

Why Most Students Skip It

Two reasons: it's slow, and it feels like going backwards.

After getting a question wrong, your instinct is to check the explanation, nod at the correct approach, and move on. Logging the error takes another five minutes. Multiply by 20 questions in a practice session and suddenly you've added an hour to your study day.

But here's what those students don't realise: they are about to get the same question wrong again in three weeks. Not that exact question — but the same type of mistake, the same cognitive trap, the same miscalculation. Because they never confronted the root cause of the error.

The error log forces you to stop and do that confrontation while the question is still fresh.

The Four Error Types

Categorising your errors is what makes the system powerful. Here's the taxonomy:

Concept gap — You didn't know the rule or formula. Fix: go back to fundamentals before doing more practice on this topic.

Careless mistake — You knew the concept but made an arithmetic error, misread the question, or forgot to check your units. Fix: identify your specific careless habits (always misread "at least"? always drop the negative sign?) and build a mental checklist you run before confirming each answer.

Time pressure — You knew the approach but ran out of time and guessed. Fix: timed drills on this question type, not more untimed practice. The problem is execution speed, not understanding.

Trap answer — The test-maker set a trap and you walked into it. Fix: study the trap itself. What was the wrong-but-tempting answer? Why was it designed to attract you? Learning the specific trap mechanics makes you immune next time.

How Frequently to Review

This is where most error log users underperform. They log their errors diligently and then never open the log again.

The review schedule that actually works:

Reviewing old errors at the start of each session also serves as a warm-up. You enter the new practice session primed on material you've already studied, not cold.

Why 50 Logged Errors Beat 200 New Questions

Here is the uncomfortable truth: doing more practice questions feels like progress but often isn't.

If you do 200 practice questions without reviewing them properly, you are mostly reinforcing your existing patterns — including your wrong ones. The student who does 50 questions, logs every error, and revisits those 50 errors three times over the course of prep will outperform the student who does 200 questions with superficial review.

This is not a theoretical claim. It's what consistently separates students who improve quickly from students who plateau.

The exam is not testing content you don't know. It's testing whether you've eliminated the errors you're prone to. The only way to eliminate errors is to study them directly.

Using the Error Log in myExamRoutine

The error log in myExamRoutine is in the Tracker tab. Here's how to use it well:

Log after every practice session, not just mock tests. The error log is most valuable when entries are fresh — when you can still reconstruct why you made the choice you made. If you wait until the weekend to log errors from Tuesday's practice session, you've lost the most important data: your actual thinking process.

Use question IDs consistently. If you're working from official practice materials, use the question numbers. If you're using GMAT Club, use the GC problem numbers. The ID means nothing in isolation — what matters is that you can find the original question when you review the entry two weeks later.

Give it two weeks before judging it. The pattern-detection benefit of the error log doesn't appear immediately. After two weeks of consistent logging, you will be able to see recurring themes: always losing points on rate problems involving two workers, always misreading CR inference questions as strengthen questions, always forgetting to flip the sign when multiplying an inequality by a negative. Those patterns are the most valuable study insight you can have — and they're invisible without the log.

The error log is not an extra thing to do alongside your prep. It is the prep.