Technique Masterclasses

Mechanics 1

A Star Gap Analysis

Provenance: written 2026-09-29. This is a synthesis/index document, not new primary-source research. Read directly this session: research/veridian/WME01-verified-facts.md (§2's calculator/formula-booklet findings and §3's mark-scheme conventions, to ground the provenance claims below — this document does not re-mine §4's per-topic content independently, since the technique-hub documents cited below have already mined it); content/veridian/curriculum/wme01/ read as a directory listing only, to confirm no existing lesson file already covers this synthesis; and, in full, the following existing WME01 technique-hub documents, which supply every specific claim below: forge-level-threshold-guide.md (the source of every threshold in Part 1), forge-battle-card.md §4 (its "Top 5 Danger List," the closest thing this hub has to a "danger phrases" ranking, reused directly in Part 2), forge-vocabulary-precision-list.md (the source of every entry in Part 3), signal-examiner-intelligence.md (the source of every pattern in Part 4), forge-error-pattern-tracker.md (the source of the tracking-table structure Part 5 builds on), forge-exam-technique-guide.md §4–§5 (the "essay with no calculations" instance and the general no-working rule reused in Part 2), and signal-frequency-and-boundaries.md §2 (the sole source of the A*/unit-grade correction in Part 0). No independent primary-source PDF was opened this session; every mark-scheme line, examiner-report line, and grade-scale fact below is reused, with its original citation preserved, from one of these seven documents. Nothing below claims a fresh primary-source read that did not happen this session, and no new diagnostic category is introduced anywhere in this document — every category below already exists, cited, in one of the seven sources. Not affiliated with or endorsed by Pearson Edexcel.

WME01 — A* Gap Analysis: Self-Diagnostic

Pearson Edexcel IAL Mechanics 1 (WME01/01)

What this document is, and isn't

This is not new research. This hub's documents that measure why marks are lost on WME01 — the level-threshold guide, the battle card's danger list, the vocabulary-precision list, the examiner-intelligence patterns, the error-pattern tracker — already exist, and between them are already unusually well developed (the level-threshold guide's own opening section says so directly). What doesn't exist yet is a single place that answers the specific question a candidate already scoring a solid, comfortable pass actually asks: of everything documented across those files, which parts are actually about the gap between a good pass and the very top of this paper, as opposed to the gap between failing and passing at all? This document answers that by re-reading each source with that one filter and indexing what survives it. It invents nothing new: every citation below already appears, in the same words, in one of the source documents named in the provenance note above.

Part 0 — Read this before anything else: this paper has no A* of its own

signal-frequency-and-boundaries.md §2 has already checked this directly against six official Pearson grade-boundary documents, and the finding matters enough to repeat here rather than let a candidate assume otherwise: WME01 is graded on Pearson's "International AS unit" table — lowercase a–e plus u, with no A* at unit level, in every series checked, regardless of whether the unit is cashed into IAS Maths, IAL Maths, or IAL Further Maths. A* exists only for the combined, six-unit qualification, calculated from A2-unit UMS averages — not from this single 75-mark paper. So a document with "A*" in its own filename, applied to one unit, is asking the wrong question if taken literally. What this document actually diagnoses is the real, unit-level equivalent: the gap between comfortably clearing grade a on WME01 and dropping so few marks that this paper is not the unit costing the qualification's overall A*. That distinction is not pedantry — forge-battle-card.md §6 already flags that this paper's own grade-a boundary has moved by a large margin between adjacent series, so treating any single number as a safe, fixed target would mean chasing a figure this paper's own record shows can shift under you. This document does not restate that boundary table itself; it already exists, sourced, in signal-frequency-and-boundaries.md §2, and this document adds no new boundary claim of its own.

Part 1 — The real shape of the gap: the threshold ladders this hub has already built

forge-level-threshold-guide.md is explicit that most of this paper's mark-by-mark ladders are already built elsewhere in this hub (its own §4 maps eleven of them, in the lesson files and CODEX deep-dives). What that document adds on top — and the only threshold material genuinely new to this hub — is three places where a script that looks "mostly right" can sit on the wrong side of a real, examiner-confirmed line. A candidate already passing comfortably should check their own last few timed scripts against these three specifically, because none of them is a physics error — each is a structural or procedural line a competent script can still cross.

1.1 — Two different floors: does the reason a number is wrong change what it costs? The mark scheme's own two rules look similar until read side by side. A genuine misread — copying a number wrong without changing what the question asks — is capped: "deduct two from any A or B marks gained" in the part affected, with every M mark surviving. A structurally broken equation — one missing a mass, a length, or (the record's own live instance) an entire acceleration term — has no such cap, because A marks cannot stand without their own M mark. The record's own quoted example: a connected-particles equation with every term a genuine, correctly-signed force, but no ma anywhere in it — an equation that, if solved, describes equilibrium rather than acceleration, and scores nothing for the method it was meant to demonstrate however tidy the following algebra looks. Self-check: when you lose a mark on a "wrong number" question, ask which floor actually applied — a capped two-mark loss, or an uncapped one running through everything chained to a missing term.

1.2 — Does a value from an earlier part still belong in this one? Oct 2022 Q3(b)'s mark scheme carries an explicit note most questions don't need: "M0 for both equations if they put X = 14.7 anywhere," X = 14.7 being part (a)'s own special value, which makes the two equations in part (b) mutually contradictory if reused. A script that writes both correct equations for part (b) but substitutes back a value found for a different scenario in part (a) can lose all eight marks bar one lone B-mark, for a mistake that has nothing to do with knowing the mechanics. Self-check: every time a later part introduces a new unknown or a new condition, confirm you are solving with that part's own value, not the previous part's — a real, quotable Pearson floor, not a hypothetical one.

1.3 — On a graph question, is the shape mark actually earning credit for the right reason? Jan 2025 Q2(a)'s three B-marks are independent of each other and of any method — the shape mark specifically requires the graph to "start on the vertical axis and not at the origin," with its own B0 condition firing on "any extra continuous lines." Two consecutive series (Jan 2025, corroborated by Jun 2025 Q3(c)) build the identical floor into their own mark schemes. Because this is a B mark, no downstream working can rescue it: a graph that is otherwise numerically sound but drawn as one continuous line where the real motion has a corner loses this mark outright, independent of the other two label marks in the same line. Self-check: on any v-t/s-t graph part, check the shape mark's own condition before checking either axis label — a script can bank both labels while losing the shape mark, and the reverse is just as possible.

Honestly flagged, not papered over: per forge-level-threshold-guide.md §3, no concrete WME01 script survives in this course's material that shows the 1.1 misread deduction actually landing on real numbers, and the two label marks in 1.3 are real and independently awarded but not laddered with their own wrong-script/right-script pair. Stated as real thresholds with a real evidence gap, not filled in to look tidier.

Part 2 — The confident-shortcut trap: a capable script can score like it did nothing

This is the mechanism most likely to catch exactly the candidate this document is written for, because it disproportionately punishes a script confident enough to skip a step that feels obvious. Two real, independently-named instances of the same underlying rule, plus the general marking guidance's own stated form of it: the front of the paper and the general marking guidance both state that "correct answers without working may not score all, or indeed any" of the marks available (forge-exam-technique-guide.md §5) — the mark exists on the working, not on the number arrived at. Jan 2025 Q6(c), a "does the box remain at rest" comparison, records candidates who wrote an "essay" with no calculations and scored nothing for it — a qualitatively sound, correctly-reasoned conclusion, denied every mark, because the paper is method-mark-driven throughout and prose does not substitute for a computed comparison. A related but distinct instance: Oct 2019 Q3's car-and-trailer question, where omitting the weight components from both particles' equations "fortuitously led to a correct value" that still received no credit, because the terms genuinely missing from the equations happened to cancel — the number was right for the wrong reason, and the mark scheme does not reward that coincidence.

The reason this belongs in a top-band self-diagnostic specifically: a candidate who needs to write out every line to reach an answer at all produces the working by necessity. A candidate confident enough to see the comparison, or the physically "obviously true" conclusion, without formally computing it is the one this rule actually catches — and a script that reasons its way to a coincidentally correct number through an incomplete equation is punished exactly as hard as one that reasons to a wrong number, because the mark scheme is checking the equation's structure, not the final digit. The gap-closing behaviour here is not "get better at the mechanics" — the mechanics were already right in both real instances above — it's writing the numeric comparison down even when the answer already feels obvious, and re-checking that an equation contains every term the physical system actually has, even when the final number looks plausible.

Honestly narrower than a rule: two named instances (Jan 2025 Q6(c), Oct 2019 Q3) plus the general stated rule is real evidence, not the three-or-more-series standard this course otherwise wants before calling something a standing convention — treated here as a confirmed, quotable mechanism worth checking your own scripts against, not a guaranteed trap on every series.

Part 3 — Vocabulary precision as a last-mile differentiator

forge-vocabulary-precision-list.md documents word-level distinctions the mark scheme is precise about, which a script that is otherwise mechanically sound routinely blurs without losing the physics — which is exactly why blurring them costs marks a review of the method alone would never catch. Three of its entries, reused here rather than re-derived:

A script that is mechanically sound throughout but treats any of these three pairs as interchangeable is losing marks a purely computational review would never flag.

Part 4 — What the examiner reports themselves say about where the gap actually sits

signal-examiner-intelligence.md finds that a WME01 report's language shifts register in a specific, quotable way exactly when it is naming a conceptual, not computational, gap: from plain retrospective description ("candidates did X") into a small, repeated verb family — "appreciate" or "be reminded" — confirmed across three independently-named series. Oct 2019's report states "candidates need to appreciate that the question refers to 'the model'" on a modelling sub-part, and separately, on the same paper, "candidates need to be reminded to show working when solving quadratics." Jan 2023 repeats the construction twice in one series: "it was necessary to appreciate that 'about to tilt' implied" one reaction had to be zero, and, on a different question, "many failed to appreciate that they needed to consider two stages of the motion." The practical read: where a report's own language makes this specific shift, it is naming the understanding it actually wanted, separably from the arithmetic — worth treating as the examiners' own words for exactly the kind of gap this document is about.

The same document finds a second, independent pattern that matters just as much for a top-band script specifically: a WME01 report that will not commit to a number for how many candidates erred will commit, with no hedge at all, to a flat causal claim about why one valid method fared worse than another. Jan 2022's report states plainly that "more efficient methods... were successfully employed" for an alternative to resolving; Jun 2024's report on a resultant-of-forces question states the cosine-rule route "tended to have more success" than resolve-and-Pythagoras; the same series' moments report goes further, stating outright that taking moments about the wrong point "inevitably led to more errors being made" — a claim about consequence, not just correlation, and Oct 2023 independently makes the identical unhedged claim on the same topic. The implication for a script that is already technically correct throughout: choosing the harder of two equally-credited methods is not an error the mark scheme penalises directly, but it is exactly the kind of choice the examiners themselves, unprompted and without hedging, say costs real candidates real marks — and it is precisely the sort of gap invisible to a review that only checks whether each step was mathematically valid.

Part 5 — Using this as an actual diagnostic, not just a reading list

This document adds no new tracking mechanism of its own — forge-error-pattern-tracker.md already has the fillable tables (its Part 2 log, Part 3 tally). What this document adds is a filter to apply before logging a lost mark there, for a script that is otherwise scoring well: before writing "silly mistake" in the tracker's log column, check the mark you lost against Parts 1–3 above first. A mark lost to the Oct 2022 Q3(b) carry-forward floor (Part 1.2) or the "essay with no calculations" trap (Part 2) is not the same category of problem as a mark lost to not knowing a method at all, and the fix is a checkable habit — re-verify which part's value you're using; write the number comparison down even when it feels obvious — not more practice of mechanics that, in both real cases above, was already correct. Use Part 4 the same way: where a method choice, not a physics error, is the actual cost, the fix is choosing the examiner-flagged easier route next time, not redoing the topic.

Flagged gaps — what this document does not claim

Sources used