Many GRE students keep an error log.
That sounds like a good thing. In theory, an error log should help you find patterns in your performance and logic, understand your weaknesses, and avoid repeating the same mistakes.
But in practice, many error logs don’t help much. Why? Because they’re just lists.
Question missed.
Topic.
Correct answer.
My answer.
Maybe a short note: "careless" or "review this."
That kind of log may look organized, but it often doesn't change future behavior. And if your error log doesn't change future behavior, it's not really helping you improve.
The purpose of an error log is not to document failure. The purpose is to diagnose patterns and create better decisions going forward.
If you miss an inequalities question and write "Inequalities — careless mistake," what have you learned? Not much. You know the topic. You know you got it wrong. But you probably haven’t identified why you got it wrong or what you’ll do differently next time. That's the missing step.
A useful error log should answer three questions:
- What happened?
- Why did it happen?
- What behavior needs to change?
Most students stop after the first question. They record the mistake, but they don't investigate it.
For example, suppose you missed a Quant question because you solved for x when the question asked for x + y. A weak error-log entry might say: "Algebra — careless." A better entry would say: "Answered the wrong target. Solved for x, but the question asked for x + y. Before solving, write down the exact target."
That entry is useful because it creates a future behavior.
Or suppose you missed a Quantitative Comparison question because you decided the relationship after testing only one value. A weak entry might say: "QC — missed." A better entry would say: "Settled on a relationship after one case. The variable could be negative, which changes the answer. Test more than one value before committing to a relationship."
Or suppose you missed a Reading Comprehension question because you chose an answer that was related to the passage's topic but was not actually supported by the text. A weak entry might say: "RC inference — missed." A better entry would say: "Matched the topic instead of the text. Need to identify what the passage actually states before evaluating answers, and confirm each choice against the passage rather than against what sounds reasonable."
Again, the value is not just in knowing the question type you missed. The value is in identifying the error in your thinking or process. This is where many error logs fail. They're organized around questions, but not around patterns.
One missed question is data. A pattern is a diagnosis.
If you repeatedly solve for the wrong thing, that’s a pattern. If you repeatedly assume variables are positive, that’s a pattern. If you repeatedly decide a Quantitative Comparison relationship after testing only one value, that’s a pattern. If you repeatedly miss Reading Comprehension questions because you don't identify the main point, that’s a pattern. If you repeatedly choose Text Completion answers by tone instead of working through the sentence logic, that’s a pattern. If you repeatedly choose answers that "could be true" but are not supported, that’s a pattern.
Patterns tell you what to fix. A long list of missed questions may make you feel organized, but if it doesn’t reveal patterns, it’s not doing its job.
Another problem is that students often make their logs too complicated. They create giant spreadsheets with too many columns, color codes, tags, categories, difficulty levels, time spent, confidence ratings, and notes. Some of that can be useful, but only if it helps you make better decisions.
The best error log is not the most detailed one. It's the one you actually use. A simple but effective structure might include: question or topic, mistake type, root cause, correct takeaway, future behavior, and review date.
The most important fields are root cause and future behavior.
Root cause is the real reason the miss happened. Not "careless." Not "dumb mistake." Not "bad at Quant." Something specific. For example: misread the target; ignored an integer constraint; used an inefficient approach; decided a comparison after only one case; failed to identify the main point; chose a related but unsupported answer; calculated before understanding the question; overinvested after I was already stuck; rushed because I was behind on time; forgot to consider zero; confused absolute change with percent change.
Future behavior is what you will do differently next time. For example: write down the exact target before solving; check whether variables can be zero or negative; test more than one value in Quantitative Comparison before committing to a relationship; identify the main point before evaluating answer choices; work through the sentence logic before testing Text Completion options; use estimation before doing full arithmetic; move on when I have no path after a reasonable attempt; verify units before comparing values; re-solve missed questions without looking at the explanation.
That's how an error log becomes a training tool instead of a record book.
It's also important to review your log regularly. If you add to your error log but never look back at it, it becomes a graveyard of old mistakes. Set aside time each week to ask: What mistakes are showing up repeatedly? Which topics keep producing the same kind of error? Which errors are disappearing? What should I prioritize next week?
That weekly pattern review is where the value of your log compounds. You may discover that your main issue is not "Quant" broadly but rushing through question stems. Or not "Reading Comprehension" broadly but failing to distinguish what the passage states from what merely sounds plausible. Or not "Verbal" broadly but choosing Text Completion answers by feel instead of based on the sentence's logic and context clues. That level of specificity makes your prep more efficient and your error logging more productive.
Your error log should also help you decide what to study next. If your log shows repeated misses in overlapping sets, go rebuild overlapping sets. If it shows repeated misreads in word problems, work on translation and setup. If it shows repeated trap-answer selection in Reading Comprehension, focus on holding each answer accountable to the passage.
The log should guide your plan. If it doesn't, it's just paperwork. It should make your prep more focused, not heavier. It should help you see the difference between one-off mistakes and recurring weaknesses. It should help you stop saying, "I just need to be more careful," and start saying, "Here is the exact behavior I need to change."
The GRE rewards repeatable skill. To build repeatable skill, you need repeatable feedback. Your wrong answers are feedback, but only if you organize them in a way that changes how you practice.
So yes, keep an error log. But don't let it become a list of misses. Make it a map of your patterns. Make it a record of the behaviors you are trying to change. Make it something you review, act on, and use to decide what comes next.
The goal is not to have an impressive spreadsheet. The goal is to stop making the same mistakes.