The GRE® Error Log: Done Right (and When It Becomes Procrastination)
If you've spent any time around GRE® prep, you've heard the advice: keep an error log. Track the questions you miss, review them regularly, and your score is supposed to follow. The advice comes from everywhere, prep courses and forums and study guides, and on its face it makes sense. A mistake you can't see is a mistake you can't fix.
So starting a log is a smart instinct, and we're not going to talk you out of it.
But an error log is a tool, and tools can run on autopilot. Logging can create a sense of progress that the fixing doesn't match, and the standard template has a blind spot built in: it records what happened on the question while skipping what you decided, which is where the fixable habits usually live. The version we teach is a three-column minimum that captures decisions along with answers, plus an honesty check for the point where logging becomes a way to avoid the harder work.
Where the standard error log breaks down
The traditional template asks for a row per missed question: topic, question type, your answer, the correct answer, a note on what to do differently. That structure sounds thorough, and it fails for predictable reasons.
The list grows faster than you can review it. After a few study sessions, a spreadsheet can hit eighty rows, and "I'll get to it this weekend" starts repeating itself.
Mistakes in one list start to look alike. A misread, a concept you haven't studied, and a question you abandoned at the two-minute mark all sit under the same heading labeled "wrong." They aren't the same problem, and they don't share a fix.
Open one of those logs and the recent misses are what fills the screen, which can leave the underlying problem untouched after you close the file. That's not a review system; it's a demotivation system. The problem isn't your discipline. The template was built to document misses, not to drive fixes.
Track decisions, not just questions
Here's the upgrade, and the GRE® happens to be the test that makes it pay: log the decision, not just the outcome.
The GRE® lets you skip questions within a section, come back to them, and change answers while time remains, and the review screen shows what you left unanswered. ETS lists that navigation flexibility among the test's design features. Nearly every question you touch involves a chain of choices before the answer arrives, and those choices are habits you can train:
- What you committed to in a Text Completion blank before you looked at the choices. A prediction forces the sentence logic to do the work; picking from the choices lets the answer choices do it instead. Our Text Completion and Sentence Equivalence guide covers the prediction habit.
- When you cut a question loose. On a pacing budget, a question that eats about twice its share, roughly three minutes in Verbal or three and a half in Quant, gets a best guess and a move on. Our timing guide has the system.
- Whether you went back. The return is a separate decision with separate stakes. A skipped question you never revisited is a different event from one you came back to and solved.
- What you left blank. An unanswered question scores nothing, while a guess has a chance. A blank is almost always worth its own row.
Outcomes tell you where you lost points, but decisions tell you why, and the why is the part you can change. Two students can miss the same Quant question for opposite reasons: one never had the setup, and one had it, second-guessed a correct answer, and changed. A traditional log gives both of them the same row ("Q14, wrong, topic: rates"). The fixes usually point in different directions.
The three-column minimum
You don't need fifteen columns, and you don't need to copy the full question into a document. Three columns capture most of what drives a fix:
| Column | What goes in it | Example |
|---|---|---|
| Where it lives | Source and question number, enough to find it again | PowerPrep 2, Quant section 1, Q7 |
| The decision | Your answer, or the move you made | Committed to (D) without predicting; cut loose at 3:30 and never returned |
| The cause | Knew how to do it and lost it anyway, or didn't know how to do it | Knew it; misread the stem |
That third column is the engine. Sort your rows by cause and two working lists fall out, the same split we teach in our guide to breaking through a score plateau:
- Execution errors (Category A): you knew how to do the question and lost it anyway, whether through a misread, a computation slip, or talking yourself out of a correct answer. The fix is a habit rule, one specific behavior such as "underline what the question asks before solving," visible during every study session.
- Knowledge gaps (Category B): you didn't know how to do it, or the approach took ten minutes. The fix is targeted learning plus re-solving the problem from scratch, pen to paper, until you can reproduce the approach reliably.
The log is the intake; the two lists are what you work from. The first 20% of a study session is a good home for that work: a handful of Category B problems re-solved from scratch, then a check on the Category A habit rule. A log entry that never reaches either list is a diary row.
When logging becomes procrastination
Now for the honesty check, because the error log has a failure mode that looks like diligence from the inside.
Logging is documentation, and documentation can substitute for the work it documents. Filling in rows can feel like a productive session while changing nothing about the next one, and that feeling is the trap. A few signals that a log has crossed into avoidance:
- The system gets more attention than the studying: new templates, new sorting rules, conditional formatting, a color scheme, etc. A note card with one rule on it can be more useful than a 200-row sheet when the sheet isn't being reviewed.
- The rows never get revisited. If entries flow in and nothing flows out, the log is a museum.
- Logging time crowds out fixing time. If writing down a mistake takes longer than re-solving an old one would, the balance is off.
- Practice test scores sit still while the log grows. Scores are the feedback worth checking against, and a log that isn't connected to them is decoration.
If the log grew this week and nothing about how you solve questions changed, the log isn't driving anything yet. What drives it is the working routine: the two lists, the first 20% of each session spent re-solving, one habit rule at a time for execution errors. The intake stays light, three columns and a few minutes after each session or practice test, and the bulk of your energy goes where the lists point.
An error log is a record of missed questions, not a measure of ability. A logged miss is a point you haven't lost on test day yet.
FAQ
What is a GRE® error log?
A GRE® error log is a system for recording questions you miss during prep so you can fix the causes instead of repeating them. The traditional version is one list of wrong answers. We recommend a three-column intake (where the question lives, what you decided, what caused the miss) that feeds two working lists: execution errors and knowledge gaps.
What should I record in my GRE® error log?
Three columns cover it: source and question number, the decision you made (your answer, when you cut the question loose, whether you returned), and the cause of the miss. Causes split into execution errors, where you knew how to do the question, and knowledge gaps, where you didn't. You don't need to copy the full question into the log as long as you can find it again.
Is keeping an error log a waste of time?
It can be, when logging replaces fixing. If the log grows but your approach to questions stays the same, if rows never get revisited, or if system-tweaking eats study time, the log has become busywork. Run the routine it feeds: re-solve knowledge-gap problems from scratch in the first 20% of each session, and keep one visible habit rule for execution errors.
Should I use a spreadsheet or an app for my GRE® error log?
Either can work; the fixes matter more than the format. A notes app with two lists and a few recent rows is enough, because the value comes from the fixes, not the format. A spreadsheet with conditional formatting and sorting rules tends to cost more maintenance time than it returns.
How often should I review my GRE® error log?
More often than a weekly marathon session, and in smaller pieces. Re-solving a handful of knowledge-gap problems at the start of each session covers that list, and a habit rule on a note card covers execution errors continuously. If you're only opening the log once a month, it probably isn't changing anything.
What's the difference between an execution error and a knowledge gap?
An execution error is a question you knew how to do and missed anyway: a misread, a computation slip, talking yourself out of a correct answer. A knowledge gap is a question you couldn't approach, or one that took far longer than its budget. Execution errors need habit change. Knowledge gaps need learning and re-solving. They need different fixes, which is why they live on different lists.
How does the skip-and-return feature change what I log?
It adds decisions to the record. Because the GRE® lets you skip, return, and change answers within a section, your navigation is a source of data: when you cut a question loose, whether you came back, and whether anything ended the section blank. Logging those moves shows whether timing habits or content gaps are behind your missed points, which changes what you study next.
Want to learn even more?
For the two-list system this log feeds:
For the pacing decisions worth logging:
For free practice tests to feed the log:
And for the broader prep structure around it:
We also talk through study strategy on our podcast.
If you want a second set of eyes on your prep system, you're welcome to book a complimentary strategy session. We'll look at where your points are going and help you figure out the best path forward.