How to Use Error Logs for A-Level Maths
How to use error logs for A-Level Maths: record mistakes, diagnose their causes and revisit questions with a practical weekly revision routine.

A student rereads a chapter on integration. The examples feel familiar, the notes make sense, and confidence rises. Two days later, faced with a blank exam question, the method disappears.
That gap between recognising a solution and producing one is where an error log becomes useful. How to use error logs for A-Level Maths is simple in principle: attempt questions without help, record meaningful mistakes, identify why each happened, then reattempt those questions after a delay. The log turns revision away from what feels comfortable and towards what actually needs attention.
This guide explains the method, the research behind it, its limits and a sample week you can follow.
The error log method at a glance
For each substantial error:
- record the topic and source of the question;
- describe the mistake precisely;
- classify its cause;
- write the correction or lesson, not a copied solution;
- choose a date for another attempt;
- reattempt from a blank page without looking;
- keep the entry active until you can solve a similar question independently.
An error log can be a notebook or spreadsheet. Its value comes from what you do with it, not how polished it looks.
Why rereading can create false confidence
Imagine the student replaces another evening of rereading with three unseen questions. The first exposes a missing chain rule factor. The second reveals a misunderstanding of conditional probability. The third is correct except for an arithmetic slip.
That session may feel worse because errors are visible. Yet it provides far more useful information.
Research on learning broadly supports two ideas behind error logs: retrieval practice, which requires learners to recall or apply knowledge, and distributed practice, which returns to material after time has passed. Reviews of revision techniques have generally found practice testing and spaced practice more effective than passive rereading alone. Feedback matters too, because an unchecked wrong answer can reinforce the wrong method.
An error log is not itself a proven shortcut. It is a practical system for combining attempts, feedback, diagnosis and delayed reattempts. Its effectiveness still depends on the quality of the questions and the honesty of the review.
For broader planning alongside this technique, begin with the MathsGenie A-Level Maths revision hub, where topic resources can be connected to your weekly schedule.
How to use error logs for A-Level Maths
Attempt a proper question first
Do not build the log from notes you have merely read. Use an exam-style question, a mini test or part of a past paper under conditions that make retrieval necessary.
Work without notes for a defined period. Mark the attempt using an official mark scheme or a reliable worked solution. MathsGenie's A-Level Maths past papers give you material for checking whether knowledge survives outside a familiar exercise.
Record only useful information
A strong entry is brief enough to revisit quickly but specific enough to change your next attempt.
| Field | What to record |
|---|---|
| Topic | The precise skill, such as integration by parts |
| Question | Paper, year and question reference |
| Error | The exact point where the solution went wrong |
| Cause | Knowledge, method choice, algebra, notation or exam interpretation |
| Correction | The rule or decision you need next time |
| Reattempt | A date and the result of a blank-page retry |
Suppose the differentiation required the chain rule:
ddx(3x+1)5=5(3x+1)4×3. \frac{d}{dx}(3x+1)^5=5(3x+1)^4\times3. dxd(3x+1)5=5(3x+1)4×3.Writing “chain rule mistake” is too vague. A more useful entry is: “Differentiated the outer power but omitted the derivative of 3x+13x+13x+1. After differentiating the outer function, multiply by the derivative of the inner function.”
Classify the cause, not just the topic
Two incorrect answers can need entirely different responses.
- Knowledge gap: you could not recall a fact, definition or result.
- Method gap: you knew several techniques but selected the wrong one.
- Execution error: the plan was sound, but algebra or arithmetic failed.
- Interpretation error: you misread the command, condition or context.
- Communication error: working was incomplete, ambiguous or poorly justified.
This classification determines your next action. A knowledge gap may require a short revision lesson. A method-choice error needs mixed practice where the technique is not announced. An execution error calls for slower checking at the risky line, not another hour of watching videos.
The student in our example begins to notice that “careless” errors are not random. Several occur when rearranging expressions containing negative indices. That pattern is actionable. The label “careless” was not.
Write a correction cue
Do not copy an entire model answer. Record the smallest prompt that would improve your decision next time.
For a mechanics question, the cue might be: “Define a positive direction before resolving forces.” For hypothesis testing, it might be: “State hypotheses using the population parameter, not the sample statistic.”
The cue should trigger thought rather than replace it.
Schedule blank-page reattempts
Return to the original question after a short delay, then later attempt a different question testing the same idea. A reasonable starting rhythm is:
- first reattempt after 222 or 333 days;
- second check about 111 week later;
- later review through mixed exam questions.
These intervals are practical suggestions, not universal scientific rules. Increase the spacing when recall becomes secure and shorten it when the method is still unavailable.
Once you have listed topics and reattempt dates, you can lightly reduce the setup work: build those sessions into the MathsGenie Revision Planner rather than relying on a growing collection of paper reminders.
A sample week of error logs revision
This example assumes five manageable sessions around school commitments. Adjust the length and number of sessions rather than sacrificing sleep or rushing every question.
| Day | Main activity | Error-log action |
|---|---|---|
| Monday | Attempt a pure maths mini test | Mark it and create entries for substantial errors |
| Tuesday | Review one weak concept | Complete targeted questions and refine correction cues |
| Wednesday | Reattempt Monday's questions | Work from blank pages without notes |
| Thursday | Attempt mixed statistics or mechanics questions | Add new entries and identify recurring causes |
| Friday | Complete a timed section from a past paper | Track timing, interpretation and communication errors |
| Saturday | Retry unresolved questions | Test similar questions, then keep or retire entries |
| Sunday | Plan the next week | Prioritise active entries and leave secure ones for later spacing |
The key is the loop:
attempt→feedback→diagnosis→reattempt. \text{attempt}\rightarrow\text{feedback}\rightarrow\text{diagnosis}\rightarrow\text{reattempt}. attempt→feedback→diagnosis→reattempt.Monday creates evidence. Wednesday tests whether the correction lasted. Saturday asks the harder question: can you transfer the lesson to a similar problem?
Topic gaps can be supported with MathsGenie A-Level Maths revision resources, while A-Level Maths papers and mark schemes help keep your practice aligned with exam-style demands.
Common mistakes with an A-Level Maths error log
Logging every lost mark
If every sign slip becomes a paragraph, the system becomes too heavy to maintain. Record errors that reveal a pattern, misconception, missing method or recurring checking failure. One-off slips can be noted briefly on the script.
Copying the mark scheme
A copied solution can look reassuring without proving that you understand it. Close the mark scheme and explain the decisive step in your own words. Then solve the question again later.
Reattempting immediately
An immediate retry often measures short-term memory of the solution. Delay creates a more meaningful retrieval test.
Revising only weaknesses
Error logs naturally focus attention on weak areas, but A-Level Maths also requires maintenance of secure topics. Keep some mixed practice in the week so previously strong skills do not fade.
Treating all errors as knowledge gaps
More content review does not fix every problem. If you know the method but repeatedly lose marks through notation, timing or interpretation, practise that exact performance skill.
What error logs cannot do
An error log cannot replace learning a topic for the first time. It cannot guarantee that a question will reappear, and it does not measure understanding perfectly. Mark schemes may allow alternative methods, while self-marking can miss unclear reasoning.
It also has a selection bias: you only log weaknesses exposed by the questions you attempt. If your practice avoids difficult modelling, proof or unfamiliar contexts, the log may give an overly comfortable picture.
Use it alongside lessons, topic practice, timed papers and occasional feedback from a teacher. The log is a compass, not the whole journey.
Turn the log into next week's schedule
The student has not removed mistakes from maths. Instead, each mistake now has a next action and a date, which is far more useful than another promise to “revise integration”. Knowing the loop is easy; consistently fitting reattempts around lessons and fixed exam dates is the difficult part.
Your turn. Build your error-log schedule in the MathsGenie Revision Planner.



