Measures of location and dispersion — mean, coding, and standard deviation
~55 min · WST01 · 2.2
WST01 · 2.2 · 55 min
Coding turns an awkward mean — 255.2 — into an easy one, 0.1. That saving isn't free: add a constant and the mean slides by exactly that constant, but multiply by one and the mean scales by it once while the *variance* scales by its square — and has to be undone by squaring again on the way back. One real WST01 examiner's report records three separate ways candidates got that one decoding step wrong, in a single sitting. The standard deviation formula fails in an even more literal way: two different exam series produced malformed versions of it — missing a division, or missing a square root in the place it actually belongs — and both examiner reports trace the damage back to the same habit, rounding a value mid-calculation instead of carrying it through exactly. None of this is really about arithmetic. It's about which few numbers this exam expects you to reconstruct from memory, because the formula booklet — deliberately — will not hand them to you.
Before you read on
Two or three questions on exactly what this lesson teaches. Being wrong here is fine — it's the fastest way to find out what to pay attention to next.
Mean — from a plain list to a grouped table
The mean is for a plain list of values — add everything up, divide by how many values there are. The moment data comes as a FREQUENCY TABLE instead of a bare list, the formula doesn't change in spirit, only in bookkeeping: each value now has a count attached (how many times it occurs), so the sum becomes (each value counted the right number of times) and the denominator becomes (the total count of data values, whatever number of distinct rows that total happens to be spread across) — .
For a GROUPED table — data sorted into class intervals like rather than exact values — there's one more step before that formula can even be applied: you don't know the exact value of any single data point inside a class, only which class it fell into, so you use the class MIDPOINT as a stand-in for every value in that class. A class – contributes its frequency at , not at or or anywhere else — the midpoint is a genuine assumption (that values are spread evenly enough across the class for its centre to represent it fairly), not a measured fact, and it's the same assumption the mechanism block later in this lesson makes explicit for interpolation.
Spec 2.2's own guidance is worth stating plainly here, because it changes what a lesson on this topic should actually spend its time on: "calculation of mean/mode/median/range/IQR will not be the direct focus of exam questions; students are expected to draw inferences and interpretations." The arithmetic of finding a mean is a means to an end on this paper, not the endpoint — which is exactly why getting the DENOMINATOR right matters so much: get it wrong, and every inference drawn from the resulting number is built on nothing.
Median and mode both sit under this same spec item (2.2), but neither gets separate treatment here — the median already carries the load-bearing explanation in this course's outliers-and-box-plots lesson (why an outlier moves the mean and leaves the median untouched), and mode has no documented exam trap in the reviewed record worth building a section around. Range — the simplest measure of spread, — gets the same brief treatment: it's real, spec-listed content (2.3), but it's exactly two numbers subtracted, and nothing in the reviewed record flags a range-specific error worth a dedicated section.
Standard deviation — the formula you have to carry in your head
Variance has two equivalent forms. The DEFINITIONAL form, , says exactly what variance means in words: take every value's distance from the mean, square it (so a distance below the mean and an equal distance above it count the same), average those squared distances. The COMPUTATIONAL form, , is algebraically identical but far faster to calculate by hand — it needs only and , both of which a running table already builds up, rather than a fresh recalculated for every single value. Standard deviation is just — the square root taken at the very end, once, wrapping the entire expression.
Here is the fact that makes this whole lesson matter: this formula — either form — is one you're expected to know from memory. The specification's own "Notation and formulae" section states outright, of the formulae in this category, that they "will not appear in the booklet." Mean and standard deviation sit on that exact list, alongside IQR (). Compare that with the discrete-random-variable versions of similar-looking formulae — , — which ARE printed in the booklet as base definitions. The pattern is consistent across the whole paper: a general, computational formula with a summation in it tends to be provided; a specific rule for THIS kind of data, with no summation to fall back on if you forget the shape, has to be internalised.
One more habit is worth building in before the worked examples below: carry EXACT values through a multi-step calculation, and round only the final answer. A real examiner report on exactly this content states it directly — "students should be encouraged to work with exact answers in their working of calculations" — because rounding the mean partway through (say, to 3 significant figures) before it's squared and subtracted inside a variance calculation was a live, documented source of inaccuracy. The accuracy instruction printed on every WST01 paper's front page backs this up from the other direction: "Inexact answers should be given to three significant figures unless otherwise stated" — that instruction is about the FINAL answer, not an invitation to round early.
Coding — trading awkward numbers for easy ones, without changing the real answer
Real data is rarely centred on a round number. A set of measurements clustered around 255 — log lengths, say — forces every mean and variance calculation to work with large, awkward numbers, multiplying the chance of an arithmetic slip at every step. Coding sidesteps this: subtract a constant close to the data's own centre, then divide (or, equivalently, multiply) by a second constant, producing a new set of values clustered near a small, easy number like 0 — usually integers or simple decimals. Every calculation is then done on the EASY coded values, and only the final answer gets translated — "decoded" — back to the original scale.
Spec 2.2's guidance names this directly: "understanding and use of coding" sits inside the measures-of-location content, and a real WST01 question tests it using exactly this shape of transformation — data coded around an assumed mean, with a scale factor applied. The rule is usually written one of two equivalent ways: (subtract, then divide) or where (subtract, then multiply by the reciprocal). Both describe the identical transformation — a real coded question can present either form, and this lesson's own worked chain below uses both forms side by side for exactly this reason, using the real assumed mean and scale factor a genuine WST01 series is confirmed to have used.
What coding does to the MEAN is simple and matches ordinary intuition: subtracting shifts every value down by , so the mean shifts down by too; multiplying by scales every value by , so the mean scales by too. Decoding just runs both steps backward, in reverse order: divide by (or multiply by ), then add back. What coding does to the VARIANCE is where the real trap sits, and it needs its own dedicated explanation — see the concept-ladder immediately below.
Why coding's variance changes by the SQUARE of the constant, not the constant itself
In plain terms
Measure a set of plant heights in millimetres, then convert every single one to centimetres by dividing by 10. The new heights are all 10 times smaller — obviously — and so is their MEAN. But ask a different question: "by how much do the plants typically differ from the average plant?" — the spread. That spread is also 10 times smaller in centimetres than in millimetres, which matches intuition fine. Now ask the SAME question but using squared differences instead of plain ones — which is exactly what variance does. Each individual difference shrank by a factor of 10, so each SQUARED difference shrank by , not 10. Squaring a number that's 10 times smaller doesn't make the square 10 times smaller — it makes it 100 times smaller, because the shrink applies twice, once for each of the two factors being multiplied together inside the square.
In the language of coding: if (a pure scaling, ignoring the additive shift for a moment, since shifting every value by the same constant doesn't stretch or squeeze the data at all — it just slides the whole picture sideways, leaving how spread-out it is completely unchanged), then every DEVIATION from the mean — — also shrinks by a factor of when coded: . Variance is built from the AVERAGE of the SQUARE of these deviations, and squaring a quantity that shrank by produces a quantity that shrank by . That's the entire mechanism — the square isn't an arbitrary rule attached to the variance formula, it's a direct, unavoidable consequence of variance itself being built from squared deviations in the first place.
Formally
Formally, for : , since subtracting the constant shifts the distribution without changing its spread. And — the constant comes out of the squared bracket as , not , precisely because it was squared along with everything else inside that bracket. Decoding is this same identity read in reverse: if , then — dividing by the SQUARE, never the plain constant, and dividing rather than multiplying, because decoding is undoing the forward transformation, not repeating it. This is the exact same mechanism this course's own lesson on and proves for a discrete random variable — coding applies the identical algebra to a DATA SET instead of a probability distribution, which is why the same square, and the same easy-to-forget square, shows up in both places under two different-looking names.
In your own words
In one sentence: when you decode a coded variance back to the original scale, why do you divide by rather than by ?
Worked, in full
Coding log lengths around an assumed mean of 255 (the real, quoted assumed mean and scale factor from a genuine WST01 series)
- 01
The lengths, (cm), of five types of log processed at a sawmill cluster tightly around 255 cm: 251, 253, 255, 257, 259, occurring with frequencies 5, 10, 15, 15, 5 (out of 50 logs measured). Working with numbers this close together directly is exactly the situation coding exists for — every mean and variance calculation on the raw values would involve subtracting numbers that agree in their first two digits, over and over. Code using — subtract the assumed mean, 255, then scale by 0.5 — turning the five values into .
Earns: B1 — states the coding rule correctly, with both real constants (255, 0.5) applied in the right order (subtract first, then scale).
- 02
Build the coded frequency table and find its mean: . .
Earns: M1 A1 — correct , correct .
- 03
Find the coded variance: . .
Earns: M1 A1 — correct , correct .
- 04
Decode the MEAN: since , rearranging gives . .
Earns: M1 A1 — correct decoding direction (multiply by the RECIPROCAL of the scale factor, then add the assumed mean back) and correct value, 255.2 cm.
- 05
Decode the VARIANCE — the step the real examiner report singles out as the one most often gone wrong. . Standard deviation: cm (3 s.f.). The two documented wrong routes to this same step: forgetting to square the 0.5 gives — half the correct value; squaring it correctly but multiplying instead of dividing gives — smaller than the coded variance itself, which should be an immediate red flag, since decoding is supposed to make the number BIGGER (X is the more spread-out, uncoded scale), not smaller.
Earns: M1 A1 — correct decoding (divide by the SQUARE of the scale factor) and correct value, , .
Source — Examiner report, Jun 2022
"correct answers for variance of W... were much rarer, with candidates not decoding, commonly including the assumed mean of 255, scaling using 0.5 instead of 0.5², or knowing they should use 0.5² but multiplying instead of dividing."
Marked, line by line
The masses, in kg, of 60 packages processed by a warehouse in one day are grouped as: , 5 packages; , 10 packages; , 20 packages; , 15 packages; , 7 packages; , 3 packages. (a) Find the mean mass. (3) (b) Find the standard deviation of the masses. (4) (c) Using linear interpolation, find and , and hence the interquartile range. (4) — VERIDIAN-original question and data set; not a reproduction of any past-paper question. Every class in this table has the same width (10), which turns out to matter for part (a)'s common wrong path — see the note attached to it below.
11 marks available
(a) — 3 marks
- 01M1
Midpoints: 5, 15, 25, 35, 45, 55. .
Method mark for using the class midpoints, each weighted by its own frequency.
- 02M1
.
Method mark for the correct total frequency, used as the denominator.
- 03A1
kg.
Accuracy mark for the correct mean, from the correct numerator and denominator.
(b) — 4 marks
- 101M1
.
Method mark for Σfx², using the same midpoints as part (a).
- 102M1
.
Method mark for the computational variance formula, correctly ordered — divide by n before subtracting x̄², using the EXACT mean (28) from part (a), not a rounded version of it.
- 103A1
(4 s.f.).
Accuracy mark for the correct variance.
- 104A1
Standard deviation kg (3 s.f.).
Accuracy mark for the square root of the EXACT variance, not a re-rounded one — and for stopping at 3 s.f. per the paper's own accuracy instruction.
(c) — 4 marks
- 201M1
Cumulative frequencies: 5, 15, 35, 50, 57, 60. position — reached exactly at the END of the class, so (no fractional interpolation needed, since the 15th value is the very last one inside that class).
Method mark for identifying the correct class from the cumulative frequencies and locating Q₁ within it.
- 202A1
kg.
Accuracy mark for the correct lower quartile.
- 203M1
position , which falls inside the class (cumulative frequency reaches 35 at the end of the previous class, 50 at the end of this one). kg (3 s.f.).
Method mark for the interpolation itself — lower boundary, plus the fraction of the way through the class, times the class width.
- 204A1
kg (3 s.f.).
Accuracy mark for the interquartile range, from the EXACT (not pre-rounded) value of Q₃ — see the mechanism block below for why this particular Q₁ is worth a second look.
Mechanism
Why interpolation works — and why the n-vs-(n+1) convention can (very slightly) disagree
Linear interpolation for a quartile rests on one assumption, stated plainly rather than left implicit: within a class, the data is spread EVENLY across it. Nobody actually knows where, inside the class, each of its 15 packages' true masses fall — only that 15 of them do — so interpolation assumes they're spaced out uniformly along that 10 kg interval, and estimates 's position accordingly. That's a genuine modelling assumption, the same kind of assumption spec 1.1 names directly ("the basic ideas of mathematical modelling as applied in probability and statistics") — it's very often close enough to be useful, and it's never claimed to be exact, which is precisely why and found this way are described as ESTIMATES of the quartiles, not their true values. The formula itself just encodes that assumption in numbers: , where is the class's lower boundary, is the cumulative frequency reached before that class starts, is the class's own frequency, and is its width — position, minus what's already been passed, as a FRACTION of the class, scaled up to the class's actual width. Spec 2.3's own guidance flags this directly: "simple interpolation may be required" — and it isn't printed in the formula booklet any more than mean or standard deviation are, so the shape of it has to be remembered, not looked up. Two conventions exist for finding the POSITION itself — or for , and correspondingly or for — and a real WST01 mark scheme is confirmed to tolerate either. They usually land in the same class and differ only in the last decimal place of the final answer. This lesson's own worked masses table above is a case where they don't quite agree even that much: lands EXACTLY on the cumulative frequency 15 reached at the boundary between the and classes, giving flat with no fraction of a class to interpolate across; lands just PAST that same boundary, inside the next class, giving instead — a genuinely different class used for the interpolation, not just a rounding difference. (This mechanism — that the two conventions can disagree specifically at a class-boundary cumulative frequency — is VERIDIAN's own reasoning about why the finding below holds, not a claim the source material itself makes.) The verified finding itself, from a real series: "those that worked with n rather than n + 1 were usually more successful" — plausibly because 's tiny extra push past a boundary like this one is exactly the kind of ambiguity that trips a rushed interpolation up, landing a student in the wrong class without them noticing. Neither convention is marked wrong on its own — but this is worth knowing before choosing one out of habit, especially since the two-quartile version of this effect compounds: this lesson's masses table gives under the convention and under (3 s.f. each) — different enough to matter, from data that never changed at all. One further, related trap belongs here by name even though its own full worked treatment lives in this course's "Show that" answer discipline lesson: on a "show that the IQR equals [given value]" question, a real examiner report records candidates "making up two ages... which differed by 16 as their 'working'" (Oct 2021, Q3(b)) — inventing two numbers with the right GAP between them instead of genuinely interpolating either quartile. That's a different failure from choosing the wrong convention; it's not attempting the method at all.
Complete it yourself
Combining two groups — recovering Σy² for a group given only its standard deviation (real anchor: SD = 2)
- 01
Group A has values, with and . From these, mean and .
- 02
Group B has values, mean, and standard deviation — the real, quoted figure from a genuine WST01 series ("the standard deviation of 2"). To combine the two groups, for group B is needed, but only its mean and SD are given.
Named traps
- mean-denominator-is-class-count-not-total-frequency
- Confirmed, and stated by the examiner report as a genuinely disappointing pattern, not a rare one: "it was disappointing to see that some students were unsure on how to calculate a mean from a frequency table. Some added the frequencies and divided by 5 whilst others used the sum of class width multiplied by the frequencies" (Jan 2023, Q1(c)). The denominator of a mean is always Σf — the total number of data values — never the number of rows the table happens to be split across.
- mean-numerator-uses-class-width-instead-of-midpoint
- The second half of the same confirmed finding: some candidates used Σ(class width × frequency) as the numerator instead of Σ(midpoint × frequency). Worth noticing explicitly: for a table where every class has the SAME width (as in the marked-solution example above), this particular wrong shortcut always collapses to exactly the class width itself, no matter what the actual frequencies are — Σ(h×f)/Σf = h when h is constant — which is itself a giveaway that something's gone wrong, since a genuine mean has to depend on where the data actually sits, not just on how the table happens to be split into intervals.
- coding-decode-forgot-to-square-constant
- Confirmed, real, and directly quoted: candidates "scaling using 0.5 instead of 0.5²" when decoding a coded variance (Jun 2022, Q3(e)). Coding's effect on variance is always squared, because variance is itself built from squared deviations — see the concept-ladder above for the full mechanism, not just the rule.
- coding-decode-multiplied-instead-of-divided
- A more subtle version of the same real question, quoted directly: candidates "knowing they should use 0.5² but multiplying instead of dividing" (Jun 2022, Q3(e)). Getting the CONSTANT right (squaring it) but the OPERATION wrong moves the variance in the wrong direction entirely — decoding should always make the variance BIGGER than the coded value, since the original data is more spread out on its own (uncoded) scale than the easy numbers coding produced.
- coding-not-decoded-at-all
- Confirmed, real, and distinct from either error above: the same examiner report records candidates "not decoding" at all — reporting the coded variance, or a value still carrying "the assumed mean of 255" folded in incorrectly, as if it were the answer for the original data. A coded answer is a WORKING TOOL, never the final one; every coded calculation has to be translated back before it answers the question that was actually asked.
- malformed-standard-deviation-formula
- Confirmed as a real pattern from a genuine examiner report — a formula that isn't shaped like a standard deviation at all, rather than a numerically close slip. WST01-verified-facts.md describes (its own summary, not a Pearson direct quotation) two specific malformed shapes candidates produced in the same series, Jan 2023 Q1(d): one missing the ÷n step before the square root, one missing the square root entirely while also dividing the whole subtraction by n instead of just the first term. Either produces a wildly implausible number — see the marked-solution's commonWrongPath above for exactly how implausible, with real numbers attached. (A related but distinct error — squaring a given standard deviation before using it, rather than misshaping the SD formula itself — is confirmed independently in Jan 2021 Q6(c); see the separate forgot-to-square-sd-recovering-sum-of-squares entry below.)
- mean-rounded-mid-calculation
- Confirmed, and directly quoted: "students should be encouraged to work with exact answers in their working of calculations" (Jan 2023, Q1(d)) — rounding the mean before it feeds into a variance calculation was a documented, real source of inaccuracy on this exact question. Carry the exact value through every intermediate step; round only the final answer, to the paper's own stated 3 significant figures unless told otherwise.
- forgot-to-square-sd-recovering-sum-of-squares
- Confirmed, real, and directly quoted: "forgot to square the standard deviation of 2 when finding Σy² for the second group" (Jan 2021, Q6(c)). Recovering Σx² from a given mean and standard deviation requires rearranging Var = Σx²/n − mean² to Σx² = n(SD² + mean²) — the SD has to be squared into a variance first, the same squaring rule that governs coding above, showing up again in a differently-shaped question.
- interpolation-convention-can-shift-the-class-at-a-boundary
- Confirmed, real, and directly quoted: "those that worked with n rather than n + 1 were usually more successful" (Jan 2023, Q1(e)). Both conventions for the quartile position — n/4 or (n+1)/4 — are genuinely accepted by the mark scheme; the risk with (n+1)/4 is specifically at a class boundary, where a small extra push past a boundary can land the position inside a DIFFERENT class than n/4 would, changing which numbers the interpolation formula actually uses. See the mechanism block above for exactly this happening with this lesson's own masses data (VERIDIAN's own explanation for why the finding holds, clearly separated there from the verified finding itself).
- interpolation-answer-reverse-engineered-to-match-a-given-target
- A distinct, real trap on "show that" interpolation questions specifically, confirmed and directly quoted: "the main errors, since the answer was given, were making up two ages... which differed by 16 as their 'working'" (Oct 2021, Q3(b)). This is not a wrong CONVENTION or a wrong FORMULA — it's inventing numbers with the right gap between them instead of genuinely interpolating either quartile. Its full treatment, including why a mark scheme structurally cannot credit this kind of working, lives in this course's "Show that" answer discipline lesson; it's named here because it's specifically an interpolation trap, and this lesson would be incomplete without at least naming it.
Retrieval — with feedback on every choice
A data set is coded as . Given , what is ?
A student's working for the standard deviation of a set of exam scores (out of 100) produces a final answer of 236. What should immediately raise suspicion, beyond re-checking the algebra?
A frequency table has values 10, 20, 30, 40 with frequencies 3, 5, 7, 5 (). What is the mean?
A grouped frequency table has . One student finds 's position using ; another uses . Both interpolate correctly from their own position within whichever class it falls into. What's true of their two final answers?
Group C has 20 data values, mean 45, standard deviation 3. To combine it with another group, you need for Group C. Which expression is correct?
- Mean: x̄ = Σx/n (list) or Σfx/Σf (table/grouped, using midpoints) — divide by the total frequency, never the number of rows.
- Standard deviation: √(Σfx²/n − x̄²) — ÷n before the subtraction, √ wraps the whole result. Not in the booklet: know it from memory.
- Coding Y = b(X − a) or (X − a)/b: decode the mean by reversing the steps; decode the variance by the SQUARE of the constant, and the OPPOSITE operation.
- Recovering Σx² from a given SD: Σx² = n(SD² + mean²) — square the SD first, always.
- Interpolation position: n/4, n/2, 3n/4 (or the n+1 versions) — both accepted, but can diverge right at a class boundary.
- Keep exact values through a calculation; round only the final answer, to 3 s.f. unless told otherwise.
- A manifestly implausible final answer is a reason to re-check the method, not just the arithmetic.
Not affiliated with or endorsed by Pearson Edexcel. Every quotation attributed to an examiner report or the specification in this lesson (the Jan 2023 Q1(c) mean-from-a-table quote; the Jun 2022 Q3(e) coding-decode quote, including its own real figures of 255 and 0.5; the Jan 2023 Q1(d) "exact answers" quote; the Jan 2021 Q6(c) "standard deviation of 2" quote; the Jan 2023 Q1(e) n-vs-(n+1) quote; the Oct 2021 Q3(b) reverse-engineered-ages quote; the spec's "will not appear in the booklet" wording) is transcribed verbatim from WST01-verified-facts.md, itself independently checked against the primary Pearson PDFs. Two things in this lesson are explicitly NOT verbatim quotations, flagged at the point they're used and again here: the two malformed standard-deviation expressions (WST01-verified-facts.md's own summary of the Jan 2023 Q1(d) report, not a direct quotation — this lesson's numbers for them, 55716 under the square root and 928.6 as the final wrong answer, are its own concrete reconstruction of that general shape of error) and the explanation for WHY the n-vs-(n+1) interpolation convention can diverge (this lesson's own reasoning about a verified finding, not a mechanism Pearson's own report states). Two real anchor numbers are used and built around rather than invented outright: 255 and 0.5 (Jun 2022 Q3(e) — the surrounding log-length data set is VERIDIAN-original) and 2 (Jan 2021 Q6(c) — every other number in that combining-groups scenario is VERIDIAN-original). Every other numeric scenario in this lesson — the 60-package masses table used across the marked-solution's three parts, every prequestion figure, and every MCQ scenario — is entirely VERIDIAN-original, built to exercise a documented trap honestly rather than reproduce a real question. Every value in every scenario, real-anchored or original, was computed independently and cross-checked by a second method (Σfx/Σf against a running total; Σfx²/n − x̄² against the definitional Σ(x−x̄)²/n form; both interpolation conventions against the same cumulative-frequency table) before being written into this file. The per-line M/A/B mark allocations attached to every VERIDIAN-original question are modelled on the verified mark-scheme conventions in WST01-verified-facts.md §4 (what M, A and B marks mean, the cao rule, the exact-answer-until-the-end discipline, the "manifestly absurd answers should never be awarded" rule), not transcribed from a real mark scheme, which for an original question does not exist.
A data set is coded as . Given , what is ?
Correct. Here the coding rule divides by 4 to produce , so decoding multiplies by to recover — the same squared-constant, reversed-operation rule as before, just written with the constant as a divisor instead of a multiplier.
- B
The direction (multiplying, to undo a division) is right, but the constant isn't squared — this is the forgot-to-square error, transplanted onto the divisor form of the coding rule instead of the multiplier form.
- C
The constant is squared correctly, but this divides instead of multiplying — since coding DIVIDED to reach , decoding has to MULTIPLY to reverse it, not divide again.
- D
Both errors together: no square, and the wrong direction. has to be LARGER than here, since coding divided the data down — this answer moves it smaller instead.
Traps tested: Coding decode forgot to square constant · Coding decode multiplied instead of divided
A student's working for the standard deviation of a set of exam scores (out of 100) produces a final answer of 236. What should immediately raise suspicion, beyond re-checking the algebra?
- 236 is far larger than any plausible spread for scores confined to a 0–100 range — and a real WST01 mark scheme states plainly that manifestly implausible answers are never credited, even under a follow-through rule that would otherwise excuse an earlier slip
Correct. Sanity-checking a final answer against what's actually being measured catches this kind of error before it's ever submitted — and it's backed by the mark scheme's own general marking guidance, which states "manifestly absurd answers should never be awarded A marks," specifically so a chain of otherwise-followed-through working can't rescue a result that plainly can't be right.
- BNothing — standard deviations can be any size, so 236 is just as plausible as any other number without more context
The DATA'S OWN RANGE is real context: scores out of 100 cannot possibly vary by more than 100 from each other, so a spread of 236 is a contradiction with the scale of the data itself, not merely an unfamiliar-looking number.
- C236 must be wrong because standard deviations are always whole numbers
Standard deviations are frequently NOT whole numbers — this isn't a real property of the statistic at all, and reaching for it here would flag plenty of perfectly correct answers as suspicious for no reason.
- D236 must be wrong because a standard deviation can never exceed the mean
This also isn't a general property of standard deviation — a data set can have a standard deviation larger than its mean, particularly one with a long tail. The real problem with 236 here is its size relative to the DATA'S OWN maximum possible range, not its size relative to the mean specifically.
Traps tested: No plausibility check on final answer · Invented property of standard deviation
A frequency table has values 10, 20, 30, 40 with frequencies 3, 5, 7, 5 (). What is the mean?
Correct. , and .
- B — dividing by the number of distinct values in the table
The number of distinct rows (4) plays the same wrong role here as "the number of classes" did in the grouped-table trap above — it isn't the total count of data values, which is what a mean's denominator always has to be.
- C — the plain sum of the four values, divided by
This ignores the frequencies in the NUMERATOR entirely, treating each value as if it occurred exactly once regardless of how many times it actually appears — the value 30 occurred 7 times and 10 occurred only 3, and a mean that doesn't weight by frequency isn't measuring the actual data set at all.
- D30, the value with the highest frequency
This is the MODE (the most common value), a different statistic entirely — reporting it as the mean confuses "most frequent" with "average," which don't have to be anywhere near each other.
Traps tested: Mean denominator is class count not total frequency · Mean numerator ignores frequency weighting · Mode picked instead of mean
A grouped frequency table has . One student finds 's position using ; another uses . Both interpolate correctly from their own position within whichever class it falls into. What's true of their two final answers?
- They may come out slightly different — a real WST01 mark scheme is confirmed to tolerate either convention, but the two positions aren't guaranteed to interpolate to the exact same value
Correct. and are close but not identical positions — in this lesson's own masses table, the equivalent pair of positions ( vs ) produced against : close, genuinely accepted either way, but not the same number.
- BThey must be identical, since n/4 and (n+1)/4 are just two ways of writing the same rule
They're two DIFFERENT rules that usually land close together, not the same rule written two ways — for large the difference between and shrinks toward nothing, but it's never exactly zero, and at a class boundary it can matter.
- CStudent B's answer (using n+1) is definitely correct, since n+1 is the more standard convention
Neither convention is "more standard" in a way that makes the other wrong — a real mark scheme accepts either. If anything, the confirmed evidence points the other way: "those that worked with n rather than n + 1 were usually more successful" on a real series.
- DStudent A's answer (using n) is definitely correct, since only n appears in the formula printed in the booklet
Neither the interpolation formula itself nor either convention for the quartile's position is printed in the formula booklet at all — both have to be remembered, which is exactly why this lesson's teach block on standard deviation makes the same point about mean and SD.
Traps tested: N and n plus 1 treated as identical · One interpolation convention assumed superior · Nonexistent booklet formula invoked
Group C has 20 data values, mean 45, standard deviation 3. To combine it with another group, you need for Group C. Which expression is correct?
Correct. , with the SD squared before it's added to the squared mean.
- B
The standard deviation (3) is used un-squared — the exact, confirmed real error on this step: candidates who "forgot to square the standard deviation... when finding Σy²" on a genuine WST01 question. 40560 is close enough to the correct 40680 that this slip is easy to miss without checking the intermediate working.
- C
This squares the SD but leaves the MEAN un-squared instead — a different mistake in the same formula, and one that produces a far more obviously wrong (tiny) result.
- D — without multiplying by at all
is a total across all 20 values, not a per-value average — leaving out the step produces a number 20 times too small to be a genuine sum of squares for this group.
Traps tested: Forgot to square sd recovering sum of squares · Mean not squared recovering sum of squares · Sum of squares not scaled by n
Practice this for real
This site teaches the mechanism; the exam is sat on Pearson's own real questions. Go find and attempt these yourself — nothing here substitutes for actually sitting a timed paper.
- Examiner report
- Jun 2022 · Q3(e) — cited directly in this lesson
Select International Advanced Level → Mathematics → any series, then look for WST01.
Up next
Outliers, Box Plots, and Comparing Distributions
A box plot's whiskers only ever touch real data. The fence that decides who counts as an outlier is arithmetic you compute and then throw away — it never appears as a mark on the finished plot — and one of the most consistently documented box-plot errors on this paper is drawing a whisker straight to that invisible number instead of stopping at the last real value before it. The formula for the fence isn't fixed, either: the specification insists every question state its own rule, precisely so a memorised "1.5 × IQR" can't quietly become the wrong number for the one sitting in front of you.
55 min