Pure Mathematics 2

Condensed sheet

Everything, on one sheet

Every method, every named trap, and every reference card in Pure Mathematics 2 — pulled straight from the lessons, so it can never drift out of sync with them.

11 lessons · 580 min, condensed

Read this once, then stop reading it. Re-reading a summary raises how familiar the material feels without changing how much of it you can produce, which is why it feels like studying and mostly isn’t. Use lookup mode when you need a specific fact. Use self-test mode — where the answers stay covered until you’ve tried to say them — for everything else.

Spec 1.1

1 lesson

Mathematical Proof: Exhaustion and Disproof by Counter-Example

A statement that claims something is true "for all" cases in a set can be proved two different ways, and the set's size is what decides between them: if it can be listed, it is proved by checking every case there is; if it can't — infinite, or every real number in some range — it is proved instead by a general argument that holds for an arbitrary case without ever listing one. The same kind of statement can be disproved by a single case that fails, whatever the set's size. Three techniques, not one difficulty repeated three times — and which one applies is not a rule to memorise, it falls straight out of what the word "all" actually means.

The card

"For all n in S" = AND over every case in S. Proving it true needs every case covered — by checking each (exhaustion) or a general argument covering them all at once; disproving it needs one false case.
Exhaustion (1.2): domain finite and bounded. List every case exactly, check each, state a conclusion — no separate mark for stating the bound itself.
General proof / contradiction (1.1): domain infinite or continuous, claim to be PROVED. Rearrange to a form true for every case at once (e.g. a squared term ⩾ 0), or assume it false and derive a contradiction.
Counter-example (1.3): claim to be DISPROVED, any domain size. Trial values, exhibit one failure with working shown, stop.
Bounded claim → exhaustion. Unbounded/continuous claim to prove → general algebra or contradiction. Any claim to disprove → counter-example.
Common losses: case list padded or short; conclusion omitted; product misread as sum; relation applied backwards; columns transposed; numerical examples treated as proof over an infinite domain; a divisibility claim asserted with no quotient shown.

Why it works — Why one counter-example is enough, and why exhaustion needs every case — the same fact, seen from both sides

A claim of the form "f(n)f(n) is true for every nn in some set SS" is not one statement — it is many statements joined together, one for each value of nn in SS: f(n1)f(n_1) AND f(n2)f(n_2) AND f(n3)f(n_3) AND … , continuing for every element SS has. That is what "for every" or "for all" actually means: not a single claim about the set, but a claim about each member of it, all asserted at once. Two facts about AND now decide everything else in this topic. First, an AND is true only when every one of its parts is true — so if you want to prove the whole conjunction, there is no shortcut: you have to establish f(n1)f(n_1), and establish f(n2)f(n_2), and so on, for every single nn in SS. If SS is finite and small enough to write out, that is exactly proof by exhaustion — list every case, check each one, and the conjunction is proved because you have directly verified every part of it. If SS is infinite, exhaustion is not slower, it is impossible: there is no way to finish writing out infinitely many checks, which is exactly why the spec's own exhaustion example restricts xx and yy to "odd integers less than 7" rather than leaving the set open-ended. Second, and this is the asymmetry that makes disproof cheap: an AND is false the moment even one of its parts is false, regardless of how many other parts are true. f(n1)f(n_1) AND f(n2)f(n_2) AND f(n3)f(n_3) is false if f(n2)f(n_2) alone is false, whatever f(n1)f(n_1) and f(n3)f(n_3) turn out to be. So disproving "f(n)f(n) is true for every nn" needs exactly one failing case, exhibited and checked — not because mathematicians are being lenient, but because one false part is structurally sufficient to make the whole AND false. This is also why the spec's counter-example guidance example is allowed to leave nn unbounded — "for all values of nn" being an infinite conjunction is not a problem for disproof the way it is for proof, because disproof was never going to need to visit every part in the first place.

Traps — 9

algebraic-proof-attempted-when-exhaustion-required
The most-documented single error in this topic, confirmed independently in two separate series. October 2022: "a significant number of attempts... using logical or algebraic approaches. Such attempts were mixed in quality and often unnecessarily long-winded... Some who obtained a cubic expression for the product just concluded it was even without any justification." October 2023, on a different question: "an attempt at an algebraic solution which proved more demanding than that of a numerical one." When a claim is already restricted to a small, explicitly bounded set of cases, listing and checking them is both the method the spec names and — confirmed twice, independently — the faster and safer route.
numerical-examples-mistaken-for-general-proof
Confirmed as the single worst-performing question on its own paper: an October 2021 report on a "prove true for all positive x, y" question states "though only a third of candidates were able to score the first mark, there were many who attempted an algebraic proof... there was also a large number who considered that several numerical examples of the inequality holding constituted a proof" — 47% of candidates scored 0 out of 4. This is exhaustion's own logic reaching past where it applies: checking a handful of values and finding the claim true every time proves nothing about a domain with no last case to reach, however many values are checked. Only a general argument — one that holds for an arbitrary case, not a list of specific ones — closes an infinite or continuous domain; see the worked algebraic-proof example above for what that argument actually looks like.
multiple-of-k-assertion-without-quotient-shown
Confirmed on a real exhaustion question checking a "multiple of 4" claim — k > 2, so unlike "even" or "multiple of 5," the property is not visible by inspecting a last digit. The real mark scheme is explicit that a bare assertion does not earn the mark: "they can be divided by 4 (on its own) is insufficient without further clarification such as 'to give whole numbers'" (Oct 2023). What it does accept is a minimal but explicit marker that the division genuinely produces a whole number — a calculation such as "40÷4=1040 \div 4 = 10," a tick against each value, or the word "prove"/"QED" next to the working — anything that shows the check was actually done, not just declared. For a "multiple of 4" claim, write "40÷4=1040 \div 4 = 10, a whole number, so 4040 is a multiple of 44," not "4040 is divisible by 44" on its own; the marker cannot tell a genuine check from a guess unless the quotient — or an equivalent explicit clarification — is shown.
product-misread-as-sum
Confirmed directly: "the definition of 'product' is not widely understood, with many students considering the sum of a, b and c instead" (Oct 2022). This is not an arithmetic mistake inside an otherwise correct method — it is checking the wrong quantity against every single case, so a perfectly executed exhaustive list still proves nothing about the question actually asked. Read what operation the question names before setting up the check, not after.
case-defining-relation-applied-backwards
Confirmed on a real exhaustion question where the cases were generated from a stated relationship between the variables: "sometimes the result of using c = b − 2 instead of c = b + 2" (Oct 2022). A relation like "c is 2 more than b" has a direction; reversing it silently generates a different — and wrong — set of cases from the very first line, so every case checked afterwards is checked against the wrong list, however carefully the rest of the working is done.
column-values-transposed-between-derived-variables
Confirmed on the same well-answered exhaustion question as above, as a separate, less prominent cause of lost marks: "a mix up between columns b and c" (Oct 2023). This is not the relation being applied backwards and not an arithmetic slip — each value can be individually correct, but written under the other variable's column head, so the row no longer records the case it claims to. It shows up specifically when two columns are both derived from the same base variable rather than from each other (here b and c are both computed from a, not from one another) — nothing forces the two labels apart the way a stated relation would, so check each entry against its own column head after filling a row in, not only that the pair of numbers is right somewhere in the row.
case-list-not-exactly-complete
Confirmed as a specific, separately-documented cause of lost marks, distinct from getting a case wrong: "the addition of extra rows" (Oct 2023) costs marks in one direction, and the mechanism above shows why an incomplete list costs them in the other — a bounded set has an exact size, established in the very first step of the proof, and the finished list has to match it exactly, neither padded with cases outside the stated bound nor missing any inside it.
conclusion-omitted
Confirmed on a well-answered exhaustion question, where the cases themselves were rarely the problem: "the solution merely required the sight of three correct rows and a minimal conclusion. Reasons for a loss of marks were:... the omission of a conclusion" (Oct 2023). A completed, correct case list is not yet a finished proof — the sentence stating that every case has been checked and the claim therefore holds is not decoration, it is the step that turns the list into a proof.
counter-example-search-continued-past-the-first-valid-one
Confirmed on a real counter-example question: "most candidates understood the principle of finding a counter-example, although many found far more than necessary" (June 2019) — the same report that states the underlying rule directly: "only one counter-example is required to prove that a statement is not true." Once one failing case has been found and justified, the disproof is complete; continuing to search costs time without earning further credit.

Say it out loud

Out loud, from memory, no notes: explain why one counter-example is enough, and why exhaustion needs every case — the same fact, seen from both sides to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 1.3

1 lesson

Mathematical Proof: Exhaustion and Disproof by Counter-Example

A statement that claims something is true "for all" cases in a set can be proved two different ways, and the set's size is what decides between them: if it can be listed, it is proved by checking every case there is; if it can't — infinite, or every real number in some range — it is proved instead by a general argument that holds for an arbitrary case without ever listing one. The same kind of statement can be disproved by a single case that fails, whatever the set's size. Three techniques, not one difficulty repeated three times — and which one applies is not a rule to memorise, it falls straight out of what the word "all" actually means.

The card

"For all n in S" = AND over every case in S. Proving it true needs every case covered — by checking each (exhaustion) or a general argument covering them all at once; disproving it needs one false case.
Exhaustion (1.2): domain finite and bounded. List every case exactly, check each, state a conclusion — no separate mark for stating the bound itself.
General proof / contradiction (1.1): domain infinite or continuous, claim to be PROVED. Rearrange to a form true for every case at once (e.g. a squared term ⩾ 0), or assume it false and derive a contradiction.
Counter-example (1.3): claim to be DISPROVED, any domain size. Trial values, exhibit one failure with working shown, stop.
Bounded claim → exhaustion. Unbounded/continuous claim to prove → general algebra or contradiction. Any claim to disprove → counter-example.
Common losses: case list padded or short; conclusion omitted; product misread as sum; relation applied backwards; columns transposed; numerical examples treated as proof over an infinite domain; a divisibility claim asserted with no quotient shown.

Why it works — Why one counter-example is enough, and why exhaustion needs every case — the same fact, seen from both sides

A claim of the form "f(n)f(n) is true for every nn in some set SS" is not one statement — it is many statements joined together, one for each value of nn in SS: f(n1)f(n_1) AND f(n2)f(n_2) AND f(n3)f(n_3) AND … , continuing for every element SS has. That is what "for every" or "for all" actually means: not a single claim about the set, but a claim about each member of it, all asserted at once. Two facts about AND now decide everything else in this topic. First, an AND is true only when every one of its parts is true — so if you want to prove the whole conjunction, there is no shortcut: you have to establish f(n1)f(n_1), and establish f(n2)f(n_2), and so on, for every single nn in SS. If SS is finite and small enough to write out, that is exactly proof by exhaustion — list every case, check each one, and the conjunction is proved because you have directly verified every part of it. If SS is infinite, exhaustion is not slower, it is impossible: there is no way to finish writing out infinitely many checks, which is exactly why the spec's own exhaustion example restricts xx and yy to "odd integers less than 7" rather than leaving the set open-ended. Second, and this is the asymmetry that makes disproof cheap: an AND is false the moment even one of its parts is false, regardless of how many other parts are true. f(n1)f(n_1) AND f(n2)f(n_2) AND f(n3)f(n_3) is false if f(n2)f(n_2) alone is false, whatever f(n1)f(n_1) and f(n3)f(n_3) turn out to be. So disproving "f(n)f(n) is true for every nn" needs exactly one failing case, exhibited and checked — not because mathematicians are being lenient, but because one false part is structurally sufficient to make the whole AND false. This is also why the spec's counter-example guidance example is allowed to leave nn unbounded — "for all values of nn" being an infinite conjunction is not a problem for disproof the way it is for proof, because disproof was never going to need to visit every part in the first place.

Traps — 9

algebraic-proof-attempted-when-exhaustion-required
The most-documented single error in this topic, confirmed independently in two separate series. October 2022: "a significant number of attempts... using logical or algebraic approaches. Such attempts were mixed in quality and often unnecessarily long-winded... Some who obtained a cubic expression for the product just concluded it was even without any justification." October 2023, on a different question: "an attempt at an algebraic solution which proved more demanding than that of a numerical one." When a claim is already restricted to a small, explicitly bounded set of cases, listing and checking them is both the method the spec names and — confirmed twice, independently — the faster and safer route.
numerical-examples-mistaken-for-general-proof
Confirmed as the single worst-performing question on its own paper: an October 2021 report on a "prove true for all positive x, y" question states "though only a third of candidates were able to score the first mark, there were many who attempted an algebraic proof... there was also a large number who considered that several numerical examples of the inequality holding constituted a proof" — 47% of candidates scored 0 out of 4. This is exhaustion's own logic reaching past where it applies: checking a handful of values and finding the claim true every time proves nothing about a domain with no last case to reach, however many values are checked. Only a general argument — one that holds for an arbitrary case, not a list of specific ones — closes an infinite or continuous domain; see the worked algebraic-proof example above for what that argument actually looks like.
multiple-of-k-assertion-without-quotient-shown
Confirmed on a real exhaustion question checking a "multiple of 4" claim — k > 2, so unlike "even" or "multiple of 5," the property is not visible by inspecting a last digit. The real mark scheme is explicit that a bare assertion does not earn the mark: "they can be divided by 4 (on its own) is insufficient without further clarification such as 'to give whole numbers'" (Oct 2023). What it does accept is a minimal but explicit marker that the division genuinely produces a whole number — a calculation such as "40÷4=1040 \div 4 = 10," a tick against each value, or the word "prove"/"QED" next to the working — anything that shows the check was actually done, not just declared. For a "multiple of 4" claim, write "40÷4=1040 \div 4 = 10, a whole number, so 4040 is a multiple of 44," not "4040 is divisible by 44" on its own; the marker cannot tell a genuine check from a guess unless the quotient — or an equivalent explicit clarification — is shown.
product-misread-as-sum
Confirmed directly: "the definition of 'product' is not widely understood, with many students considering the sum of a, b and c instead" (Oct 2022). This is not an arithmetic mistake inside an otherwise correct method — it is checking the wrong quantity against every single case, so a perfectly executed exhaustive list still proves nothing about the question actually asked. Read what operation the question names before setting up the check, not after.
case-defining-relation-applied-backwards
Confirmed on a real exhaustion question where the cases were generated from a stated relationship between the variables: "sometimes the result of using c = b − 2 instead of c = b + 2" (Oct 2022). A relation like "c is 2 more than b" has a direction; reversing it silently generates a different — and wrong — set of cases from the very first line, so every case checked afterwards is checked against the wrong list, however carefully the rest of the working is done.
column-values-transposed-between-derived-variables
Confirmed on the same well-answered exhaustion question as above, as a separate, less prominent cause of lost marks: "a mix up between columns b and c" (Oct 2023). This is not the relation being applied backwards and not an arithmetic slip — each value can be individually correct, but written under the other variable's column head, so the row no longer records the case it claims to. It shows up specifically when two columns are both derived from the same base variable rather than from each other (here b and c are both computed from a, not from one another) — nothing forces the two labels apart the way a stated relation would, so check each entry against its own column head after filling a row in, not only that the pair of numbers is right somewhere in the row.
case-list-not-exactly-complete
Confirmed as a specific, separately-documented cause of lost marks, distinct from getting a case wrong: "the addition of extra rows" (Oct 2023) costs marks in one direction, and the mechanism above shows why an incomplete list costs them in the other — a bounded set has an exact size, established in the very first step of the proof, and the finished list has to match it exactly, neither padded with cases outside the stated bound nor missing any inside it.
conclusion-omitted
Confirmed on a well-answered exhaustion question, where the cases themselves were rarely the problem: "the solution merely required the sight of three correct rows and a minimal conclusion. Reasons for a loss of marks were:... the omission of a conclusion" (Oct 2023). A completed, correct case list is not yet a finished proof — the sentence stating that every case has been checked and the claim therefore holds is not decoration, it is the step that turns the list into a proof.
counter-example-search-continued-past-the-first-valid-one
Confirmed on a real counter-example question: "most candidates understood the principle of finding a counter-example, although many found far more than necessary" (June 2019) — the same report that states the underlying rule directly: "only one counter-example is required to prove that a statement is not true." Once one failing case has been found and justified, the disproof is complete; continuing to search costs time without earning further credit.

Say it out loud

Out loud, from memory, no notes: explain why one counter-example is enough, and why exhaustion needs every case — the same fact, seen from both sides to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 1.2

1 lesson

Mathematical Proof: Exhaustion and Disproof by Counter-Example

A statement that claims something is true "for all" cases in a set can be proved two different ways, and the set's size is what decides between them: if it can be listed, it is proved by checking every case there is; if it can't — infinite, or every real number in some range — it is proved instead by a general argument that holds for an arbitrary case without ever listing one. The same kind of statement can be disproved by a single case that fails, whatever the set's size. Three techniques, not one difficulty repeated three times — and which one applies is not a rule to memorise, it falls straight out of what the word "all" actually means.

The card

"For all n in S" = AND over every case in S. Proving it true needs every case covered — by checking each (exhaustion) or a general argument covering them all at once; disproving it needs one false case.
Exhaustion (1.2): domain finite and bounded. List every case exactly, check each, state a conclusion — no separate mark for stating the bound itself.
General proof / contradiction (1.1): domain infinite or continuous, claim to be PROVED. Rearrange to a form true for every case at once (e.g. a squared term ⩾ 0), or assume it false and derive a contradiction.
Counter-example (1.3): claim to be DISPROVED, any domain size. Trial values, exhibit one failure with working shown, stop.
Bounded claim → exhaustion. Unbounded/continuous claim to prove → general algebra or contradiction. Any claim to disprove → counter-example.
Common losses: case list padded or short; conclusion omitted; product misread as sum; relation applied backwards; columns transposed; numerical examples treated as proof over an infinite domain; a divisibility claim asserted with no quotient shown.

Why it works — Why one counter-example is enough, and why exhaustion needs every case — the same fact, seen from both sides

A claim of the form "f(n)f(n) is true for every nn in some set SS" is not one statement — it is many statements joined together, one for each value of nn in SS: f(n1)f(n_1) AND f(n2)f(n_2) AND f(n3)f(n_3) AND … , continuing for every element SS has. That is what "for every" or "for all" actually means: not a single claim about the set, but a claim about each member of it, all asserted at once. Two facts about AND now decide everything else in this topic. First, an AND is true only when every one of its parts is true — so if you want to prove the whole conjunction, there is no shortcut: you have to establish f(n1)f(n_1), and establish f(n2)f(n_2), and so on, for every single nn in SS. If SS is finite and small enough to write out, that is exactly proof by exhaustion — list every case, check each one, and the conjunction is proved because you have directly verified every part of it. If SS is infinite, exhaustion is not slower, it is impossible: there is no way to finish writing out infinitely many checks, which is exactly why the spec's own exhaustion example restricts xx and yy to "odd integers less than 7" rather than leaving the set open-ended. Second, and this is the asymmetry that makes disproof cheap: an AND is false the moment even one of its parts is false, regardless of how many other parts are true. f(n1)f(n_1) AND f(n2)f(n_2) AND f(n3)f(n_3) is false if f(n2)f(n_2) alone is false, whatever f(n1)f(n_1) and f(n3)f(n_3) turn out to be. So disproving "f(n)f(n) is true for every nn" needs exactly one failing case, exhibited and checked — not because mathematicians are being lenient, but because one false part is structurally sufficient to make the whole AND false. This is also why the spec's counter-example guidance example is allowed to leave nn unbounded — "for all values of nn" being an infinite conjunction is not a problem for disproof the way it is for proof, because disproof was never going to need to visit every part in the first place.

Traps — 9

algebraic-proof-attempted-when-exhaustion-required
The most-documented single error in this topic, confirmed independently in two separate series. October 2022: "a significant number of attempts... using logical or algebraic approaches. Such attempts were mixed in quality and often unnecessarily long-winded... Some who obtained a cubic expression for the product just concluded it was even without any justification." October 2023, on a different question: "an attempt at an algebraic solution which proved more demanding than that of a numerical one." When a claim is already restricted to a small, explicitly bounded set of cases, listing and checking them is both the method the spec names and — confirmed twice, independently — the faster and safer route.
numerical-examples-mistaken-for-general-proof
Confirmed as the single worst-performing question on its own paper: an October 2021 report on a "prove true for all positive x, y" question states "though only a third of candidates were able to score the first mark, there were many who attempted an algebraic proof... there was also a large number who considered that several numerical examples of the inequality holding constituted a proof" — 47% of candidates scored 0 out of 4. This is exhaustion's own logic reaching past where it applies: checking a handful of values and finding the claim true every time proves nothing about a domain with no last case to reach, however many values are checked. Only a general argument — one that holds for an arbitrary case, not a list of specific ones — closes an infinite or continuous domain; see the worked algebraic-proof example above for what that argument actually looks like.
multiple-of-k-assertion-without-quotient-shown
Confirmed on a real exhaustion question checking a "multiple of 4" claim — k > 2, so unlike "even" or "multiple of 5," the property is not visible by inspecting a last digit. The real mark scheme is explicit that a bare assertion does not earn the mark: "they can be divided by 4 (on its own) is insufficient without further clarification such as 'to give whole numbers'" (Oct 2023). What it does accept is a minimal but explicit marker that the division genuinely produces a whole number — a calculation such as "40÷4=1040 \div 4 = 10," a tick against each value, or the word "prove"/"QED" next to the working — anything that shows the check was actually done, not just declared. For a "multiple of 4" claim, write "40÷4=1040 \div 4 = 10, a whole number, so 4040 is a multiple of 44," not "4040 is divisible by 44" on its own; the marker cannot tell a genuine check from a guess unless the quotient — or an equivalent explicit clarification — is shown.
product-misread-as-sum
Confirmed directly: "the definition of 'product' is not widely understood, with many students considering the sum of a, b and c instead" (Oct 2022). This is not an arithmetic mistake inside an otherwise correct method — it is checking the wrong quantity against every single case, so a perfectly executed exhaustive list still proves nothing about the question actually asked. Read what operation the question names before setting up the check, not after.
case-defining-relation-applied-backwards
Confirmed on a real exhaustion question where the cases were generated from a stated relationship between the variables: "sometimes the result of using c = b − 2 instead of c = b + 2" (Oct 2022). A relation like "c is 2 more than b" has a direction; reversing it silently generates a different — and wrong — set of cases from the very first line, so every case checked afterwards is checked against the wrong list, however carefully the rest of the working is done.
column-values-transposed-between-derived-variables
Confirmed on the same well-answered exhaustion question as above, as a separate, less prominent cause of lost marks: "a mix up between columns b and c" (Oct 2023). This is not the relation being applied backwards and not an arithmetic slip — each value can be individually correct, but written under the other variable's column head, so the row no longer records the case it claims to. It shows up specifically when two columns are both derived from the same base variable rather than from each other (here b and c are both computed from a, not from one another) — nothing forces the two labels apart the way a stated relation would, so check each entry against its own column head after filling a row in, not only that the pair of numbers is right somewhere in the row.
case-list-not-exactly-complete
Confirmed as a specific, separately-documented cause of lost marks, distinct from getting a case wrong: "the addition of extra rows" (Oct 2023) costs marks in one direction, and the mechanism above shows why an incomplete list costs them in the other — a bounded set has an exact size, established in the very first step of the proof, and the finished list has to match it exactly, neither padded with cases outside the stated bound nor missing any inside it.
conclusion-omitted
Confirmed on a well-answered exhaustion question, where the cases themselves were rarely the problem: "the solution merely required the sight of three correct rows and a minimal conclusion. Reasons for a loss of marks were:... the omission of a conclusion" (Oct 2023). A completed, correct case list is not yet a finished proof — the sentence stating that every case has been checked and the claim therefore holds is not decoration, it is the step that turns the list into a proof.
counter-example-search-continued-past-the-first-valid-one
Confirmed on a real counter-example question: "most candidates understood the principle of finding a counter-example, although many found far more than necessary" (June 2019) — the same report that states the underlying rule directly: "only one counter-example is required to prove that a statement is not true." Once one failing case has been found and justified, the disproof is complete; continuing to search costs time without earning further credit.

Say it out loud

Out loud, from memory, no notes: explain why one counter-example is enough, and why exhaustion needs every case — the same fact, seen from both sides to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 2.1

1 lesson

Algebraic Division, the Factor Theorem and the Remainder Theorem

Neither theorem on this spec item is a formula to memorise. Both are the same single line of algebra, read at one cleverly-chosen value of xx. Write down what division actually produces — f(x)(divisor)×(quotient)+(remainder)f(x) \equiv (\text{divisor}) \times (\text{quotient}) + (\text{remainder}) — and then substitute the one value of xx that makes the divisor zero. The quotient, the part you would otherwise have to grind out by long division, is multiplied by nothing and vanishes, leaving the remainder on its own. That is the ; the is the same sentence with the remainder equal to zero. And the paper's own examiners have recorded which of those two routes — substitute, or divide — students actually get marks with.

The card

Division identity: f(x) ≡ (ax − b)q(x) + r; r is constant for a linear divisor.
Remainder theorem: dividing by (ax − b) leaves f(b/a); by (ax + b), f(−b/a). Solve the bracket, never read it off.
Factor theorem: (ax − b) is a factor ⟺ f(b/a) = 0 — the same identity with r = 0.
Set f(root) equal to the stated remainder, not 0, unless told 'factor'.
Factorise completely: divide out the known factor, factorise the quadratic quotient, answer as a product of integer-coefficient linear factors.
Remainder wanted? Substitute. Quotient wanted? Divide, or compare coefficients.

Why it works — Where both theorems come from — one identity, evaluated at the value that deletes the quotient

Start with what division produces, before either theorem is stated. Dividing f(x)f(x) by a linear expression (axb)(ax - b) gives some quotient q(x)q(x) and leaves some remainder rr, and that is exactly the statement f(x)(axb)q(x)+r.f(x) \equiv (ax - b)\,q(x) + r. Two details in that line are doing all the work later, so they are worth pinning down now. First, rr is a constant. The division only stops when what is left over is too small to be divided again — if anything of degree 1 or more remained, the divisor (degree 1) would still go into it — so the remainder's degree must be strictly less than the divisor's, and "less than degree 1" means degree 0: a plain number, possibly zero. Second, the symbol is \equiv, not ==. This is an identity: the two sides are the same expression written two ways, so it is true for every single value of xx, not for a special few. That is not pedantry — it is the entire lever. Because the identity holds for every xx, you are free to choose the most convenient xx there is. Choose the value that makes the divisor zero. (axb)=0(ax - b) = 0 when x=bax = \frac{b}{a}, so substituting that value gives f ⁣(ba)=(abab)q ⁣(ba)+r=0×q ⁣(ba)+r=r.f\!\left(\tfrac{b}{a}\right) = \left(a \cdot \tfrac{b}{a} - b\right) q\!\left(\tfrac{b}{a}\right) + r = 0 \times q\!\left(\tfrac{b}{a}\right) + r = r. That is the remainder theorem, and notice what it cost: nothing was assumed about q(x)q(x) at all. Whatever the quotient is — however long, however awkward — it is multiplied by zero and disappears. This is why substitution beats division for a remainder: the division's entire output, the quotient, is the part you were never asked for, and choosing x=bax = \frac{b}{a} deletes it in one step rather than computing it and then throwing it away. The factor theorem is now not a second fact. Saying (axb)(ax-b) is a factor of f(x)f(x) means it divides exactly — i.e. r=0r = 0 — and the identity then reads f(x)(axb)q(x)f(x) \equiv (ax-b)q(x). Run the same substitution: f ⁣(ba)=r=0f\!\left(\frac{b}{a}\right) = r = 0. And the converse runs backwards down the identical line: if f ⁣(ba)=0f\!\left(\frac{b}{a}\right) = 0 then r=0r = 0, so f(x)(axb)q(x)f(x) \equiv (ax-b)q(x) and (axb)(ax-b) is a factor. Both directions come from the one identity, which is why the factor theorem is an "if and only if" rather than a one-way test: (axb)(ax - b) is a factor of f(x)f(x) exactly when f ⁣(ba)=0f\!\left(\frac{b}{a}\right) = 0. Everything the exam does to trip you here is a distortion of the substitution step, so read it once more slowly. The value substituted is the value that makes the *divisor* zero — solve axb=0ax - b = 0, do not read a number off the bracket. For (x2)(x - 2) that value is +2+2; for (x+2)(x + 2) it is 2-2; for (2x+1)(2x + 1) it is 12-\frac{1}{2}, not 12\frac{1}{2} and not 2-2. And what the substitution equals is rr, the *stated remainder* — which is zero only when the question has actually said "factor".

Traps — 8

root-sign-taken-straight-from-the-bracket
The dominant error on this spec item, confirmed on a real three-part factor-and-remainder question in both directions at once: candidates were recorded "setting f(12)=0f(\frac{1}{2}) = 0 in part (a) and/or setting f(2)=25f(-2) = -25 in part (b)" where the correct substitutions were f(12)f(-\frac{1}{2}) and f(2)f(2) (Oct 2023, Q4). The fix is mechanical rather than mnemonic: never read a number off a bracket, solve the bracket for xx. (2x+1)=0(2x+1)=0 gives x=12x = -\frac{1}{2}; (x+2)=0(x+2)=0 gives x=2x = -2; (3x2)=0(3x-2)=0 gives x=23x = \frac{2}{3}. One extra line, and the most expensive error on the topic cannot happen.
remainder-equation-set-to-zero
Confirmed on an accessible opening question: the commonest conceptual errors were "using f(2)f(-2) or f(3)f(3) rather than f(2)f(2) or setting equal to 3-3 or 00, rather than 33" (Jan 2024, Q1). Setting the substitution equal to zero is the factor-theorem reflex applied to a remainder question — and it is worth seeing that it is the same identity in both cases, f(x)(axb)q(x)+rf(x) \equiv (ax-b)q(x) + r, with rr being whatever the question said it was. Zero is a value of rr, not the default.
long-division-chosen-when-substitution-was-asked-for
Not wrong, but measurably worse, and the examiners have said so in as many words: "Candidates who chose to use division gave themselves a more difficult task and tended to be less successful, with many giving up part way through the division" (Jan 2024, Q1), on a question where "the remainder theorem was the most efficient approach." Division computes the entire quotient in order to discard it. Reach for it when a later part actually wants the quotient; otherwise substitute.
factorisation-stopped-one-step-short
Confirmed as a specific, separately-recorded cause of lost marks: "leaving the answer to (c) as (2x+1)(2x2+x15)(2x+1)(2x^2 + x - 15)" (Oct 2023, Q4). That quadratic does factorise — 2x2+x15=(2x5)(x+3)2x^2 + x - 15 = (2x-5)(x+3) — which is exactly why the answer was marked short: "factorise completely" is not satisfied while any factor still factorises. After dividing out the known factor, always ask whether the quadratic quotient breaks down further, and check its discriminant if it is not obvious.
hence-factorise-reached-without-using-the-given-factor
On a "hence factorise" part, the word "hence" is a mark-scheme instruction, not decoration: the working must derive the factorisation from the already-established factor, and reaching the identical, completely correct final answer by any other route earns nothing on that part. A real mark scheme is explicit about it, on the same question this lesson's worked chain and marked solution are modelled on: "The question states 'Hence' so there is an expectation that they use the factor of (2x+1)(2x+1) which is given. Solutions that just state 4x3+4x229x15=(2x+1)(2x5)(x+3)4x^3 + 4x^2 - 29x - 15 = (2x+1)(2x-5)(x+3) score M0 and therefore A0 A0" (Oct 2023, Q4(c)(ii)) — a fully correct factorisation, worth zero, purely because the shown working never used the given factor. The matching real error is recorded in the same series' examiner report: candidates "using a calculator to solve 4x3+4x229x15=04x^3 + 4x^2 - 29x - 15 = 0 and writing x=3,12,52x = -3, -\frac{1}{2}, \frac{5}{2}" — solving the cubic directly, on a paper where calculators are permitted throughout, instead of dividing out the factor the question had already given them. Every worked chain, chain drill and marked solution in this lesson models the division route for exactly this reason: on a "hence" question, showing the division or comparison is not supporting style, it is the entire mark allocation for that part, independent of whether the final product is right.
non-integer-factor-form-given
A genuine "mathematically equivalent but marked wrong" trap, confirmed on a real question whose final step was a factorisation: a candidate "giving the factor as x72x - \frac{7}{2}... This is incorrect as integer values were required" (June 2025 Regional 01R, Q8). (x72)\left(x - \frac{7}{2}\right) and (2x7)(2x-7) have the same root and are the same factor up to a constant, and the scheme still wants the integer-coefficient form. When a root comes out as a fraction ba\frac{b}{a}, write the factor as (axb)(ax - b).
answer-left-as-a-list-not-a-product
A real mark scheme states the required form of a factorised cubic explicitly, requiring it "written out as a product of factors (not as a list) and isw" (Jan 2020). Listing the three factors, or listing the three roots, is not the same object as their product — the question asked for f(x)f(x) factorised, so the answer is an expression equal to f(x)f(x). The isw (ignore subsequent working) note is the encouraging half: once the product is correctly written down, later scribbling does not undo it.
show-that-steps-omitted
On a "show that" part, the printed answer is not the thing being marked — the route to it is. A real report records marks lost for "not showing the =0= 0 or intermediate lines when attempting to prove (a)" (Oct 2023, Q4), and the general marking guidance's cso convention makes the standard explicit: "There must be no errors in this part of the question to obtain this mark." Write the substitution, write the line that clears the fractions, then write the printed result — a solution that leaps from one to the other has demonstrated nothing that could be checked.

Say it out loud

Out loud, from memory, no notes: explain where both theorems come from — one identity, evaluated at the value that deletes the quotient to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 3.1

1 lesson

Coordinate Geometry of the Circle

A is not a special formula to memorise — it is Pythagoras' theorem, written for a point that is free to move. Every fact this topic tests falls out of that one identity: where the centre and radius are hiding inside an equation that has been multiplied out, why a radius meets its at a right angle, why the line from a centre to a 's midpoint is perpendicular to the chord, why any triangle drawn on a diameter has a right angle at its third vertex. And the paper's own examiners record that the single most commonly lost mark on this topic isn't a hard one — it's the very first one on a question, spotting the centre inside an equation that doesn't look like (xa)2+(yb)2=r2(x-a)^2 + (y-b)^2 = r^2 yet.

The card

(x−a)² + (y−b)² = r²: centre (a,b), radius r. Sign flips — centre coordinate is minus the value in the bracket.
General form x²+y²+2gx+2fy+c=0: complete the square first. Centre (−g,−f); r² = g²+f²−c.
Radius ⊥ tangent at any point on the circle: gradients multiply to −1.
Perpendicular from centre bisects a chord. Angle in a semicircle = 90° for any point on the circle.
Give radii and coordinates exactly (surd form) — never a rounded decimal unless told otherwise.

Why it works — Where the circle's equation actually comes from — Pythagoras, applied to a point that moves

Take a centre (a,b)(a, b) and ask which points (x,y)(x, y) sit at distance exactly rr from it. Draw the right-angled triangle formed by the horizontal gap xax - a, the vertical gap yby - b, and the straight-line distance between the two points as the hypotenuse. Pythagoras' theorem gives that distance directly: (xa)2+(yb)2=r\sqrt{(x-a)^2 + (y-b)^2} = r. Squaring both sides — legal here because both sides are non-negative, a distance and a radius — removes the square root and produces exactly (xa)2+(yb)2=r2(x-a)^2 + (y-b)^2 = r^2. Nobody invented this equation as a definition to memorise; it is the distance formula, itself just Pythagoras' theorem restated in coordinates, applied to every point that happens to be exactly rr away from one fixed point. This is also why the coefficients of x2x^2 and y2y^2 in ANY valid circle equation are always equal (both 11, after dividing through if needed): both terms come from squaring a genuine coordinate gap in the same Pythagorean sum, and an equation where they differ, or where an xyxy term appears, is not describing a circle at all. Now multiply the standard form out and see what general form actually is. (xa)2+(yb)2=r2(x-a)^2 + (y-b)^2 = r^2 expands to x22ax+a2+y22by+b2=r2x^2 - 2ax + a^2 + y^2 - 2by + b^2 = r^2, which rearranges to x2+y22ax2by+(a2+b2r2)=0x^2 + y^2 - 2ax - 2by + (a^2+b^2-r^2) = 0. Matching this term by term against x2+y2+2gx+2fy+c=0x^2+y^2+2gx+2fy+c=0 gives 2g=2a2g = -2a, so a=ga = -g; identically b=fb = -f; and c=a2+b2r2c = a^2+b^2-r^2, so r2=a2+b2c=g2+f2cr^2 = a^2+b^2-c = g^2+f^2-c. Every part of "complete the square, then read off the centre and radius" is just running this exact expansion in reverse — the coefficient of xx is always 2×-2 \times(the centre's x-coordinate), which is precisely why the centre's x-coordinate is minus half that coefficient, and the constant term always has r2r^2 hidden inside it as g2+f2cg^2+f^2-c, which is precisely why the radius cannot be read off without first isolating that combination. There is no separate fact to memorise here beyond this one piece of algebra, expanded once and then run the other way every time a general-form equation shows up.

Traps — 8

centre-sign-not-flipped
A real WMA12 centre/radius question confirms candidates stating the circle's centre with a sign flip — the value read straight off a completed-square bracket, instead of its negative (Jan 2023, Q6). (x+3)2(x+3)^2 is zero at x=3x=-3, not x=3x=3: the bracket has to be interpreted, not transcribed. This is the exact same mechanism the WMA11 pilot documents for a quadratic's turning point, and it costs a mark for the identical reason in both places.
general-form-read-as-centre-radius-form
Completing the square in both xx and yy is not optional preparation, it is the entire first step whenever a circle's equation is presented multiplied out — reading a centre or radius off general form directly, without converting first, is a genuine error type. It is not, however, the step most candidates actually lose the mark on: a real WMA12 general-form question confirms the vast majority of candidates successfully completed this conversion (Jan 2023, Q6), with the one error that does recur being the sign flip covered in the next trap item, not a failure to attempt the conversion at all.
solved-parameter-not-substituted-into-earlier-general-centre
When a circle's equation is given in terms of an unresolved constant (e.g. centre (k,2k)(k, 2k), found correctly in an earlier part), and a later part requires a SPECIFIC numeric value of that constant — found by solving elsewhere in the same question — the mark for "identifying the centre" in that later part requires substituting the specific solved value back into the earlier general expression, not re-deriving from the original equation and not stopping after substituting the value into the circle's own equation without extracting actual coordinates. A real WMA12 examiner report confirms this directly, on a question where this exact substitution step was the single biggest mark-loss point of the whole question: "after nearly 90% of candidates successfully navigating the first two parts, fewer than 60% managed even the first mark, for identifying the centre of the circle... A few candidates chose the wrong value of k and so lost the mark, while others attempted to use the original equation to find where the circle meets the x axis thus making no progress at all with the question. Others simply put the value of k into the equation of the circle and then stopped. This did not gain any marks" (Jan 2021, Q9). Whenever a constant is left unresolved across multiple parts of the same question, the centre to use from that point on is the one built from the specific value just solved for — not the general symbolic form quoted correctly in an earlier part.
radius-given-as-decimal-not-exact-surd
The general marking guidance's exact-answer rule states plainly that "where, for example, an exact answer is asked for, or working with surds is clearly required, marks will normally be lost if the candidate resorts to using rounded decimals" — and a real WMA12 circle question specifically required an exact-form radius rather than a decimal approximation (Jan 2023, Q6). A radius of 252\sqrt{5} rounded to 4.474.47 looks harmless; the mark scheme treats it as a lost mark.
implicit-differentiation-chosen-over-the-property
A tangent's gradient can, in principle, be found by implicitly differentiating the circle's equation instead of using the radius-perpendicularity property — but a real WMA12 report records that "very few attempted to differentiate the equation of the circle, and these often made little progress even though the next method marks were available" (Jan 2021, Q9). Valid on paper is not the same as safe under time pressure: the perpendicularity property reaches the same gradient in two lines, with no unfamiliar technique to execute correctly first.
origin-and-circle-centre-both-labelled-o
A real WMA12 question let a circle's centre and the point O — meaning the origin — sit in the same problem, and a report records "the misunderstanding that O was the centre of the circle rather than the origin... a special case was permitted, and candidates were able to score all but the final A mark" (Jan 2021, Q9). The scheme was generous that one time; reading which O is which before starting is the version of this habit that doesn't rely on generosity.
substitution-direction-not-checked-for-fractions
Before substituting a rearranged line into a circle equation, check which variable's coefficient is smaller — a real WMA12 mark scheme records that "the (−2y−10) substitution for x was more successful than the (−0.5x−5) for y which led to work involving fractions" on a genuine tangent-and-normal intersection question (Jan 2023, Q6). Both directions reach the same answer for the same marks; only one of them does it without an extra fraction-clearing step in the middle.
general-area-formula-chosen-over-axis-aligned-base-height
When a triangle's base lies along an axis, its height is simply the third vertex's coordinate on the other axis — no trig or formula needed. But a real WMA12 examiner report records that "many candidates [were] not using the simple formula for the area of the triangle, electing instead to use ½ab sinC" or even a shoelace formula, "not appreciating the geometry of the situation, with the requisite triangle being right-angled" (Jan 2021, Q9). The mark scheme itself credits either route as a complete method, so no mark is actually lost by reaching for the general formula — but the marked solution above finds T on the x-axis and reads the base OT and height (A's y-coordinate) straight off in two lines precisely because that axis-alignment is there to exploit, while ½ab sinC or a shoelace calculation forces extra side-length and angle work under time pressure for the same credit.

Say it out loud

Out loud, from memory, no notes: explain where the circle's equation actually comes from — pythagoras, applied to a point that moves to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.1

1 lesson

Sequences, Recurrence Relations and Arithmetic Series

A sequence can be handed to you two structurally different ways — a formula that computes any term directly, or a rule, xn+1=f(xn)x_{n+1} = f(x_n), that only tells you how to get the next term from the one you already have — and almost every mark lost on this topic comes from treating the second kind like the first: applying a rule one time too many or too few, because "the 4th term" and "4 applications of the rule" are not the same count. Arithmetic sequences are the one case where both descriptions collapse into the same clean formula, un=a+(n1)du_n = a + (n-1)d, and the proof of where that formula — and its partner for the sum, Sn=12n[2a+(n1)d]S_n = \frac{1}{2}n[2a+(n-1)d] — actually comes from is not optional background reading. The specification says outright that you are expected to be able to produce it.

The card

uₙ = a + (n−1)d. Term n from term 1 takes (n−1) steps, not n.
Sₙ = ½n[2a+(n−1)d] = ½n(a+l), l = a+(n−1)d = last term. The (a+l) form needs no d.
Sum proof: write forwards, write reversed, add — every pair totals 2a+(n−1)d, n pairs.
Arithmetic: uₙ₊₁−uₙ = d, constant. Geometric (later): uₙ₊₁/uₙ = r, constant. Check which before choosing a formula.
Increasing: uₙ₊₁>uₙ ∀n. Decreasing: uₙ₊₁<uₙ ∀n. Periodic, period k: uₙ₊ₖ=uₙ ∀n.

Why it works — Why $u_n = a + (n-1)d$ — it falls out of the recurrence, it is not a separate rule to learn

Start from the recurrence itself, un+1=un+du_{n+1} = u_n + d, with first term u1=au_1 = a, and apply it repeatedly rather than accepting the closed formula as given. u2=u1+d=a+du_2 = u_1 + d = a + d. u3=u2+d=(a+d)+d=a+2du_3 = u_2 + d = (a+d) + d = a + 2d. u4=u3+d=(a+2d)+d=a+3du_4 = u_3 + d = (a+2d) + d = a + 3d. The pattern is exactly what "add dd every step" should produce: to reach unu_n from u1u_1 takes (n1)(n-1) steps, each adding one more dd, so un=a+(n1)du_n = a + (n-1)d. This is not a coincidence discovered by trying a few cases and guessing the pattern — it is a direct consequence of what "arithmetic" was defined to mean in the first place, and it is the same (n1)(n-1)-not-nn counting from the recurrence-relation teach block above, now packaged into a formula so that it never has to be counted by hand again. Two consequences follow directly. First, this is exactly why u1u_1 corresponds to (n1)=0(n-1) = 0 rather than (n1)=1(n-1) = 1: the first term needs zero applications of the recurrence to exist, and the formula has to agree with that or it would be wrong at its own starting point. Second, an arithmetic sequence is fully determined by exactly two numbers, aa and dd — every other term is a deterministic consequence of those two, which is the reason a question that gives you two arbitrary terms of an arithmetic sequence (not necessarily the first two) is always secretly a simultaneous-equations question: two unknowns, two given data points, one linear system.

Traps — 7

sum-proof-last-term-off-by-one
Confirmed directly on the standard sum-formula proof: "a surprising proportion of candidates struggled to write a correct expression of Sₙ at the start of their proof, often having the last term incorrect" (Jan 2020, Q8(i)). The fix is the same mechanism taught earlier in this lesson: reaching the nth term from the first takes (n − 1) steps of the recurrence, so the last term of an n-term series is a + (n − 1)d, never a + nd.
sum-proof-reversal-skipped
Confirmed on the same question: "Others failed to reverse the terms in the sum correctly, or at all" (Jan 2020, Q8(i)). Without the reversed copy, there is nothing for the forward copy to pair against, and the whole argument — every pair summing to the same constant — has no pairs to point at. This step is not optional decoration on the proof; it is the entire mechanism.
sum-proof-insufficient-terms-shown
Confirmed on the same question: candidates "did not display a sufficient number of terms to make subsequent steps in their proof to complete" (Jan 2020, Q8(i)). Two terms at each end plus an ellipsis — a+(a+d)++(a+(n2)d)+(a+(n1)d)a + (a+d) + \cdots + (a+(n-2)d) + (a+(n-1)d) — is the minimum that actually shows the pattern; a single "..." with no visible terms either side of it gives an examiner nothing to check the pairing against.
induction-attempted-for-standard-proof
Confirmed on the same question: "Attempts at proof by induction were also seen in a few cases, though little progress was made in most of these" (Jan 2020, Q8(i)). Induction can, in principle, prove this result, but it is not the proof the specification names, and the report records it as the less successful choice in practice. Where a question asks to "prove the standard formula," the pairing argument is the direct, expected route.
sum-proof-assumes-the-result
Confirmed on the same question: "Some candidates either started with, or used something that they were trying to prove, e.g. starting with Sn=12n(a+L)S_n = \frac{1}{2}n(a+L), or attempting to use a summation formula that is a generalisation of the result they needed to show" (Jan 2020, Q8(i)). This scores zero on an "ag" (answer given) proof no matter how cleanly the rest of the working is presented, because it assumes the very fact being proved rather than deriving it — a "prove that" question can never legitimately start from a form of its own target result. The only safe starting point is the definition of the series itself, written out term by term, exactly as the mechanism block above does.
sum-proof-pairing-fails-for-odd-n
Confirmed on the same question: some candidates instead tried pairing terms within a single copy of the sum — first-plus-last, second-plus-second-to-last, and so on — "but they did not give due consideration to what happens when there are an odd number of terms, and were unable to score the accuracy mark as a result" (Jan 2020, Q8(i)). An odd number of terms leaves one unpaired middle term this method has no clean way to handle, which is exactly why the write-forwards/write-backwards/add version taught in this lesson is the safer standard route — it pairs the full sum against a full reversed copy of itself, so it never needs nn to be even and never has a leftover term to account for separately.
arithmetic-and-geometric-formulas-confused
Confirmed as a recurring, named error category across at least two series (June 2019 and October 2020): candidates reach for the wrong series formula mid-question — applying the geometric sum formula to an arithmetic series, or the reverse — because the two topics sit close together and use similarly-shaped notation. The one-line check that catches it before it starts: an arithmetic sequence has a constant DIFFERENCE between consecutive terms (un+1un=du_{n+1} - u_n = d, the same value every time); a geometric one has a constant RATIO instead. Confirm which quantity is actually constant before reaching for either sum formula.

Say it out loud

Out loud, from memory, no notes: explain why $u_n = a + (n-1)d$ — it falls out of the recurrence, it is not a separate rule to learn to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.2

2 lessons

Sequences, Recurrence Relations and Arithmetic Series

A sequence can be handed to you two structurally different ways — a formula that computes any term directly, or a rule, xn+1=f(xn)x_{n+1} = f(x_n), that only tells you how to get the next term from the one you already have — and almost every mark lost on this topic comes from treating the second kind like the first: applying a rule one time too many or too few, because "the 4th term" and "4 applications of the rule" are not the same count. Arithmetic sequences are the one case where both descriptions collapse into the same clean formula, un=a+(n1)du_n = a + (n-1)d, and the proof of where that formula — and its partner for the sum, Sn=12n[2a+(n1)d]S_n = \frac{1}{2}n[2a+(n-1)d] — actually comes from is not optional background reading. The specification says outright that you are expected to be able to produce it.

The card

uₙ = a + (n−1)d. Term n from term 1 takes (n−1) steps, not n.
Sₙ = ½n[2a+(n−1)d] = ½n(a+l), l = a+(n−1)d = last term. The (a+l) form needs no d.
Sum proof: write forwards, write reversed, add — every pair totals 2a+(n−1)d, n pairs.
Arithmetic: uₙ₊₁−uₙ = d, constant. Geometric (later): uₙ₊₁/uₙ = r, constant. Check which before choosing a formula.
Increasing: uₙ₊₁>uₙ ∀n. Decreasing: uₙ₊₁<uₙ ∀n. Periodic, period k: uₙ₊ₖ=uₙ ∀n.

Why it works — Why $u_n = a + (n-1)d$ — it falls out of the recurrence, it is not a separate rule to learn

Start from the recurrence itself, un+1=un+du_{n+1} = u_n + d, with first term u1=au_1 = a, and apply it repeatedly rather than accepting the closed formula as given. u2=u1+d=a+du_2 = u_1 + d = a + d. u3=u2+d=(a+d)+d=a+2du_3 = u_2 + d = (a+d) + d = a + 2d. u4=u3+d=(a+2d)+d=a+3du_4 = u_3 + d = (a+2d) + d = a + 3d. The pattern is exactly what "add dd every step" should produce: to reach unu_n from u1u_1 takes (n1)(n-1) steps, each adding one more dd, so un=a+(n1)du_n = a + (n-1)d. This is not a coincidence discovered by trying a few cases and guessing the pattern — it is a direct consequence of what "arithmetic" was defined to mean in the first place, and it is the same (n1)(n-1)-not-nn counting from the recurrence-relation teach block above, now packaged into a formula so that it never has to be counted by hand again. Two consequences follow directly. First, this is exactly why u1u_1 corresponds to (n1)=0(n-1) = 0 rather than (n1)=1(n-1) = 1: the first term needs zero applications of the recurrence to exist, and the formula has to agree with that or it would be wrong at its own starting point. Second, an arithmetic sequence is fully determined by exactly two numbers, aa and dd — every other term is a deterministic consequence of those two, which is the reason a question that gives you two arbitrary terms of an arithmetic sequence (not necessarily the first two) is always secretly a simultaneous-equations question: two unknowns, two given data points, one linear system.

Traps — 7

sum-proof-last-term-off-by-one
Confirmed directly on the standard sum-formula proof: "a surprising proportion of candidates struggled to write a correct expression of Sₙ at the start of their proof, often having the last term incorrect" (Jan 2020, Q8(i)). The fix is the same mechanism taught earlier in this lesson: reaching the nth term from the first takes (n − 1) steps of the recurrence, so the last term of an n-term series is a + (n − 1)d, never a + nd.
sum-proof-reversal-skipped
Confirmed on the same question: "Others failed to reverse the terms in the sum correctly, or at all" (Jan 2020, Q8(i)). Without the reversed copy, there is nothing for the forward copy to pair against, and the whole argument — every pair summing to the same constant — has no pairs to point at. This step is not optional decoration on the proof; it is the entire mechanism.
sum-proof-insufficient-terms-shown
Confirmed on the same question: candidates "did not display a sufficient number of terms to make subsequent steps in their proof to complete" (Jan 2020, Q8(i)). Two terms at each end plus an ellipsis — a+(a+d)++(a+(n2)d)+(a+(n1)d)a + (a+d) + \cdots + (a+(n-2)d) + (a+(n-1)d) — is the minimum that actually shows the pattern; a single "..." with no visible terms either side of it gives an examiner nothing to check the pairing against.
induction-attempted-for-standard-proof
Confirmed on the same question: "Attempts at proof by induction were also seen in a few cases, though little progress was made in most of these" (Jan 2020, Q8(i)). Induction can, in principle, prove this result, but it is not the proof the specification names, and the report records it as the less successful choice in practice. Where a question asks to "prove the standard formula," the pairing argument is the direct, expected route.
sum-proof-assumes-the-result
Confirmed on the same question: "Some candidates either started with, or used something that they were trying to prove, e.g. starting with Sn=12n(a+L)S_n = \frac{1}{2}n(a+L), or attempting to use a summation formula that is a generalisation of the result they needed to show" (Jan 2020, Q8(i)). This scores zero on an "ag" (answer given) proof no matter how cleanly the rest of the working is presented, because it assumes the very fact being proved rather than deriving it — a "prove that" question can never legitimately start from a form of its own target result. The only safe starting point is the definition of the series itself, written out term by term, exactly as the mechanism block above does.
sum-proof-pairing-fails-for-odd-n
Confirmed on the same question: some candidates instead tried pairing terms within a single copy of the sum — first-plus-last, second-plus-second-to-last, and so on — "but they did not give due consideration to what happens when there are an odd number of terms, and were unable to score the accuracy mark as a result" (Jan 2020, Q8(i)). An odd number of terms leaves one unpaired middle term this method has no clean way to handle, which is exactly why the write-forwards/write-backwards/add version taught in this lesson is the safer standard route — it pairs the full sum against a full reversed copy of itself, so it never needs nn to be even and never has a leftover term to account for separately.
arithmetic-and-geometric-formulas-confused
Confirmed as a recurring, named error category across at least two series (June 2019 and October 2020): candidates reach for the wrong series formula mid-question — applying the geometric sum formula to an arithmetic series, or the reverse — because the two topics sit close together and use similarly-shaped notation. The one-line check that catches it before it starts: an arithmetic sequence has a constant DIFFERENCE between consecutive terms (un+1un=du_{n+1} - u_n = d, the same value every time); a geometric one has a constant RATIO instead. Confirm which quantity is actually constant before reaching for either sum formula.

Say it out loud

Out loud, from memory, no notes: explain why $u_n = a + (n-1)d$ — it falls out of the recurrence, it is not a separate rule to learn to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Geometric Series and the Sum to Infinity

An arithmetic sequence moves by adding the same amount every step; a geometric one moves by multiplying by the same amount every step. That single swap — +d+d becomes ×r\times r — changes everything downstream, and changes it in ways that are derivable rather than arbitrary: the nth-term formula becomes un=arn1u_n = ar^{n-1}, the proof of the sum formula stops working by reversing-and-adding and starts working by multiplying-and-subtracting, and something genuinely new appears that has no arithmetic counterpart at all. Add infinitely many terms of an arithmetic series and the total always runs away. Add infinitely many terms of a geometric series and, provided r<1|r| < 1, it settles on a finite number — S=a1rS_\infty = \frac{a}{1-r} — because each term is a fixed fraction of the one before it and the terms shrink toward nothing fast enough to leave a finite total behind. The specification asks for the proof of the finite sum formula by name, and examiners have said outright that students should know the standard proofs for both the arithmetic and the geometric series. This lesson derives both formulae, and derives the r<1|r| < 1 condition rather than quoting it.

The card

uₙ = ar^(n−1); Sₙ = a(1−rⁿ)/(1−r) = a(rⁿ−1)/(r−1), r ≠ 1; S∞ = a/(1−r), |r| < 1 — all three printed in the booklet.
Proof: write Sₙ, write rSₙ, subtract — the shared middle terms cancel.
|r| < 1 because rⁿ is the only n-dependent part: |r| < 1 ⇒ rⁿ → 0.
Geometric: uₙ₊₁/uₙ constant. Arithmetic: uₙ₊₁ − uₙ constant. Check which first.
Mixed series: the shared term counts once — the GP starts at (shared term)×r.
Quote the formula before substituting; a bare calculator total scores nothing.

Why it works — Why $S_n = \frac{a(1-r^n)}{1-r}$ — multiply by $r$ and subtract, and why that is the move

The arithmetic sum proof works by writing the series a second time in reverse and adding, because arithmetic terms are related by *addition* — stepping forward through one copy and backward through the other changes each side by +d+d and d-d, which cancel, so every pair lands on the same total. None of that survives the switch to multiplication. Reverse a geometric series and add it to itself and the pairs are a+arn1a + ar^{n-1}, ar+arn2ar + ar^{n-2}, ar2+arn3ar^2 + ar^{n-3} — try it with 3,6,12,243, 6, 12, 24 and the pairs come out 27,18,18,2727, 18, 18, 27, plainly not constant. The arithmetic move fails here, and it fails for a reason you can name: constant pair-sums came from a constant additive step, and this series does not have one. What this series does have is a constant *multiplicative* step, so the move that exploits its structure is multiplication. Write the sum out in full: Sn=a+ar+ar2++arn2+arn1S_n = a + ar + ar^2 + \cdots + ar^{n-2} + ar^{n-1} — and note the last term is arn1ar^{n-1}, not arnar^n, for the same (n1)(n-1)-counting reason established above. Now multiply the whole equation by rr: rSn=ar+ar2+ar3++arn1+arnrS_n = ar + ar^2 + ar^3 + \cdots + ar^{n-1} + ar^n Look at what multiplying by rr actually did: it turned every term into the *next* term, which slides the entire list one place along. The second line is the first line shifted by one. That means the two lines share almost all of their terms — everything from arar up to arn1ar^{n-1} appears in both — and only two terms fail to have a partner: the aa at the start of the first line, and the arnar^n at the end of the second. Subtracting is what collects that observation: SnrSn=aarnS_n - rS_n = a - ar^n Every shared term cancelled, exactly n1n-1 of them, because each appeared once on each side. Factorise both sides — Sn(1r)=a(1rn)S_n(1-r) = a(1-r^n) — and divide by (1r)(1-r) to finish: Sn=a(1rn)1rS_n = \frac{a(1-r^n)}{1-r} That final division carries a condition worth stating rather than glossing: it is only legal when 1r01-r \neq 0, i.e. r1r \neq 1. The formula genuinely does not apply when r=1r = 1, and it does not need to — a geometric series with r=1r = 1 is a+a+a+a + a + a + \cdots, the same number repeated, whose sum to nn terms is just nana by inspection. This is not an exception bolted onto the formula from outside; it is the one case the derivation itself excluded, showing up exactly where the derivation said it would. So the two proofs in this pair of lessons are not two unrelated tricks to memorise. Each one applies the operation that matches how its own series is built: an additively-generated series is attacked by adding a reversed copy, a multiplicatively-generated series is attacked by subtracting a multiplied copy. Knowing which is which is knowing what the series is.

Traps — 8

arithmetic-and-geometric-formulas-confused
Confirmed as a recurring, named error category across at least two series (June 2019 and October 2020): candidates reach for the wrong series type's formula mid-question, because the two topics sit adjacent in the specification, use similarly-shaped notation, and are printed one above the other on the same formula-booklet page. Seen from the geometric side, the tell is any appearance of dd, of (n1)d(n-1)d, or of 12n\frac{1}{2}n in working about a series whose terms are multiplying. The two-line check that catches it before a single mark is at stake: compute un+1unu_{n+1} - u_n and un+1/unu_{n+1}/u_n for two consecutive pairs, and see which of the two comes out the same both times.
overlap-term-double-counted
Confirmed on a January 2022 mixed arithmetic-then-geometric question, verified as that paper's biggest discriminator. The examiner records that candidates "were not able to correctly process the overlap of the 20th term of the arithmetic series with the first term of the geometric series, and double counted this term" (Jan 2022). When one series ends on the same term another begins with, that term belongs to exactly one of the two sums. The report itself names both legal fixes: the geometric series starts at (shared term) × r, "or alternatively" the shared term is subtracted out of the arithmetic total — either one, never neither, never both.
geometric-series-restarted-from-the-original-first-term
Confirmed on the same January 2022 question, and distinct from the double-count above: "many candidates failed to understand the context with many assuming they had to start the geometric series from the first term of a=100a = 100 again" (Jan 2022). Where a sequence changes character partway through, the geometric part inherits its first term from wherever the arithmetic part left off — not from the beginning of the whole sequence. Reading the question's "from the kkth term onwards" literally, and writing down what that term actually equals before doing anything else, is the fix.
sum-to-infinity-first-term-misidentified
Confirmed on a January 2024 sum-to-infinity question: candidates "often used a = 6 instead of a = 1.5 in the sum to infinity formula" (Jan 2024, Q5(i)) — taking the sequence's original first term rather than the first term of the series actually being summed. This bites whenever a question asks for the sum of everything after some term, or re-expresses a series starting from a later index. The aa in a1r\frac{a}{1-r} is not "the first term of the sequence"; it is the first term of the sum you are being asked for. The self-check: the answer to "sum everything after the first term" must be smaller than the answer to "sum everything" by exactly that first term.
calculator-summation-shown-without-formula
Confirmed on the same January 2024 question: "a number resorted to using the summation button on their calculator which, even if [the value] was found, no marks were scored" (Jan 2024, Q5(i)). Calculators are permitted throughout this paper, which makes this trap easier to fall into rather than harder — a correct number with no visible formula and no visible substitution earns nothing, because the marks on offer are method marks and there is no method on the page to award them to. The mark scheme's standing principle says the same thing in general terms: where a learnt formula is used, "the formula should be quoted first."
standard-proofs-not-known
Confirmed on the January 2020 arithmetic sum-formula proof, with the examiner's advice naming both series explicitly: students "would be well advised to make sure they know the standard proofs for the arithmetic and geometric series to ensure they are able to give should it be required" (Jan 2020, Q8(i)). The specification's own guidance for item 4.4 says the same — "the proof of the sum formula for a finite series should be known." These are the only marks in the topic that a formula booklet cannot rescue: the formulae are printed, the proofs are not.
geometric-proof-subtraction-direction-reversed
Confirmed on the October 2020 geometric sum-formula proof: "A significant number started correctly and knew they had to subtract but subtracted the wrong way round to obtain e.g. SnrSn=arnaS_n - rS_n = ar^n - a and a significant number of candidates obtained SnrSn=a+arnS_n - rS_n = a + ar^n" (Oct 2020, Q8(a)). The correct line is SnrSn=aarnS_n - rS_n = a - ar^n: the survivors of the subtraction are whichever terms belong to the line that was NOT shifted (the aa from SnS_n) minus whichever belong to the line that WAS (the arnar^n from rSnrS_n), in that order — reverse which line each survivor is taken from, or turn the subtraction into an addition under exam pressure, and the result no longer factorises to the printed answer no matter how the rest of the algebra is handled. The examiner report records this immediately alongside the same question's other confirmed proof error (importing the arithmetic proof's reverse-and-add method), making the two the two most-recorded ways this specific proof goes wrong.
convergence-condition-read-as-r-less-than-one
Derived from the mechanism rather than quoted — the facts bank records no examiner finding on this specific error, and this entry carries no citation. Reading r<1|r| < 1 as "r<1r < 1" admits every negative ratio, including r=2r = -2 and r=1.5r = -1.5, whose terms grow without limit while alternating in sign. The modulus is a statement about size: SS_\infty exists precisely when each term is smaller in size than the one before it, regardless of sign. The related boundary case is r=1r = -1, where rnr^n alternates between 1-1 and 11 forever and the partial sums alternate between aa and 00 — never settling, which is why the specification's inequality is strict.

Say it out loud

Out loud, from memory, no notes: explain why $s_n = \frac{a(1-r^n)}{1-r}$ — multiply by $r$ and subtract, and why that is the move to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.3

1 lesson

Sequences, Recurrence Relations and Arithmetic Series

A sequence can be handed to you two structurally different ways — a formula that computes any term directly, or a rule, xn+1=f(xn)x_{n+1} = f(x_n), that only tells you how to get the next term from the one you already have — and almost every mark lost on this topic comes from treating the second kind like the first: applying a rule one time too many or too few, because "the 4th term" and "4 applications of the rule" are not the same count. Arithmetic sequences are the one case where both descriptions collapse into the same clean formula, un=a+(n1)du_n = a + (n-1)d, and the proof of where that formula — and its partner for the sum, Sn=12n[2a+(n1)d]S_n = \frac{1}{2}n[2a+(n-1)d] — actually comes from is not optional background reading. The specification says outright that you are expected to be able to produce it.

The card

uₙ = a + (n−1)d. Term n from term 1 takes (n−1) steps, not n.
Sₙ = ½n[2a+(n−1)d] = ½n(a+l), l = a+(n−1)d = last term. The (a+l) form needs no d.
Sum proof: write forwards, write reversed, add — every pair totals 2a+(n−1)d, n pairs.
Arithmetic: uₙ₊₁−uₙ = d, constant. Geometric (later): uₙ₊₁/uₙ = r, constant. Check which before choosing a formula.
Increasing: uₙ₊₁>uₙ ∀n. Decreasing: uₙ₊₁<uₙ ∀n. Periodic, period k: uₙ₊ₖ=uₙ ∀n.

Why it works — Why $u_n = a + (n-1)d$ — it falls out of the recurrence, it is not a separate rule to learn

Start from the recurrence itself, un+1=un+du_{n+1} = u_n + d, with first term u1=au_1 = a, and apply it repeatedly rather than accepting the closed formula as given. u2=u1+d=a+du_2 = u_1 + d = a + d. u3=u2+d=(a+d)+d=a+2du_3 = u_2 + d = (a+d) + d = a + 2d. u4=u3+d=(a+2d)+d=a+3du_4 = u_3 + d = (a+2d) + d = a + 3d. The pattern is exactly what "add dd every step" should produce: to reach unu_n from u1u_1 takes (n1)(n-1) steps, each adding one more dd, so un=a+(n1)du_n = a + (n-1)d. This is not a coincidence discovered by trying a few cases and guessing the pattern — it is a direct consequence of what "arithmetic" was defined to mean in the first place, and it is the same (n1)(n-1)-not-nn counting from the recurrence-relation teach block above, now packaged into a formula so that it never has to be counted by hand again. Two consequences follow directly. First, this is exactly why u1u_1 corresponds to (n1)=0(n-1) = 0 rather than (n1)=1(n-1) = 1: the first term needs zero applications of the recurrence to exist, and the formula has to agree with that or it would be wrong at its own starting point. Second, an arithmetic sequence is fully determined by exactly two numbers, aa and dd — every other term is a deterministic consequence of those two, which is the reason a question that gives you two arbitrary terms of an arithmetic sequence (not necessarily the first two) is always secretly a simultaneous-equations question: two unknowns, two given data points, one linear system.

Traps — 7

sum-proof-last-term-off-by-one
Confirmed directly on the standard sum-formula proof: "a surprising proportion of candidates struggled to write a correct expression of Sₙ at the start of their proof, often having the last term incorrect" (Jan 2020, Q8(i)). The fix is the same mechanism taught earlier in this lesson: reaching the nth term from the first takes (n − 1) steps of the recurrence, so the last term of an n-term series is a + (n − 1)d, never a + nd.
sum-proof-reversal-skipped
Confirmed on the same question: "Others failed to reverse the terms in the sum correctly, or at all" (Jan 2020, Q8(i)). Without the reversed copy, there is nothing for the forward copy to pair against, and the whole argument — every pair summing to the same constant — has no pairs to point at. This step is not optional decoration on the proof; it is the entire mechanism.
sum-proof-insufficient-terms-shown
Confirmed on the same question: candidates "did not display a sufficient number of terms to make subsequent steps in their proof to complete" (Jan 2020, Q8(i)). Two terms at each end plus an ellipsis — a+(a+d)++(a+(n2)d)+(a+(n1)d)a + (a+d) + \cdots + (a+(n-2)d) + (a+(n-1)d) — is the minimum that actually shows the pattern; a single "..." with no visible terms either side of it gives an examiner nothing to check the pairing against.
induction-attempted-for-standard-proof
Confirmed on the same question: "Attempts at proof by induction were also seen in a few cases, though little progress was made in most of these" (Jan 2020, Q8(i)). Induction can, in principle, prove this result, but it is not the proof the specification names, and the report records it as the less successful choice in practice. Where a question asks to "prove the standard formula," the pairing argument is the direct, expected route.
sum-proof-assumes-the-result
Confirmed on the same question: "Some candidates either started with, or used something that they were trying to prove, e.g. starting with Sn=12n(a+L)S_n = \frac{1}{2}n(a+L), or attempting to use a summation formula that is a generalisation of the result they needed to show" (Jan 2020, Q8(i)). This scores zero on an "ag" (answer given) proof no matter how cleanly the rest of the working is presented, because it assumes the very fact being proved rather than deriving it — a "prove that" question can never legitimately start from a form of its own target result. The only safe starting point is the definition of the series itself, written out term by term, exactly as the mechanism block above does.
sum-proof-pairing-fails-for-odd-n
Confirmed on the same question: some candidates instead tried pairing terms within a single copy of the sum — first-plus-last, second-plus-second-to-last, and so on — "but they did not give due consideration to what happens when there are an odd number of terms, and were unable to score the accuracy mark as a result" (Jan 2020, Q8(i)). An odd number of terms leaves one unpaired middle term this method has no clean way to handle, which is exactly why the write-forwards/write-backwards/add version taught in this lesson is the safer standard route — it pairs the full sum against a full reversed copy of itself, so it never needs nn to be even and never has a leftover term to account for separately.
arithmetic-and-geometric-formulas-confused
Confirmed as a recurring, named error category across at least two series (June 2019 and October 2020): candidates reach for the wrong series formula mid-question — applying the geometric sum formula to an arithmetic series, or the reverse — because the two topics sit close together and use similarly-shaped notation. The one-line check that catches it before it starts: an arithmetic sequence has a constant DIFFERENCE between consecutive terms (un+1un=du_{n+1} - u_n = d, the same value every time); a geometric one has a constant RATIO instead. Confirm which quantity is actually constant before reaching for either sum formula.

Say it out loud

Out loud, from memory, no notes: explain why $u_n = a + (n-1)d$ — it falls out of the recurrence, it is not a separate rule to learn to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.4

1 lesson

Geometric Series and the Sum to Infinity

An arithmetic sequence moves by adding the same amount every step; a geometric one moves by multiplying by the same amount every step. That single swap — +d+d becomes ×r\times r — changes everything downstream, and changes it in ways that are derivable rather than arbitrary: the nth-term formula becomes un=arn1u_n = ar^{n-1}, the proof of the sum formula stops working by reversing-and-adding and starts working by multiplying-and-subtracting, and something genuinely new appears that has no arithmetic counterpart at all. Add infinitely many terms of an arithmetic series and the total always runs away. Add infinitely many terms of a geometric series and, provided r<1|r| < 1, it settles on a finite number — S=a1rS_\infty = \frac{a}{1-r} — because each term is a fixed fraction of the one before it and the terms shrink toward nothing fast enough to leave a finite total behind. The specification asks for the proof of the finite sum formula by name, and examiners have said outright that students should know the standard proofs for both the arithmetic and the geometric series. This lesson derives both formulae, and derives the r<1|r| < 1 condition rather than quoting it.

The card

uₙ = ar^(n−1); Sₙ = a(1−rⁿ)/(1−r) = a(rⁿ−1)/(r−1), r ≠ 1; S∞ = a/(1−r), |r| < 1 — all three printed in the booklet.
Proof: write Sₙ, write rSₙ, subtract — the shared middle terms cancel.
|r| < 1 because rⁿ is the only n-dependent part: |r| < 1 ⇒ rⁿ → 0.
Geometric: uₙ₊₁/uₙ constant. Arithmetic: uₙ₊₁ − uₙ constant. Check which first.
Mixed series: the shared term counts once — the GP starts at (shared term)×r.
Quote the formula before substituting; a bare calculator total scores nothing.

Why it works — Why $S_n = \frac{a(1-r^n)}{1-r}$ — multiply by $r$ and subtract, and why that is the move

The arithmetic sum proof works by writing the series a second time in reverse and adding, because arithmetic terms are related by *addition* — stepping forward through one copy and backward through the other changes each side by +d+d and d-d, which cancel, so every pair lands on the same total. None of that survives the switch to multiplication. Reverse a geometric series and add it to itself and the pairs are a+arn1a + ar^{n-1}, ar+arn2ar + ar^{n-2}, ar2+arn3ar^2 + ar^{n-3} — try it with 3,6,12,243, 6, 12, 24 and the pairs come out 27,18,18,2727, 18, 18, 27, plainly not constant. The arithmetic move fails here, and it fails for a reason you can name: constant pair-sums came from a constant additive step, and this series does not have one. What this series does have is a constant *multiplicative* step, so the move that exploits its structure is multiplication. Write the sum out in full: Sn=a+ar+ar2++arn2+arn1S_n = a + ar + ar^2 + \cdots + ar^{n-2} + ar^{n-1} — and note the last term is arn1ar^{n-1}, not arnar^n, for the same (n1)(n-1)-counting reason established above. Now multiply the whole equation by rr: rSn=ar+ar2+ar3++arn1+arnrS_n = ar + ar^2 + ar^3 + \cdots + ar^{n-1} + ar^n Look at what multiplying by rr actually did: it turned every term into the *next* term, which slides the entire list one place along. The second line is the first line shifted by one. That means the two lines share almost all of their terms — everything from arar up to arn1ar^{n-1} appears in both — and only two terms fail to have a partner: the aa at the start of the first line, and the arnar^n at the end of the second. Subtracting is what collects that observation: SnrSn=aarnS_n - rS_n = a - ar^n Every shared term cancelled, exactly n1n-1 of them, because each appeared once on each side. Factorise both sides — Sn(1r)=a(1rn)S_n(1-r) = a(1-r^n) — and divide by (1r)(1-r) to finish: Sn=a(1rn)1rS_n = \frac{a(1-r^n)}{1-r} That final division carries a condition worth stating rather than glossing: it is only legal when 1r01-r \neq 0, i.e. r1r \neq 1. The formula genuinely does not apply when r=1r = 1, and it does not need to — a geometric series with r=1r = 1 is a+a+a+a + a + a + \cdots, the same number repeated, whose sum to nn terms is just nana by inspection. This is not an exception bolted onto the formula from outside; it is the one case the derivation itself excluded, showing up exactly where the derivation said it would. So the two proofs in this pair of lessons are not two unrelated tricks to memorise. Each one applies the operation that matches how its own series is built: an additively-generated series is attacked by adding a reversed copy, a multiplicatively-generated series is attacked by subtracting a multiplied copy. Knowing which is which is knowing what the series is.

Traps — 8

arithmetic-and-geometric-formulas-confused
Confirmed as a recurring, named error category across at least two series (June 2019 and October 2020): candidates reach for the wrong series type's formula mid-question, because the two topics sit adjacent in the specification, use similarly-shaped notation, and are printed one above the other on the same formula-booklet page. Seen from the geometric side, the tell is any appearance of dd, of (n1)d(n-1)d, or of 12n\frac{1}{2}n in working about a series whose terms are multiplying. The two-line check that catches it before a single mark is at stake: compute un+1unu_{n+1} - u_n and un+1/unu_{n+1}/u_n for two consecutive pairs, and see which of the two comes out the same both times.
overlap-term-double-counted
Confirmed on a January 2022 mixed arithmetic-then-geometric question, verified as that paper's biggest discriminator. The examiner records that candidates "were not able to correctly process the overlap of the 20th term of the arithmetic series with the first term of the geometric series, and double counted this term" (Jan 2022). When one series ends on the same term another begins with, that term belongs to exactly one of the two sums. The report itself names both legal fixes: the geometric series starts at (shared term) × r, "or alternatively" the shared term is subtracted out of the arithmetic total — either one, never neither, never both.
geometric-series-restarted-from-the-original-first-term
Confirmed on the same January 2022 question, and distinct from the double-count above: "many candidates failed to understand the context with many assuming they had to start the geometric series from the first term of a=100a = 100 again" (Jan 2022). Where a sequence changes character partway through, the geometric part inherits its first term from wherever the arithmetic part left off — not from the beginning of the whole sequence. Reading the question's "from the kkth term onwards" literally, and writing down what that term actually equals before doing anything else, is the fix.
sum-to-infinity-first-term-misidentified
Confirmed on a January 2024 sum-to-infinity question: candidates "often used a = 6 instead of a = 1.5 in the sum to infinity formula" (Jan 2024, Q5(i)) — taking the sequence's original first term rather than the first term of the series actually being summed. This bites whenever a question asks for the sum of everything after some term, or re-expresses a series starting from a later index. The aa in a1r\frac{a}{1-r} is not "the first term of the sequence"; it is the first term of the sum you are being asked for. The self-check: the answer to "sum everything after the first term" must be smaller than the answer to "sum everything" by exactly that first term.
calculator-summation-shown-without-formula
Confirmed on the same January 2024 question: "a number resorted to using the summation button on their calculator which, even if [the value] was found, no marks were scored" (Jan 2024, Q5(i)). Calculators are permitted throughout this paper, which makes this trap easier to fall into rather than harder — a correct number with no visible formula and no visible substitution earns nothing, because the marks on offer are method marks and there is no method on the page to award them to. The mark scheme's standing principle says the same thing in general terms: where a learnt formula is used, "the formula should be quoted first."
standard-proofs-not-known
Confirmed on the January 2020 arithmetic sum-formula proof, with the examiner's advice naming both series explicitly: students "would be well advised to make sure they know the standard proofs for the arithmetic and geometric series to ensure they are able to give should it be required" (Jan 2020, Q8(i)). The specification's own guidance for item 4.4 says the same — "the proof of the sum formula for a finite series should be known." These are the only marks in the topic that a formula booklet cannot rescue: the formulae are printed, the proofs are not.
geometric-proof-subtraction-direction-reversed
Confirmed on the October 2020 geometric sum-formula proof: "A significant number started correctly and knew they had to subtract but subtracted the wrong way round to obtain e.g. SnrSn=arnaS_n - rS_n = ar^n - a and a significant number of candidates obtained SnrSn=a+arnS_n - rS_n = a + ar^n" (Oct 2020, Q8(a)). The correct line is SnrSn=aarnS_n - rS_n = a - ar^n: the survivors of the subtraction are whichever terms belong to the line that was NOT shifted (the aa from SnS_n) minus whichever belong to the line that WAS (the arnar^n from rSnrS_n), in that order — reverse which line each survivor is taken from, or turn the subtraction into an addition under exam pressure, and the result no longer factorises to the printed answer no matter how the rest of the algebra is handled. The examiner report records this immediately alongside the same question's other confirmed proof error (importing the arithmetic proof's reverse-and-add method), making the two the two most-recorded ways this specific proof goes wrong.
convergence-condition-read-as-r-less-than-one
Derived from the mechanism rather than quoted — the facts bank records no examiner finding on this specific error, and this entry carries no citation. Reading r<1|r| < 1 as "r<1r < 1" admits every negative ratio, including r=2r = -2 and r=1.5r = -1.5, whose terms grow without limit while alternating in sign. The modulus is a statement about size: SS_\infty exists precisely when each term is smaller in size than the one before it, regardless of sign. The related boundary case is r=1r = -1, where rnr^n alternates between 1-1 and 11 forever and the partial sums alternate between aa and 00 — never settling, which is why the specification's inequality is strict.

Say it out loud

Out loud, from memory, no notes: explain why $s_n = \frac{a(1-r^n)}{1-r}$ — multiply by $r$ and subtract, and why that is the move to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 4.5

1 lesson

Binomial Expansion of (a + bx)ⁿ for Positive Integer n

Every term in the expansion of (a+bx)n(a+bx)^n answers the same question, asked nn times over: out of nn identical brackets, how many ways can you pick which rr of them contribute the bxbx? That headcount — written (nr)\binom{n}{r} or nCr{}^nC_r — is the entire , and nothing about it needs memorising once you see it as counting rather than as a formula. The paper's most common trap isn't getting that count wrong; it's attaching a correctly-computed count to the wrong power in the first place.

The card

(a+bx)ⁿ, n a positive integer: n+1 terms, C(n,r)aⁿ⁻ʳ(bx)ʳ. Powers of a and bx in any term always add to n.
C(n,r) = n!/(r!(n−r)!) — a headcount of which r of n brackets give bx, not a formula to memorise alone.
The power of x in a term IS r. Write r = (power wanted) on its own line before anything else.
(bx)ʳ = bʳxʳ: raise the number too, not just the variable. Negative b alternates sign with the parity of r.
Pascal's row n has n+1 entries, C(n,0)…C(n,n). Check any answer: set x = 1, total should equal (a+b)ⁿ.
Writing several terms or a full Pascal's row? State the one answering the question on its own line — a correct value left unlabelled in a list can still lose the mark (Jan 2024 Q2).

Why it works — Where ⁿCᵣ actually comes from — it is a headcount, not a formula to memorise

Write (a+bx)n(a+bx)^n out as nn separate brackets multiplied together: (a+bx)(a+bx)(a+bx)(a+bx)(a+bx)\cdots(a+bx). Expanding this product term by term means picking, from EVERY bracket, either the aa or the bxbx — one choice per bracket — and multiplying all nn choices together; that is what "expanding a product of sums" means, mechanically. A term that ends up as anr(bx)ra^{n-r}(bx)^r is exactly the result of a selection that picked bxbx from rr of the nn brackets and aa from the other nrn - r — and every selection that picks the SAME set of rr brackets multiplies out to the identical term, so instead of writing that term out once per selection, the selections are counted and the count becomes the coefficient. (nr)\binom{n}{r} is, by definition, the number of ways to choose which rr of nn brackets contribute the bxbx — nothing more exotic than that, and nothing that needs a separate rule to justify why it's the coefficient. Now derive the factorial form from the same counting argument rather than quoting it: line the nn brackets up and decide, for each, whether it's an "aa-bracket" or a "bxbx-bracket." There are n!n! ways to put nn distinct objects in order — but the objects here aren't actually distinct once you only care about the FINAL split into two groups: swapping the order of the rr brackets already labelled "bxbx" among themselves doesn't create a new selection, so the n!n! orderings over-count by a factor of r!r! (the number of ways to shuffle those rr brackets among themselves); and swapping the order of the remaining nrn-r "aa"-brackets among themselves doesn't create a new selection either, over-counting by a further factor of (nr)!(n-r)!. Dividing out both gives (nr)=n!r!(nr)!\binom{n}{r} = \dfrac{n!}{r!(n-r)!} — not a formula handed down, but the direct consequence of removing the two kinds of reordering that don't actually change which brackets were chosen.

Traps — 6

term-index-mismatched-to-power
Confirmed directly on a real WMA12 question: common mistakes included "using the wrong power (usually 4 or 6 instead of 5 for the fractional part) or using the wrong binomial coefficient (¹²C₆, ¹²C₈ and ⁷C₅ instead of ¹²C₇)" (Jan 2024, Q2). The power of xx in the general term (nr)anr(bx)r\binom{n}{r}a^{n-r}(bx)^r is rr itself — no "one more" or "one less." State rr explicitly, on its own line, before touching any other number, and this error becomes almost impossible to make by accident.
general-series-form-chosen-over-combinatorial-form
The P2 formula booklet page prints two binomial formulas side by side: the combinatorial (a+b)n(a+b)^n expansion for positive integer nn, and the general series (1+x)n=1+nx+(1+x)^n = 1+nx+\ldots for real nn and x<1|x|<1 — the second is P4 content, not required here, and genuinely harder to apply. An examiner report confirms most candidates default correctly: "Part (a) was generally done very well with candidates mostly using the (a+b)ⁿ form of the binomial expansion where n is a positive integer rather than (1+x)ⁿ where n is a rational number" (June 2025, Q1) — but a regional variant paper shows exactly what the harder route costs once a question adds a second unknown: "Many candidates struggled to make a start with this question due to the fact that there were two unknowns, n and k, within the binomial expression (1+kx)ⁿ" (June 2025 Regional 01R, Q7). On P2, nn is always a known positive integer — default to (a+b)n(a+b)^n every time.
bx-term-not-raised-as-a-whole
Confirmed directly on a real WMA12 question, not just derived from the arithmetic: the examiner report for the same anchor question cited elsewhere in this lesson names this as the most common way of losing the accuracy mark for the unsimplified term — "using invisible brackets that were not recovered in further work (4x⁷ instead of (4x)⁷) resulting in multiplication by 4 instead of 4⁷" (Jan 2024, Q2). (bx)r(bx)^r means both bb and xx are raised to the power rr(4x)3=43x3=64x3(4x)^3 = 4^3x^3 = 64x^3, not 4x34x^3. Losing the power on the numeral while keeping it on the variable is easy to miss on the page, because the x3x^3 still looks correct; only the coefficient in front of it is wrong. Write (bx)r(bx)^r as brxrb^r x^r before evaluating brb^r, so the two pieces are never handled in the same breath.
sign-lost-on-odd-powers-of-a-negative-b
When bb is negative, (bx)r=brxr(bx)^r = b^r x^r carries the sign of brb^r — negative when rr is odd, positive when rr is even, for the same reason (1)3=1(-1)^3 = -1 while (1)4=1(-1)^4 = 1. The terms of an expansion like (32x)7(3-2x)^7 therefore alternate strictly by the parity of rr, not by any other pattern — dropping the sign on just one term, usually by writing (2)r(-2)^r as 2r2^r out of habit, produces an answer that looks structurally right and is numerically wrong by exactly a factor of 1-1.
pascal-triangle-row-miscounted
Row nn of Pascal's triangle — counting the single "1" at the top as row 0 — has exactly n+1n+1 entries, (n0)\binom{n}{0} through (nn)\binom{n}{n}. Starting the count at row 1 instead of row 0 reads off the coefficients for n1n-1, one whole row too early, and every coefficient taken from it is wrong even though every addition inside the triangle was done correctly. Before reading off a row, count its entries: n+1n+1 numbers, not nn.
required-term-not-isolated-from-a-list
Confirmed directly on the anchor WMA12 question: the examiner report states the final accuracy mark "was commonly not awarded to candidates who failed to isolate the required term from a list" (Jan 2024, Q2), and the mark scheme itself warns "the term or coefficient must be identified if they have more than one term." Writing several terms, a full expansion, or a whole row of Pascal's triangle is not itself an error — but once the value asked for has been found, it has to be pointed to on its own, not left sitting unlabelled inside the longer list. State it on its own final line (or circle/box it) the moment it's reached.

Say it out loud

Out loud, from memory, no notes: explain where ⁿcᵣ actually comes from — it is a headcount, not a formula to memorise to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 5.1

1 lesson

Exponential Graphs, the Laws of Logarithms and Solving aˣ = b

Every law of logarithms on this page is a law of indices, read backwards. That is not a simplification for beginners — it is the actual content of spec 5.2, and it is why the five identities never need memorising as five separate facts. The real difficulty on this paper is not the algebra of the laws themselves: real scripts show candidates reaching the correct rearranged equation and then simply not finishing it, or reaching for a log law that does not exist. Both of those are what this lesson targets.

The card

logₐb = c ⇔ aᶜ = b (a>0, a≠1, b>0). y=aˣ passes through (0,1), asymptote y=0, never negative.
logₐ(xy)=logₐx+logₐy; logₐ(x/y)=logₐx−logₐy; logₐ(xᵏ)=k·logₐx; logₐ(1/x)=−logₐx; logₐa=1.
Change of base (in the booklet): logₐx = log_b x / log_b a. The other four laws are not — memorise them.
Solving aˣ=b: isolate the exponential first, then take logs — finish the rearrangement, not just the bracket.
If a question names the required form (e.g. x = logₐk), an unsimplified logₐb − c earns only the intermediate mark — combine it into the single required log to earn the final one (Jan 2021, Q3(i)).
A log of a sum does not split apart. Subtracting logs never divides the logs themselves, only their arguments.
A combined-log equation can gain a root the original excludes — check each argument is positive before accepting it.

Why it works — Why the laws hold — the laws of indices, read through one definition

Let logax=p\log_a x = p and logay=q\log_a y = q — by the definition above, this means precisely that ap=xa^p = x and aq=ya^q = y, nothing more. Every law of logarithms is what happens to that pair of equations when you multiply, divide or raise them to a power, translated back into log notation. Multiply the two equations: x×y=ap×aqx \times y = a^p \times a^q. The laws of indices already say ap×aq=ap+qa^p \times a^q = a^{p+q} — indices add when you multiply powers of the same base — so xy=ap+qxy = a^{p+q}. Taking loga\log_a of both sides (asking 'what power of aa gives this?') recovers p+qp + q exactly, because ap+qa^{p+q} passed back through loga\log_a just returns its own exponent: loga(xy)=p+q=logax+logay\log_a(xy) = p + q = \log_a x + \log_a y. The subtraction law is the same argument run on division: x/y=ap/aq=apqx/y = a^p/a^q = a^{p-q} by the quotient rule for indices, so loga(x/y)=pq=logaxlogay\log_a(x/y) = p - q = \log_a x - \log_a y. The power law comes from raising the first equation to the power kk: xk=(ap)k=apkx^k = (a^p)^k = a^{pk} by the laws of indices (a power raised to a power multiplies the exponents), so loga(xk)=pk=klogax\log_a(x^k) = pk = k\log_a x — the exponent kk moves from inside the log's argument to a multiplier in front, which is the entire content of the law, and the reason (logay)2(\log_a y)^2 is a genuinely different expression from loga(y2)\log_a(y^2): squaring the NUMBER logay\log_a y is not the same operation as squaring the ARGUMENT yy before taking its log. The remaining two laws are special cases already covered: loga(1/x)=loga1logax\log_a(1/x) = \log_a 1 - \log_a x by the subtraction law, and loga1=0\log_a 1 = 0 always (since a0=1a^0 = 1 for any valid base), so loga(1/x)=logax\log_a(1/x) = -\log_a x; and logaa=1\log_a a = 1 is immediate from the definition itself, since a1=aa^1 = a. None of these five statements is a separate fact to memorise — they are the laws of indices, read backwards through the one definition that connects a power to a log.

Traps — 6

log-subtraction-rewritten-as-division
Confirmed directly on a real WMA12 log-manipulation question: "A fairly common mistake was to rewrite log₃(5x+7) − log₃4x as log₃(5x+7)/log₃4x. Some then crossed out log₃ in the numerator and denominator as though simplifying a fraction" (Jan 2023, Q4(i)). The subtraction law says logaxlogay=loga(x/y)\log_a x - \log_a y = \log_a(x/y) — the two ARGUMENTS are divided, the two log SYMBOLS never are. Writing log3(5x+7)/log34x\log_3(5x+7)/\log_34x treats "log₃" as a common factor that can be cancelled, which it is not: loga\log_a is a function name, not a multiplier.
log-of-a-sum-expanded-as-sum-of-logs
Confirmed on the same question: "Another mistake, common for this type of question, was to expand the brackets within the log function, writing log₃(5x+7) as log₃5x + log₃7" (Jan 2023, Q4(i)). No law distributes a log across a sum or difference inside its own argument — the addition law only COMBINES two separate logs into one, it never SPLITS a single log open. loga(x+y)\log_a(x+y) has no simpler form; treating it like loga(xy)\log_a(xy) applies the multiplication law to an expression that is added, not multiplied.
log-squared-confused-with-log-of-the-square
Confirmed on a harder question, described as "one of the most challenging parts on the paper": "understanding the difference between logₐ(y²) and (logₐy)²... rewriting (logₐy)² as 2logₐy was a very common mistake" (Jan 2023, Q4(ii)). The power law moves an exponent sitting INSIDE the log — it says nothing about an exponent sitting OUTSIDE the whole expression. (logay)2(\log_a y)^2 means "square the number logay\log_a y produces," and no law turns that squaring into a multiplication by 2 — the two expressions are built from the same symbols in a different order and are not generally equal.
exponent-rearrangement-left-unfinished
Confirmed on a solving-aˣ=b question with a measured mark-by-mark drop-off: "A fall off from nearly 90% to just over 70% between the first two marks is revealing" (Jan 2021, Q3(i)) — the gap between the M1 for setting up (x+2)log7=log3(x+2)\log 7 = \log 3 and the first A1 for reaching ANY correct exact expression for xx. Taking logs correctly is not the same as finishing the algebra — once the exponent has been isolated as an expression like 2x12x-1 or x+1x+1, every remaining operation (adding, subtracting, dividing) still has to be carried out on both sides before an exact expression for xx exists at all. (A separate, later-stage error — reaching a correct exact expression for xx but leaving it uncombined into a single required log form — is a distinct trap: see "single-log-form-left-uncombined" below.)
single-log-form-left-uncombined
Confirmed on the same question, describing the steeper of its two mark-by-mark drops — "with only 50% scoring all three. For example, [many] achieved x = log₇3 − 2 but then did not reach the required form, failing to deal with the −2" (Jan 2021, Q3(i)). This is NOT an unfinished-rearrangement error: x=log732x = \log_7 3 - 2 is already a fully isolated, fully-credited exact expression for xx — it earns the A1 the trap above describes. The mark actually lost here is a further, distinct accuracy mark for combining that expression into the single logarithm the question specifically demanded ("giving your answer in the form x=log7ax = \log_7 a, aa rational"): log732=log73log749=log7349\log_7 3 - 2 = \log_7 3 - \log_7 49 = \log_7\dfrac{3}{49}, using log749=2\log_7 49 = 2 since 72=497^2 = 49 — i.e. rewriting the constant 22 via logaa=1\log_a a = 1, here 2=2log77=log7(72)=log7492 = 2\log_7 7 = \log_7(7^2) = \log_7 49. Whenever a question specifies the answer form this precisely, a correct but unsimplified expression like logabc\log_a b - c earns only the intermediate accuracy mark, never the final one.
logs-taken-before-the-equation-is-rearranged
A direct piece of technique advice from the same report, given as general guidance rather than a specific error: "Although the question asked for an answer in log form, it is not always advisable to take logs first when the equation is presented in index form" (Jan 2021, Q3(i)). Where a constant multiplies or divides the exponential term, isolating it algebraically first — before any logarithm is taken — removes an entire log law (usually the addition or subtraction law) from the working. Taking logs immediately is not wrong, but it adds a step, and every added step is an added chance for one of the other traps on this list to strike.

Say it out loud

Out loud, from memory, no notes: explain why the laws hold — the laws of indices, read through one definition to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 5.2

1 lesson

Exponential Graphs, the Laws of Logarithms and Solving aˣ = b

Every law of logarithms on this page is a law of indices, read backwards. That is not a simplification for beginners — it is the actual content of spec 5.2, and it is why the five identities never need memorising as five separate facts. The real difficulty on this paper is not the algebra of the laws themselves: real scripts show candidates reaching the correct rearranged equation and then simply not finishing it, or reaching for a log law that does not exist. Both of those are what this lesson targets.

The card

logₐb = c ⇔ aᶜ = b (a>0, a≠1, b>0). y=aˣ passes through (0,1), asymptote y=0, never negative.
logₐ(xy)=logₐx+logₐy; logₐ(x/y)=logₐx−logₐy; logₐ(xᵏ)=k·logₐx; logₐ(1/x)=−logₐx; logₐa=1.
Change of base (in the booklet): logₐx = log_b x / log_b a. The other four laws are not — memorise them.
Solving aˣ=b: isolate the exponential first, then take logs — finish the rearrangement, not just the bracket.
If a question names the required form (e.g. x = logₐk), an unsimplified logₐb − c earns only the intermediate mark — combine it into the single required log to earn the final one (Jan 2021, Q3(i)).
A log of a sum does not split apart. Subtracting logs never divides the logs themselves, only their arguments.
A combined-log equation can gain a root the original excludes — check each argument is positive before accepting it.

Why it works — Why the laws hold — the laws of indices, read through one definition

Let logax=p\log_a x = p and logay=q\log_a y = q — by the definition above, this means precisely that ap=xa^p = x and aq=ya^q = y, nothing more. Every law of logarithms is what happens to that pair of equations when you multiply, divide or raise them to a power, translated back into log notation. Multiply the two equations: x×y=ap×aqx \times y = a^p \times a^q. The laws of indices already say ap×aq=ap+qa^p \times a^q = a^{p+q} — indices add when you multiply powers of the same base — so xy=ap+qxy = a^{p+q}. Taking loga\log_a of both sides (asking 'what power of aa gives this?') recovers p+qp + q exactly, because ap+qa^{p+q} passed back through loga\log_a just returns its own exponent: loga(xy)=p+q=logax+logay\log_a(xy) = p + q = \log_a x + \log_a y. The subtraction law is the same argument run on division: x/y=ap/aq=apqx/y = a^p/a^q = a^{p-q} by the quotient rule for indices, so loga(x/y)=pq=logaxlogay\log_a(x/y) = p - q = \log_a x - \log_a y. The power law comes from raising the first equation to the power kk: xk=(ap)k=apkx^k = (a^p)^k = a^{pk} by the laws of indices (a power raised to a power multiplies the exponents), so loga(xk)=pk=klogax\log_a(x^k) = pk = k\log_a x — the exponent kk moves from inside the log's argument to a multiplier in front, which is the entire content of the law, and the reason (logay)2(\log_a y)^2 is a genuinely different expression from loga(y2)\log_a(y^2): squaring the NUMBER logay\log_a y is not the same operation as squaring the ARGUMENT yy before taking its log. The remaining two laws are special cases already covered: loga(1/x)=loga1logax\log_a(1/x) = \log_a 1 - \log_a x by the subtraction law, and loga1=0\log_a 1 = 0 always (since a0=1a^0 = 1 for any valid base), so loga(1/x)=logax\log_a(1/x) = -\log_a x; and logaa=1\log_a a = 1 is immediate from the definition itself, since a1=aa^1 = a. None of these five statements is a separate fact to memorise — they are the laws of indices, read backwards through the one definition that connects a power to a log.

Traps — 6

log-subtraction-rewritten-as-division
Confirmed directly on a real WMA12 log-manipulation question: "A fairly common mistake was to rewrite log₃(5x+7) − log₃4x as log₃(5x+7)/log₃4x. Some then crossed out log₃ in the numerator and denominator as though simplifying a fraction" (Jan 2023, Q4(i)). The subtraction law says logaxlogay=loga(x/y)\log_a x - \log_a y = \log_a(x/y) — the two ARGUMENTS are divided, the two log SYMBOLS never are. Writing log3(5x+7)/log34x\log_3(5x+7)/\log_34x treats "log₃" as a common factor that can be cancelled, which it is not: loga\log_a is a function name, not a multiplier.
log-of-a-sum-expanded-as-sum-of-logs
Confirmed on the same question: "Another mistake, common for this type of question, was to expand the brackets within the log function, writing log₃(5x+7) as log₃5x + log₃7" (Jan 2023, Q4(i)). No law distributes a log across a sum or difference inside its own argument — the addition law only COMBINES two separate logs into one, it never SPLITS a single log open. loga(x+y)\log_a(x+y) has no simpler form; treating it like loga(xy)\log_a(xy) applies the multiplication law to an expression that is added, not multiplied.
log-squared-confused-with-log-of-the-square
Confirmed on a harder question, described as "one of the most challenging parts on the paper": "understanding the difference between logₐ(y²) and (logₐy)²... rewriting (logₐy)² as 2logₐy was a very common mistake" (Jan 2023, Q4(ii)). The power law moves an exponent sitting INSIDE the log — it says nothing about an exponent sitting OUTSIDE the whole expression. (logay)2(\log_a y)^2 means "square the number logay\log_a y produces," and no law turns that squaring into a multiplication by 2 — the two expressions are built from the same symbols in a different order and are not generally equal.
exponent-rearrangement-left-unfinished
Confirmed on a solving-aˣ=b question with a measured mark-by-mark drop-off: "A fall off from nearly 90% to just over 70% between the first two marks is revealing" (Jan 2021, Q3(i)) — the gap between the M1 for setting up (x+2)log7=log3(x+2)\log 7 = \log 3 and the first A1 for reaching ANY correct exact expression for xx. Taking logs correctly is not the same as finishing the algebra — once the exponent has been isolated as an expression like 2x12x-1 or x+1x+1, every remaining operation (adding, subtracting, dividing) still has to be carried out on both sides before an exact expression for xx exists at all. (A separate, later-stage error — reaching a correct exact expression for xx but leaving it uncombined into a single required log form — is a distinct trap: see "single-log-form-left-uncombined" below.)
single-log-form-left-uncombined
Confirmed on the same question, describing the steeper of its two mark-by-mark drops — "with only 50% scoring all three. For example, [many] achieved x = log₇3 − 2 but then did not reach the required form, failing to deal with the −2" (Jan 2021, Q3(i)). This is NOT an unfinished-rearrangement error: x=log732x = \log_7 3 - 2 is already a fully isolated, fully-credited exact expression for xx — it earns the A1 the trap above describes. The mark actually lost here is a further, distinct accuracy mark for combining that expression into the single logarithm the question specifically demanded ("giving your answer in the form x=log7ax = \log_7 a, aa rational"): log732=log73log749=log7349\log_7 3 - 2 = \log_7 3 - \log_7 49 = \log_7\dfrac{3}{49}, using log749=2\log_7 49 = 2 since 72=497^2 = 49 — i.e. rewriting the constant 22 via logaa=1\log_a a = 1, here 2=2log77=log7(72)=log7492 = 2\log_7 7 = \log_7(7^2) = \log_7 49. Whenever a question specifies the answer form this precisely, a correct but unsimplified expression like logabc\log_a b - c earns only the intermediate accuracy mark, never the final one.
logs-taken-before-the-equation-is-rearranged
A direct piece of technique advice from the same report, given as general guidance rather than a specific error: "Although the question asked for an answer in log form, it is not always advisable to take logs first when the equation is presented in index form" (Jan 2021, Q3(i)). Where a constant multiplies or divides the exponential term, isolating it algebraically first — before any logarithm is taken — removes an entire log law (usually the addition or subtraction law) from the working. Taking logs immediately is not wrong, but it adds a step, and every added step is an added chance for one of the other traps on this list to strike.

Say it out loud

Out loud, from memory, no notes: explain why the laws hold — the laws of indices, read through one definition to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 5.3

1 lesson

Exponential Graphs, the Laws of Logarithms and Solving aˣ = b

Every law of logarithms on this page is a law of indices, read backwards. That is not a simplification for beginners — it is the actual content of spec 5.2, and it is why the five identities never need memorising as five separate facts. The real difficulty on this paper is not the algebra of the laws themselves: real scripts show candidates reaching the correct rearranged equation and then simply not finishing it, or reaching for a log law that does not exist. Both of those are what this lesson targets.

The card

logₐb = c ⇔ aᶜ = b (a>0, a≠1, b>0). y=aˣ passes through (0,1), asymptote y=0, never negative.
logₐ(xy)=logₐx+logₐy; logₐ(x/y)=logₐx−logₐy; logₐ(xᵏ)=k·logₐx; logₐ(1/x)=−logₐx; logₐa=1.
Change of base (in the booklet): logₐx = log_b x / log_b a. The other four laws are not — memorise them.
Solving aˣ=b: isolate the exponential first, then take logs — finish the rearrangement, not just the bracket.
If a question names the required form (e.g. x = logₐk), an unsimplified logₐb − c earns only the intermediate mark — combine it into the single required log to earn the final one (Jan 2021, Q3(i)).
A log of a sum does not split apart. Subtracting logs never divides the logs themselves, only their arguments.
A combined-log equation can gain a root the original excludes — check each argument is positive before accepting it.

Why it works — Why the laws hold — the laws of indices, read through one definition

Let logax=p\log_a x = p and logay=q\log_a y = q — by the definition above, this means precisely that ap=xa^p = x and aq=ya^q = y, nothing more. Every law of logarithms is what happens to that pair of equations when you multiply, divide or raise them to a power, translated back into log notation. Multiply the two equations: x×y=ap×aqx \times y = a^p \times a^q. The laws of indices already say ap×aq=ap+qa^p \times a^q = a^{p+q} — indices add when you multiply powers of the same base — so xy=ap+qxy = a^{p+q}. Taking loga\log_a of both sides (asking 'what power of aa gives this?') recovers p+qp + q exactly, because ap+qa^{p+q} passed back through loga\log_a just returns its own exponent: loga(xy)=p+q=logax+logay\log_a(xy) = p + q = \log_a x + \log_a y. The subtraction law is the same argument run on division: x/y=ap/aq=apqx/y = a^p/a^q = a^{p-q} by the quotient rule for indices, so loga(x/y)=pq=logaxlogay\log_a(x/y) = p - q = \log_a x - \log_a y. The power law comes from raising the first equation to the power kk: xk=(ap)k=apkx^k = (a^p)^k = a^{pk} by the laws of indices (a power raised to a power multiplies the exponents), so loga(xk)=pk=klogax\log_a(x^k) = pk = k\log_a x — the exponent kk moves from inside the log's argument to a multiplier in front, which is the entire content of the law, and the reason (logay)2(\log_a y)^2 is a genuinely different expression from loga(y2)\log_a(y^2): squaring the NUMBER logay\log_a y is not the same operation as squaring the ARGUMENT yy before taking its log. The remaining two laws are special cases already covered: loga(1/x)=loga1logax\log_a(1/x) = \log_a 1 - \log_a x by the subtraction law, and loga1=0\log_a 1 = 0 always (since a0=1a^0 = 1 for any valid base), so loga(1/x)=logax\log_a(1/x) = -\log_a x; and logaa=1\log_a a = 1 is immediate from the definition itself, since a1=aa^1 = a. None of these five statements is a separate fact to memorise — they are the laws of indices, read backwards through the one definition that connects a power to a log.

Traps — 6

log-subtraction-rewritten-as-division
Confirmed directly on a real WMA12 log-manipulation question: "A fairly common mistake was to rewrite log₃(5x+7) − log₃4x as log₃(5x+7)/log₃4x. Some then crossed out log₃ in the numerator and denominator as though simplifying a fraction" (Jan 2023, Q4(i)). The subtraction law says logaxlogay=loga(x/y)\log_a x - \log_a y = \log_a(x/y) — the two ARGUMENTS are divided, the two log SYMBOLS never are. Writing log3(5x+7)/log34x\log_3(5x+7)/\log_34x treats "log₃" as a common factor that can be cancelled, which it is not: loga\log_a is a function name, not a multiplier.
log-of-a-sum-expanded-as-sum-of-logs
Confirmed on the same question: "Another mistake, common for this type of question, was to expand the brackets within the log function, writing log₃(5x+7) as log₃5x + log₃7" (Jan 2023, Q4(i)). No law distributes a log across a sum or difference inside its own argument — the addition law only COMBINES two separate logs into one, it never SPLITS a single log open. loga(x+y)\log_a(x+y) has no simpler form; treating it like loga(xy)\log_a(xy) applies the multiplication law to an expression that is added, not multiplied.
log-squared-confused-with-log-of-the-square
Confirmed on a harder question, described as "one of the most challenging parts on the paper": "understanding the difference between logₐ(y²) and (logₐy)²... rewriting (logₐy)² as 2logₐy was a very common mistake" (Jan 2023, Q4(ii)). The power law moves an exponent sitting INSIDE the log — it says nothing about an exponent sitting OUTSIDE the whole expression. (logay)2(\log_a y)^2 means "square the number logay\log_a y produces," and no law turns that squaring into a multiplication by 2 — the two expressions are built from the same symbols in a different order and are not generally equal.
exponent-rearrangement-left-unfinished
Confirmed on a solving-aˣ=b question with a measured mark-by-mark drop-off: "A fall off from nearly 90% to just over 70% between the first two marks is revealing" (Jan 2021, Q3(i)) — the gap between the M1 for setting up (x+2)log7=log3(x+2)\log 7 = \log 3 and the first A1 for reaching ANY correct exact expression for xx. Taking logs correctly is not the same as finishing the algebra — once the exponent has been isolated as an expression like 2x12x-1 or x+1x+1, every remaining operation (adding, subtracting, dividing) still has to be carried out on both sides before an exact expression for xx exists at all. (A separate, later-stage error — reaching a correct exact expression for xx but leaving it uncombined into a single required log form — is a distinct trap: see "single-log-form-left-uncombined" below.)
single-log-form-left-uncombined
Confirmed on the same question, describing the steeper of its two mark-by-mark drops — "with only 50% scoring all three. For example, [many] achieved x = log₇3 − 2 but then did not reach the required form, failing to deal with the −2" (Jan 2021, Q3(i)). This is NOT an unfinished-rearrangement error: x=log732x = \log_7 3 - 2 is already a fully isolated, fully-credited exact expression for xx — it earns the A1 the trap above describes. The mark actually lost here is a further, distinct accuracy mark for combining that expression into the single logarithm the question specifically demanded ("giving your answer in the form x=log7ax = \log_7 a, aa rational"): log732=log73log749=log7349\log_7 3 - 2 = \log_7 3 - \log_7 49 = \log_7\dfrac{3}{49}, using log749=2\log_7 49 = 2 since 72=497^2 = 49 — i.e. rewriting the constant 22 via logaa=1\log_a a = 1, here 2=2log77=log7(72)=log7492 = 2\log_7 7 = \log_7(7^2) = \log_7 49. Whenever a question specifies the answer form this precisely, a correct but unsimplified expression like logabc\log_a b - c earns only the intermediate accuracy mark, never the final one.
logs-taken-before-the-equation-is-rearranged
A direct piece of technique advice from the same report, given as general guidance rather than a specific error: "Although the question asked for an answer in log form, it is not always advisable to take logs first when the equation is presented in index form" (Jan 2021, Q3(i)). Where a constant multiplies or divides the exponential term, isolating it algebraically first — before any logarithm is taken — removes an entire log law (usually the addition or subtraction law) from the working. Taking logs immediately is not wrong, but it adds a step, and every added step is an added chance for one of the other traps on this list to strike.

Say it out loud

Out loud, from memory, no notes: explain why the laws hold — the laws of indices, read through one definition to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 6.2

1 lesson

Trigonometric Identities and Solving Equations in a Given Interval

Two identities turn a mixed-up trig equation into a quadratic you already know how to solve — and then the paper asks you for every solution the calculator button never gives you. tanθ=sinθcosθ\tan\theta = \dfrac{\sin\theta}{\cos\theta} and sin2θ+cos2θ=1\sin^2\theta + \cos^2\theta = 1 are not separate facts to memorise; both fall out of one picture, a point on a circle of radius 1. And "solve for 0x<360°0 \leqslant x < 360°" is not a suggestion to report whatever arcsin hands back — it is an instruction to find every value in that range, which is usually more than one, and the paper is built to reward whoever knows how to go looking for the rest.

The card

tan θ = sin θ/cos θ (undefined where cos θ = 0); sin²θ + cos²θ = 1 — both from (cos θ, sin θ) on the unit circle.
Mixed sin/cos equation → substitute the identity → solve in one function, usually a 3-term quadratic.
"Solve for [interval]": find the calculator's value, then use quadrant signs for every other solution.
Never divide by sin θ, cos θ or tan θ — factorise instead, or a solution branch is lost.
sin θ, cos θ = ±1 give ONE solution per revolution, not two. Match degrees/radians; don't round early — and if radians are asked "in the form kπ", convert back to the exact standard-angle fraction, never leave it decimal.

Why it works — Where $\tan\theta = \sin\theta/\cos\theta$ and $\sin^2\theta + \cos^2\theta = 1$ actually come from

Both identities are the same one picture, read two different ways. Draw a circle of radius 1 centred at the origin, and let θ\theta be the angle measured anticlockwise from the positive x-axis. The point P where that angle's ray meets the circle is, BY DEFINITION, the point (cosθ,sinθ)(\cos\theta, \sin\theta) — this is the actual definition of sine and cosine once an angle is allowed to be bigger than 90° or negative, the one that extends the right-triangle picture (opposite over hypotenuse, adjacent over hypotenuse) to every real angle, because a triangle stops making sense past 90° but a point on a circle never does. Read the picture the first way: P lies on a circle of radius 1, so its coordinates satisfy x2+y2=1x^2 + y^2 = 1 — that is simply the equation of the circle, nothing more mysterious than Pythagoras applied to the right-angled triangle formed by P, the origin, and P's foot on the x-axis, whose legs have lengths cosθ|\cos\theta| and sinθ|\sin\theta| and whose hypotenuse is the radius, 1. Substitute x=cosθx = \cos\theta and y=sinθy = \sin\theta and the circle's own equation reads cos2θ+sin2θ=1\cos^2\theta + \sin^2\theta = 1. Nobody chose this identity as a rule; it is the coordinate form of "P sits on a circle of radius 1," which was true by construction before any trig was involved at all. Read the same picture the second way, for tan: the gradient of the line from the origin O to P is, by the standard definition of gradient, change in ychange in x=sinθcosθ\frac{\text{change in } y}{\text{change in } x} = \frac{\sin\theta}{\cos\theta} — and that ratio is exactly what tanθ\tan\theta means (it is also, for an acute angle, opposite over adjacent in the same right triangle, since dividing sinθ\sin\theta by cosθ\cos\theta cancels the shared hypotenuse of length 1). So tanθ=sinθcosθ\tan\theta = \frac{\sin\theta}{\cos\theta} is not a separate fact either — it is "gradient of OP" read off the same coordinates the first identity just used. And this is exactly why tanθ\tan\theta is undefined precisely when cosθ=0\cos\theta = 0: that is the moment P sits directly above or below the origin, the line OP is vertical, and a vertical line has no defined gradient — not a rule to memorise, a direct geometric consequence of what "gradient" means.

Traps — 9

divides-out-a-common-trig-factor
Confirmed on a real WMA12 identity-substitution question: after multiplying through by cosθ and factorising, the correct path reaches sinθ(2 + 3cosθ) = 0 — but "many however cancelled the sinθ and hence only produced solutions from cosθ = −⅔" (Oct 2023, Q3), silently discarding the whole sinθ = 0 branch. This is structurally the identical error to dividing a polynomial equation by x instead of factoring it out — cancelling a factor from both sides of an equation throws away every solution where that factor is zero. Factorise; never divide by an expression that could itself be zero.
wrong-identity-substituted-for-cos-squared
Confirmed on a real WMA12 question, in an examiner report quoted as: "cos2θ was occasionally replaced with 1 − sinθ" (Oct 2022, Q5) — read in context, immediately alongside a separate note about the sin²θ + cos²θ = 1 identity, this is cos²θ being substituted with 1 − sinθ instead of the real identity, 1 − sin²θ: the SQUARED sine dropped to a plain sine. It is the same shape of error the prequestion in this lesson previews with a clean fraction (cosθ = 1 − sinθ) — a real, recorded exam mistake, not a hypothetical one. The identity relates the squares of sin and cos, never the functions themselves directly.
coefficient-dropped-when-distributing-after-substitution
Confirmed on the same question: "3(1 − sin²θ) expanded to 3 − sin²θ" (Oct 2022, Q5) — the leading coefficient multiplied only one of the two terms inside the bracket instead of both. This is exactly the error modelled on the wrong path of the marked-solution above, just with a 3 in place of a 2. The check that catches it costs five seconds: expand the resulting expression back out and confirm it returns what you started with.
incomplete-multiply-through-after-tan-substitution
The same distribute-across-every-term hazard as the coefficient-dropped trap above, but at the fraction-clearing step rather than a bracket-expansion step: once tan θ = sin θ/cos θ has been substituted into a mixed equation, EVERY term has to be multiplied through by cos θ to clear the fraction, not just the term that already had a cos θ sitting in it. The real WMA12 mark scheme for a tan-substitution question of this shape names this as its own credited action, worded to allow for exactly this slip: "Multiplies through by cosθ (on at least 2 of the 3 terms in the equation) and attempts to use ±sin²θ±cos²θ=±1 to set up a quadratic equation in cosθ" (June 2025, Q8(ii) mark scheme) — "on at least 2 of the 3 terms" is a direct acknowledgement that clearing the fraction on only some of the terms is the common failure mode being marked around. The worked-chain above models the full clear-then-substitute sequence and flags exactly where that slip would happen.
compound-angle-not-isolated-before-inverse-function
Confirmed on a compound-angle equation, tan(2x + π/5) = k, solved in radians: "some did not recognise that they should isolate the tan(2x + π/5) term before attempting to take arctan" (June 2025, Q8(i)) — a small structural failure with a large consequence, since every later step depends on the bracket being isolated first. There were also candidates who worked in degrees on this exact question despite the radian-form interval — the units of an interval have to be matched throughout, not switched to whichever is more familiar partway through.
coefficient-distributed-across-the-whole-compound-angle
Confirmed on the same question: "distributing the coefficient of the tangent term throughout the angle resulting in tan(6x + 3π/5)" (June 2025, Q8(i)) — multiplying a coefficient into the angle INSIDE the trig function, when it should only ever multiply the function's output. tan(2x + π/5) has no coefficient to distribute into its argument at all; the 3 in "3tan(2x + π/5) = k" multiplies the tan value once it is found, never the angle itself.
compound-angle-bracket-range-scaled-by-coefficient
Confirmed in the mark scheme for the same compound-angle question, not the examiner report: "Correct order of operations 2x + π/5 = π/6, 7π/6, 13π/6 ... to find a value for x which does not need to be in the given range (e.g. condone −π/60)" (June 2025, Q8(i) mark scheme) — three candidate bracket-values, not the usual one or two, and the dM1 mark is for the METHOD of generating them, before anything is checked against the range. Every "compound angle" example elsewhere in this lesson has a coefficient of 1 on x, where the bracket's range matches x's own interval exactly — here the coefficient is 2, so solving (2x + π/5) = k over 0 ⩽ x < π means the BRACKET sweeps an interval TWICE as wide, two full periods of tan (period π) rather than one, and the calculator's value needs tan's period added repeatedly across that whole doubled range before anything is converted back. From arctan(1/√3) = π/6: adding π once gives 7π/6, adding it again gives 13π/6 — both additional candidates a coefficient of 1 would never produce. Converting each via x = (bracket − π/5)/2 gives x = −π/60 (from π/6), x = 29π/60 (from 7π/6) and x = 59π/60 (from 13π/6); only the accuracy mark, A1, actually enforces 0 ⩽ x < π — which is exactly why −π/60 is explicitly condoned at the method stage and only rejected once the final answer is stated. The method mark rewards generating enough candidates across the scaled range; the accuracy mark is what filters them.
decimal-given-instead-of-exact-kπ-radian-form
Confirmed on the same compound-angle question: "A few did not take note of the required form of the answer kπ (with k rational) and used decimals. There were also candidates who worked in degrees" (June 2025, Q8(i) examiner report) — a distinct failure from the traps above about this equation, none of which turn on whether the final answer is left decimal or kept exact. Even after correctly isolating and solving tan(2x + π/5) = √3/3, the calculator's decimal output (2x + π/5 ≈ 0.628…) has to be recognised as a standard angle (arctan(1/√3) = π/6) and carried through in that exact form — "in the form kπ" is an explicit instruction that a decimal, however accurately rounded, does not satisfy; the mark scheme's own accuracy line states plainly that the final answer "must be exact and in radians" (June 2025, Q8(i) mark scheme). This is not the same rule as "don't round early": that rule protects a genuinely decimal final answer (as in Q8(ii)) from accumulating rounding error; this one requires recognising when the final answer isn't decimal at all.
premature-rounding-before-final-angle
Confirmed on a three-term quadratic in cosθ where the roots did not factorise: "some candidates rounded the exact solution for cosθ to 3 significant figures which caused rounding errors when finding θ and a loss of the final accuracy mark" (June 2025, Q8(ii)) — directly confirming the WMA12 general marking guidance's exact-answer rule for this exact topic. Keep the un-rounded value (a surd, a fraction, or extra decimal places) all the way through and round only the final angle, to whatever precision the question actually asks for.

Say it out loud

Out loud, from memory, no notes: explain where $\tan\theta = \sin\theta/\cos\theta$ and $\sin^2\theta + \cos^2\theta = 1$ actually come from to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 6.1

1 lesson

Trigonometric Identities and Solving Equations in a Given Interval

Two identities turn a mixed-up trig equation into a quadratic you already know how to solve — and then the paper asks you for every solution the calculator button never gives you. tanθ=sinθcosθ\tan\theta = \dfrac{\sin\theta}{\cos\theta} and sin2θ+cos2θ=1\sin^2\theta + \cos^2\theta = 1 are not separate facts to memorise; both fall out of one picture, a point on a circle of radius 1. And "solve for 0x<360°0 \leqslant x < 360°" is not a suggestion to report whatever arcsin hands back — it is an instruction to find every value in that range, which is usually more than one, and the paper is built to reward whoever knows how to go looking for the rest.

The card

tan θ = sin θ/cos θ (undefined where cos θ = 0); sin²θ + cos²θ = 1 — both from (cos θ, sin θ) on the unit circle.
Mixed sin/cos equation → substitute the identity → solve in one function, usually a 3-term quadratic.
"Solve for [interval]": find the calculator's value, then use quadrant signs for every other solution.
Never divide by sin θ, cos θ or tan θ — factorise instead, or a solution branch is lost.
sin θ, cos θ = ±1 give ONE solution per revolution, not two. Match degrees/radians; don't round early — and if radians are asked "in the form kπ", convert back to the exact standard-angle fraction, never leave it decimal.

Why it works — Where $\tan\theta = \sin\theta/\cos\theta$ and $\sin^2\theta + \cos^2\theta = 1$ actually come from

Both identities are the same one picture, read two different ways. Draw a circle of radius 1 centred at the origin, and let θ\theta be the angle measured anticlockwise from the positive x-axis. The point P where that angle's ray meets the circle is, BY DEFINITION, the point (cosθ,sinθ)(\cos\theta, \sin\theta) — this is the actual definition of sine and cosine once an angle is allowed to be bigger than 90° or negative, the one that extends the right-triangle picture (opposite over hypotenuse, adjacent over hypotenuse) to every real angle, because a triangle stops making sense past 90° but a point on a circle never does. Read the picture the first way: P lies on a circle of radius 1, so its coordinates satisfy x2+y2=1x^2 + y^2 = 1 — that is simply the equation of the circle, nothing more mysterious than Pythagoras applied to the right-angled triangle formed by P, the origin, and P's foot on the x-axis, whose legs have lengths cosθ|\cos\theta| and sinθ|\sin\theta| and whose hypotenuse is the radius, 1. Substitute x=cosθx = \cos\theta and y=sinθy = \sin\theta and the circle's own equation reads cos2θ+sin2θ=1\cos^2\theta + \sin^2\theta = 1. Nobody chose this identity as a rule; it is the coordinate form of "P sits on a circle of radius 1," which was true by construction before any trig was involved at all. Read the same picture the second way, for tan: the gradient of the line from the origin O to P is, by the standard definition of gradient, change in ychange in x=sinθcosθ\frac{\text{change in } y}{\text{change in } x} = \frac{\sin\theta}{\cos\theta} — and that ratio is exactly what tanθ\tan\theta means (it is also, for an acute angle, opposite over adjacent in the same right triangle, since dividing sinθ\sin\theta by cosθ\cos\theta cancels the shared hypotenuse of length 1). So tanθ=sinθcosθ\tan\theta = \frac{\sin\theta}{\cos\theta} is not a separate fact either — it is "gradient of OP" read off the same coordinates the first identity just used. And this is exactly why tanθ\tan\theta is undefined precisely when cosθ=0\cos\theta = 0: that is the moment P sits directly above or below the origin, the line OP is vertical, and a vertical line has no defined gradient — not a rule to memorise, a direct geometric consequence of what "gradient" means.

Traps — 9

divides-out-a-common-trig-factor
Confirmed on a real WMA12 identity-substitution question: after multiplying through by cosθ and factorising, the correct path reaches sinθ(2 + 3cosθ) = 0 — but "many however cancelled the sinθ and hence only produced solutions from cosθ = −⅔" (Oct 2023, Q3), silently discarding the whole sinθ = 0 branch. This is structurally the identical error to dividing a polynomial equation by x instead of factoring it out — cancelling a factor from both sides of an equation throws away every solution where that factor is zero. Factorise; never divide by an expression that could itself be zero.
wrong-identity-substituted-for-cos-squared
Confirmed on a real WMA12 question, in an examiner report quoted as: "cos2θ was occasionally replaced with 1 − sinθ" (Oct 2022, Q5) — read in context, immediately alongside a separate note about the sin²θ + cos²θ = 1 identity, this is cos²θ being substituted with 1 − sinθ instead of the real identity, 1 − sin²θ: the SQUARED sine dropped to a plain sine. It is the same shape of error the prequestion in this lesson previews with a clean fraction (cosθ = 1 − sinθ) — a real, recorded exam mistake, not a hypothetical one. The identity relates the squares of sin and cos, never the functions themselves directly.
coefficient-dropped-when-distributing-after-substitution
Confirmed on the same question: "3(1 − sin²θ) expanded to 3 − sin²θ" (Oct 2022, Q5) — the leading coefficient multiplied only one of the two terms inside the bracket instead of both. This is exactly the error modelled on the wrong path of the marked-solution above, just with a 3 in place of a 2. The check that catches it costs five seconds: expand the resulting expression back out and confirm it returns what you started with.
incomplete-multiply-through-after-tan-substitution
The same distribute-across-every-term hazard as the coefficient-dropped trap above, but at the fraction-clearing step rather than a bracket-expansion step: once tan θ = sin θ/cos θ has been substituted into a mixed equation, EVERY term has to be multiplied through by cos θ to clear the fraction, not just the term that already had a cos θ sitting in it. The real WMA12 mark scheme for a tan-substitution question of this shape names this as its own credited action, worded to allow for exactly this slip: "Multiplies through by cosθ (on at least 2 of the 3 terms in the equation) and attempts to use ±sin²θ±cos²θ=±1 to set up a quadratic equation in cosθ" (June 2025, Q8(ii) mark scheme) — "on at least 2 of the 3 terms" is a direct acknowledgement that clearing the fraction on only some of the terms is the common failure mode being marked around. The worked-chain above models the full clear-then-substitute sequence and flags exactly where that slip would happen.
compound-angle-not-isolated-before-inverse-function
Confirmed on a compound-angle equation, tan(2x + π/5) = k, solved in radians: "some did not recognise that they should isolate the tan(2x + π/5) term before attempting to take arctan" (June 2025, Q8(i)) — a small structural failure with a large consequence, since every later step depends on the bracket being isolated first. There were also candidates who worked in degrees on this exact question despite the radian-form interval — the units of an interval have to be matched throughout, not switched to whichever is more familiar partway through.
coefficient-distributed-across-the-whole-compound-angle
Confirmed on the same question: "distributing the coefficient of the tangent term throughout the angle resulting in tan(6x + 3π/5)" (June 2025, Q8(i)) — multiplying a coefficient into the angle INSIDE the trig function, when it should only ever multiply the function's output. tan(2x + π/5) has no coefficient to distribute into its argument at all; the 3 in "3tan(2x + π/5) = k" multiplies the tan value once it is found, never the angle itself.
compound-angle-bracket-range-scaled-by-coefficient
Confirmed in the mark scheme for the same compound-angle question, not the examiner report: "Correct order of operations 2x + π/5 = π/6, 7π/6, 13π/6 ... to find a value for x which does not need to be in the given range (e.g. condone −π/60)" (June 2025, Q8(i) mark scheme) — three candidate bracket-values, not the usual one or two, and the dM1 mark is for the METHOD of generating them, before anything is checked against the range. Every "compound angle" example elsewhere in this lesson has a coefficient of 1 on x, where the bracket's range matches x's own interval exactly — here the coefficient is 2, so solving (2x + π/5) = k over 0 ⩽ x < π means the BRACKET sweeps an interval TWICE as wide, two full periods of tan (period π) rather than one, and the calculator's value needs tan's period added repeatedly across that whole doubled range before anything is converted back. From arctan(1/√3) = π/6: adding π once gives 7π/6, adding it again gives 13π/6 — both additional candidates a coefficient of 1 would never produce. Converting each via x = (bracket − π/5)/2 gives x = −π/60 (from π/6), x = 29π/60 (from 7π/6) and x = 59π/60 (from 13π/6); only the accuracy mark, A1, actually enforces 0 ⩽ x < π — which is exactly why −π/60 is explicitly condoned at the method stage and only rejected once the final answer is stated. The method mark rewards generating enough candidates across the scaled range; the accuracy mark is what filters them.
decimal-given-instead-of-exact-kπ-radian-form
Confirmed on the same compound-angle question: "A few did not take note of the required form of the answer kπ (with k rational) and used decimals. There were also candidates who worked in degrees" (June 2025, Q8(i) examiner report) — a distinct failure from the traps above about this equation, none of which turn on whether the final answer is left decimal or kept exact. Even after correctly isolating and solving tan(2x + π/5) = √3/3, the calculator's decimal output (2x + π/5 ≈ 0.628…) has to be recognised as a standard angle (arctan(1/√3) = π/6) and carried through in that exact form — "in the form kπ" is an explicit instruction that a decimal, however accurately rounded, does not satisfy; the mark scheme's own accuracy line states plainly that the final answer "must be exact and in radians" (June 2025, Q8(i) mark scheme). This is not the same rule as "don't round early": that rule protects a genuinely decimal final answer (as in Q8(ii)) from accumulating rounding error; this one requires recognising when the final answer isn't decimal at all.
premature-rounding-before-final-angle
Confirmed on a three-term quadratic in cosθ where the roots did not factorise: "some candidates rounded the exact solution for cosθ to 3 significant figures which caused rounding errors when finding θ and a loss of the final accuracy mark" (June 2025, Q8(ii)) — directly confirming the WMA12 general marking guidance's exact-answer rule for this exact topic. Keep the un-rounded value (a surd, a fraction, or extra decimal places) all the way through and round only the final angle, to whatever precision the question actually asks for.

Say it out loud

Out loud, from memory, no notes: explain where $\tan\theta = \sin\theta/\cos\theta$ and $\sin^2\theta + \cos^2\theta = 1$ actually come from to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 7.1

1 lesson

Stationary Points and Curve Sketching

Every on this paper reduces to solving one equation for x — and every mark after that depends on what you do next, not on finding it. Setting dy/dx = 0 locates where a curve's gradient is momentarily flat; it says nothing yet about whether that flat point is a peak, a trough, or something stranger. The second derivative, substituted at that exact x-value and nowhere else, is what turns a bare coordinate into a genuine maximum or minimum — and a real WMA12 examiner report shows that this one substitution step, not the algebra before it, is where the marks are actually won or lost.

The card

Stationary point: dy/dx = 0. Solve for x, then substitute back into the ORIGINAL y — not into dy/dx — for the coordinate.
Second derivative test: d²y/dx² > 0 → minimum; < 0 → maximum; = 0 → inconclusive — test the sign of dy/dx either side instead.
Increasing where dy/dx > 0; decreasing where dy/dx < 0. A stationary point is exactly where one can turn into the other.
Sketch: y-intercept from c, stationary points classified by coordinate, end behaviour from the sign and degree of the leading term.

Why it works — Where the second derivative test actually comes from — the gradient's own rate of change

Picture a stationary point that is a minimum: the curve falls into it from the left and rises away from it on the right. That means the GRADIENT itself — not the height of the curve, the actual value of dy/dx — goes from negative, through zero exactly at the stationary point, to positive, as x increases through it. A quantity that moves from negative to positive as x increases is, by definition, ITSELF increasing at that point. And "the rate of change of dy/dx with respect to x" is exactly what d2ydx2\dfrac{d^2y}{dx^2} means — the derivative of the derivative. So a minimum is precisely the case where the gradient is increasing through the stationary point, which is precisely d2ydx2>0\dfrac{d^2y}{dx^2} > 0 there: not a rule to memorise, but a restatement, one level of abstraction up, of the same falling-then-rising shape that makes it a minimum in the first place. Run the identical argument for a maximum — curve rising into it, falling away from it, so the gradient goes from positive to negative, meaning the gradient is DECREASING through the point — and d2ydx2<0\dfrac{d^2y}{dx^2} < 0 falls out the same way. And this is exactly why d2ydx2=0\dfrac{d^2y}{dx^2} = 0 resolves nothing: it says only that the gradient's own rate of change happens to be zero at that one instant, which is equally consistent with the gradient having just finished increasing, just finished decreasing, or doing something stranger besides — the single number d2ydx2=0\dfrac{d^2y}{dx^2}=0 cannot distinguish between them. What CAN distinguish between them is returning to the definition itself and checking the sign of dy/dx directly, just below and just above the point — the fallback method is not a weaker, approximate substitute for the second-derivative test; it is the more fundamental fact the test itself was built from, applied one step closer to the source instead of one step removed.

Traps — 7

second-derivative-found-but-never-substituted
Confirmed on a real WMA12 question testing exactly this mark: having correctly found the second derivative, examiners recorded that "there were many who did not then substitute the values for x found in part (a) into their second derivative" (Jan 2021 Q2) — the expression itself was right, but the one step that turns it into an actual answer, plugging in the specific x-value already found, was skipped. An expression in x has no sign at all until a number goes into it.
y-coordinates-found-when-only-x-was-asked
Confirmed on the same real WMA12 question (Jan 2021 Q2), and about part (a) rather than part (b): "candidates often went on to do unnecessary work by finding the y coordinates of the stationary points or assumed this was what was required of part (b)" — but part (a) on that exact question asked only for the x-coordinates, and part (b) (justify the nature of each stationary point) needs no y-value at all, only the x-value substituted into the second derivative. Read what a part is actually asking before doing the extra work: finding a coordinate you weren't asked for costs real time on a timed paper and earns nothing extra, and assuming a later part needs something it doesn't is a comprehension error, not a calculus one.
second-derivative-set-to-zero-and-solved
Confirmed on the same real WMA12 question: "a common error was to try to solve for the second derivative" (Jan 2021 Q2) — treating d²y/dx²=0 as a fresh equation to solve for x, the way dy/dx=0 was solved to find the stationary points in the first place. This finds a genuinely different feature of the curve (where its concavity itself changes, its point of inflection) and answers nothing about the nature of the stationary points the question actually asked about — this lesson's own marked-solution above shows exactly what that produces when carried all the way through.
y-values-eyeballed-instead-of-gradient-tested
Confirmed on the same real WMA12 question, contrasting two methods for classifying a stationary point when the second-derivative test is unavailable or unused: testing the sign of the gradient either side earned "full credit as it used further calculus", but "a rarely used method looking at the shape of the curve by looking at the y values either side of the stationary point was not given credit as it did not use further calculus as asked for in the question" (Jan 2021 Q2). The two methods can look similar on the page — both compare 'either side' of the point — but only one of them is actually calculus, and the mark scheme cares about the method, not just a correct-looking conclusion.
critical-value-inequality-wrong-region-chosen
Confirmed on a real cross-topic WMA12 question combining differentiation, factorisation and integration to test a decreasing-function region (spec 7.1): a documented wrong final answer read "x < −5 or x > ⅔" (Jun 2025, WMA12/01A, Q8) — the region OUTSIDE the two critical values, the opposite side from the one actually being asked for. dy/dx, as a quadratic in x, is positive outside its own two roots and negative between them (for a positive leading coefficient), or the reverse for a negative one — and the only way to know which side is correct is to test the sign of dy/dx at one value actually inside the interval in question, not to guess from which side 'looks like' the answer.
second-derivative-test-inconclusive-mishandled
Not attached to a real examiner-report quote in the facts bank behind this course — the WMA12 differentiation questions reviewed for this lesson document the failure to substitute into an already-nonzero second derivative (see above), not a case where the test itself returns exactly zero. It is included anyway because it is genuine, checkable spec-7.1 content, and follows directly from this lesson's own mechanism: d²y/dx²=0 says only that the gradient's own rate of change happens to be zero at that one instant — not that 'there is no information available' and not that the point must automatically be a point of inflection, both conclusions the test never supported. The only fix is to go back to testing the sign of dy/dx directly, either side, which this lesson's method-comparison above shows earning exactly as much credit as the second-derivative route in the first place.
stationary-point-x-coordinate-rounded-instead-of-exact
Not every dy/dx = 0 quadratic reduces to the tidy, monic, integer-rooted case most of this lesson's own worked examples use: 3x22x8=(3x+4)(x2)=03x^2-2x-8=(3x+4)(x-2)=0 factorises just as cleanly — no formula needed — and still gives x=43x=-\dfrac{4}{3}, a genuine fraction. The method mark for solving the quadratic is earned by the factorisation itself, regardless of how the root is then written down; it is the accuracy mark for the coordinate that the fraction protects and a decimal forfeits. The general marking guidance's exact-answer rule states plainly that "where, for example, an exact answer is asked for, or working with surds is clearly required, marks will normally be lost if the candidate resorts to using rounded decimals" — so x=43x=-\dfrac{4}{3} (or an equivalent single fraction) is required, and x=1.33x=-1.33 loses the mark even though the decimal is correctly rounded.

Say it out loud

Out loud, from memory, no notes: explain where the second derivative test actually comes from — the gradient's own rate of change to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 8.2

1 lesson

Definite Integration and Areas Bounded by Curves and Lines

A is a number you can compute mechanically in three lines — the entire topic is really asking whether you know when that number is allowed to be called an area. Evaluating abf(x)dx\int_a^b f(x)\,dx is bookkeeping: integrate, substitute, subtract. Whether the result you get is the enclosed area, the negative of it, or a number that isn't the area of anything at all depends on one thing the bookkeeping never checks for you — whether the curve stays on one side of the x-axis, or the correct boundary, for the whole interval. The paper builds almost every mark in this topic around exactly that gap.

The card

FTC: ∫ₐᵇf(x)dx = F(b) − F(a), F′(x)=f(x). Integrate termwise: power up by 1, divide by the new power.
Area = the integral ONLY where the curve doesn't cross the axis in (a,b). If it does, split at each root, take |value| per piece, add.
Curve/line or curve/curve: integrate (upper − lower) between the true intersection points — solve for them, don't guess.
Exact answer required: quote the method. A calculator's numerical integration checks a value; it doesn't earn the marks.

Why it works — Where 'area equals the integral' actually comes from — thin strips, not a definition to accept on faith

Cut the interval [a,b][a,b] into nn equal strips of width Δx=ban\Delta x = \frac{b-a}{n}. Approximate the area of the ii-th strip by a rectangle of width Δx\Delta x and height f(xi)f(x_i), where xix_i is some point inside that strip. The total area under the curve is approximately the sum of these rectangles, i=1nf(xi)Δx\sum_{i=1}^{n} f(x_i)\,\Delta x. As nn \to \infty the strips narrow, the rectangles hug the curve more and more closely, and the error in the approximation shrinks to zero — the limit of that sum is, by definition, the definite integral abf(x)dx\int_a^b f(x)\,dx. So far this only says the integral is the LIMIT of a sum of signed rectangle areas — it does not yet say that limit equals the geometric area, because a rectangle's height f(xi)f(x_i) is only a genuine, non-negative geometric length when f(xi)0f(x_i) \geq 0. When f(x)0f(x) \geq 0 across the whole of [a,b][a,b], every rectangle in the sum has a non-negative height, the sum really is approximating physical area, and the limit — the integral — equals that area exactly. The two other pieces of the topic follow directly from the same picture. First, why the mechanical evaluation method (find FF, substitute, subtract) gives the same number as this geometric limit: define A(x)=axf(t)dtA(x) = \int_a^x f(t)\,dt, the accumulated signed area up to xx. Widening the interval by a sliver δx\delta x adds a sliver of area approximately f(x)δxf(x)\,\delta x, so A(x)=f(x)A'(x) = f(x)AA is itself an antiderivative of ff. Any other antiderivative FF differs from AA by a constant, and since A(a)=0A(a) = 0, that constant is fixed by F(a)F(a): A(x)=F(x)F(a)A(x) = F(x) - F(a), so A(b)=F(b)F(a)A(b) = F(b) - F(a) — exactly the evaluation rule from the teach block above, now derived rather than asserted. Second, why the whole thing breaks the moment ff goes negative somewhere in (a,b)(a,b) — covered as its own mechanism next, because it is where almost every mark in this topic is actually lost.

Traps — 6

answer-produced-with-no-method-shown
Confirmed on a real area-between-a-line-and-a-curve question: "it is noteworthy that there were a number of students who relied on a calculator to evaluate the definite integral for them, which is not advisable when an exact answer is required as permitted calculators are supposed to only be able to carry out numerical integration, which will commonly give a decimal answer only... full method must be shown for full credit" (Jan 2020, Q4). Permitted calculators on this paper can do numerical integration — approximate, decimal — but not the symbolic integration a written method has to show; the two are not interchangeable when the question asks for an exact value.
curve-and-line-subtracted-in-the-wrong-order
Confirmed on the same question: "it was not uncommon to see the difference the wrong way round, though students would generally realise the final answer must be positive at the end and recover the marks" (Jan 2020, Q4). The mechanism is exactly this lesson's diagram: subtracting (line − curve) instead of (upper − lower) flips the sign of the whole answer. It is self-correcting only for a student who actually checks the sign of the final number against "area must be positive" — silently accepting a negative result loses the mark this trap describes.
line-boundary-ignored-entirely
Confirmed independently on two different real series, both testing this exact spec point — a genuinely recurring trap, not a one-off. On a two-region area question with a curve and a line: "Many attempted solutions simply integrated the equation of the curve and evaluated between the limits 0 and 1, thus completely ignoring the requirement to subtract the area under the line l. This gained no credit as it was not a correct strategy for R1" (Jan 2023, Q9(c)). And on a separate curve-and-line area question: "One common error, aside from bracketing mistakes, made in this question was that only the area under the curve being found, 31√5⁄3 being given as the area of the region R" (Jan 2020, Q4) — echoed again on a third series, "Some candidates, however, did not know how to deal with the additional line and just found the area under the curve" (June 2025, Q3). Reading the question fully before starting — is the region bounded by the curve ALONE, or by the curve and something else — is the entire fix, and it has to happen before any integral is written down, not after.
sign-change-inside-the-interval-not-split
Not attached to a real examiner-report quote in the facts bank behind this course — the archived area questions reviewed for WMA12 all use curve-and-line or curve-and-curve regions that stay one sign throughout, not a region where the curve itself crosses the axis. It is included anyway because it is genuine, checkable spec-8.2 content, and it follows directly from the mechanism derived earlier in this lesson: integrating straight across a root mixes a positive and a negative contribution into one running total before either can be made positive, producing a number that is neither the honest signed integral nor the true area. See the marked-solution's common wrong path for exactly what number that mistake produces.
slowest-valid-method-chosen-under-time-pressure
Confirmed as a real, quoted efficiency comparison between mathematically equivalent methods on an area-between-curve-and-line question: one valid strategy "was a more time-consuming approach requiring either five terms to be integrated or terms to be collected resulting in occasional sign errors" (June 2025, Q3) than the other creditable strategies for the same question. All three methods in this lesson's method-comparison earn full marks — but under a 90-minute paper with 75 marks across the whole thing, picking the slower of two equally valid routes is a real cost even when it produces the right answer.
y-values-used-as-x-limits
Confirmed on the same real anchor question as this lesson's y-axis-boundary worked example above: "Another mistake seen on numerous occasions was to use the y values of 7 and 17 as their limits to an integration with respect to x, which was incorrect and usually meant only the first two marks were scored" (Jan 2020, Q4). The two numbers named there are the curve's value at x = 0 and the height of the bounding line — real numbers on the diagram, but y-values, never x-values, and ∫(…)dx only ever takes x-values as its limits. It is exactly the shape the worked-chain above is built to guard against: one limit found by solving curve = line, the other supplied directly by the y-axis as x = 0 — never by reading off the curve's or the line's own y-coordinate at that point.

Say it out loud

Out loud, from memory, no notes: explain where 'area equals the integral' actually comes from — thin strips, not a definition to accept on faith to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 8.1

1 lesson

Definite Integration and Areas Bounded by Curves and Lines

A is a number you can compute mechanically in three lines — the entire topic is really asking whether you know when that number is allowed to be called an area. Evaluating abf(x)dx\int_a^b f(x)\,dx is bookkeeping: integrate, substitute, subtract. Whether the result you get is the enclosed area, the negative of it, or a number that isn't the area of anything at all depends on one thing the bookkeeping never checks for you — whether the curve stays on one side of the x-axis, or the correct boundary, for the whole interval. The paper builds almost every mark in this topic around exactly that gap.

The card

FTC: ∫ₐᵇf(x)dx = F(b) − F(a), F′(x)=f(x). Integrate termwise: power up by 1, divide by the new power.
Area = the integral ONLY where the curve doesn't cross the axis in (a,b). If it does, split at each root, take |value| per piece, add.
Curve/line or curve/curve: integrate (upper − lower) between the true intersection points — solve for them, don't guess.
Exact answer required: quote the method. A calculator's numerical integration checks a value; it doesn't earn the marks.

Why it works — Where 'area equals the integral' actually comes from — thin strips, not a definition to accept on faith

Cut the interval [a,b][a,b] into nn equal strips of width Δx=ban\Delta x = \frac{b-a}{n}. Approximate the area of the ii-th strip by a rectangle of width Δx\Delta x and height f(xi)f(x_i), where xix_i is some point inside that strip. The total area under the curve is approximately the sum of these rectangles, i=1nf(xi)Δx\sum_{i=1}^{n} f(x_i)\,\Delta x. As nn \to \infty the strips narrow, the rectangles hug the curve more and more closely, and the error in the approximation shrinks to zero — the limit of that sum is, by definition, the definite integral abf(x)dx\int_a^b f(x)\,dx. So far this only says the integral is the LIMIT of a sum of signed rectangle areas — it does not yet say that limit equals the geometric area, because a rectangle's height f(xi)f(x_i) is only a genuine, non-negative geometric length when f(xi)0f(x_i) \geq 0. When f(x)0f(x) \geq 0 across the whole of [a,b][a,b], every rectangle in the sum has a non-negative height, the sum really is approximating physical area, and the limit — the integral — equals that area exactly. The two other pieces of the topic follow directly from the same picture. First, why the mechanical evaluation method (find FF, substitute, subtract) gives the same number as this geometric limit: define A(x)=axf(t)dtA(x) = \int_a^x f(t)\,dt, the accumulated signed area up to xx. Widening the interval by a sliver δx\delta x adds a sliver of area approximately f(x)δxf(x)\,\delta x, so A(x)=f(x)A'(x) = f(x)AA is itself an antiderivative of ff. Any other antiderivative FF differs from AA by a constant, and since A(a)=0A(a) = 0, that constant is fixed by F(a)F(a): A(x)=F(x)F(a)A(x) = F(x) - F(a), so A(b)=F(b)F(a)A(b) = F(b) - F(a) — exactly the evaluation rule from the teach block above, now derived rather than asserted. Second, why the whole thing breaks the moment ff goes negative somewhere in (a,b)(a,b) — covered as its own mechanism next, because it is where almost every mark in this topic is actually lost.

Traps — 6

answer-produced-with-no-method-shown
Confirmed on a real area-between-a-line-and-a-curve question: "it is noteworthy that there were a number of students who relied on a calculator to evaluate the definite integral for them, which is not advisable when an exact answer is required as permitted calculators are supposed to only be able to carry out numerical integration, which will commonly give a decimal answer only... full method must be shown for full credit" (Jan 2020, Q4). Permitted calculators on this paper can do numerical integration — approximate, decimal — but not the symbolic integration a written method has to show; the two are not interchangeable when the question asks for an exact value.
curve-and-line-subtracted-in-the-wrong-order
Confirmed on the same question: "it was not uncommon to see the difference the wrong way round, though students would generally realise the final answer must be positive at the end and recover the marks" (Jan 2020, Q4). The mechanism is exactly this lesson's diagram: subtracting (line − curve) instead of (upper − lower) flips the sign of the whole answer. It is self-correcting only for a student who actually checks the sign of the final number against "area must be positive" — silently accepting a negative result loses the mark this trap describes.
line-boundary-ignored-entirely
Confirmed independently on two different real series, both testing this exact spec point — a genuinely recurring trap, not a one-off. On a two-region area question with a curve and a line: "Many attempted solutions simply integrated the equation of the curve and evaluated between the limits 0 and 1, thus completely ignoring the requirement to subtract the area under the line l. This gained no credit as it was not a correct strategy for R1" (Jan 2023, Q9(c)). And on a separate curve-and-line area question: "One common error, aside from bracketing mistakes, made in this question was that only the area under the curve being found, 31√5⁄3 being given as the area of the region R" (Jan 2020, Q4) — echoed again on a third series, "Some candidates, however, did not know how to deal with the additional line and just found the area under the curve" (June 2025, Q3). Reading the question fully before starting — is the region bounded by the curve ALONE, or by the curve and something else — is the entire fix, and it has to happen before any integral is written down, not after.
sign-change-inside-the-interval-not-split
Not attached to a real examiner-report quote in the facts bank behind this course — the archived area questions reviewed for WMA12 all use curve-and-line or curve-and-curve regions that stay one sign throughout, not a region where the curve itself crosses the axis. It is included anyway because it is genuine, checkable spec-8.2 content, and it follows directly from the mechanism derived earlier in this lesson: integrating straight across a root mixes a positive and a negative contribution into one running total before either can be made positive, producing a number that is neither the honest signed integral nor the true area. See the marked-solution's common wrong path for exactly what number that mistake produces.
slowest-valid-method-chosen-under-time-pressure
Confirmed as a real, quoted efficiency comparison between mathematically equivalent methods on an area-between-curve-and-line question: one valid strategy "was a more time-consuming approach requiring either five terms to be integrated or terms to be collected resulting in occasional sign errors" (June 2025, Q3) than the other creditable strategies for the same question. All three methods in this lesson's method-comparison earn full marks — but under a 90-minute paper with 75 marks across the whole thing, picking the slower of two equally valid routes is a real cost even when it produces the right answer.
y-values-used-as-x-limits
Confirmed on the same real anchor question as this lesson's y-axis-boundary worked example above: "Another mistake seen on numerous occasions was to use the y values of 7 and 17 as their limits to an integration with respect to x, which was incorrect and usually meant only the first two marks were scored" (Jan 2020, Q4). The two numbers named there are the curve's value at x = 0 and the height of the bounding line — real numbers on the diagram, but y-values, never x-values, and ∫(…)dx only ever takes x-values as its limits. It is exactly the shape the worked-chain above is built to guard against: one limit found by solving curve = line, the other supplied directly by the y-axis as x = 0 — never by reading off the curve's or the line's own y-coordinate at that point.

Say it out loud

Out loud, from memory, no notes: explain where 'area equals the integral' actually comes from — thin strips, not a definition to accept on faith to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Spec 8.3

1 lesson

The Trapezium Rule and Justifying an Over- or Underestimate

Two-thirds of this topic is arithmetic you cannot get wrong if you build it correctly, and the exam's own examiners record the last third — the one-mark reasoning question — as the single hardest mark to earn on the whole paper. The replaces a curve you may not be able to integrate exactly with a chain of straight lines you can measure exactly, and the formula for doing that is printed in front of you in the exam. What isn't printed is the sentence that explains WHY your answer came out too big or too small — and "it's less than the true value" is not that sentence, however true it is, because it restates the conclusion instead of giving the reason for it.

The card

Trapezium rule: ∫ₐᵇy dx ≈ ½h{(y₀+yₙ) + 2(y₁+y₂+…+yₙ₋₁)}, h = (b−a)/n. Printed in the formula booklet.
n strips need n+1 ordinates. h = interval length ÷ number of STRIPS, never ÷ number of points.
Double every interior ordinate (shared by two strips). Endpoints y₀, yₙ are used once each.
Curve bends towards the x-axis → chords sit below it → underestimate. Bends away → chords above it → overestimate.
"It's smaller than the true value" restates the conclusion, not the reason. Name how the curve bends.
More, narrower strips → chords hug the curve more closely → estimate moves closer to the true area.

Why it works — Where the doubled interior ordinates come from — derive it, don't memorise it

Write the nn individual trapezium areas out in full and add them. The first strip contributes 12h(y0+y1)\frac{1}{2}h(y_0+y_1); the second, 12h(y1+y2)\frac{1}{2}h(y_1+y_2); the third, 12h(y2+y3)\frac{1}{2}h(y_2+y_3); and so on up to the last, 12h(yn1+yn)\frac{1}{2}h(y_{n-1}+y_n). Summed: 12h(y0+y1)+12h(y1+y2)++12h(yn1+yn)\frac{1}{2}h(y_0+y_1) + \frac{1}{2}h(y_1+y_2) + \cdots + \frac{1}{2}h(y_{n-1}+y_n). Every term shares the same factor 12h\frac{1}{2}h, so factor it out once: 12h[(y0+y1)+(y1+y2)+(y2+y3)++(yn1+yn)]\frac{1}{2}h\big[(y_0+y_1) + (y_1+y_2) + (y_2+y_3) + \cdots + (y_{n-1}+y_n)\big]. Now count how many times each ordinate is written inside that bracket. y0y_0 appears once — only the first strip touches it. yny_n appears once — only the last strip touches it. But y1y_1 appears twice: once as the right edge of the first strip, once as the left edge of the second. The same is true of y2y_2, of y3y_3, of every ordinate strictly between the two ends — each is the shared edge of exactly two neighbouring strips, so it is written down twice when the strips' areas are listed separately. Collecting those repeated terms is precisely 12h{(y0+yn)+2(y1+y2++yn1)}\frac{1}{2}h\{(y_0+y_n) + 2(y_1+y_2+\cdots+y_{n-1})\} — the doubling is not a rule about the formula, it is what happens automatically when adjacent strips are written out in full and their shared edges are collected together. This is also exactly why the bracket has to stay one bracket: the 12h\frac{1}{2}h was factored out of every individual trapezium's area at once, so it multiplies the WHOLE of what is left, endpoints and doubled interior terms alike — splitting the expression back into 12h(y0+yn)\frac{1}{2}h(y_0+y_n) added separately to 2(y1++yn1)2(y_1+\cdots+y_{n-1}), with the second part never multiplied by 12h\frac{1}{2}h at all, breaks exactly the step that produced the formula in the first place. A real examiner report records the resulting error directly: "A few candidates closed the brackets after the initial addition of two terms, then adding the rest afterwards, thus gaining no credit" (January 2023) — the arithmetic doesn't just come out wrong, it stops representing the trapezium rule at all.

Traps — 5

strip-width-from-point-count-not-gap-count
Confirmed directly, and described as something every examiner marking the series saw: "All examiners saw candidates who thought that the strip width was 0.2, obtained from dividing 1 by the 5 points rather than the 4 spaces" (October 2020). Five ordinates bound four strips, not five — the number of x-values in a table is always one more than the number of strips it describes, because each interior ordinate is shared between two neighbouring strips rather than belonging to a strip of its own.
endpoints-and-interior-ordinates-swapped
Confirmed as the commonest single arithmetic error on a real trapezium-rule question: "The commonest error was to double the three given values" (October 2020) — losing track of which ordinates sit at the two ends of the region (used once each in the sum) and which sit strictly between them (used twice each). The mechanism block above derives exactly why the split runs this way: an interior ordinate belongs to two adjacent strips at once when the strips' individual areas are added, an endpoint ordinate belongs to only one.
bracket-closed-before-scaling
Confirmed, and structurally distinct from the doubling error above even though both look similar on the page: "A few candidates closed the brackets after the initial addition of two terms, then adding the rest afterwards, thus gaining no credit" (January 2023). The 12h\frac{1}{2}h has to multiply the ENTIRE bracket — endpoints and doubled interior ordinates together — because it was factored out of every individual trapezium's area at once. Splitting the expression into two separately-scaled pieces breaks the algebra that produced the compressed formula in the first place, and the mark scheme gives no partial credit for the resulting number.
conclusion-restated-instead-of-reasoned
Confirmed as the hardest single mark on the whole paper to earn in the series it was checked in: "Part (c) was perhaps found to be the most difficult mark for candidates to achieve. Stating that the answer... is an underestimate because it is less than the true area is not giving a reason as to why it is less. It was important for candidates to allude to the fact that the sum of the areas of trapezia found in part (a) was less than the shaded area, hence it is an underestimate" (October 2023). "It's smaller, so it's an underestimate" repeats the definition of the word; the credited reason names the mechanism — the chords sit below the curve because of how the curve bends — that makes the sum come out smaller in the first place. This mark is also, on every verified instance, ONE mark rather than two: the scheme reads "B1: States underestimate AND gives a valid reason" (October 2023 Q6c), a single combined requirement, not a label mark plus a separate reason mark. The same pattern holds outside this topic too — June 2021's analogous "state direction, give reason" mark for a binomial-expansion truncation error is likewise a single combined B1 with no partial credit for the label alone. Do not expect a mark for writing "underestimate" (or "overestimate") on its own; the mechanism has to be there in the same sentence.
trapezium-rule-assumed-tested-in-isolation
The trapezium rule is regularly combined with other spec content rather than tested as a standalone calculation — confirmed across at least two series. One examiner report on a genuinely unusual question format states directly: "Part (i) was a novel way of testing the trapezium rule via logarithms" (January 2025); a separate report on a different series records the same rule embedded in a "real life" water-flow context (October 2023, Q6). A student who has only ever practised the trapezium rule attached to a bare polynomial or root function is unprepared for a question that requires setting up the ordinate table from a log expression, or from a context described in words, before the trapezium-rule arithmetic itself even begins.

Say it out loud

Out loud, from memory, no notes: explain where the doubled interior ordinates come from — derive it, don't memorise it to someone who has never seen this topic — where does your explanation get vague or hand-wavy? That's the exact spot to re-study, and it only works if you check it: read back over the mechanism above the moment you finish talking and mark precisely where you drifted from it.

Say these out loud before the exam

Every prompt below is answerable from the sheet above. If one stops you, that’s the page to go back to — and the fact that it stopped you is worth more than another read-through of the pages that didn’t.

  1. In one sentence: why does finding a single failing case fully disprove a "for all" statement, while proving the same kind of statement true needs either every case checked or a general argument that covers them all at once?
  2. What is the "algebraic-proof-attempted-when-exhaustion-required" trap, and how do you catch it?
  3. What is the "numerical-examples-mistaken-for-general-proof" trap, and how do you catch it?
  4. What is the "multiple-of-k-assertion-without-quotient-shown" trap, and how do you catch it?
  5. What is the "product-misread-as-sum" trap, and how do you catch it?
  6. What is the "case-defining-relation-applied-backwards" trap, and how do you catch it?
  7. What is the "column-values-transposed-between-derived-variables" trap, and how do you catch it?
  8. What is the "case-list-not-exactly-complete" trap, and how do you catch it?
  9. What is the "conclusion-omitted" trap, and how do you catch it?
  10. What is the "counter-example-search-continued-past-the-first-valid-one" trap, and how do you catch it?
  11. Without looking: what does this lesson say about proof, and the two shapes a wma12 question can take?
  12. Without looking: what does this lesson say about before you pick a method: is the set of cases finite??
  13. In one sentence: why does substituting x=bax = \frac{b}{a} into f(x)f(x) give the remainder on dividing by (axb)(ax - b), without your ever having to know what the quotient is?
  14. What is the "root-sign-taken-straight-from-the-bracket" trap, and how do you catch it?
  15. What is the "remainder-equation-set-to-zero" trap, and how do you catch it?
  16. What is the "long-division-chosen-when-substitution-was-asked-for" trap, and how do you catch it?
  17. What is the "factorisation-stopped-one-step-short" trap, and how do you catch it?
  18. What is the "hence-factorise-reached-without-using-the-given-factor" trap, and how do you catch it?
  19. What is the "non-integer-factor-form-given" trap, and how do you catch it?
  20. What is the "answer-left-as-a-list-not-a-product" trap, and how do you catch it?
  21. What is the "show-that-steps-omitted" trap, and how do you catch it?
  22. Without looking: what does this lesson say about what spec 2.1 actually asks for — and what the formula booklet does not give you?
  23. Without looking: what does this lesson say about doing the division itself: long division, or writing the identity down and comparing coefficients?
  24. In one sentence: why does the same right-angled-triangle argument that shows the perpendicular from a centre bisects a chord also show why a tangent has to be perpendicular to its radius?
  25. What is the "centre-sign-not-flipped" trap, and how do you catch it?
  26. What is the "general-form-read-as-centre-radius-form" trap, and how do you catch it?
  27. What is the "solved-parameter-not-substituted-into-earlier-general-centre" trap, and how do you catch it?
  28. What is the "radius-given-as-decimal-not-exact-surd" trap, and how do you catch it?
  29. What is the "implicit-differentiation-chosen-over-the-property" trap, and how do you catch it?
  30. What is the "origin-and-circle-centre-both-labelled-o" trap, and how do you catch it?
  31. What is the "substitution-direction-not-checked-for-fractions" trap, and how do you catch it?
  32. What is the "general-area-formula-chosen-over-axis-aligned-base-height" trap, and how do you catch it?
  33. Without looking: what does this lesson say about the two forms a circle's equation takes, and why only one of them can be read at a glance?
  34. Without looking: what does this lesson say about building a circle's equation from geometric information, not just reading it back?
  35. In one sentence: why does proving Sn=12n[2a+(n1)d]S_n = \frac{1}{2}n[2a+(n-1)d] require writing the series twice — once forwards, once in reverse — rather than just adding the nn terms in the order they were written?
  36. What is the "sum-proof-last-term-off-by-one" trap, and how do you catch it?
  37. What is the "sum-proof-reversal-skipped" trap, and how do you catch it?
  38. What is the "sum-proof-insufficient-terms-shown" trap, and how do you catch it?
  39. What is the "induction-attempted-for-standard-proof" trap, and how do you catch it?
  40. What is the "sum-proof-assumes-the-result" trap, and how do you catch it?
  41. What is the "sum-proof-pairing-fails-for-odd-n" trap, and how do you catch it?
  42. What is the "arithmetic-and-geometric-formulas-confused" trap, and how do you catch it?
  43. Without looking: what does this lesson say about two ways to describe a sequence — a formula, and a rule for the next term?
  44. Without looking: what does this lesson say about arithmetic sequences, and three families of behaviour?
  45. In one sentence: the arithmetic sum formula is proved by writing the series in reverse and adding, and the geometric one by multiplying by rr and subtracting — what is it about how each kind of series is generated that makes its own move the one that produces cancellation?
  46. What is the "arithmetic-and-geometric-formulas-confused" trap, and how do you catch it?
  47. What is the "overlap-term-double-counted" trap, and how do you catch it?
  48. What is the "geometric-series-restarted-from-the-original-first-term" trap, and how do you catch it?
  49. What is the "sum-to-infinity-first-term-misidentified" trap, and how do you catch it?
  50. What is the "calculator-summation-shown-without-formula" trap, and how do you catch it?
  51. What is the "standard-proofs-not-known" trap, and how do you catch it?
  52. What is the "geometric-proof-subtraction-direction-reversed" trap, and how do you catch it?
  53. What is the "convergence-condition-read-as-r-less-than-one" trap, and how do you catch it?
  54. Without looking: what does this lesson say about one swap from arithmetic — and everything that follows from it?
  55. Without looking: what does this lesson say about what the booklet hands you, and the one thing it doesn't?
  56. Without looking: what does this lesson say about reading \sum notation — the same series, written differently?
  57. In one sentence: why do the general term formula and Pascal's triangle always produce the same coefficient for the same n and r?
  58. What is the "term-index-mismatched-to-power" trap, and how do you catch it?
  59. What is the "general-series-form-chosen-over-combinatorial-form" trap, and how do you catch it?
  60. What is the "bx-term-not-raised-as-a-whole" trap, and how do you catch it?
  61. What is the "sign-lost-on-odd-powers-of-a-negative-b" trap, and how do you catch it?
  62. What is the "pascal-triangle-row-miscounted" trap, and how do you catch it?
  63. What is the "required-term-not-isolated-from-a-list" trap, and how do you catch it?
  64. Without looking: what does this lesson say about what (a + bx)ⁿ means, and where p2 draws the line?
  65. Without looking: what does this lesson say about where the exam hides the mismatch?
  66. In one sentence: why does solving log2(x+3)+log2(x3)=4\log_2(x+3) + \log_2(x-3) = 4 produce a value of xx that has to be checked against the original equation, when solving log2(x+3)=4\log_2(x+3) = 4 alone would not?
  67. What is the "log-subtraction-rewritten-as-division" trap, and how do you catch it?
  68. What is the "log-of-a-sum-expanded-as-sum-of-logs" trap, and how do you catch it?
  69. What is the "log-squared-confused-with-log-of-the-square" trap, and how do you catch it?
  70. What is the "exponent-rearrangement-left-unfinished" trap, and how do you catch it?
  71. What is the "single-log-form-left-uncombined" trap, and how do you catch it?
  72. What is the "logs-taken-before-the-equation-is-rearranged" trap, and how do you catch it?
  73. Without looking: what does this lesson say about what y = aˣ is, and what a logarithm undoes?
  74. Without looking: what does this lesson say about the laws of logarithms — five statements, before the mechanism behind them?
  75. In one sentence: why does the equation cosθ=1\cos\theta = 1 produce only ONE solution in a full 360° sweep, when cosθ=12\cos\theta = \frac{1}{2} produces two?
  76. What is the "divides-out-a-common-trig-factor" trap, and how do you catch it?
  77. What is the "wrong-identity-substituted-for-cos-squared" trap, and how do you catch it?
  78. What is the "coefficient-dropped-when-distributing-after-substitution" trap, and how do you catch it?
  79. What is the "incomplete-multiply-through-after-tan-substitution" trap, and how do you catch it?
  80. What is the "compound-angle-not-isolated-before-inverse-function" trap, and how do you catch it?
  81. What is the "coefficient-distributed-across-the-whole-compound-angle" trap, and how do you catch it?
  82. What is the "compound-angle-bracket-range-scaled-by-coefficient" trap, and how do you catch it?
  83. What is the "decimal-given-instead-of-exact-kπ-radian-form" trap, and how do you catch it?
  84. What is the "premature-rounding-before-final-angle" trap, and how do you catch it?
  85. Without looking: what does this lesson say about the two identities, and what "solve in a given interval" actually asks for?
  86. Without looking: what does this lesson say about how a mixed equation collapses to one function?
  87. In one sentence: why does a second derivative of exactly zero fail to tell you whether a stationary point is a maximum or a minimum?
  88. What is the "second-derivative-found-but-never-substituted" trap, and how do you catch it?
  89. What is the "y-coordinates-found-when-only-x-was-asked" trap, and how do you catch it?
  90. What is the "second-derivative-set-to-zero-and-solved" trap, and how do you catch it?
  91. What is the "y-values-eyeballed-instead-of-gradient-tested" trap, and how do you catch it?
  92. What is the "critical-value-inequality-wrong-region-chosen" trap, and how do you catch it?
  93. What is the "second-derivative-test-inconclusive-mishandled" trap, and how do you catch it?
  94. What is the "stationary-point-x-coordinate-rounded-instead-of-exact" trap, and how do you catch it?
  95. Without looking: what does this lesson say about what a stationary point is, and how dy/dx = 0 finds it?
  96. Without looking: what does this lesson say about classifying a stationary point — the second derivative test, and what happens when it doesn't decide?
  97. In one sentence: why does the number 19/3 never appear if you integrate x² − 5x + 4 from x = 0 to x = 4 in a single calculation, rather than splitting at the root?
  98. What is the "answer-produced-with-no-method-shown" trap, and how do you catch it?
  99. What is the "curve-and-line-subtracted-in-the-wrong-order" trap, and how do you catch it?
  100. What is the "line-boundary-ignored-entirely" trap, and how do you catch it?
  101. What is the "sign-change-inside-the-interval-not-split" trap, and how do you catch it?
  102. What is the "slowest-valid-method-chosen-under-time-pressure" trap, and how do you catch it?
  103. What is the "y-values-used-as-x-limits" trap, and how do you catch it?
  104. Without looking: what does this lesson say about evaluating a definite integral — the mechanics, before the meaning?
  105. Without looking: what does this lesson say about the definite integral as area — and exactly what the spec restricts it to?
  106. In one sentence: why does writing out every individual trapezium's area separately and adding them, rather than trusting the compressed formula, make it obvious which ordinates get doubled and which don't?
  107. What is the "strip-width-from-point-count-not-gap-count" trap, and how do you catch it?
  108. What is the "endpoints-and-interior-ordinates-swapped" trap, and how do you catch it?
  109. What is the "bracket-closed-before-scaling" trap, and how do you catch it?
  110. What is the "conclusion-restated-instead-of-reasoned" trap, and how do you catch it?
  111. What is the "trapezium-rule-assumed-tested-in-isolation" trap, and how do you catch it?
  112. Without looking: what does this lesson say about what the trapezium rule is doing, and the formula the booklet already gives you?
  113. Without looking: what does this lesson say about reading the question: how many strips, and how accurate an answer?

Beyond the spec

Every item below already lives inside a lesson, labelled the same way there — content the spec doesn’t strictly require, pulled into one place because it’s worth carrying alongside the rest of the sheet, not because it’s tested.

  1. Binomial Expansion of (a + bx)ⁿ for Positive Integer n

    Set x=1x=1 in (a+bx)n=r=0n(nr)anr(bx)r(a+bx)^n = \sum_{r=0}^{n}\binom{n}{r}a^{n-r}(bx)^r: every (bx)r(bx)^r becomes brb^r, and the whole right-hand side collapses to (a+b)n(a+b)^n again — obvious algebraically, since substituting a number for xx can't change which identity holds, but genuinely useful practically, because it turns the sum of every coefficient in a worked expansion into a number you can check independently: (a+b)n(a+b)^n. Set a=b=1a=b=1 specifically, and the identity becomes r=0n(nr)=2n\sum_{r=0}^{n}\binom{n}{r} = 2^n — the familiar fact that a full row of Pascal's triangle sums to a power of two, which is not a separate fact to memorise but the same substitution used to check every worked example in this lesson, with the two simplest possible numbers chosen for aa and bb. Set x=1x=-1 instead, with a=ba=b, and every term (nr)anr(a)r\binom{n}{r}a^{n-r}(-a)^r picks up a sign of (1)r(-1)^r; the terms cancel in pairs whenever n1n \geq 1, giving (aa)n=0(a-a)^n = 0 — which is exactly why an alternating row of Pascal's triangle, taken with alternating ++ and - signs, always sums to zero.

    Spec 4.5 only asks for the expansion and specific terms of it; it never asks for a proof about the row of coefficients as a whole. This is the one-line reason the "check by substituting x = 1" habit used throughout this lesson is not a trick — it works because the entire expansion, evaluated at x = 1, IS the sum of every coefficient, and that sum is forced to equal (a+b)ⁿ by the very identity being checked. It is not examined at P2 and no question will ask for it directly.

  2. Stationary Points and Curve Sketching

    A point of inflection, in general, is any point where the curve's concavity changes — where d2ydx2\dfrac{d^2y}{dx^2} changes sign — and nothing in that definition requires the gradient to be zero there at all. Take y=x33x2y=x^3-3x^2: dydx=3x26x=3x(x2)\dfrac{dy}{dx}=3x^2-6x=3x(x-2), stationary at x=0x=0 and x=2x=2 — neither of those is where the concavity changes. d2ydx2=6x6\dfrac{d^2y}{dx^2}=6x-6, which is zero at x=1x=1, and checking either side confirms a genuine sign change (d2y/dx2=6d^2y/dx^2=-6 at x=0x=0, d2y/dx2=6d^2y/dx^2=6 at x=2x=2) — concave before x=1x=1, convex after. But dydx\dfrac{dy}{dx} at x=1x=1 is 3(1)26(1)=33(1)^2-6(1)=-3, nowhere near zero: the curve is still falling, at its steepest, exactly as it flexes from one kind of curve to the other. This is the general case; a STATIONARY point of inflection — the one this lesson's mechanism derives, where d2y/dx2=0d^2y/dx^2=0 AND dy/dx=0dy/dx=0 coincide at the same x-value — is the special, rarer case where a concavity change happens to land exactly on a flat gradient too. Every stationary point of inflection is a point of inflection, but the reverse is false, and this lesson's own marked-solution above has an unforced example of the general case sitting inside its own wrong path: x=1x=1, the point the wrong-path candidate mistakenly solved for, is a genuine point of inflection of that cubic — just not a stationary one, and not what the question was asking for at all.

    Spec 7.1 asks only for maxima, minima and stationary points — a stationary point where the second-derivative test returns exactly zero is, at most, called a 'stationary point of inflection' when it needs naming at all, and nothing in the P2 spec requires the broader term. This is the one-paragraph argument for why that narrower picture is incomplete, and why understanding the fuller one makes the d²y/dx²=0 case in this lesson's own mechanism far less mysterious. It is not examined at P2 and no question will ask for it by name.

Pure Mathematics 2 · condensed sheet · not affiliated with or endorsed by Pearson Edexcel