How to build an error log that actually changes your score

Why a log beats a score

A percentage tells you how you did. It does not tell you what to do on Monday. Two people can both score 62 percent for entirely different reasons: one lacks knowledge of fluids, the other reads stems too fast. Their next weeks of study should look nothing alike.

An error log forces the question that matters: why did I miss this one? After a few weeks it also shows patterns you would never spot by feel.

What goes in the log

Keep it light, or you will stop. A spreadsheet or a notebook with these columns is enough.

• Date and source, for example “set 14, tutor mode”.
• Topic or domain.
• What you chose and what was correct, in a few words.
• Cause of the miss (see the next section).
• The rule: one sentence in your own words that would have got you the answer.
• Card made? Yes or no.
• Date to revisit.

Four causes of error

Label each miss with one cause.

1. Knowledge gap: you did not know the fact or principle.
2. Misread: you answered a different question from the one asked, for example missing “first” or “not”.
3. Rushed: you knew it but went too quickly or changed a correct answer.
4. Guess: you had no idea and picked one, and it was wrong. A lucky correct guess belongs in the log too.

Two example entries

These are invented to show the format, not real exam items.

Entry one. Topic: fluids. Chose: give a bolus. Correct: check the pulse and blood pressure before deciding. Cause: rushed. Rule: assess before intervening, unless the stem says the patient is already peri-arrest. Card: no, this is a technique rule. Revisit: in one week.

Entry two. Topic: medication safety. Chose: the first drug listed. Correct: the one with a high-risk label. Cause: knowledge gap. Rule: know the high-alert drug classes. Card: yes, one card per class. Revisit: in three days.

The weekly review

Once a week, spend 20 to 30 minutes with the log. Count the causes. If most of your misses are misreads, your problem is technique, and more content will not fix it, so read the single best answer guide. If most are knowledge gaps, group them by topic and study the largest group first. If many are rushed, practise pacing in timed sets.

Then pick the three most repeated errors and write a rule for each at the top of the log. Read those three rules before every session for the next week.

Turning entries into cards

Not every entry needs a card. Knowledge gaps about a discrete fact do. Technique errors do not: put those on a rules page instead. A card from a log entry is usually a better card than one copied from a textbook, because it is aimed at a gap you actually have. See the flashcard writing rules.

Setting it up in ten minutes

You can start today with nothing more than a spreadsheet. Create columns for date, source, topic, what I chose, what was right, cause, rule and revisit date. Freeze the top row. Add a drop-down list for cause with the four options, so that you spend no thought on labels.

Create a second tab called “Rules” where you will paste the best rules each week, grouped by topic. This tab becomes the page you read in the last week before the exam. Add a third tab for counts, with a simple table of how many errors of each cause you logged each week.

Do not decorate it. A log that is pleasant to look at but takes five minutes per entry will be abandoned by the second week.

Reading the patterns after four weeks

After a month you will have 100 or more entries. Sort by topic and look at the biggest group. Sort by cause and look at the proportions. A typical log might show, for example, that a third of misses are misreads, a third are knowledge gaps clustered in fluids and calculations, and the rest are guesses. That gives you a clear plan: a technique drill, two focused topic weeks and a rule to stop guessing on questions that you can reason out.

Also look at repeats: any question or concept that appears three times. These are the points where your understanding is wrong, not missing, and they deserve a proper rewrite of your notes.

Why logs fail and how to keep yours alive

The usual reasons are that the log is too detailed, that entries are made late, or that nobody looks at it. Keep entries to one line each. Make them within five minutes of finishing a set. Put a weekly 20-minute review in your calendar as a fixed appointment. If you miss it two weeks in a row, shrink the log, for example by logging only questions you were sure about but got wrong.

What a good week of logging looks like

Suppose you do 120 questions in a week and miss 36. You log all 36 in about 80 minutes across the week. When you count, fourteen are knowledge gaps, eleven are misreads, seven are rushed and four are guesses. You decide that misreads are your biggest fixable problem, since they cost nothing to repair except attention. Your fix for the next week is to underline the question word, such as “first”, “most” or “not”, before you read the options. Your knowledge gaps cluster in endocrine, so you plan two focused sessions there.

Next week, you repeat the exercise and compare. If the misreads fall to six, the fix worked. If they do not, you change the fix, perhaps by reading the last line of the stem first.

Being honest about causes

It is tempting to label everything as “rushed” because it feels forgivable. Be strict. If you had time and still chose the wrong answer, the cause is a gap or a misread. If you answered in under twenty seconds on a question that normally takes sixty, “rushed” is fair. A log that flatters you gives you the wrong plan.

Using the log with mock exams

After a full mock, add every wrong answer to the log with the mock’s name in the source column. Because mocks are timed, you will see more rushed and misread errors than in tutor-mode sets. Compare the cause counts between the two kinds of session. If misreads and rushed errors rise sharply under time pressure, the issue is pace and technique, which you can improve with timed sets of twenty or thirty questions. If knowledge gaps rise instead, you may be tired in the third hour, which is worth knowing before exam day.

Where the log fits in your system

After each set of questions, spend two minutes per missed question on the log, while the memory is fresh. In the mock exam analysis, the log becomes your data set. Meddex performance analytics can show which domains drag your score; the log explains the why behind those numbers.

In the last fortnight, the log doubles as your revision list: re-read the rules, not the whole question bank.

Frequently asked questions