studynotes.app

Build an Exam Error Log from Practice Papers

Turn marked practice papers into a concise error log. Record the cause, a checked correction and a fresh question to test the improvement later.

A structured study notebook beside corrected practice work and a retry card

An exam error log connects a wrong answer to the next learning action. It is most useful when it explains what went wrong and gives you a way to check whether the correction worked. Copying a model answer into a notebook can preserve information without showing that you can use it.

Start with one marked practice paper and a reliable mark scheme, worked solution or teacher explanation. Keep the original question reference so that you can return to the full context without copying every page.

Record an observable error

Write the question reference and the step where your response stopped matching the task. Use a specific description such as I used the diameter as the radius, rather than I am bad at geometry. The first description identifies something you can check on the next attempt.

Separate a missing fact from a wrong method, an arithmetic slip, a misread instruction or an incomplete explanation. These categories are working labels, not fixed diagnoses. If you cannot explain the cause, mark it as uncertain and ask for clarification before writing a confident correction.

Keep the correction tied to a source

Record the correct principle in your own words and add the page, question or source link that supports it. If a mark scheme gives only a final number, use the course explanation to understand the method. Do not invent intermediate reasoning simply to fill the log.

EEF's feedback guidance emphasizes planning how learners will use feedback. An error log can support that action when each entry leads to a new attempt. The log format here is a practical suggestion, not a claim that a particular template has been experimentally validated.

Work through a small example

Suppose a circle has diameter 10 cm and the question asks for area. A response of 100π square centimetres used 10 as the radius. The correction is to identify the radius as half the diameter: 5 cm. The area is then π × 5² = 25π square centimetres.

A useful entry says: I treated diameter as radius; label the given length before substituting; area uses the radius squared. The follow-up question can use diameter 14 cm. Its radius is 7 cm and its area is 49π square centimetres. A changed value tests the correction more clearly than copying the original result.

Write a cue that tests the weak decision

Create a short question such as What must I check before using a given circle length in the area formula? Put the answer out of sight. The cue should target the missing decision while the full worked problem remains available in your notes.

For an essay, the cue might ask which evidence supports a particular claim or what a command word requires. Avoid turning every paragraph into a flashcard. Some weaknesses need a complete comparison paragraph or a timed explanation, so make that the follow-up task.

Retry after the correction is no longer in view

Close the source and attempt a new question using the same principle. Record the result and any remaining difficulty. A correct immediate repeat can help establish the step, but a later independent attempt gives different information about what you can retrieve.

Set a realistic review date and return to a small selection of entries. Keep the failed attempt as well as the correction so you can see whether the same error recurs. If it does, change the practice task or revisit the prerequisite instead of merely adding another copy of the answer.

Keep the log small enough to use

After a paper, prioritize recurring errors, prerequisite gaps and mistakes that affected substantial parts of a response. Record a minor isolated slip when it suggests a useful check, but avoid spending the whole study session rewriting the paper.

Use the template below in the Study Notes Workspace or in your own document. The note-to-quiz tool can help draft prompts from concise notes; check the generated wording and answers before using them. Export a backup after substantial edits, and keep the original practice material available until the review is finished.

Keep the original attempt beside the explanation

A polished correction can hide the reason the original answer failed. Preserve enough of your first attempt to see the decision that caused the problem. For a calculation, that might be one substituted value or a missing unit. For an essay, it might be the sentence that made a claim without evidence. You do not need to copy every line when a question reference and one short excerpt identify the issue.

Use separate spaces for what you wrote, what the source explains and what you will try next. This prevents the corrected answer from being mistaken for the response you produced independently. When working with a partner, compare the reasoning before sharing a model response. If feedback changes your interpretation of the question, record that change explicitly. The log then preserves the learning decision instead of presenting a false picture in which every original attempt was nearly correct.

Turn an essay comment into an observable revision

Suppose feedback says that a paragraph describes two sources but does not compare them. A weak log entry simply repeats compare more. A useful entry identifies the missing action: state one shared issue, explain the two positions on that issue and support the contrast with evidence from each source. Keep the course's actual criteria beside the entry, because comparison tasks differ across subjects.

For the follow-up, write a short comparison using a different pair of approved sources. Check whether the paragraph makes a relationship explicit instead of placing two summaries next to each other. If evidence is missing, revise that part and identify where the supporting material came from. This follow-up is an application task, so a flashcard containing a definition of comparison is not enough by itself. Record both the useful cue and the paragraph-level practice that demonstrates the skill.

Review patterns across several practice papers

After a few papers, group entries by the action they need. Several unit errors may suggest a final units check. Several unsuccessful explanations may suggest difficulty connecting evidence to a claim. Several questions you could not start may reveal a missing prerequisite. Use the grouping to plan a small practice task, while keeping each original question reference available.

Do not treat the group labels as permanent descriptions of your ability. Check whether the pattern remains after targeted practice and whether it appears in a new context. A topic that improves can move out of the active log while an unresolved question stays visible. Before an assessment, use the log to select a manageable set of representative attempts rather than rereading every correction passively. Afterwards, add only the new evidence that changes your next action. This keeps the record useful as the course progresses.

Copyable planning template

Paper, date and question:
My original response:
Observable error:
Likely cause or uncertainty:
Correct principle in my words:
Supporting source or explanation:
Recall cue:
Fresh practice question:
Next attempt date:
Result without notes:
Next action:

Frequently asked questions

Should I log every lost mark?

Prioritize entries that lead to a useful action: repeated mistakes, important prerequisites and misunderstood instructions. A shorter log that you revisit is more useful than a complete transcript you never practise.

What if I disagree with the mark scheme?

Record the uncertainty and compare the course's criteria with your reasoning. Ask the instructor about the specific step. Keep a provisional note instead of treating an unverified answer as the correction.

When can I stop reviewing an entry?

Look for independent success on a later, changed task and whether the idea remains relevant to the course. Archive resolved entries so they stay available without dominating every session.

Sources and further reading

Related tools

Related guides

Your notes stay in this browser. Export a backup to keep a separate copy. Sitemap