TL;DR: A GMAT error log works only if you categorize the error type, not just the question type. Use four categories: Content, Strategy, Timing, and Anxiety. Review weekly to spot patterns. The GMAT Focus Edition's three sections (Quant, Verbal, Data Insights) each have distinct error profiles, and your log should reflect that.
Every GMAT tutor tells you to track your mistakes. Write them down. Review them. Find patterns.
The advice is right. The execution almost never is.
Most students who keep an error log do the same thing: they record the question, look up the correct answer, maybe copy the explanation, and move on. That is not an error log. That is a list of questions you got wrong. And a list of wrong answers tells you nothing about what to change.
The error log that actually shifts your score tracks the type of error, not just the error itself.
Why an Error Log Matters More on the GMAT Focus Edition
The GMAT Focus Edition is adaptive at the question level. Each question you see is selected based on how you answered the previous ones. That means when you get a question wrong, the algorithm adjusts immediately. You do not get to power through a bad stretch the way you could on a section-adaptive test.
This makes error analysis more important, not less. You need to know whether your wrong answers are coming from gaps in content knowledge, from strategic mistakes on specific question formats, or from time pressure. The algorithm does not care why you got it wrong. It only cares that you did. Your error log is where the "why" lives.
The GMAT Focus also lets you bookmark questions and edit up to 3 answers per section at the end, but only if you have time remaining. If your log shows you are consistently running out of time, the bookmark-and-edit feature becomes useless. That is the kind of insight an error log surfaces.
The Mistake Most People Make
The most common error log mistake is recording the question category without recording the error type.
Writing down "I missed a Data Sufficiency question" tells you to review Data Sufficiency. But if you look at your work and realize you actually set up the problem correctly and then forgot to check whether Statement 2 alone was sufficient because you were rushing, the issue is pacing. More Data Sufficiency drills will not fix that.
Writing down "I missed a Critical Reasoning question" tells you to practice Critical Reasoning. But if you narrowed it down to two answer choices, knew the right one, and then talked yourself out of it under pressure, the problem is confidence under test conditions. More CR practice will not fix that either.
The question type and the error type are two different things. Conflating them sends your study sessions in the wrong direction.
The Four Error Categories
Each entry in your error log should include the question type, your answer and reasoning, the correct answer in your own words, the error category, and one specific note about what to do differently.
The error category is the field that matters most. Four types cover nearly everything you will encounter across all three GMAT Focus sections.
Content (C): You did not know the concept, formula, or rule. This is a genuine knowledge gap. The fix is studying the underlying material.
Strategy (S): You knew the concept but applied the wrong approach, fell for a trap answer, or made a setup error. The fix is drilling that specific question format with attention to common traps.
Timing (T): You knew how to solve it but were rushing and made a careless error, or you spent too long on an earlier question and had to guess on this one. The fix is pacing work, not content review.
Anxiety (A): You knew the answer but second-guessed yourself, or froze and could not think clearly. The fix is test-day simulation and pressure management.
Applying This Across All Three Sections
The GMAT Focus Edition has three sections, and each one produces its own error patterns.
Quant (21 questions, 45 minutes) covers Problem Solving only. Data Sufficiency has moved out of this section entirely. Common error patterns here tend to cluster around content gaps (forgetting properties of exponents, ratio setups, combinatorics formulas) and timing pressure. With just over two minutes per question, students who spend four minutes on an early problem often cascade into timing errors for the rest of the section.
Verbal (23 questions, 45 minutes) covers Reading Comprehension and Critical Reasoning. Strategy errors are the most common culprit here. Students who know the content frequently eliminate the correct answer because they misread the question stem or confuse "most strengthens" with "proves." The question types reward precision in reading, and most errors come from reading too fast rather than from not knowing the material.
Data Insights (20 questions, 45 minutes) is the section most students underestimate. It includes five question types: Data Sufficiency, Multi-Source Reasoning, Graphics Interpretation, Two-Part Analysis, and Table Analysis. Each type demands a different approach. Data Sufficiency requires systematic checking of each statement alone and then together. Multi-Source Reasoning requires synthesizing information from multiple tabs. Graphics Interpretation requires reading charts accurately before doing any math. The variety means your error log for this section needs to be especially specific about which DI question type triggered the error. "I missed a Data Insights question" is too broad. "I missed a Multi-Source Reasoning question because I only checked two of the three information tabs" is useful.
How to Review Your Error Log
Recording errors is half the system. The review habit is the other half.
Once a week, scan your full log and look for patterns across entries. The questions to ask yourself are straightforward.
Which error type appears most often? If Content errors dominate, you need more concept review and less practice volume. If Strategy errors dominate, drill the specific question formats where you keep falling for the same traps. If Timing errors dominate, the problem is pacing, not knowledge.
Which section has the most entries? If Data Insights accounts for 50% of your errors, that is your improvement ceiling. Working on Quant when DI is the bottleneck will not move your total score.
Do errors cluster at the end of a section? The GMAT Focus gives you 45 minutes per section, and a score penalty for unanswered questions. If your errors consistently show up in the last five questions, you are spending too long on earlier questions. The penalty for leaving questions blank is real, and your log is telling you to move faster on the questions you know.
Are the same "what to do differently" notes repeating? If you have written "check both statements individually before combining" eight times for Data Sufficiency, that is a persistent habit problem, not an isolated mistake. It needs targeted drill work until the new pattern replaces the old one.
How Weekly Review Compounds Into Score Gains
When you review wrong answers right after a practice session, the experience is fresh. You understand the explanation easily because you just did the question.
When you review the same entries two days later, you are testing whether the lesson transferred. If you look at an entry and immediately understand why you got it wrong, the learning stuck. If the explanation feels new again, it did not.
A weekly full-log review does two things. It shows which lessons are sticking and which are not. And it repeatedly surfaces your specific failure patterns until they become part of your awareness during live practice. Students who do this consistently report catching themselves mid-question: "This is a Two-Part Analysis where I need to check both columns satisfy the constraint, not just one." The log trains pattern recognition before the error happens, not after.
Over time, you will also see the distribution of error types shift. In week one, Content errors might be 60% of your log. By week four, they may be 20% and Strategy errors have moved to the top. That shift is measurable progress, even if your practice scores have not jumped yet. The score follows the error distribution. It always does.
Practical Notes on Format
A spreadsheet works well. Make columns for date, section (Quant/Verbal/DI), specific question type (Problem Solving, Critical Reasoning, Multi-Source Reasoning, etc.), your answer, correct answer, error type (C/S/T/A), and your "what to do differently" note. Filtering by error type or by section gives you an instant view of where to focus.
A notes app or physical notebook also works. The format matters less than consistency. Review it weekly without exception.
If you are working through practice sets on our platform, the GRE practice tools include a built-in meta-question layer that prompts you to categorize each wrong answer after review. The categorization framework is the same one described here, and the data accumulates across sessions so you can spot patterns over time.
What to Do Next
- Build your error log today. Six columns: date, section, question type, your answer, correct answer, error type (C/S/T/A), and what to do differently.
- After your next practice session, log every wrong answer before reading the explanation. Categorizing first forces you to diagnose before you see the solution.
- At the end of this week, filter by error type and identify the dominant category. That category sets your study focus for next week.
- If Timing errors dominate, run a full section under strict 45-minute conditions and count how many questions you leave unanswered. If the number is more than two, your pacing strategy needs work before anything else.
- If your errors cluster in Data Insights, break the section down by its five question types and figure out which specific type is generating the most mistakes. The fix for Graphics Interpretation errors is different from the fix for Data Sufficiency errors.
The GRE course is $25 per month with a free diagnostic if the GRE is worth exploring. The playbook's test strategy module covers how to use error data to know when your score is ready and when to shift focus to the application. If your error log keeps pointing to the same patterns and you are not sure how to break through them, coaching can read your error data and build a study plan around it.