The log is hard to review
Use this if entries are long, fields are excessive or the log is easy to abandon.
Use the simplified templateMistake review tool
Mistake Log Template for Medical Exams
A useful mistake log should help you identify error patterns, choose small repairs and retest similar tasks — not create a large spreadsheet that becomes another study burden.
Many candidates record mistakes but do not use the log to change future performance. The goal is to make each entry answer one practical question: what should I do differently before this pattern appears again?
Quick orientation
Start by making the log smaller and more action-focused.
A mistake log works when it helps you see recurring patterns, choose repairs and schedule retests.
The log records topics but not error types
Use this if entries say “cardiology” or “renal” without explaining why the mistake happened.
Use error typesThe log does not create retests
Use this if entries accumulate but similar mistakes return.
Review the log weeklyMistake log template
Use a mistake log that points to the next action.
The mistake log should record only the information needed to identify the error pattern, choose a repair and decide when to retest it.
Field
Question to answer
Purpose
Date
When did the mistake happen?
Helps review timing and progress.
Source
Where did it come from?
Practice question, case, station, viva or recall task.
Topic
What broad area was tested?
Keeps the entry searchable.
Task
What were you asked to do?
Identifies the decision or performance task.
Key clue
What information should have changed the answer?
Shows what to notice next time.
Error type
What kind of mistake was it?
Points to the right repair.
Repair
What is the smallest useful fix?
Turns the entry into action.
Retest
How will you check the pattern later?
Prevents one-off review.
Status
Open, scheduled, improved, recurring or archived?
Keeps the log current.
If the log becomes too hard to maintain, remove fields before adding more.
Start here
Which mistake log problem sounds most familiar?
Start with the pattern that makes your mistake log least useful.
My mistake log is too large
Too many entries, too many fields and too much detail make the log hard to review.
Use essential fieldsI record mistakes but do not improve
Entries accumulate, but similar errors keep returning.
Use the 2-minute entryI only record the topic
The log names content areas but not the decision error.
Add error typesI copy long explanations
Entries become paragraphs and are hard to scan later.
Leave out low-value detailI never review the log
Entries accumulate but recurring patterns are not identified.
Use weekly reviewI do not know when to remove items
Old, easy or low-impact items clutter the active log.
Use archive rulesA mistake log is not a storage system.
It is tempting to use a mistake log as a place to store explanations, topic summaries and every detail from a missed question.
That usually makes the log harder to use. A useful mistake log is a decision tool. It should make the next study action clearer.
If the log does not help you decide what to do next, it is not yet doing its job.
Why mistake logs become overwhelming.
Mistake logs usually become overwhelming when candidates add too much and retire too little.
Too much recorded
Every missed question becomes a long entry.
No pattern named
The log stores detail rather than diagnosis.
No retest plan
Entries do not return later.
Performance unchanged
The same error repeats.
A mistake log needs rules for adding items and rules for closing items.
What should you include in a mistake log?
The best mistake log entries are short, diagnostic and action-focused.
What was required?
What information mattered?
What kind of mistake was it?
What will be changed?
How will this be checked later?
Open, retested, recurring or archived?
The essential fields are task, clue, error type, repair and retest.
What should you leave out of a mistake log?
A mistake log becomes less useful when it stores too much detail.
Usually leave out
- full copied question explanations
- long textbook summaries
- beautiful rewritten notes
- every minor fact
- low-yield details
- errors already fully understood
Usually keep active
- repeated errors
- high-risk decisions
- unclear reasoning patterns
- items with no retest plan
- mistakes that affect marks or safety
- confidence, timing or structure patterns
If an entry does not point to a next action, it may not belong in the active mistake log.
Common error types to use in your mistake log.
Error types help you see whether mistakes are mainly about knowledge, reasoning, stems, distractors, time pressure or confidence.
Error type
What it means
Likely repair
Knowledge
The required content was not known.
Short relearning and active recall.
Retrieval
The content was known later but not accessible during the task.
Timed active recall.
Reasoning
Facts were known but linked incorrectly.
Why-this-not-that review.
Stem
A key detail, qualifier or instruction was missed.
Stem-clue practice.
Distractor
A plausible wrong option pulled attention away.
Contrast prompts.
Timing / confidence
The error involved rushing, getting stuck, changing or guessing.
Timed sets and confidence tracking.
Structure
The answer was correct in content but incomplete or poorly organised.
Answer structure practice.
Use enough error types to identify patterns, but not so many that the log becomes hard to complete.
Simple first repair
Use a 2-minute mistake log entry.
If your mistake log takes too long, use a shorter entry process.
Task, clue and error type
Write what was required, what clue mattered and what kind of mistake occurred.
Repair, retest and status
Write the smallest repair, the retest plan and the current status.
Example output
Task: choose the safest next step. Key clue: patient unstable. Error type: priority / safety. Repair: practise immediate vs delayed management decisions. Retest: five similar acute management questions tomorrow. Status: open.
A short entry that leads to a retest is better than a long entry that is never used.
How to use the mistake log each week.
A mistake log becomes useful when it is reviewed for patterns, not just filled in after mistakes.
Look for repeated error types
Choose the top one or two patterns
Choose the smallest repair
Schedule recall, review or practice
Archive improved items
Watch for recurring patterns
The weekly review should answer: what pattern is most worth repairing next?
How to connect the mistake log to active recall.
Some mistakes reveal knowledge or retrieval gaps. Those should become short active recall prompts.
Use active recall when
- the fact was forgotten
- the concept was confused
- the answer was known later but not retrieved
- a criterion, pathway or threshold keeps returning
- the mistake reflects slow recall
Active Recall for Medical Exams
Use this if recurring gaps need retrieval practice.
Read Active RecallDo not turn every mistake into a flashcard. Turn recurring, important or forgotten material into recall prompts.
How to connect the mistake log to spaced review.
Some mistakes need to return later. Spaced review helps prevent repaired errors from disappearing again.
Use spaced review when
- the mistake is important
- the same error occurred more than once
- the topic fades between sessions
- the repair needs to be retested later
- the mistake involves high-risk safety or priority decisions
How to Build a Spaced Review System
Use this if repeated errors need scheduled return.
Read Spaced ReviewA mistake log and spaced review system work together: the log identifies the pattern, and spaced review brings the pattern back.
When should you drop or archive a mistake log item?
A useful mistake log should not keep every item active forever.
Archive when
Keep active when
Reason
The item has been retested successfully.
The item has not been retested.
Retesting confirms whether the repair worked.
The error has stopped recurring.
The same error keeps returning.
Recurring patterns deserve active attention.
The item is low-yield or one-off.
The error is high-risk or exam-changing.
The log should protect high-value repair time.
The entry no longer changes future practice.
The pattern affects performance repeatedly.
Active entries should guide action.
Archiving is part of keeping the mistake log usable.
What useful mistake log review looks like.
Useful mistake log review checks whether entries are changing future performance.
Mistake happens → long note written → log grows → no pattern reviewed → same error repeats
Mistake happens → error type named → repair chosen → retest scheduled → pattern reviewed weekly → item archived when improved
Review progression
- Does this entry name the task?
- Does it identify the key clue?
- Does it classify the error type?
- Does it choose a repair?
- Does it schedule a retest?
- Has the same pattern appeared before?
- Should this become active recall, spaced review or practice?
- Can this item be archived?
A mistake log is working when it makes repeated errors easier to see and easier to repair.
Common mistake log problems.
These are common reasons mistake logs become large without improving performance.
How to Review Mistakes
Use this for the broader mistake review method.
Read this guideHow to Review Practice Question Mistakes
Use this for question-specific review.
Read this guideDoing Practice Questions but Not Improving
Use this if more questions are not changing results.
Read this guideActive Recall for Medical Exams
Use this if repeat gaps need retrieval practice.
Read this guideHow to Build a Spaced Review System
Use this if recurring items need scheduled return.
Read this guideLosing Marks Despite Knowing the Diagnosis
Use this if knowledge is present but not converting into marks.
Read this guideWhat this page is — and is not.
This page is about
Building a simple mistake log, choosing useful fields, classifying errors, keeping entries short, scheduling retests, reviewing weekly patterns and archiving improved items.
This page is not about
A complete spreadsheet system, a full medical exam study plan, a full question bank strategy, copying proprietary explanations or guaranteeing exam outcomes.
This page may help if…
This page is for candidates who want a mistake log that is simple enough to maintain and useful enough to change future performance.
- You keep a mistake log but rarely review it.
- Your mistake log is too large.
- You copy long explanations into your notes.
- You record topics but not error types.
- You do not know what fields to include.
- You repeat the same mistakes despite logging them.
- You do not connect mistakes to active recall or spaced review.
- You do not know when to archive old mistakes.
What this page helps with — and what usually needs individual planning.
This page gives a public framework for building a simple mistake log. It does not replace a personalised review of your exam format, question bank performance, recurring error patterns, confidence habits, study schedule and available preparation time.
What this page helps with
Choosing mistake log fields, classifying error types, keeping entries short, choosing repairs, scheduling retests and reviewing weekly patterns.
What usually needs individual planning
Your specific mistake patterns, exam format, question bank strategy, topic priorities, confidence habits, review workload and repair sequence.
If your mistake log is growing but not improving performance, a 1:1 session can help simplify the system and identify what should be repaired first.
Common questions
Questions about using a medical exam mistake log.
What should I include in a medical exam mistake log?
Include the task, key clue, error type, repair, retest plan and status. Optional fields include topic, source, confidence rating and time pressure rating.
Should I record every mistake?
No. Record mistakes that are important, repeated, high-risk, confusing or likely to affect future performance.
Should I copy full explanations into my mistake log?
Usually no. Full explanations can make the log too large. Summarise the decision error and the repair needed.
How often should I review my mistake log?
A brief weekly review is usually more useful than only adding entries. Look for repeated error types and choose one or two patterns to repair.
How do I connect a mistake log to active recall?
Turn repeated, forgotten or important knowledge gaps into short active recall prompts.
When should I archive a mistake log item?
Archive an item when it has been retested successfully, no longer recurs, is low-yield, or no longer changes future practice.
Need a mistake log that actually changes performance?
If your mistake log is growing but not improving your answers, the next step may be to simplify the template, identify your recurring error types and connect each entry to a repair and retest plan.
