An error log should make the student need the error log less over time. It is not a collection of wrong answers. It is a repair system that turns repeated mistakes into better decisions.
For Punggol students preparing for 2027 SEC G1, G2 or G3 Mathematics, a useful error log answers three questions: what failed, why did it fail, and has the skill been retested successfully?
The six columns that matter
| Column | What to record |
|---|---|
| Topic | The mathematical area involved |
| Error type | What actually caused the mark loss |
| AO | AO1, AO2 or AO3 |
| Repair | The corrected method or habit |
| Retest date | When the skill will be checked again |
| Status | Unstable, improving or stable |
That is enough. An error log should be useful, not decorative.
Use real error categories
- concept gap;
- forgotten prerequisite;
- method-selection error;
- question-reading error;
- algebra or arithmetic slip;
- calculator input;
- rounding or unit error;
- missing working;
- time-pressure failure.
“Careless” is too vague. A missing negative sign and a misunderstood percentage are different failures and need different repairs.
Add AO1, AO2 or AO3
This extra label makes the log more powerful.
- AO1: the student did not know or could not execute the method.
- AO2: the student knew the method but did not recognise, select or connect it correctly.
- AO3: the student could not justify or communicate the mathematical reasoning clearly.
See 2027 SEC Mathematics AO1, AO2 and AO3 for the full framework.
The repair must match the error
| Error | Repair |
|---|---|
| Concept gap | Reteach the idea, then practise a small focused set |
| Prerequisite gap | Step backward and repair the load-bearing skill |
| Method selection | Use mixed questions without chapter labels |
| Reading error | Annotate target, data and conditions |
| Calculator input | Re-enter with a written setup and plausibility check |
| Time pressure | Use short timed sets with a move-on rule |
Retesting is the part most students skip
Students often correct the question once, feel relief and move on.
But correction under guidance is not proof of independent retrieval. Schedule a retest several days later using a similar question.
If the error returns, the status stays unstable. If the student solves it independently more than once, the error can be retired.
Do not copy full model answers into the log
The log should contain the smallest useful correction.
- the rule that was missed;
- the decision that should have been made;
- the one line of algebra that broke;
- the calculator input habit that needs changing.
Long copied solutions create reading. Short repair notes create retrieval.
G1 error logs should protect routine reliability
G1 students should pay special attention to repeated standard-technique errors, calculator input, units, contextual reading and the transition from short questions to longer context questions.
G2 error logs should track Paper 2 choices
For G2, record not only whether a Section B question was wrong, but whether the original choice was sensible. A poor choice is an exam-decision error even if the Mathematics itself is understood.
G3 error logs should expose transfer failures
G3 students should distinguish “I did not know this” from “I knew the ingredients but failed to connect them”. The second problem needs mixed and unfamiliar practice rather than another page of routine drills.
Review the log weekly, not only before exams
Once a week, choose one or two unstable entries and retest them. This keeps the log active and stops it becoming an archive.
Before prelims and SEC, sort the log by frequency and impact. The most repeated high-value errors should become the final repair list.
Mathematics Tuition in Punggol: every repeated error deserves a named repair
Write less, diagnose better and retest. A good error log becomes smaller because old mistakes stop returning.
Families who want to discuss a 2027 SEC Mathematics repair system can WhatsApp eduKatePunggol.
