If you've looked into GMAT® prep, you've probably heard about error logs.
The advice is everywhere. Track your mistakes. Build a spreadsheet. Log every wrong answer. Review it regularly. Watch your score go up.
It sounds right. Tracking your mistakes is a smart instinct. If you don't know what you're getting wrong, how are you supposed to fix it?
But here's the thing. Most error logs don't help. And the reason they don't help isn't that you're using the wrong template or the wrong app. It's that the traditional error log has a structural problem — one that turns a good idea into a system that rarely produces results.
Why Most GMAT® Error Logs Fail
The standard advice is to keep one list of every question you get wrong. Topic, question type, what you did, what the right answer was, what you should do differently next time.
That sounds thorough. But it creates a few problems.
First, the list grows faster than you can review it. Every practice session adds new entries. Within a couple weeks, you have 80 or 100 items on a spreadsheet. When are you going to review all of those? Most people tell themselves they'll come back to it later.
Later usually doesn't come.
Second, lumping every mistake into one list treats all errors as if they're the same thing. They're not.
A misread — you solved for x when the question asked for y — is a completely different problem from not knowing how to approach a mixture problem. The first is a habit issue. The second is a knowledge issue. They need different fixes.
When you combine them in one list, you can't see the patterns. You might have 30 entries that are all variations of the same habit error, and 10 entries that are all different knowledge gaps. But on one list, they all look like "mistakes you need to fix." So you review them the same way — usually by reading the explanation and moving on — and nothing changes.
Third, the traditional error log tends to become a guilt list. A record of everything you got wrong. You open it, feel bad, close it. That's not a review system. That's a demotivation system.
The Two-List System
Instead of one error log, split your mistakes into two separate lists. This is the system we use with students, and it's based on a simple idea: different types of mistakes need different types of fixes.
List 1: Execution Errors (Category A)
Category A mistakes are questions you knew how to do but got wrong anyway.
Misreads. Computation errors. Rushing through a step you understand. Doing math in your head when you should have written it down. Solving for the wrong variable. Eliminating the right answer and talking yourself into a wrong one.
These are not knowledge gaps. You know the material. The problem is that your execution broke down somewhere between knowing what to do and doing it.
The fix for Category A is not more content review. Reading another explanation of how to solve ratio problems won't help if your issue is that you misread the question stem.
The fix is habit change.
List 2: Knowledge Gaps (Category B)
Category B mistakes are questions you didn't know how to do.
Unfamiliar content. A strategy you haven't practiced enough. A question type you've never seen before. A concept you sort of know but can't apply under time pressure.
These are real gaps in your understanding. The fix for Category B is not a habit reminder. A note card that says "read carefully" won't help if you don't know how to approach a permutations problem.
The fix is targeted learning and repetition.
How to Fix Category A Mistakes
Category A is where most score loss happens for students who have been studying for a while. You've learned the content. You've done the practice questions. But you keep losing points on questions you know how to do.
Here's the system.
Find the Pattern
Look at your Category A list across your entire prep — not just one practice session. Look for the single most common cause of missed questions.
Maybe it's misreading the question stem. Maybe it's computation errors when you rush. Maybe it's eliminating the right answer on critical reasoning because the correct answer "doesn't sound right."
Find the one pattern that shows up most often.
Create One Specific Rule
Not "stop making computation mistakes." That's too vague to be actionable.
Something specific. Like: "Check the previous step every time you write a new line on your scratch paper."
Or: "Underline what the question is asking before you start solving."
Or: "Write down why each wrong answer is wrong before eliminating it on critical reasoning."
The rule should be one sentence. It should describe a specific action you can take in the moment — not a general intention to "be more careful."
Remind Yourself Constantly
This is the part most people skip. And it's the part that matters most.
Write your rule on a note card. Put it on your desk. Look at it before every study session. Look at it during every study session.
If you're studying digitally, make it your desktop background. Or a note that stays open on your screen.
The key insight here: most of us need to be reminded more than we need to be taught. You already know what you should be doing. You just need to be reminded to do it.
A lot of students build elaborate error logs with 15 columns and conditional formatting. Those logs look impressive. But if the log doesn't change what you do in the moment — while you're solving a problem — it's not helping.
A note card with one rule, visible during every study session, will outperform a 200-row spreadsheet almost every time.
Track Compliance
After each study session, ask yourself one question: did you execute the new behavior today?
Not "did you try to." Did you actually do it? Did you underline the question stem before solving? Did you check each computation step? Did you write down why each wrong answer was wrong?
Three study sessions in a row of perfect execution is the minimum before moving to the next habit. If you can't string together three sessions, the rule is either too ambitious or the reminder isn't visible enough.
Once a habit becomes automatic — you do it without thinking about it — you can take it off the card and add a new one. But don't rush this. One habit at a time. Build it until it's part of your process.
Update Over Time
Your Category A list will change over time. Early in your prep, misreads might be your biggest issue. Later, it might be talking yourself out of correct answers on critical reasoning. As you fix one pattern, a new one may emerge.
Keep the list current. Remove habits that have become automatic. Add new ones as patterns surface. The note card is a living document, not a one-time setup.
How to Fix Category B Mistakes
Category B mistakes are knowledge gaps. You didn't know how to do the question. The fix is learning and repetition — but the way most people approach it doesn't work either.
Here's what usually happens. You get a question wrong. You read the explanation. You think "oh, got it." You add it to your error log. You tell yourself you'll come back to it.
Most people don't come back to it.
Three weeks later, you see a similar question. You get it wrong again. Same gap. Same confusion. Different day.
Re-Solve Instead of Re-Read
Reading an explanation is passive. It feels like learning. It isn't. You can follow someone else's logic and understand each step without being able to produce that logic yourself.
The fix is to re-solve the problem. Solve it again. From scratch. No looking at the explanation. Pen to paper, work through it, and see if you can get to the right answer.
If you can't, look at the explanation. Figure out where you went wrong. Then solve it again. And again. Until the moment you read the question, you can see the path to the answer.
Pick Five Per Day
Don't try to review your entire Category B list. That's overwhelming and usually doesn't happen.
Pick five problems per day. Five questions you got wrong previously. Re-solve them from scratch at the start of your study session.
Five is small enough to get done. Over a week, that's 25 problems. Over a month, that's 100. That's a lot of repetition on the exact questions that are challenging for you.
This approach is comically straightforward compared to a fancy spreadsheet. But it works because it addresses what builds durable skills: repeated retrieval, not passive review.
Don't Chase Novelty
Your brain is wired to prefer new problems over old ones. Novelty is one of the top pleasure-producing stimuli for human beings. New problems feel productive. Going back to old problems feels like admitting you didn't learn it the first time.
But the students who improve the fastest are the ones who spend less time on new problems and more time re-solving old ones. The repetition is what builds the recognition that makes answers automatic on test day.
If you've been doing hundreds of new practice questions and your score isn't moving, this is probably why. You're building breadth without building depth. Re-solving old questions builds depth.
What to Actually Record
You don't need a 15-column spreadsheet. But you do need to capture some information. Here's what's useful for each list.
For Category A (Execution Errors)
Keep it minimal. The point isn't documentation — it's pattern identification.
- What was the mistake? (one phrase: "misread question stem," "computation error," "eliminated right answer")
- What section? (quant, verbal, data insights)
- What was the fix? (the specific rule you're working on)
That's all you need. You don't need to copy the full question. You don't need to write out the explanation. You need enough to spot the pattern.
Once you've identified the pattern and created your rule, most Category A entries become unnecessary. The note card replaces the log.
For Category B (Knowledge Gaps)
- Question number and source (so you can find it again)
- Topic or concept
- What you didn't know (one sentence: "didn't know how to set up a mixture problem")
- Date you first got it wrong
- Date you re-solved it correctly
- Date you re-solved it correctly again (to confirm retention)
The re-solve dates matter. They tell you whether you've actually closed the gap or just read the explanation and moved on.
A question that you got wrong, re-solved correctly once, and then got wrong again two weeks later is telling you something. You haven't built durable understanding yet. Keep it in the rotation.
Common Error Log Mistakes to Avoid
Over-Engineering the System
The more complex your tracking system, the less likely you are to maintain it. A spreadsheet with conditional formatting, color coding, and pivot tables looks impressive. It also takes time to maintain — time that could go to actual studying.
Start with a piece of paper or a simple notes app. If you outgrow it, upgrade. But don't start with a system that requires more effort to maintain than it produces in value.
Never Reviewing the Log
An error log that you rarely review is just a record of failure. It's not a tool. It's a guilt trap.
If you're going to track mistakes, build in a review rhythm. For Category A, the review is the note card — you see it every session. For Category B, the review is the five-per-day re-solve routine.
If you're not doing either of those things, the log isn't helping.
Tracking Everything Equally
Not every mistake deserves the same attention. A misread on a question you know how to do is worth tracking — it's a pattern you can fix. A question on an obscure topic you've never studied is less useful to log — it's a knowledge gap, and the fix is learning the topic, not logging the error.
Be selective. Track what you can act on.
Confusing Activity with Improvement
Filling out an error log feels productive. Each entry feels like progress. But documentation isn't progress. The progress comes from the fixes — the habit changes for Category A, the re-solving for Category B.
If your log is growing but your practice test scores aren't moving, you're tracking without fixing. That's the most common trap.
How This Connects to Practice Tests
The two-list system works for both daily practice and practice tests. But practice tests add one more layer: timing analysis.
When you take a practice test, the first thing to review isn't which questions you got wrong. It's whether you had enough time to answer every question within your skill set. If you ran out of time on the last five questions — some of which you knew how to do — that's a timing problem, not a knowledge problem. And timing problems mask your real ability.
Our guide on how to review GMAT® practice tests walks through the full three-layer review system: timing first, then the two-list error separation, then question-by-question review.
If you're only using the error log for daily practice, you're missing the bigger picture. Practice tests show you how your habits and knowledge hold up under real conditions. The two-list system works the same way — just with the added layer of timing.
When You're Stuck
If you've been tracking mistakes for weeks and your score isn't moving, there are a few likely explanations.
One: you're tracking Category A but not fixing the habits. The log exists, the pattern is clear, but you haven't built the reminder system or the specific rule. Reading about your mistakes isn't the same as changing the behavior that produces them.
Two: you're tracking Category B but not re-solving. You're logging knowledge gaps and reading explanations, but you're not going back and solving the problems again. Passive review doesn't build durable skills.
Three: you're not addressing timing. If you're rushing through questions you know how to do because you spent too long on questions you didn't, your error log will show a mix of mistakes that looks like a content problem. But the root cause is time management. Our guide on when to let go of a GMAT® question covers this directly.
Four: you might be in a score plateau that needs a system-level change, not just better tracking. Our guide on breaking through a GMAT® score plateau addresses what to do when the usual fixes aren't working.
FAQ
What is a GMAT® error log?
An error log is a system for tracking questions you get wrong during GMAT® prep. Most error logs record the question, your answer, the correct answer, and notes on what went wrong. The traditional version uses one list for all mistakes. We recommend splitting mistakes into two lists — execution errors (Category A) and knowledge gaps (Category B) — because they need different fixes.
Should I use a spreadsheet for my GMAT® error log?
A spreadsheet can work, but it's not necessary. For Category A mistakes, a note card on your desk with one specific rule will outperform a spreadsheet because it reminds you of the fix in the moment. For Category B mistakes, a simple list of question numbers and re-solve dates is enough. The system that works is the one you'll actually maintain.
How many mistakes should I track?
Track every mistake you can act on. But don't treat all mistakes equally. Category A mistakes (execution errors on questions you knew how to do) are higher priority because they represent points you're losing on material you've already mastered. Category B mistakes (knowledge gaps) are important but need a different response — re-solving, not just logging.
How often should I review my error log?
For Category A, the review is continuous — the note card stays visible during every study session. For Category B, review happens daily through the five-per-day re-solve routine. If you're only reviewing your log once a month, you're not getting value from it.
What's the difference between Category A and Category B mistakes?
Category A mistakes are execution errors — questions you knew how to do but got wrong because of misreads, computation errors, rushing, or other habit breakdowns. Category B mistakes are knowledge gaps — questions you didn't know how to do. Category A needs habit change. Category B needs targeted learning and repetition. Combining them in one list makes it hard to see which fix to apply.
Can I use an app for my GMAT® error log?
You can, but keep it simple. The more complex the system, the less likely you are to maintain it. A notes app with two lists (Category A and Category B) works fine. The value comes from the fixes you apply, not the sophistication of the tracking tool.
What if my score isn't improving even with an error log?
If your score isn't moving, check whether you're actually fixing the mistakes you're logging. Tracking without fixing is the most common trap. For Category A, make sure you've created a specific rule and a visible reminder. For Category B, make sure you're re-solving old problems, not just reading explanations. If both systems are in place and your score still isn't moving, you may need a system-level change. Our guide on breaking through a GMAT® score plateau covers what to do.
Want to learn even more?
We cover the two-list mistake tracking system in detail in our podcast series. Isaac explains why the traditional error log is a scourge on the GMAT® community, how to build habit-change systems for execution errors, and why re-solving old problems beats reading explanations every time.
You can listen on Spotify, on Apple Podcasts, or check out the full podcast page for more episodes.
If you're building a complete study plan, our guide on how to study for the GMAT® covers all three sections. And if you want to improve your scratch work — which prevents many Category A mistakes before they happen — our guide on how writing down more improves your GMAT® score walks through what to write down in each section.