Getting a question wrong once is normal. Getting the same type of question wrong three times is a pattern you can fix — if you're tracking it. Here's how to build an error log that actually changes your score, not just your guilt.
An error log is exactly what it sounds like: a running record of the mistakes you make in practice, categorized enough that patterns become visible. Most students skip this step because reviewing mistakes feels less productive than doing more practice questions. In reality, an hour spent properly logging and understanding 10 mistakes usually moves your score more than an hour spent doing 30 new questions you don't review closely.
Why a plain wrong-answer count isn't enough
Knowing you got 6 out of 22 wrong on a set tells you almost nothing actionable. Knowing that 4 of those 6 were the same type of error — say, sign mistakes when distributing a negative, or misreading which variable a question is asking for — tells you exactly what to fix. The difference between a score and an error log is the difference between a symptom and a diagnosis.
What to record for each mistake
Keep the format simple enough that you'll actually maintain it. For each wrong answer, log:
- The subtopic (one of the 19 official SAT Math subtopics, not a vague label like "word problems").
- The difficulty tier — Easy, Medium, or Hard — since the same subtopic can fail for different reasons at different tiers.
- The error type — conceptual gap, careless slip, misread question, or ran out of time.
- What you'd do differently — one sentence, written in your own words, not just "be more careful."
A simple table works better than a long paragraph log, because it makes patterns visible at a glance:
| Subtopic | Difficulty | Error type | Fix |
|---|---|---|---|
| Linear inequalities in two variables | Medium | Misread question | Re-read what's being asked before solving, every time |
| Right triangles and trigonometry | Hard | Conceptual gap | Review when to use sine vs. cosine before next attempt |
| Percentages | Easy | Careless slip | Double-check whether it's percent of original or new value |
| Nonlinear functions | Medium | Ran out of time | Practice recognizing the function type faster before solving |
Turning the log into a study plan
Once you've logged mistakes across several practice sessions, review the log itself, not just individual sets. Look for:
- Repeated subtopics. If the same subtopic keeps showing up, that's your next practice priority — go back to that subtopic's practice set and work it at the tier where the errors happened.
- Repeated error types across different subtopics. If "misread question" shows up constantly regardless of topic, the fix isn't more content review — it's slowing down on the read-through, which is a pacing and habit fix, not a knowledge fix.
- Difficulty-specific patterns. If your errors cluster at Hard but not Medium, you likely understand the core concept and need more exposure to multi-step versions of it.
This connects directly to how you review each practice attempt in the first place — see our guide on how to review wrong answers after a practice set for the step you should be doing right before you log anything.
Common error categories worth tracking separately
Not all mistakes deserve the same label. Breaking errors into a few consistent categories makes your log far more useful when you review it later:
- Conceptual gaps — you didn't know the rule or method needed. These point directly to a subtopic that needs review, not just more timed reps.
- Careless slips — sign errors, copying a number wrong, skipping a step you actually know. These point to pacing and attention, not content knowledge.
- Misread questions — you solved a different problem than the one being asked. Often clustered around questions with longer setups or multi-part scenarios.
- Time-pressure errors — you knew the method but ran out of time or rushed the last few steps. These call for more timed practice at the same difficulty, not new content review.
Tagging each mistake with one of these categories, alongside the subtopic, is usually enough structure to spot a pattern within two or three weeks of consistent logging. If you're not sure which subtopics deserve the most logging attention in the first place, revisit what's tested on SAT Math to see how much weight each domain carries, and start your log with Algebra practice sets, since algebra mistakes tend to be the most common early on.
Making the log easy to maintain
The most common failure mode with error logs is starting one, then abandoning it after a week because it feels like extra work on top of practice. A few things make it sustainable:
- Log immediately after reviewing a set, while the mistake is still fresh, not days later from memory.
- Only log genuine misses — don't log a question you got right just because it took a while.
- Review the whole log once a week, not just after each session, to catch cross-session patterns.
Because GetSATMath's SAT Math practice sets keep every past attempt available in "My attempts," with full explanations for each question, you already have the raw material for an error log without re-deriving anything from memory — you're just organizing what's already there into the pattern-spotting format above.
Review your error log before your next study session, not just after it. Knowing your recurring mistakes going in changes how carefully you read each new question.
An error log pairs naturally with a diagnostic at the start of your prep — see how to find your weak topics with an SAT Math diagnostic — and with choosing the right difficulty tier as you progress, covered in our guide to SAT Math practice by difficulty. Together, these three habits form a tighter feedback loop than practicing volume alone ever will.
What a few weeks of a well-kept log usually reveals
Students who stick with an error log for several weeks tend to notice the same broad pattern: a small number of recurring habits explain a disproportionate share of their wrong answers. It's rarely 19 unrelated weaknesses — it's usually two or three habits (rushing the read-through, a specific sign-error pattern, or forgetting a particular formula) showing up across several different subtopics wearing different disguises. Once you can name that habit specifically, fixing it tends to raise your score across multiple subtopics at once, rather than requiring you to separately re-learn each one. That's the real payoff of logging consistently instead of just reviewing each set once and moving on.
Frequently asked questions
How often should I update my error log?
Right after reviewing each practice set, while the mistake is still clear in your mind. Trying to reconstruct errors from memory a few days later loses most of the useful detail.
What if I don't have time to log every single mistake?
Prioritize logging mistakes on subtopics you've already flagged as weak, and any mistake you don't immediately understand. Careless errors on topics you're strong in are lower priority to log in detail.
Does an error log replace reviewing explanations?
No — it comes after. Read the full explanation for a wrong answer first to understand the correct reasoning, then summarize the mistake and fix into your log in your own words.
Should I keep my error log digitally or on paper?
Whichever you'll actually maintain consistently. A simple spreadsheet is easy to sort and filter by subtopic or error type, while a paper notebook can feel faster to jot in right after a session — the format matters far less than whether you keep it updated.
For more on building a complete review habit, see more SAT Math guides on reviewing wrong answers and choosing the right difficulty tier.