Ask any GRE tutor what separates students who improve from students who plateau and they will tell you the same thing: error logging. Track your mistakes. Review them. Find patterns.
The advice is correct. The execution is almost always wrong.
Most students who build error logs do the same thing: they write down the question, look up the right answer, and note that they missed it. Maybe they copy in the explanation. Then they move on.
That is not an error log. That is a list of questions you got wrong. And a list of questions you got wrong does not tell you anything about why you got them wrong or what to do differently next time.
The error log that actually changes your score tracks the error type, not just the error.
What an Error Log Is Actually For
An error log is a diagnostic tool. Its purpose is to reveal patterns in your thinking, not just in your outcomes.
When you miss a question, you learn one data point. When you miss twenty questions and categorize each one, you see something more useful: that 70% of your Verbal misses are on Reading Comprehension questions where you chose the answer that restated the passage rather than answered the specific question asked. Or that 80% of your Quant misses happen on questions that require setting up equations from word problems, not on the calculation itself. Or that your errors cluster in the final 5 questions of every section, pointing directly to a pacing issue.
One data point tells you to review that question. Twenty categorized data points tell you exactly what to change in your approach.
The Mistake Most People Make
The most common error log mistake is recording the question without recording the error type.
Writing down "I missed this geometry question" tells you to review geometry. But if you look at your work and realize you set up the correct equation and made an arithmetic error in the last step, the problem is not geometry knowledge. The problem is arithmetic carelessness on the final step, probably under time pressure. More geometry review will not fix that.
Writing down "I missed this Text Completion question" tells you to review vocabulary or sentence logic. But if you look at the answer choices and realize you knew the correct word, you just eliminated it because you misread a pivot word in the sentence structure, the problem is reading strategy. More vocabulary review will not fix that.
The category of the question type (geometry, text completion, reading comprehension) is not the same as the category of the error. These are different things, and conflating them sends your study sessions in the wrong direction.
The Right Format for an Error Log
Each entry in your error log should capture five things:
The question type. Not just "Quant" but the specific type: Quantitative Comparison, Problem Solving, Data Interpretation. Not just "Verbal" but: Text Completion, Sentence Equivalence, Reading Comprehension inference, Reading Comprehension main idea.
Your answer. What did you choose and why? Even a brief note like "chose B because I thought the word meant X" is useful.
The correct answer. What was right and why. Write this in your own words. If you cannot explain why the correct answer is correct, you have not actually learned it yet.
The error type. This is the critical field. Use a specific taxonomy. Four core types cover almost everything:
- Content (C): I did not know the concept, formula, or vocabulary word.
- Strategy (S): I knew the concept but approached the question incorrectly, fell for a trap, or made a setup error.
- Timing (T): I knew how to solve it but was rushing and made an error, or ran out of time and guessed.
- Anxiety (A): I knew it but second-guessed myself, or could not think clearly under pressure.
What to do differently. One specific, actionable note. Not "study harder." Something like: "When I see a QC question with variables, try all three cases (positive, negative, zero) before comparing" or "For RC inference questions, eliminate answers that go beyond what the passage states."
How to Review Your Error Log
The review habit matters as much as the recording habit. Most students look at individual entries. The value is in looking at the aggregate.
Once a week, scan your entire log and look for patterns across entries. Ask yourself:
Which error type shows up most often? If content errors dominate, your study sessions should shift toward concept learning and away from practice volume. If strategy errors dominate, drill the specific question types where you keep falling for the same traps. If timing errors dominate, your problem is pacing, not knowledge.
Which question types have the most entries? If Reading Comprehension accounts for 60% of your Verbal log, that is where your improvement ceiling sits. Improving vocabulary will not move your score as much as improving RC performance.
Do errors cluster in specific sections or positions? If your errors consistently appear in the last 5-6 questions of a section, that is a pacing signal. If they cluster in Section 2 rather than Section 1, that may be fatigue or the difficulty increase from adaptive routing.
Are the same "what to do differently" notes repeating? If you have written "read all answer choices before eliminating" twelve times, you have a persistent strategy habit to break, not just an isolated error to fix.
How Frequent Review Compounds Improvement
The error log works through spaced repetition applied to your failure patterns.
When you review wrong answers immediately after a practice session, you are in a low-retrieval-effort state. You just did the questions. The experience is fresh. You understand the explanation easily.
When you review the same entries two days later, you are testing whether the lesson actually stuck. If you look at an entry and understand exactly why you got it wrong and what to do differently, the learning is solid. If you look at an entry and the explanation feels new again, the lesson did not transfer.
A weekly review of your full error log, combined with re-attempting a sample of questions from the log, does two things: it identifies which lessons stuck and which need more work, and it repeatedly surfaces your specific failure patterns until they become part of your awareness going into a practice session.
Students who do this consistently report that they start catching themselves mid-question: "This is a Text Completion where I want to fill the blank before reading the answer choices, I need to do that." The error log teaches you to recognize the patterns before you fall into them.
Practical Notes on Format
A spreadsheet works well because you can sort and filter. Make columns for date, question type, your answer, correct answer, error type (C/S/T/A), and your "what to do differently" note. Filtering by error type gives you an instant view of where to focus.
You can also use a notes app or a physical notebook. The format matters less than the consistency. Review it weekly without exception.
The practice section on this platform includes a built-in meta-question layer that prompts you to categorize each wrong answer immediately after review. The structure mirrors what an effective manual log should do, and the categorizations accumulate into data you can review across sessions. If you prefer working natively within the platform rather than maintaining a separate spreadsheet, the tracking is already there.
One More Thing
The error log also fixes a common psychological problem in GRE prep: the sense that practice is not working.
When you track errors without categorizing them, you end up with a list that says "I am still getting things wrong." That feels discouraging even when you are actually improving. When you categorize errors, you start to see the distribution shift over time. In week one, content errors are 70% of your log. In week three, they are 30% and strategy errors have moved to the top. That is real progress, and the log makes it visible.
You are getting better. The log shows you exactly where.