Originally published 3 June 2017 as an A-Math tuition promotion. Rebuilt in 2026 as a noindexed guide to rebuilding the earliest broken dependency in Additional Mathematics. Grade guarantees, “tricks”, dated service claims and unrelated image clutter have been retired.
Quick answer: “teach A-Math from scratch” should not mean restarting the whole subject every time a student struggles. The useful job is to locate the earliest dependency that is preventing the current topic from working, repair that dependency to functional stability, reconnect it to the present A-Math task, then test whether the repair survives mixed and delayed work.
This page is intentionally noindex. Its reader job is prerequisite repair inside A-Math, while the broader Additional Mathematics architecture remains owned by the stronger canonical guide.
A-Math weakness often appears later than it begins
A student may appear to be weak in a current topic when the actual failure began much earlier.
- weak factorisation can surface inside quadratic work;
- fragile algebraic fractions can surface inside identities;
- poor graph interpretation can surface inside functions;
- sign control can surface almost everywhere;
- weak equation solving can corrupt later symbolic chains.
The visible chapter name is therefore not always the correct repair target.
Start with the current failure, then trace backward
Use the student’s actual working.
- find the first incorrect, unsupported or missing line;
- identify what capability that line required;
- ask whether that capability is stable in a simpler setting;
- step backward only as far as necessary;
- repair there;
- reconnect to the original A-Math problem.
The goal is not to descend indefinitely into “basics”. It is to find the nearest dependency whose failure explains the observed problem.
Distinguish four common failure types
| Failure type | What it looks like | Repair |
|---|---|---|
| Concept | Does not understand the mathematical relationship | Rebuild meaning and representation |
| Recognition | Understands method once shown but does not select it | Mixed method-selection practice |
| Algebra | Correct idea collapses during symbolic manipulation | Target exact algebra dependency |
| Execution | Method secure but signs/copying/arithmetic fail | Visible working + checking routine |
These failure types can coexist, but separating them prevents broad, inefficient reteaching.
Observed, interpreted, unresolved
A disciplined diagnosis might read:
- Observed: the student understands the quadratic condition but cannot factorise reliably.
- Interpreted: the current A-Math concept may be stronger than the algebra carrying it.
- Unresolved: whether factorisation fails from weak pattern recognition or sign control.
The next task should separate those possibilities.
Rebuild only the dependency that is actually broken
If the issue is factorisation, use a short, focused repair:
- simple examples;
- contrast with non-factorisable forms;
- sign variation;
- reverse expansion;
- mixed recognition;
- delayed retrieval.
Then return to the A-Math topic immediately enough that the student can see why the prerequisite matters.
Do not confuse simplification with dilution
Teaching “from scratch” does not mean making the subject permanently easy. It means making the dependency visible enough to rebuild it.
The sequence should climb back toward the full demand:
simple dependency → varied dependency → current topic → mixed topic → unfamiliar transfer.
Use representation to expose hidden structure
A student may be stuck because the representation is hiding the relationship.
- graph ↔ equation;
- expanded ↔ factorised form;
- symbolic condition ↔ verbal description;
- function notation ↔ input/output relationship;
- geometric information ↔ algebraic condition.
Changing representation can reveal whether the concept is weak or whether the student simply cannot access it in the current form.
Mixed practice is the test for recognition
Blocked practice tells the student which method is expected. Mixed practice removes that cue.
A prerequisite is more useful when the student can recognise when to use it among several possible methods.
Keep the current A-Math topic in view
Students can become frustrated when prerequisite repair feels like being sent backwards. Make the connection explicit.
- “We are repairing this algebra because it is the line breaking your current function question.”
- “Once this is stable, we return to the original problem.”
The repair should feel like structural maintenance, not demotion.
Do not repair everything that looks imperfect
Some weaknesses are low-frequency and not currently limiting performance. Prioritise dependencies that are:
- recurrent;
- high-leverage;
- used across many topics;
- responsible for substantial downstream failure.
Resolution matters more than perfectionism.
A dependency ledger
| Current topic | First failed dependency | Repair | Return test |
|---|---|---|---|
| Quadratics | Factorisation | Pattern/sign repair | New quadratic problem |
| Functions | Graph interpretation | Graph↔equation translation | Changed function graph |
| Trigonometry | Algebraic fractions | Focused manipulation | Mixed identity problem |
Delayed retest prevents false recovery
Immediate success after a repair shows that the explanation is available in working memory. Return later without announcing the method.
- different numbers;
- different representation;
- different topic context;
- less prompting;
- same underlying dependency.
If the repair survives, it is becoming part of the student’s mathematical infrastructure.
Reconnection is the crucial final step
A repaired prerequisite that is never reattached to the current A-Math problem has not completed its job.
The sequence should end with the student returning to the original question and explaining:
- where the old chain failed;
- what was repaired;
- how the repair changes the solution;
- what cue should trigger the knowledge next time.
Historical classroom context
The original 2017 page described teaching A-Math “from scratch” in small groups. The useful purpose was accessibility: students should not be left behind because an earlier gap was assumed rather than taught. The rebuilt version makes that idea more precise—start from the earliest failed dependency, not from page one of the entire subject.
A compact dependency-repair cycle
current failure → first failed line → classify dependency → probe simpler form → smallest repair → variation → reconnect → mix → delay → retest.
What parents, tutors and students can measure
- Can the first failed dependency be named?
- Is the current concept stronger than the algebra carrying it?
- Does the repair work in a simpler setting?
- Can it reconnect to the original A-Math problem?
- Does it survive mixed practice?
- Does it survive after a delay?
- Is the same dependency failing fewer topics?
What not to conclude
- Struggling in one A-Math topic does not mean the whole subject must be restarted.
- The visible topic may not own the real weakness.
- Concept, recognition, algebra and execution failures require different repairs.
- Easy examples are useful only if they reconnect to the full task.
- Immediate correction does not prove durable repair.
- The best “from scratch” teaching starts at the earliest dependency necessary—and then climbs back to the present problem.
Related A-Math routes
- Additional Mathematics Learning Architecture — Algebra Spine, Trigonometry, Calculus and Transfer
- Why Sec 3 Additional Mathematics Feels Hard
- How to Revise E-Math and A-Math Together Without Letting One Hide the Other
Deep routes: rebuild A-Math dependencies through the Additional Mathematics Master Gateway, use the Mathematics Learning Library for prerequisite algebra and representation, and the Learning and Study Skills Library for diagnosis, practice and transfer.