To err is human; to forgive, divine.

Alexander Pope said it best in his An Essay On Criticism (which contains other gems, such as "A little learning is a dangerous thing" and "For fools rush in where angels fear to tread"). To err certainly is normal. We're all human. We all make mistakes. The question is, what do we do about them?

Why An Error Log Helps

Let's consider why an error log might help reduce the number of mistakes you make in the future. Some premises:

• To fix a problem, we must be aware of it.
• By "aware" of it, I mean "aware of its precise nature". For example, labeling a mistake "careless" is hardly precise.
• By tracking our mistakes, we become more aware of them.
• If you want to fix a problem, the more responsibility you take for it, the better.
• Your plan to fix something must contain concrete, observable, volitional steps.
• An error log is most important for official ETS questions.
• Just like any part of GRE prep that feels like a chore, most people will have to discipline themselves to use an error log.

How To Create An Error Log

A basic template for an error log just needs a few columns:

1. Problem location (page #, etc.)
2. What caused the mistake
3. What you learned
4. Plan

For instance, let's say you made a mistake with an exponent. First, make sure you redo the question from start to finish to prove to yourself you can do it. Then, pinpoint the cause. Not "careless mistake", and not "exponents". We want to be descriptive. For example, if you thought (2x)² was 2x², you would write down something like "I only applied the exponent to the variable and should have applied it to both the variable and the coefficient."

What you learned here might go without saying, so no need to write anything down in that column this time, perhaps. But you do need a plan. For example: Drill that particular operation (use Chat GPT to create new questions or write your own). Tip: make part of your plan to double-check that kind of operation (exponents with parentheses) right after doing it in the future. And be careful - doing more than one math step in your head is dangerous. (H/t to fellow GRE tutor Blake Jensen, who helped with these ideas).

Verbal Error Log Challenges

If you're creating an entry for a verbal error, a word of caution. There is a good chance that, without exercising some care, you will be fuzzy on exactly what caused the error, or on what you learned, or both. It's really important to be as precise as you can be with these things, so I highly recommend discussing verbal errors on the Gregmat forums. Believe me, this will help - articulating to another person how a verbal question works will improve your skill, and you'll probably get helpful feedback.

Reviewing The Log

Since an error log contains valuable insight when done correctly, I suggest doing a weekly review. See if you can identify things like:

• questions that still seem challenging
• error patterns
• places where additional steps are needed to remedy the cause of the error

Finally, don't beat yourself up. Treat yourself like you'd treat a close friend. You made a mistake? Welcome to the human race!

The Bottom Line

Just like almost anything in life that we take the trouble to track, your GRE errors will be mitigated if you diligently keep a record of them. Looking forward to seeing your discussion of your errors on the forum!