Feynman AI

Exam Error Log: Turn Mistakes Into a Study Plan

Build an exam error log that connects each mistake to a specific practice task. Includes a simple template, error categories, and a worked example.

Feynman AI Apps · Published

After a test, the score tells you how many marks you earned but not how to use your next study session. Copying the correct answers may leave the original difficulty untouched. An error log helps you connect feedback with an observable next step. This guide offers an editorial template inspired by exam reflection and retrieval practice; it does not predict a grade improvement or assume a particular country's exam format.

Match a likely source of error to a practice task
Possible difficultyWhat to checkPractice to try
UnderstandingCan I explain the idea and why the solution works?Revisit the explanation, then solve a different example.
RecallDid I understand the idea but fail to retrieve it?Answer a focused question without the notes.
Method or executionDid I choose the wrong method, unit, or sequence?Explain the method choice and check each step.
Question reading or timeDid I miss a condition or leave part unfinished?Practise identifying the required output in a timed set.

A practical workflow

  1. Start with evidence from the marked work

    Keep the question number, topic, your original response, and the available feedback together. Check the marking guidance where you are allowed to access it. If the reason for losing marks is unclear, ask for clarification rather than inventing the examiner's reasoning. Carnegie Mellon's guidance on post-exam reflection encourages students to review error patterns and preparation when planning future study.

  2. Record the error precisely

    Write what happened in one sentence: I used the formula without checking its conditions is more useful than I am bad at this topic. Separate a missing idea from a calculation slip or an unfinished response. A question may involve more than one difficulty, so treat the categories as prompts for investigation rather than fixed labels about your ability.

  3. Write the correction in your own words

    Explain the step or distinction that changes the answer, with a page or slide reference you can revisit. Do not copy the whole worked solution and call that understanding. If you use an AI explanation, compare it with the course source and feedback. Leave an uncertain correction marked as unresolved until you can verify it.

  4. Choose a specific next task

    Use a compact entry: question reference, topic, error, corrected reasoning, next practice task, and review date. Select one or two recurring issues for the next session. A useful task might be to explain why a method applies or compare two easily confused terms. Reread the chapter is harder to assess because it does not say what you need to do afterward.

  5. Retest with a comparable question

    After a gap, try a fresh question that uses the same concept, without the notes or the corrected solution. Check your reasoning as well as the final answer. If you still make the mistake, adjust the task and keep the entry open. If you can answer and explain it, record that result and revisit the topic as part of your normal review schedule.

Worked example

A student chooses a percentage formula correctly but uses the final value instead of the original value as the comparison base. The log records the mistaken choice of denominator, explains the role of the starting value, and assigns two new comparison questions. The later check asks the student to justify the denominator before calculating. This fictional example turns a vague calculation mistake into a practice task that can be checked.

What to check

Repeatedly solving the exact same question can make its answer familiar without showing that you can handle a new one. Keep the original as evidence, but include a comparable problem in your check. Use only questions and feedback you are permitted to keep, and follow your course's rules for exam materials.

Feynman AI

Use the study app to prepare explanations, quizzes, or flashcards for the topics your error log identifies. Verify generated answers against the course material before adding them to review.

Check the App Store listing for current language support, availability, and purchase options. A translated guide does not mean every app feature supports that language.

Open in the App Store

Frequently asked questions

What should an exam error log include?

Record a question reference, topic, specific error, corrected reasoning, next practice task, and review date. Keep a source reference when it helps you verify the correction.

Should I log every mistake from a practice paper?

You can record each missed question, then group recurring issues when planning the next session. The goal is to choose useful practice, not to spend all your study time maintaining the log.

When can I mark an error as resolved?

Record a successful check when you can answer a comparable question and explain the reasoning without the solution in view. That is evidence for this review, not a promise that you will never miss the concept again.

Sources and further reading

These sources explain the underlying methods. The workflows and examples are editorial suggestions, not evidence of results for a particular app.

Read in another language