How to Turn Practice-Test Mistakes Into Study Notes

Most candidates review a practice test carefully, nod at each explanation, feel the gap close — and have lost the lesson by the following weekend. The review was real; the record of it never existed. What separates candidates who climb between mocks from those who repeat the same misses is not sharper analysis, it is a written system: an error log that turns each wrong answer into a note you can retrieve, requiz and eventually retire.

This article is about that system only — the note format, where to keep it, and the cadence for reviewing it. The upstream step, working out why each answer was wrong straight after a test, is its own workflow, covered in how to review your mistakes after a practice test.

What an error log is (and what it is not)

An error log is a running list of every practice question you got wrong or guessed, rewritten as a short, self-testing note. It is not a copy of the question. Copying questions verbatim trains you to recognise that item — a habit that quietly becomes answer memorisation, a trap with fixes of its own described in how to avoid memorising practice-test answers. The note should capture the rule or concept the question tested, phrased so it would help you on any question about that topic, not just the one you missed.

There is solid reason to make the notes self-testing rather than summary-style. Roediger and Karpicke's 2006 work on the testing effect showed that practising recall produces stronger long-term retention than restudying, and Dunlosky and colleagues' 2013 review rated practice testing among the highest-utility learning techniques while rereading rated low. A note you can quiz yourself from is a tiny practice test; a note you can only reread is just more material.

The five-field note format

Whether you use a spreadsheet, a notes app or a paper notebook, give every mistake the same five fields. Consistency is what makes the log reviewable months later.

1. Objective/domain. The exam objective the question maps to (e.g. "Domain 2 — Azure architecture and services"). This is the field that later tells you where your errors cluster; it is also how you find the right section of the official guide to reread.
2. The trigger. One line describing the situation the question presented, stripped of its specifics: "asked to choose the most cost-effective storage option", "scenario involved a service I confused with a similar one".
3. The rule. The generalised fact, distinction or decision rule you were missing, in your own words. Writing it yourself matters — if you cannot phrase the rule without the answer explanation open, you have found a second gap.
4. Why I missed it. One of a small set of tags: knowledge gap, misread the question, confused two options, ran out of time, careless. Tags let you see patterns — a log full of "misread" entries prescribes a different fix from a log full of knowledge gaps.
5. Self-test prompt. A one-line question you can cover the rest of the note and answer from memory: "When does option A beat option B for cost?" This field is what turns the log from an archive into a revision tool.

A complete entry takes two to three minutes. If you are writing five-minute essays per miss, you are transcribing rather than distilling; if entries take thirty seconds, you are probably copying the explanation instead of rephrasing it.

Where to keep it

The best home for an error log is whichever tool you will actually reopen, but two features are worth insisting on: the ability to filter or sort by objective, and the ability to hide the answer for self-testing. A spreadsheet does both (one row per error, columns for the five fields, answer column collapsed during review). Flashcard apps work well too, with the self-test prompt on the front and the rule on the back — though flashcards suit some material better than others, a trade-off examined in flashcards vs practice tests. A paper notebook works if you leave a margin for tick marks; what matters is one log, not scattered notes across three tools.