The Error Log Method for Exam Prep

An error log is a running record of every practice question you miss, written down with the topic, the reason, and a fix. Instead of closing a mock and moving on, you capture the miss while the reasoning is fresh, then act on the pattern later. Over a full prep cycle the log becomes a map of your weak spots, ranked by how often each one repeats.

If nothing forces you to name the reason for a miss, the same question type is free to come back weeks later unchanged. A log fixes this by turning a scattered pile of wrong answers into one file you review on a schedule. This guide covers what to record for each miss, how to sort errors into three reason tags, how to turn the log into a weekly drill plan, when to reopen it before a full mock, and when a fixed entry earns retirement.

What to Record for Each Missed Question

Write down five fields for every miss, right after you review it, not days later. A reason reconstructed later from memory is a guess, while one written on the spot records what went through your head during the question. Keep each field to a single line so logging stays fast enough to survive a long prep cycle. Use the five fields below as your column headers.

After you finish a mock, practice test, or drill with us, the results screen flags every question you missed and offers a review option built around them, plus a filter showing only the questions you got wrong. Each reviewed question carries a correct or incorrect badge, your answer, the correct answer, and a written explanation when one exists. Between them those items feed four of the five fields in the table above: the topic, your answer, the correct answer, and the evidence behind your reason tag. The fix stays yours to write, and so does the final call on which reason applies.

We also keep a private note field on each question, capped at 5000 characters. Notes save on your device always and sync to your account once you sign in, so a note written during mock review is still there when you open the drill built from it. Use the note to hold your reason tag and your fix in one place. Keep the master log outside the app as well, in a spreadsheet or a notebook, because sorting and counting across topics is where the method pays off.

Tagging Errors: Content Gap vs Careless vs Timing

Sort every miss into exactly one of three reason tags. A question rarely fits two tags cleanly, and forcing a single choice keeps the log honest about what went wrong. Our player stores no reason field of its own: correct or incorrect state and your private note are all it holds, so the tagging step lives in your own log. The three tags below split misses by cause, not by section.

Content Gap

A content gap means you did not know the rule, formula, or vocabulary the question tested. You read the explanation and learn something new, not something you already knew and rushed past. Content gap misses point straight at the topic to drill next.

Careless Mistake

A careless mistake means you knew the rule but slipped: misread the question, picked the wrong choice by accident, or skipped a step you know well. You reread the question after seeing the answer and think, I knew this. Careless misses point at process, not knowledge, so the fix is a habit change, for example reading the full question stem before looking at the choices.

Timing Pressure

Timing pressure means you rushed the question because time was running low, or spent too long on it and later questions suffered. Check your pace notes or section time, if you log it, before tagging a miss timing pressure. Timing misses point at pacing practice on full mocks, not content review.

Turn the Log into a Weekly Drill Plan

Once a week, open the log and count how often each topic shows up under a content gap tag. Rank the topics by count, highest first, and set aside the one-off misses at the bottom of the list. The top two or three become your drill targets for the week. Work the plan below in order.

1. Sort log entries by topic and count content gap tags per topic.
2. Pick the two or three topics with the highest count.
3. Choose a drill level, easy, medium, or hard, based on your current accuracy on the topic.
4. Run the drill before your next full mock, then log any fresh misses under the same topic.
5. Drop a topic from the plan once its content gap count stops growing.

Our tests come in three kinds: full mocks, section practice, and drills. Drills carry a level of easy, medium, or hard and are routed to a specific topic set, so a content gap tag maps onto a drill set covering the same skill. Start one from our practice tests page, free with no signup required. Log every fresh miss from the drill under the same topic, and the running count tells you whether the gap is closing.

Review the Log Before a Full Mock

Open the log again in the day or two before a full mock, not on the morning of it. Read every open entry and mark the topics still repeating across weeks. Leave yourself room to run one short drill on whatever repeats, because a review finding a gap you have no time to close only adds pressure. Go into the mock knowing the two or three traps you are most likely to hit.

Full mock results show a scorecard for each section, with a raw score and, where the exam supports it, an estimated scaled score. We label the scaled number as an estimate, and your official score is not guaranteed to match it. Read the estimate next to your log rather than on its own: a low section score paired with the same topic repeating as a content gap points at one clear priority. Treat the section as your main target for the next study block.

Space your reviews instead of stacking them into one sitting the night before. Our guide on spaced repetition for exam prep covers how spaced reviews hold recall better than a single re-read. Pair the two methods: the log tells you what to review, spacing tells you when. Two short passes over the log across a week beat one long pass on the last evening.

Keep the mock itself under real conditions once the review is done. Our guide on how to take a practice test properly covers timing, breaks, and section order. Running the mock inside a routine mirroring test day keeps your timing tags honest, because a paused or split mock hides pacing problems. Log the misses from it in the same session, while the reasoning is still with you.

When to Retire a Resolved Entry

Not every logged miss deserves a permanent spot in the file. An entry earns retirement once the fix holds under retest, not once you feel better about the topic. Retiring entries keeps the weekly count meaningful, because fixed entries left open inflate the topic ranking and send you back to skills already handled. Set one retirement check into the same weekly session where you build the drill plan.

Retest a resolved topic before you retire it. Opening a test with review missed active on our player launches a replay deck built only from the missed questions of a prior attempt. Finishing the replay clears fixed items from the stored missed list without touching the original attempt's stats, so your recorded score stays intact. Use the replay as the first of two checks on any fix.

Retire an entry once you answer the same skill correctly across two separate reviews, not on the immediate retry alone. A single correct retry proves short-term recall of an explanation you read minutes earlier. A repeat success in a later session proves the fix held. Move retired entries to a separate part of the log instead of deleting them, so you keep the record of what used to go wrong.

Build the log from real attempts rather than from memory. Run a full mock or a topic drill on our practice tests, review the flagged misses on the results screen, and copy the fields into your log in the same session. Practice is free, and no signup is required.

Sources

• 10exam Practice Tests