An error log is useful only if it changes future behaviour. Copying every wrong answer into a notebook creates an archive. A learning log identifies the type of failure, its cause, the repair rule and the evidence that the repair can be used independently later.
Record mechanisms, not embarrassment
“Careless mistake” is rarely diagnostic. Replace it with a mechanism: missed the negative in the question; selected a true but irrelevant option; copied source wording; used a comma between independent clauses; made a claim broader than the evidence.
The six-column error log
- Task: what was I trying to do?
- Error: what went wrong?
- Cause: what decision or missing knowledge produced it?
- Repair: what rule or method fixes it?
- Retest: what fresh task tested the repair?
- Status: recurring, improving or stable?
Worked entry
Task: infer the speaker’s attitude. Error: answered “angry”. Cause: chose a strong emotion without checking the language evidence. Repair: identify tone evidence first, then choose the narrowest defensible label. Retest: new passage correctly identified sceptical tone from contrast and word choice. Status: improving.
Group errors into families
Individual mistakes become powerful when grouped. Useful families include task reading, inference, evidence selection, paraphrase, vocabulary in context, grammar, sentence control, paragraph structure, argument, oral development, listening and time management.
Count recurrence, not just marks
A one-mark error repeated ten times may deserve more attention than one unusual four-mark error. Track frequency. Repeated mechanisms reveal the highest-return repair targets.
Keep repaired errors visible until stable
Do not remove an item after one correct attempt. Mark it improving, then retest after a delay and in a different context. Stability means the student can perform without the original correction sitting beside the task.
Use the log to choose practice
If the largest cluster is inference, another full composition may not address it. If sentence boundaries dominate, targeted editing may produce faster improvement. The log should control what happens next.
Weekly review
- Count recurring error families.
- Select the top one or two mechanisms.
- Choose short practice that isolates them.
- Retest with unfamiliar material.
- Update status only from independent performance.
Avoid turning the log into punishment
The log is a control instrument, not a record of failure. It should become shorter in active problems as skills stabilise, while older entries remain evidence of what has already been repaired.
Continue the recovery route
Continue with Diagnosing Mark Loss, Retrieval and Transfer Revision, and Practice Under Time Pressure. Connect to the Diagnostics & Recovery Hub.