- Foundation
- About 12 min
- 5 practice questions
The error log: writing down what went wrong and what to do about it
Keep a simple error log with six columns, fill it in within a day of the mock, and redo each logged question after a week to see whether the fix worked.
If something looks wrong, please tell us.
After a mock, most students look at the right answers, say 'I see', and move on. A week later they make the same mistake again. Seeing the right answer is not the same as learning from the wrong one. An error log makes you write down what went wrong and what you will do differently, which is where the learning happens. This lesson shows how to keep one. The examples are invented.
What goes in the log
| Column | What you write | Example |
|---|---|---|
| Question | Number, topic and a few words | Q14, percentages |
| My answer and the right one | Both, briefly | I chose 24; right answer 30 |
| Why it went wrong | Not knew, misread or careless, and one line of detail | Misread: 'of the total', not 'of the part' |
| Correct method | The steps in your own words | Find the total first, then take the percentage |
| Fix | One action for next time | Underline what the percentage is OF |
| Redo on | A date about a week later | Redo next Sunday |
The log is short. Each entry should take two to four minutes. If an entry takes ten minutes, you are probably rewriting a textbook; write the key idea and the page to see.
Worked example 1: Nandini logs three mistakes
- Entry 1: Q7, ratio. My answer: 12; right: 15. Why: did not know; I mixed up the order of the ratio. Method: write the ratio with labels before using it. Fix: label every ratio. Redo: Sunday.
- Entry 2: Q19, passage. My answer: C; right: B. Why: misread; I missed the word 'except'. Method: circle the keyword, say the task aloud. Fix: circle every 'not' and 'except'. Redo: Sunday.
- Entry 3: Q31, sum. My answer: 46; right: 64. Why: careless; I swapped two digits in the last step. Method: check the answer by estimating. Fix: estimate every answer before marking. Redo: Sunday.
- Check: each entry has a different reason, so each has a different fix. A single instruction such as 'be more careful' would have helped none of them.
When to fill it in
Fill in the log within a day of the mock, while you still remember what you were thinking. If you wait a week, you will see the right answer but not your own mistake. Do the redo after about a week, without looking at the log first. If you get it right, mark the entry done; if not, it stays on the list.
Worked example 2: how long does the review take?
- Step 1: Nandini got 18 questions wrong in a mock.
- Step 2: at about 3 minutes an entry, the log takes 18 x 3 = 54 minutes, which is 0.9 hours.
- Step 3: she thinks this is too long for one evening and splits the log into two evenings.
- Step 4: she logs the questions she misread or carelessly lost first, because those are marks she already owns, and the topics she did not know second.
- Step 5: next week she redoes the 18 questions in about 20 minutes, since she only needs to re-solve, not to write a log.
- Result: 54 minutes of review and 20 minutes of redo, against one mock that took several hours to sit. The review is where much of the value is.
A mistake is useful only when you write down why it happened and what you will do differently, and test it again later.
Key takeaways
- An error log has six columns: question, answer, reason, method, fix and redo date.
- Each entry needs its own reason and its own fix.
- Fill in the log within a day; redo the questions after about a week.
- Keep entries short.
Check your understanding
-
1. Why must each log entry have its own reason?
- It makes the log look longer
- Each reason needs its own fix
- It is a rule of every paper
- Reasons are rarely very useful
Show answer
Answer: B. A knowledge gap needs study, a misreading needs a reading routine and a slip needs a check. One general instruction would not fit all.
-
2. When should you fill in the error log?
- After a month
- Just before the next exam only
- Never, if you got a good score
- Within a day of the mock
Show answer
Answer: D. Within a day you still remember your thinking, which is the thing you need to record.
-
3. A student has 12 wrong answers and spends 3 minutes on each log entry. How long does it take?
- 36 minutes
- 24 minutes
- 30 minutes
- 48 minutes
Show answer
Answer: A. 12 x 3 = 36 minutes.
-
4. What is the purpose of the 'redo on' column?
- To record the date of the mock
- To list all the right answers
- To test later if the fix worked
- To count the questions asked
Show answer
Answer: C. Redoing the question later checks that the learning stuck. A question solved correctly can be marked done.
-
5. Which fix is specific enough to help?
- Be much more careful next time
- Try harder on every question
- Read faster and finish earlier
- Circle every 'not' in the stem
Show answer
Answer: D. A specific action can be carried out and checked. 'Be more careful' says nothing about what to do.
Sign in to keep track of the lessons you finish.