What an error log is
An error log is a running record of every question you get wrong while studying, kept in one place, in a consistent format, and reviewed on a schedule. That's the whole idea. It is not a diary, not a set of notes, and not a list of topics you feel shaky on — it is a list of specific questions that actually took marks off you, with enough context to re-attempt each one later.
Top scorers in almost every high-stakes exam system keep one, whether they call it that or not: medical students reviewing question banks, HSC and VCE students grinding past papers, SAT students drilling practice tests, A-Level students working through mark schemes. The common thread is that they treat a wrong answer as an asset to be processed, not an embarrassment to move past. If you want the case for why this beats another pass over your notes, read your mistakes are worth more than your notes.
Why it works
Three reasons, all boring, all backed by how memory actually behaves:
- Your mistakes cluster. They feel random, but log two weeks of them and you'll find that a large share come from a handful of causes — one algebra habit, one misread question stem, one formula you half-know. You cannot see the cluster without the log.
- Re-attempting a failed question is recall practice at its most targeted. Re-reading notes trains recognition, which is why revised material still vanishes in the exam room — see why you blank on exam questions you've already revised. A logged wrong answer is a ready-made recall test on exactly the thing you couldn't do.
- It ends repeat mistakes. Most students lose more marks to errors they've made before than to material they never learned. The log is the mechanism that breaks the repeat cycle — more on that in why you keep making the same mistakes in exams.
What goes in each entry
Keep the format small enough that you'll actually fill it in when you're tired. Five fields cover it:
- The question — a photo, screenshot, or reference (paper, year, question number). Enough to re-attempt it cold later. Don't copy it out by hand; that friction kills logs.
- Your answer vs the correct answer — what you wrote, what the mark scheme wanted.
- Why you got it wrong — one honest sentence. "Didn't know the trig identity" and "knew it, rushed the sign" are different problems with different fixes.
- Category — see below. This is the field that makes the log analysable rather than just a pile of regrets.
- Resolved? — a checkbox you only tick after you've re-attempted the question later and got it right without help.
If you want this ready-made, we publish a free error log template with these exact columns.
Categorise every mistake
Every mistake belongs to one of three families, and only one of them is fixed by more revision:
- Knowledge gap — you didn't know it. Fix: revise that specific point, then re-attempt.
- Application error — you knew it but misapplied it: wrong method chosen, step skipped, concept used outside its conditions. Fix: more practice questions of that type, not more notes.
- Execution slip — you knew it and rushed: arithmetic slip, misread stem, answered a different question than the one asked. Fix: exam technique — checking routines, underlining what's asked, slowing the final step.
Treating all three with "more revision" wastes your time on two of them. The category column is what tells you, at a glance, which family is actually costing you marks in each subject.
The review routine
A log nobody reviews is a graveyard. The routine that works, and takes under an hour a week:
- Logging (daily, 1 minute per mistake). The moment a mistake happens, it goes in — question, answer, one-line why, category. Never batch this to "later"; later never comes and the context is gone.
- Weekly review (20–40 minutes). Re-attempt every unresolved entry from scratch, no notes. Right without help → tick resolved. Wrong again → it stays, and that entry is now flagged as a genuine weak point worth dedicated study time.
- Pre-exam sweep (the payoff). In the final weeks before an exam, the log is your revision list. Every entry is a question that took marks off you specifically — no textbook or shared revision guide can match that relevance.
Common ways error logs die
- Too much friction per entry. If logging a mistake takes five minutes of copying and formatting, you'll stop within a week. Photos and screenshots, not transcription.
- No categories. Without them the log is a scrapbook. You can't spot patterns in prose.
- No re-attempts. Reading your old mistakes feels like review but trains nothing. The value is in re-doing the question cold.
- Wrong tool. A paper notebook is fast to write but impossible to search or analyse; a spreadsheet is analysable but miserable for maths working and diagrams. We compare the options honestly in notebook vs spreadsheet vs app.
Keeping the log automatically
Everything above works with a pen or a spreadsheet — students were running this method long before software. The part that makes people quit is the clerical work: capturing the question, writing the diagnosis, filing it under a topic, remembering to re-test.
That clerical layer is what errorboard automates. It watches while you study (only when you ask it to), captures the mistake with a screenshot or photo, writes the what-went-wrong analysis, categorises it, and files it into a per-topic automatic error log that quizzes you on old entries until you stop getting them wrong. It's free to start on Windows, with the notebook and photo studio on iPad and the web.
But tool or no tool: start the log. Two weeks from now, the pattern in your own mistakes will tell you more about where your marks are going than any amount of re-reading.