Latimer Tuition

Navigation

Latimer Tuition

Revision systems

How to Build a Revision Error Log That Turns Mistakes Into Useful Revision

Diagnose why an answer went wrong, record the right fix and retry the skill later without the solution in front of you.

Match me with a tutorFind a tutor

Editorial

  • Portrait of Robin GibbonsLead authorFounder & CEO·Latimer Tuition
  • Reviewed byHeather LatimerTutor Matching & Customer Service·Latimer Tuition
  • Published
  • Last reviewed

Current answer

What is a revision error log?

A revision error log is a short, revisitable record of meaningful mistakes from practice questions, past papers, homework, quizzes or assessed work. For each useful mistake, record what went wrong, why it happened, the correct reasoning, one specific next action, when you will retry the skill without the answer, and what happened on the retry.

Use this cycle: attempt → diagnose → correct → choose an action → retry without help after a gap → record the outcome. A list of scores or copied correct answers is not an error log because it does not change what you do next.

The Rutgers University Learning Centers page describes a related Common Error Log as a way to “evaluate why those errors were made and detect any patterns”. — Rutgers University Learning Centers

The log can support better revision when it leads to changed practice, but the template itself does not guarantee a higher grade.

Four types of mistake to diagnose

Use these as practical organising categories, not rigid boxes. The aim is to identify a cause that leads to a different next action. If two categories overlap, choose the deeper cause first.

Compare four common error types, the question to ask and the corrective action that follows.

Error typeWhat it meansAsk yourselfMatched corrective action

Knowledge gap

A fact, concept, definition, quotation, rule or piece of vocabulary was not known or could not be retrieved.

What did I need to know that I could not produce?

Relearn the small missing point, turn it into a retrieval question and test it later in context.

Method error

Some relevant knowledge was available, but the process, sequence, method choice or application went wrong.

At which step did my reasoning move off course?

Compare your work with a reliable worked method, explain why each step is valid, then solve a similar but not identical question.

Misread question

A command word, value, unit, condition, source, time period, comparison or scope was missed or misunderstood.

Which part of the task did my answer fail to respond to?

Identify the decisive wording, restate the task in plain English and practise a new question with the same demand.

Checking failure

The work contained an inconsistency that a realistic, named check could reasonably have exposed.

Which specific check would have caught this?

Create a named check: substitution, estimation, units, evidence, or matching the final answer to the exact question.

Which mistakes are worth logging?

“Look for patterns, not just a score.” — Latimer Tuition

A useful log is selective. Instead of writing “silly mistake” or “careless”, describe the observable cause and the action that could change it.

  • Log recurring errors

    Record a mistake that has appeared more than once or keeps returning after correction.

  • Log misunderstood ideas

    Include an error that exposes a missing concept, rule, definition or relationship.

  • Log errors with wider consequences

    Prioritise mistakes that lose meaningful marks, affect later steps or appear across several questions.

  • Log reusable checks

    Record patterns that suggest a named check you can use again, such as substitution, estimation, units or matching evidence to the claim.

  • Do not copy without diagnosing

    A copied question and model answer add little unless you explain why your original approach failed.

  • Do not use vague labels

    Replace “rushed”, “careless” or “exam technique” with a precise cause such as “missed the unit” or “described instead of comparing”.

  • Do not record everything

    Skip tiny one-off slips you already understand unless they begin to form a pattern. Avoid score-only entries and intentions such as “try harder”.

A simple mistake log template

Copy these headings into a notebook, spreadsheet or notes app. No format is automatically better; choose the one you can reopen and update consistently. A confidence rating is optional and only earns its place if it changes what you do next.

The minimum fields for a practical revision mistake log.

FieldWhat to recordWhy it helps

Date and source

Date, paper or task, and question number.

Lets you find the original evidence without copying the whole question.

Subject and topic

A precise label, such as “simultaneous equations: elimination”.

Makes patterns and revision priorities easier to spot.

Error type

Knowledge gap, method error, misread question or checking failure, plus a short tag if useful.

Turns a wrong answer into a diagnosis rather than a score.

What went wrong

One factual sentence describing the failure.

Separates observable evidence from self-judgement.

Correct reasoning

The missing fact, correct method or better answer structure, including why it works.

Converts feedback into knowledge you can use again.

Next-time cue

One observable instruction, such as “check units before the final answer”.

Makes the intended behaviour specific.

Retry date

A real date or named revision session.

Prevents the correction from disappearing into old notes.

Retry result

Wrong for the same reason, wrong for a new reason, correct with help, or correct unaided.

Shows whether your action worked and what should happen next.

Status

Open, improving or secure.

Keeps attention on unresolved entries while allowing fixed patterns to leave active revision.

How to build and use your revision error log

Follow the same small cycle after marked practice, a past paper, a quiz, an essay or teacher feedback. Correct the misunderstanding while reliable feedback is available, but separate that correction from the later unaided retry.

  • 1. Set up a compact log

    Create the minimum fields for source, topic, error type, diagnosis, correction, next action, retry and outcome. Keep it short enough to revisit.

  • 2. Choose a meaningful mistake

    Add an error that is recurring, important, revealing or reusable. Record where it came from so you can return to the evidence.

  • 3. Diagnose the cause

    Choose the closest category and write one factual sentence about what failed. If “checking failure” is your choice, name the check that would have exposed the problem.

  • 4. Correct it and choose one next action

    Establish the correct answer or reasoning while a reliable solution, mark scheme, teacher or tutor explanation is available. Then write one action you can observe next time. If you still do not understand the method, use teaching, a worked example and guided practice before another unaided test.

  • 5. Schedule a clean retry

    Put the solution away and retry at the next relevant revision session. If that works, use a similar but not identical task after a longer gap, then place the skill in mixed practice where the method is not announced in advance.

  • 6. Record the outcome

    Mark the entry open, improving or secure. Rediagnose a repeated error, record a new cause separately when needed, and reopen a supposedly secure entry if the pattern returns.

Worked example: a method error in maths

For a method error, record why the corrected steps work rather than copying the final answer. Explain the principle behind each step, then test it on a similar question without notes.

A complete example entry for a linear-equation method error.

Log fieldExample entry

Source

Algebra practice, question 6.

Topic

Solving linear equations.

Original error

For 3(x − 2) = 12, I divided by 3 to get x − 2 = 4, then stopped and wrote x = 4.

Error type

Method error.

What went wrong

I completed the first inverse operation but did not undo the −2.

Correct reasoning

Divide both sides by 3: x − 2 = 4. Add 2 to both sides: x = 6. Check by substitution: 3(6 − 2) = 12.

Next-time cue

After each inverse operation, rewrite the whole equation. Substitute the final value into the original equation.

Clean retry

At the next maths session, cover the correction and solve 4(y + 1) = 20 without notes. After attempting it, check that y = 4.

Outcome and status

If correct unaided, mark improving and schedule a varied equation later. If the same stopping error returns, keep it open and recheck the diagnosis.

What the log looks like in different subjects

The cycle stays the same, but the evidence and retry should match the subject. These are generic examples rather than rules for every board or qualification.

Recommendation

Science: an incomplete explanation

What went wrong: The response says that particles move faster when temperature rises but leaves out the causal link required by the taught explanation.

Likely category: Knowledge gap if the mechanism was unknown; method error if it was known but omitted.

Next-time cue: Build the explanation as a cause-and-effect chain, not a list of facts.

Later retry: Explain the relationship from memory on a fresh question, then compare it with reliable feedback.

Recommendation

Essay or source response: description instead of evaluation

What went wrong: The answer describes one position but does not weigh evidence or reach a supported judgement.

Likely category: Misread question or method error if the relevant content was known.

Next-time cue: Identify the command word and disputed claim, then write a one-sentence provisional judgement before planning.

Later retry: Plan a different evaluation task and check whether every paragraph helps answer the judgement.

Recommendation

Checking routine: name the check

What went wrong: The method was sound, but the final value or unit was implausible.

Likely category: Checking failure only if a realistic check was already available.

Next-time cue: Replace “check my work” with a named action: estimate the size, check the unit, substitute the answer, match evidence to the claim, or reread the final sentence against the exact task.

Later retry: Use the named check on a new task and record whether it catches an inconsistency.

What your retry result means

A correct answer is evidence, not proof of permanent mastery. Move an entry towards secure after successful unaided attempts separated in time, including a similar-but-not-identical or mixed-context task where appropriate. Reopen it if the pattern returns.

Use the result of each retry to choose the next revision action.

Retry outcomeWhat it suggestsNext action

Wrong for the same reason

The correction did not address the cause, or the new learning is not yet secure.

Recheck the diagnosis. Use another explanation, worked example or guided practice, then retry a suitable task.

Wrong for a different reason

The original issue may have improved, but another gap has appeared.

Record the new cause separately if it is meaningful, then match it to its own corrective action.

Correct with notes or a hint

There is progress, but the skill is not yet independent.

Mark improving and schedule an unaided attempt.

Correct unaided on the same item

The original item has been repaired, but selection and transfer are not yet tested.

Attempt a similar but not identical question after a gap.

Correct unaided on a varied item

There is stronger evidence that you can select and apply the skill.

Move towards secure, then include the skill in mixed revision.

Keep the system light enough to use

The best error log is not the most detailed one. It is the one you can revisit, update and use to choose the next piece of practice.

  • Write short entries

    Use one factual sentence for the cause and one clear next action. Avoid rewriting the whole lesson.

  • Protect the essential cycle

    You can reduce the number of columns, but keep diagnosis, corrected reasoning, a later retry and the outcome.

  • Choose a low-friction format

    Use a notebook, spreadsheet, notes app, spoken note or speech-to-text entry. Choose the format that makes open entries easy to find and revisit.

  • Make labels accessible

    Use short labels and pair symbols with words rather than relying on colour alone.

  • Review open entries together

    Use a regular revision session to scan open and improving items instead of constantly rewriting the log.

  • Prioritise practice over presentation

    Spend more time doing the retry than decorating the record.

  • Do not diagnose yourself from the pattern

    Repeated misreading, slow processing or inconsistent checking does not by itself establish dyslexia, ADHD, anxiety or any other condition. Ask a teacher, tutor or appropriate professional for support when needed.

Sources and further reading

These sources support the learning principles, assessment caveats and Latimer service wording used in this guide.

  • Education Endowment Foundation: Metacognition and Self-Regulated Learning

    Second edition, published 13 November 2025

    Open source 1

  • Education Endowment Foundation: Feedback

    Living evidence page, accessed 4 August 2026

    Open source 2

  • Retrieval Practice Consistently Benefits Student Learning

    Educational Psychology Review, 2021

    Open source 3

  • Rutgers University Learning Centers: Metacognition

    Includes the Common Error Log resource

    Open source 4

  • AQA: Command words (GCSE Psychology)

    Current subject-linked guidance, accessed 4 August 2026

    Open source 5

  • OCR: Understanding GCSE Geography A questions and examiner expectations

    Updated 5 October 2023

    Open source 6

  • Ofqual: Student guide to exams and assessments in 2026

    Published 15 January 2026; applies to England

    Open source 7

  • Qualifications Scotland: Launching our new digital service

    Current transition information, accessed 4 August 2026

    Open source 8

  • Latimer Tuition: Common Revision Mistakes to Avoid

    Published 5 May 2026

    Open source 9

  • Latimer Tuition: Match Me With a Tutor

    Current service page, accessed 4 August 2026

    Open source 10

  • Latimer Tuition: Find a Tutor

    Current directory page, accessed 4 August 2026

    Open source 11

Related guidance

More guidance from this section

More guidance from this part of the Ed Centre that may help with the same decision, stage or next step.

Related guidance

Common revision mistakes to avoid

Revision can feel busy without being useful. Spot low-impact habits such as rereading, highlighting-only study, delayed practice questions and impossible timetables, then swap them for actions you can check.

Support and clarity

Frequently asked questions

Straight answers to the questions people ask most often.

How do I make a revision error log?

Create the minimum fields, add a meaningful mistake, diagnose the cause, record the correct reasoning and one next-time cue, schedule an unaided retry, then record the result and status. Keep each explanation short enough to revisit.

What should a mistake log template include?

Include the source, subject and topic, error type, what went wrong, correct reasoning, next-time cue, retry date, retry result and status. A confidence rating is optional and should stay only if it changes a later decision.

Should I record every mistake?

No. Prioritise recurring errors, misunderstood ideas, meaningful mark losses, errors that affect later steps and patterns that suggest a reusable check. Skip tiny one-off slips you already understand unless they begin to form a pattern.

How often should I retry a question after getting it wrong?

Correct the reasoning while reliable feedback is available, then make the first clean retry at the next relevant revision session rather than immediately copying the answer again. Use a longer gap and a similar or mixed-context task later, adjusting the timing for urgency, difficulty and previous success rather than following a universal calendar.

What should I do if I make the same mistake again?

Recheck the diagnosis. The correction may not have addressed the real cause, or the method may still need teaching, another worked example, guided practice or clearer feedback. Do not keep repeating the same test unchanged when the underlying process is not understood.

How do I stop making 'silly' or careless mistakes in exams?

Replace the label with a specific cause: missing knowledge, a method step, a misread condition or a named check that was not used. A checking failure only fits when a realistic check could have exposed the problem; repeated patterns are information, not a judgement about your ability.

When is an error secure enough to leave active revision?

Move an entry towards secure after successful unaided attempts separated in time, including a similar-but-not-identical or mixed-context task where appropriate. Secure is a practical status, not proof of permanent mastery, so reopen the entry if the pattern returns.

Should I keep one error log for every subject or separate logs?

Either can work. Use one notebook with subject sections, separate tabs or separate files—whichever makes open entries and patterns easiest to find. There is no established best format for every student, so keep the system low-friction.

Sources and references

Sources and references

Official guidance

Peer-reviewed research

Internal pages

Other sources

  • 1.
    Metacognition

    Rutgers University Learning Centers · Accessed

    Includes a Common Error Log for tracking errors, analysing causes and detecting patterns.