# How to Make a Mistake Log for Studying

> Turn missed practice questions into a short, source-checked mistake log. Use it to identify error patterns, choose the next study task, and test the fix.

- Canonical page: https://brainden.app/blog/how-to-make-a-mistake-log-for-studying
- Published: 2026-10-09
- Author: BrainDen Team
- Category: Study Methods
- Reading time: 9 min read

To make a **mistake log for studying**, record a missed question, what you actually did, why that answer failed, the checked correction, and a new task that tests the same idea. Keep a link or page reference to the course source. Reattempt the task without looking at the correction. When you can solve a different version and explain why, mark the entry resolved.

A mistake log is a decision tool, not a collection of wrong answers. It helps you distinguish a concept you do not understand from a method you know but applied poorly. This guide gives you a small template, two worked examples, and a review routine that works on paper or in a digital study library.

## What belongs in a useful mistake log?

Each entry should answer six questions:

1. **What was the task?** Name the topic and question type. Keep a question number or source reference.
2. **What did I do?** Record your answer or the step where your reasoning changed direction.
3. **Why did it fail?** Identify the cause from evidence, not from frustration.
4. **What is the checked correction?** Use the answer key, instructor feedback, or assigned material.
5. **What will I try next?** Choose one practice task that tests the weak point.
6. **Did the fix hold?** Record a later attempt on a new or changed question.

The goal is to make the next study action obvious. A row that says `careless mistake` and nothing else does not tell you what to practice. A row that says `I used the total rather than the change in total when calculating the rate` does.

[Princeton's guide to analyzing problem-solving exams](https://mcgraw.princeton.edu/analyzing-your-problem-solving-exam) asks students to examine whether errors came from reading, preparation, or problem-solving. [Virginia Tech's exam-wrapper guidance](https://teaching.vt.edu/teachingresources/adjustinginstruction/exam-wrappers-and-test-analyses.html) also recommends looking for patterns and changing future preparation. A mistake log turns that reflection into an entry you can revisit.

## Start with one practice set, not your whole semester

Choose a recent practice quiz, problem set, returned assessment, or self-test. Begin with three to five errors that seem important. You can add more later. Do not copy every question into a new document just to make the log look complete.

Use the original task under the access rules that apply to it. If your instructor restricts sharing or copying, record a question number and your own description. Do not upload or publish a protected exam or answer key. If you cannot review a returned question, ask your instructor which topic or skill you should practice.

Before you read the solution, mark your confidence beside each answer when possible: `sure`, `unsure`, or `guess`. A confidently wrong answer can signal a different problem from a question you knew you could not solve. Use confidence as a clue, not as a grade.

[Cornell's practice-exam guidance](https://lsc.cornell.edu/how-to-study/studying-for-and-taking-exams/what-to-do-with-practice-exams/) recommends using practice exams under realistic conditions and then reviewing what you learned from them. Try the questions closed-note first. Otherwise, the log may measure how well you can find an answer, rather than what you can do independently.

## Use a compact mistake-log template

Copy this format into a notebook, spreadsheet, or study note:

```text
Course and topic:
Practice source and date:
Question number or short task description:
My answer or failed step:
Correct answer and source location:
Cause of error:
One next practice task:
Next attempt date and result:
Status: open / needs clarification / resolved
```

The `source location` can be a textbook page, lecture slide, timestamp, worked solution, or instructor comment. It makes the correction checkable. If two sources disagree, do not choose the nicer explanation. Record the disagreement and ask for clarification.

Keep one entry per **underlying error**, not necessarily one per lost mark. Three wrong answers caused by the same mistaken rule may need one entry with three question references. One question that exposes two separate gaps may need two entries.

For longer courses, add a consistent course and topic label. You can then find every error about a concept without moving all of your original notes into an `Errors` folder. In BrainDen, [links and backlinks between notes](/features/linked-notes) can connect an error note to the relevant lecture or reading while each note stays in its course folder. That is a way to preserve context; BrainDen does not provide a dedicated automatic mistake-log feature.

## Diagnose the cause before you choose a fix

Use a few specific categories. The category should describe what went wrong and point to a different next action.

| Cause | What you might observe | Better next task |
| --- | --- | --- |
| Concept gap | You cannot explain the rule or idea in your own words | Revisit the source, then explain it without notes |
| Retrieval gap | You recognize the answer but cannot produce it alone | Use a closed-note question after a delay |
| Method gap | You know the idea but choose the wrong procedure | Compare two problem types and state when each method applies |
| Application gap | You know the definition but miss a new case | Work through a different example and explain each choice |
| Reading error | You miss a condition, unit, or command word | Underline the condition before solving a new question |
| Time or sequence issue | You can solve it later but not under the test limit | Practice the full sequence under a realistic time limit |

These are working labels, not diagnoses. An error can have more than one cause. For example, a student may misread a unit because they do not understand what that unit measures. Use the checked solution and your own written steps to decide what needs work.

Do not call every wrong answer `careless`. That word hides the cause. State the visible action instead: `I copied 0.05 as 0.5`, `I did not compare the two definitions`, or `I started the calculation before reading the final condition`.

## Write a correction that you can test

First, find the correct answer in a reliable source. Then explain why your answer did not meet the task. A copied answer key is useful for checking, but it does not show whether you understand the difference.

Write the correction in three parts:

1. **Rule or idea:** State the principle in one or two sentences.
2. **Boundary:** Name the condition that changes the answer.
3. **Check:** Give yourself a new question or prediction.

For a physics problem, the boundary might be a sign convention or a change in units. For a history question, it might be the difference between a cause and evidence for that cause. For a short-answer biology item, it might be a condition that makes a mechanism possible.

If an AI tool drafts the correction, compare it with the assigned source and the instructor's marking rule. A fluent explanation can still use the wrong assumption. Keep the verified version in the log and label unresolved points clearly.

## Worked example: a missed calculation

Suppose an economics student answers a practice question about percentage change. They divide the change by the final value. The checked solution divides it by the starting value.

```text
Course and topic: Economics, percentage change
Practice source: Week 4 practice set, question 6
My step: Change divided by final value
Checked correction: Change divided by starting value
Source: Lecture 4 slide 18 and worked example 2
Cause: Method gap; I did not identify the reference value
Next task: Solve two new examples with different starting values
Later result: Explain the denominator choice before calculating
```

The useful part is not the corrected number. It is the decision about the denominator. On the next attempt, the student should say what the reference value is before doing arithmetic. If they still pick the final value, the entry remains open.

For a calculation-heavy course, a mistake log can link to a separate worked solution. Keep the log short enough to scan. The full derivation belongs in the source note or solution, where you can check each step.

## Worked example: a weak written answer

Suppose a history student is asked why a policy changed. Their answer names an event but does not explain how that event affected the decision. The marking guide asks for a causal link supported by evidence.

The entry should not say only `Need more detail`. It could say:

```text
Task: Explain why the policy changed
My answer: Named the event but skipped the mechanism
Checked correction: Connect the event to the decision and cite evidence
Source: Assigned reading, pages 42-45; seminar feedback
Cause: Application gap in causal explanation
Next task: Write a three-sentence answer for a different policy
Check: Does each sentence have a clear role: claim, mechanism, evidence?
```

The student can compare the new answer with the rubric and ask a tutor to check the causal step. This is more useful than memorizing the first model answer. It practices the structure needed for another question.

For more about building questions from checked material, see [how to make a quiz from study notes](/blog/how-to-make-a-quiz-from-study-notes). That guide covers question design. The mistake log here decides **which** question to make next.

## Review the log in short cycles

After each practice set, add only the errors that change what you will study. Before the next study session, scan open entries and select one or two. Do the new task closed-note. Check the result against the source. Record what changed.

Use these status rules:

- **Open:** You have identified the error but have not tested a correction.
- **Needs clarification:** The source, answer key, or feedback does not explain the difference.
- **Resolved:** You can handle a different version and explain the reason without the correction in view.

Do not close an entry just because you can repeat the exact old answer. Change the numbers, context, wording, or example. For a concept question, explain it to someone else or write an answer from memory. For a method question, decide which method applies before calculating.

This mirrors a useful part of an exam wrapper: review the error, adjust preparation, and revisit the adjustment before the next assessment. [Boston University's exam-wrapper examples](https://www.bu.edu/excellence/resources/exam-wrappers/) show students reviewing errors and planning changes after a quiz. A private mistake log lets you apply that cycle to practice work between graded assessments.

If the same cause appears often, change the study task. More rereading may not fix a retrieval gap. More flashcards may not fix a method choice. If the error remains unclear, bring the original question, your step, and the source reference to office hours or a study group.

## Avoid making the log another task to maintain

Your log has failed if you spend longer formatting entries than testing corrections. Use plain text or a small table. Do not add charts, elaborate tags, or a separate file for every question unless they solve a real finding problem.

Also avoid these traps:

- **Copying full solutions without your failed step.** You lose the reason the task was difficult.
- **Logging only low scores.** A correct guess or a confident but fragile answer may also need review.
- **Treating all errors as memory failures.** Some tasks require interpretation, method choice, or careful reading.
- **Repeating the same question until it feels familiar.** Test the principle with a changed example.
- **Sharing protected material.** Keep question references and your own explanations when the original assessment has restrictions.

A good log should become shorter as you resolve problems. Archive old entries when they no longer guide your next study choice. Keep the source links so you can reopen the explanation if the same error returns.

## Make the next attempt the measure of progress

The practical sequence is simple: attempt, inspect, explain, check the source, choose a new task, and reattempt later. Your score tells you where to look. Your next independent answer tells you whether the correction worked.

Start with one practice set and three important errors. Give each entry a cause, a checked source, and one new question. Then close the log and try that question from memory.

If you want to build focused practice from a checked course note, [turn your notes into a BrainDen quiz](/tools/turn-notes-into-quiz). Check each generated answer against your source before you use it to resolve a mistake.

## Use BrainDen

Apply this workflow to your own material in the [BrainDen web app](https://learn.brainden.app), or install BrainDen for [iPhone and iPad](https://apps.apple.com/us/app/brainden-ai-study-companion/id6757434859) or [Android](https://play.google.com/store/apps/details?id=com.brainden.app).