Error Analysis: Turn Wrong Answers into a Repair Map
A wrong answer is not yet a diagnosis. The useful question is: where did the mathematical route first become invalid, and what capability failed there?
Students often correct Additional Mathematics by copying a worked solution, writing the correct final answer and moving on. That can create the appearance of repair without changing the underlying system. The same error then returns in a new question because the learner repaired the page, not the capability.
This guide builds an error-analysis system for Secondary 3 A-Math. The method separates concept errors from recognition, representation, method-selection, algebra, notation, domain, interpretation and examination-control errors. It then uses the smallest useful correction followed by targeted retesting and delayed return.
AI Extraction Box: The Repair Loop
attempt → find first wrong step → classify cause → repair rule → near transfer → changed-surface retest → delayed return → mixed-paper test.
- Concept error: mathematical relationship itself is not understood.
- Recognition error: student does not identify the object or topic.
- Representation error: student cannot move to a useful form.
- Selection error: knows methods but chooses an unsuitable one.
- Execution error: valid route, faulty algebra/arithmetic.
- Notation error: symbols, brackets, signs, units or interval notation mishandled.
- Constraint error: domain, exact-form, interval or physical restriction ignored.
- Interpretation error: mathematical result not converted into what the question asks.
- Examination-control error: time, checking, recovery or answer presentation fails.
Find the First Wrong Step, Not the Last Wrong Number
Suppose a student differentiates y=(3x+1)⁵ and writes 5(3x+1)⁴. The final expression is wrong, but the important diagnosis is not “calculus mistake”. The first invalid step is omission of the inner derivative 3. That is a Chain Rule error.
Suppose another student writes the correct derivative 15(3x+1)⁴ but later expands it incorrectly. That is not the same weakness. Both answers may be wrong, but the teaching response should differ.
Two wrong answers can require completely different repairs.
The Error Taxonomy in Practice
| Error class | Typical A-Math example | Repair |
|---|---|---|
| Concept | does not understand why discriminant zero means tangency | rebuild line-curve intersection and repeated-root meaning |
| Recognition | does not see quadratic in sin θ | substitute u=sin θ and compare structure |
| Representation | cannot expose circle centre from general equation | complete squares |
| Selection | expands full binomial for one requested term | use general term |
| Execution | sign error after correct method chosen | target sign/bracket manipulation |
| Notation | fourth term uses r=4 | re-map Tr+1 |
| Constraint | accepts negative log argument | write domain first |
| Interpretation | gives x-coordinate when asked for minimum value | return to question target |
| Exam control | spends 12 minutes on one dead-end route | install abandonment and recovery rule |
Correction Is Not Copying
A useful correction should contain at least three parts:
- First wrong step: identify exactly where validity was lost.
- Repair rule: state the principle that would prevent the error next time.
- Independent re-solve: close the worked solution and solve again from the start.
For example:
Error: tangent condition used Δ>0.
Repair rule: tangent = exactly one repeated intersection = Δ=0.
Retest: solve a changed line-curve tangency problem without notes.
The repair rule is more portable than the corrected answer.
Near Transfer Before Far Transfer
Immediately after correction, the learner needs a nearby test that preserves the same underlying method but changes the numbers or surface slightly.
Example sequence for a surd-rationalisation error:
- Correct 3/(2+√5).
- Retest 4/(3−√2).
- Later embed rationalisation inside a larger algebraic expression.
- Finally meet it without a chapter label in a mixed set.
Jumping immediately from a corrected error to a much harder mixed problem can obscure whether the basic repair worked. Near transfer confirms the repair; far transfer tests ownership.
Worked Diagnosis 1: Quadratic Positivity
Question: find k such that x²+4x+k is positive for all real x.
Student writes Δ≤0 and obtains k≥4.
The error is subtle. “Positive” means strictly greater than zero, so the parabola must not touch the x-axis. The correct condition is Δ<0, giving k>4.
Error class: constraint/language precision.
Repair rule: positive excludes zero; non-negative allows zero.
The retest should change the wording to “non-negative” so the learner must discriminate between the two conditions.
Worked Diagnosis 2: Trigonometric Equation
Question: solve cos θ=−1/2 for 0°≤θ≤360°.
Student enters cos⁻¹(−1/2) and writes θ=120° only.
The calculator produced a principal value, not the complete interval solution. Cosine is negative in Quadrants II and III, so the solutions are 120° and 240°.
Error class: interpretation/solution-set completeness.
Repair rule: inverse trig gives a principal angle; equations require all solutions in the stated interval.
Worked Diagnosis 3: Partial Fractions
Denominator: (x+1)(x+2)². Student writes A/(x+1)+B/(x+2).
The algebra may later become impossible because the template itself is incomplete. The correct setup needs:
A/(x+1)+B/(x+2)+C/(x+2)².
Error class: representation/template error.
Repair rule: repeated linear factor requires every power up to its multiplicity.
Repeating coefficient arithmetic will not fix a broken decomposition template. The repair must occur earlier.
Worked Diagnosis 4: Calculus Product Rule
Question: differentiate x²eˣ. Student writes 2xeˣ.
The student differentiated x² and kept eˣ, but omitted the second product-rule contribution.
Error class: method execution.
Repair rule: product of two changing functions gives u′v+uv′, not one branch only.
A good retest changes the surface to x sin x or (x+1)ln x.
Worked Diagnosis 5: Kinematics Distance
A particle moves from displacement 2 to displacement 7, then back to displacement 3. Student reports total distance 1 because final−initial=1.
Net displacement is 1. Distance travelled is |7−2|+|3−7|=5+4=9.
Error class: concept/interpretation.
Repair rule: displacement is signed change; distance accumulates path length.
Build an Error Log That Changes Behaviour
An error log should not become another notebook full of copied solutions. Keep entries compact and operational:
| Field | What to record |
|---|---|
| Question type | short structural label, not full question copy |
| First wrong step | exact line where validity was lost |
| Error class | concept, recognition, representation, selection, execution, notation, constraint, interpretation, exam control |
| Repair rule | one sentence that prevents recurrence |
| Near retest | result on similar but changed question |
| Delayed return | result after time gap |
| Mixed-paper return | whether method survives without chapter cue |
The log should shrink repeated errors over time. If it merely grows, the correction loop is not closing.
Retesting Must Change the Surface
A student can remember the correction to a specific question without owning the method. Retesting therefore needs at least one meaningful change:
- different coefficients;
- different representation;
- different wording;
- reverse direction of the problem;
- different interval;
- same method embedded in another topic;
- removal of the obvious chapter cue.
If the learner succeeds only when the corrected question is nearly identical, the repair has not yet transferred.
Delayed Return: Test Memory, Not Echo
An immediate retest checks whether the explanation was understood. A delayed retest checks whether it remains retrievable. Both matter.
A practical return schedule can include:
- same session: one near-transfer question;
- 2–3 days later: one changed-surface question;
- 1–2 weeks later: one mixed-topic return;
- next practice paper: observe whether the same error class reappears spontaneously.
Correction becomes learning only when it survives time and change.
Not Every Error Deserves the Same Amount of Practice
One accidental arithmetic slip after an otherwise reliable method does not need a 30-question worksheet. A repeated structure error that contaminates many chapters does.
Prioritise errors by:
- frequency: how often does it recur?
- spread: how many topics does it affect?
- severity: how many marks or later steps does it destroy?
- recoverability: can the student notice and self-correct?
- dependency level: is it upstream algebra or a narrow local fact?
Weak algebraic fraction control may deserve priority over a rare late-stage arithmetic slip because it affects functions, trigonometry, calculus and rational expressions.
Paper Review Should Produce an Error Map
After a practice paper, do not organise errors only by chapter. Create a second map by failure type:
- three method-selection errors;
- two sign errors;
- one log-domain error;
- two incomplete trig solution sets;
- one time-control abandonment failure.
This view can reveal a cross-topic cause that chapter totals hide. If four different topics contain sign errors, the problem may be symbolic control rather than four separate topic weaknesses.
A Correction Decision Tree
- Did the student know what object this was? If no, repair recognition.
- Did the student know a valid method? If no, repair concept/procedure.
- Was the method suitable? If no, repair selection.
- Was the first step valid? If no, locate representation/notation issue.
- Did execution fail later? Target the exact manipulation.
- Was the mathematics correct but answer invalid? Check domain, interval, units and wording.
- Did time pressure cause abandonment or rushing? Install examination-control rule.
A 45-Minute Error-Repair Session
- 8 minutes: select four recent errors and identify the first wrong step without looking at model solutions.
- 8 minutes: classify the four errors and write one-sentence repair rules.
- 12 minutes: complete one near-transfer question for each error.
- 8 minutes: complete two changed-surface questions that hide the original chapter cue.
- 5 minutes: update the error log with success/failure evidence.
- 4 minutes: schedule delayed returns for the highest-spread error classes.
What Mastery Looks Like
- The learner can identify the first wrong step instead of only the final wrong answer.
- The learner distinguishes concept, selection and execution failures.
- The learner writes short repair rules that transfer to new questions.
- The learner retests on changed surfaces rather than copying corrections.
- The learner returns to repaired errors after delay.
- The learner prioritises high-frequency and high-spread weaknesses.
- Practice papers produce a cross-topic error map, not merely a score.
- Repeated error classes shrink over time.
Return to the Additional Mathematics Learning Hub
Additional Mathematics Learning Hub | Secondary 3–4 A-Math Guides
Continue with Secondary 4 Handover, Revision Architecture and Readiness.