Building an SPM Additional Mathematics error log from past papers

The marks you lose in practice are the most valuable information you have, they are a precise list of what to fix before the exam. Most students throw it away, glancing at a wrong answer and moving on.

An error log captures it instead: a running record of every mistake, why it happened, and how to do it right. Over a few weeks it stops being a diary of failures and becomes your revision plan, because it tells you exactly what to practise next.

This guide shows you how our teachers help students build one from past papers: what to record for each error, how to sort mistakes into types that need different fixes, and how to review the log so entries actually retire instead of piling up.

A useful log is short and specific. For every mark you drop, capture just enough to rebuild the mistake and the fix, no more.

A few columns do the job.

• Topic and question type: e.g. 'differentiation, gradient of a curve', so you can group entries later.
• What I did: the actual wrong step, in one line, not the whole attempt.
• The cause: the real reason it broke,'forgot to change the sign when moving a term', not just 'careless'.
• The fix: the correct method or the check that would have caught it, written so your future self can act on it.
• Cause type: method gap, careless slip, or misread question, one tag, for sorting.
• Review dates: when you last re-tested it and whether you got it right.

Not all mistakes need the same fix, so tag each one. The tag decides what you do about it.

1. 1

   Method gap

   You did not know what to do, or used the wrong approach. Fix: relearn the method from your notes, then do two or three fresh questions of that exact type until it is reliable.

2. 2

   Careless slip

   You knew the method but mis-signed, miscopied, or mis-keyed the calculator. Fix: add a specific check to your routine,'verify signs after every rearrangement', rather than just resolving to be careful.

3. 3

   Misread question

   You solved for the wrong thing, missed a 'hence', or ignored the required form or accuracy. Fix: practise reading the command word and underlining what the question actually asks before you start.

4. 4

   Count the tags

   Every week, tally which type is costing you most marks. That single number tells you whether this week's revision should be relearning topics, tightening checks, or slowing down to read questions.

A log you only add to is a to-do list that never shrinks. The point is to re-test entries and clear them.

• Re-test on a spacing: try an entry again after a few days, then a week or two later. Passing both times means it can retire.
• Retire deliberately: mark an entry closed only after you have redone that question type correctly, unaided, on a later day.
• Keep it visible: a log buried in a notebook you never reopen does nothing, review it at the start of each study session.
• Watch the shape change: as method gaps retire, careless slips usually become the biggest column, which tells you to shift from learning to checking.

The hardest part of an error log is naming the real cause, students often write 'careless' when the true problem is a method they never fully secured. In our sessions, we look at your marked scripts with you and help you find the honest reason each mark broke, so the fix targets the right thing.

We help you sort entries into method gaps, slips, and misreads, and we set the next questions from your own log rather than a generic list. As entries retire, we watch the pattern of your mistakes shift, and we keep steering your practice at whatever is currently costing the most, which is how a log becomes real, visible progress rather than a growing list of regrets.