On this page
An SAT error log should not be a museum of questions you once missed. It should tell you what to do next. Most logs fail because they collect too much: copied questions, long explanations, color codes with constitutional complexity. The useful version records one broken reasoning step, one prevention rule, and one date to prove the fix stuck.
Key takeaways
- Log the cause, not just the question topic or correct answer.
- Use six repeatable labels: knowledge, task read, setup, execution, trap choice, and pacing.
- Write a prevention rule that starts with an action: label, predict, substitute, draw, or leave.
- Retest the original question after a delay. A log entry closes only when the fix survives retrieval.
What to put in an SAT error log
| Field | Write this | Not this |
|---|---|---|
| Skill | Transitions | Reading |
| First broken step | Named contrast before reading sentence 2 | Got confused |
| Cause | Trap choice | Careless |
| Prevention rule | Predict the relationship before choices | Try harder |
| Retest | July 17, blank copy | Review later |
Add the question source and number so you can find it again, plus confidence and time if you track them. Do not reproduce copyrighted questions in a shared document. A reference and your own diagnosis are enough. The point is to preserve the decision that failed, not rebuild the entire test booklet in a spreadsheet.
Use cause labels that lead to action
- 1
Missing knowledge
You did not know the rule, formula, word, or concept. Learn it, then retrieve it without notes.
- 2
Misread task
You answered a nearby question. Circle or restate the requested quantity before solving.
- 3
Setup error
You knew the content but built the wrong equation or model. Practice translation before calculation.
- 4
Execution error
The setup was right and arithmetic, signs, or copying failed. Add a targeted check at the risky step.
- 5
Trap choice
You abandoned the text or math for a plausible option. Predict first and demand direct evidence.
- 6
Pacing decision
You rushed a bankable point or overspent on one item. Set an exit rule and practice it timed.
“Careless” describes how the mistake feels after you see it. Name the exact move: copied 36 as 63, dropped a negative while distributing, or answered for radius squared instead of radius. The most common SAT mistakes are worth reading once as a checklist, because naming a pattern someone else already catalogued is faster than rediscovering it.
Write a prevention rule you can perform
A useful prevention rule changes behavior at the moment the error would occur. “Be careful” cannot be observed. “Box what the stem asks for before solving” can. “Remember signs” is fog. “When dividing an inequality by a negative, draw the flipped sign on a new line before calculating” has a trigger and an action.
Reflection
I should have known that the transition was “however.”
Rule
Before viewing transition choices, describe sentence 2 as support, contrast, cause, example, or sequence.
Keep the rule in your own language. If a tutor's explanation uses three terms you would never say, translate it until you could use the rule halfway through module 2. The explain-it-out-loud method is excellent here because gaps become audible before they become expensive.
Close the loop with a retest
After logging a miss, solve two or three fresh questions that require the same move. Then schedule the original problem for a blank-paper retry in three to seven days. Cover the old work. If you solve it cleanly and explain the prevention rule, mark the entry repaired. If not, revise the diagnosis. Perhaps the “sign error” was actually weak distribution.
Once a week, count causes and skills. Your next study block should follow the largest repeated pattern, not the question that annoyed you most recently. Combine the log with the full practice-test review process and spaced repetition. The log finds the leak; spacing checks whether the patch holds.
Choose the skill behind your largest error-log pattern and practice the exact move that keeps breaking.
Start a Targeted Repair →Frequently asked questions
- What is an SAT error log?
- An SAT error log is a short record of missed, guessed, or slow questions that identifies the first broken reasoning step, the cause, a prevention rule, and a date to retest the fix.
- Should I put every wrong SAT answer in my error log?
- Log every meaningful miss, plus guesses and unusually slow correct answers. Repeated identical errors can be grouped once the pattern is clear, as long as you still schedule a repair and retest.
- What categories should I use in an SAT error log?
- Useful categories are missing knowledge, misread task, setup error, execution error, trap choice, and pacing decision. Each category points toward a different kind of repair.
- How often should I review my SAT error log?
- Scan it after each practice session and count patterns once a week. Retest individual entries after several days, then use the weekly pattern count to choose the next skills and methods to study.