Technique Masterclasses

Mechanics 1

Mock Paper Protocol

Provenance: written 2026-09-29, from a full read of research/veridian/WME01-verified-facts.md (17 series with at least one genuine primary document reviewed, Oct 2018–Jun 2025) and the three existing WME01 technique-hub documents in full — forge-exam-technique-guide.md, signal-frequency-and-boundaries.md, codex-formula-and-method-bank.md — plus the nine codex-deep-dive-*.md and eight signal-topic-brief-*.md files' own headers (to confirm no worked exemplar below duplicates one), the ten lesson files in content/veridian/curriculum/wme01/, and content/veridian/question-bank/wme01.ts. Two pieces of checking are new to this document: (1) a citation-footprint grep sweep of all ten WME01 curriculum lesson files for every named exam series in the facts bank, counting how many files cite each one by name — the method and full results are in §2; (2) a direct directory listing of every archive folder in this session's mounted working directories (~/Documents/SOL/Papers, ~/Downloads/PAPERI, and the other Downloads/Documents folders this session has access to) for anything matching "WME01" or "mechanics" — see §2's own findings. No new primary-source PDF was fetched for this document; every mark-scheme rule, examiner-report quote and figure below traces to the facts bank or one of the three named technique-hub documents, each of which already names the real Pearson file it came from. Not affiliated with or endorsed by Pearson Edexcel.

WME01 — Mock Paper Protocol

Pearson Edexcel IAL Mathematics, Unit M1: Mechanics 1

0. What this is, and what it deliberately doesn't repeat

This is the operational layer that sits on top of the three documents already in this hub, not a fourth re-teach of any of them. forge-exam-technique-guide.md ("FORGE") already owns the paper's real timing budget, the M/A/B/DM mark-coding system and its Mechanics-specific extensions, a self-mark checklist, a common-error digest mapped to individual lesson files, and an exam-day protocol. signal-frequency-and- boundaries.md ("SIGNAL") already owns topic frequency and the six real grade-boundary series Pearson has published. codex-formula-and-method-bank.md ("CODEX") already owns the formula masterlist and short method skeletons. Where any of those is the right place to look, this document names it and moves on.

What this document adds instead: which real paper to actually sit, honestly accounting for the fact that — unlike this course's Pure Mathematics papers — there is no local archive of WME01 past papers anywhere this session can reach (§2); how to set a mock up so it actually measures what the real exam measures, using facts already verified for this paper but never assembled into a single pre-flight sequence (§4); a self-mark order built specifically around this paper's own documented failure shapes, sequencing FORGE's existing checklist rather than repeating it verbatim (§6); and how to read the timing data a mock produces, using the only two real, complete, question-by-question mark tables this course has ever built for this paper (§7).

One structural gap is worth naming here rather than pretending otherwise: this course's Pure Mathematics papers (e.g. WMA11) each have a small family of FORGE-prefixed documents — a battle card, a 48-hour checklist, an extended exam-day protocol, a dedicated error-pattern tracker with its own EP-codes. No equivalent documents exist for WME01. Everything FORGE gives this paper — timing, marking, self-marking, error digest, exam-day protocol — lives inside the one forge-exam-technique-guide.md file, in its §§1–5. This document treats that as the real, current state of the hub, not an oversight to paper over; where a WMA11-style mock protocol would point to a dedicated tracker file, this one points to the matching section of FORGE instead, and says so plainly (see §6 and §9).

1. What a mock on this paper is actually rehearsing for

FORGE §2's own worked example is the sharpest single illustration of this paper's real risk, and it is worth restating here because a mock is specifically the place to catch it live: a connected-particles equation of motion that looks structurally fine — T − 2mg = 3mg − T — but contains no ma anywhere in it. Solved through, that equation describes a system with zero acceleration; the real dynamics never entered it. Every term present is a genuine force, correctly signed for its own particle — the error isn't a sign slip, it's a missing kind of term, and FORGE's own general M-mark rule (§2) explains exactly why that costs the method mark itself, not just the accuracy mark riding on it: an M mark in Mechanics has to produce a dimensionally correct equation, not merely something that looks like an attempt.

FORGE §4's "genuinely new patterns" list, built from a full deep-read of the two most recent series (January and June 2025), adds four more real, quoted instances of the same general shape — a correct method that stops one step short of what was actually asked: a resultant force found correctly then left as a vector when the question asked for its magnitude (Jan 2025 Q1a); a found system acceleration correctly derived in one part, then abandoned for g in the very next part instead of being carried forward (Jan 2025 Q7b); a "does it remain at rest" conclusion written as prose with no numbers behind it, which a Mechanics mark scheme credits nothing for regardless of how well-reasoned the prose is (Jan 2025 Q6c); and a non-vector method attempted on a question explicitly built around position vectors, which scored nothing no matter how sound the arithmetic (Jan 2025 Q5). None of these is a knowledge gap in the ordinary sense — the candidate knew the physics up to the point where the mark was actually lost. A mock's real value against this specific risk is that it surfaces the error live, on a question where you haven't been told in advance which step is the one that matters — which is exactly what a single worked example, read in advance, cannot do.

The paper's single strongest cross-series-confirmed trap is narrower and lives at the very end of a solution: reporting a signed value where an unsigned one was asked for, confirmed independently in four series — Jan 2020, Oct 2022, Jun 2024, and Jan 2025 on a different question type again (FORGE §2, "Sign-convention consistency"). A mock is the only way to find out, honestly and for yourself, whether this is a trap you still fall into under real time pressure, rather than one you merely recognise when someone else names it.

The clock matters for a separate, genuinely timing-shaped reason: FORGE §1's two full mark-by-mark tables (January and June 2025 — the only two series this course has ever mapped question-by-question) both put the single heaviest question last, and both make it the same structural combination — a connected-particles system followed by a free-motion continuation once a string goes slack or a particle lands (15 of 75 marks in January, 17 of 75 in June). FORGE names this explicitly as a two-series pattern, short of the three-plus series this course otherwise wants before calling something a standing convention — treat it as a strong prior worth planning a mock's own pacing around, not a guarantee about whatever paper you actually sit.

A mock that finishes with time to spare is therefore not, by itself, evidence of a good result. It is only a good result if what got written down actually answered what was asked. §6 below builds the self-mark order around checking that specific thing early, ahead of the slower literal mark-scheme pass.

2. Sourcing a real paper to sit — and the honest limits of what's available

This paper has no local past-paper archive anywhere this session can reach. This is a genuine, checked finding, not an assumption: a direct directory listing of every mounted working directory this session has access to — ~/Documents/SOL/Papers/IAL_Paper1_Complete through IAL_Paper4_Complete, ~/Downloads/PAPERI, and the remaining Downloads/Documents folders named in this session's environment — shows that the "Paper1 through Paper4" archives are organised by Mathematics unit number, and hold only Units 1–4 (P1–P4, this course's WMA11–WMA14) for the Mathematics subject folder in every one of those archives. No folder, in any archive this session can reach, is named for Mechanics, M1, or WME01 anywhere. This is a real, structural difference from this hub's own WMA11 mock protocol, which draws on two full local 16–17-series archives — no equivalent exists for this paper. A genuinely cold mock therefore has to be sourced live from Pearson directly, not pulled from a local folder the way a WMA11 mock can be.

Confirmed, real sourcing paths, per the facts bank's and FORGE's own citations, every one of them a file this course's own research has actually fetched and verified as a genuine PDF (via file and pdftotext, not assumed from a filename alone):

The confirmed 17-series list this course's own research has actually checked (facts bank §5): Oct 2018, Jan 2019, Jun 2019, Oct 2019, Jan 2020, Oct 2020, Jan 2021, Jun 2021, Jan 2022, Oct 2022, Jan 2023, Jun 2023, Oct 2023, Jan 2024, Jun 2024, Jan 2025, Jun 2025. "Confirmed to exist in this course's past research" is not the same as "sitting in a local folder ready to use" — every one of these still has to be actively fetched before a mock, the same way any of the facts and quotations in this hub's other three documents were.

A dated gap worth naming plainly, because today's date makes it checkable. This document is written 2026-09-29. Pearson's own June 2025 series was already confirmed and partly mined before this pass (facts bank, resolved 2026-09-25). An October 2025 WME01 series would ordinarily have been sat, marked, and had its mark scheme and examiner report published well before now — but no source in this hub has checked whether that series' documents exist at the URL pattern above. If they do, that series is very likely the single best genuinely cold option available for a mock, better than anything tiered below, precisely because nothing written for this course could have mined it yet. This is flagged as an open, checkable fact, not asserted as confirmed — check qualifications.pearson.com directly before relying on this document's own tiering below for the most recent series.

Tiering by this course's own citation footprint

Method. A grep sweep, done for this document, of every series name against all ten WME01 curriculum lesson files in content/veridian/curriculum/wme01/, counting how many distinct files cite each series by name. This measures the same thing WMA11's own mock protocol measures — whether a specific real question from a series has already been shown to a student as a worked example, not how exhaustively a series has been read — and it is a different, narrower measure than "does a technique-hub document mention this series at all," which is noted separately where it changes the picture.

SeriesCurriculum files citing itWhat that citation footprint actually is
Jun 20249 of 10The most heavily mined series in this course's WME01 material — specific content from at least Q2, Q3, Q5, Q6, Q7 sits inside individual lesson trap-taxonomies.
Jan 20228 of 10Q1, Q5, Q6, Q7 each carry specific findings built into lessons.
Jan 20237 of 10Q1, Q4, Q6 each carry specific findings; Q1's mark table anchors part of FORGE §1's own older, pre-2025 timing discussion.
Oct 20226 of 10Q1, Q3, Q4 each carry specific findings.
Jan 20205 of 10Q1 and Q2 each carry a specific, quoted finding (the sign-convention anchor and a tension-ratio misread).
Oct 20194 of 10Q6 (modelling-critique) carries the lesson's sole real spec-1.1 anchor; a narrower footprint than the count alone suggests, since it's essentially one question mined in depth rather than several.
Oct 20233 of 10Q1 (moments pivot-choice) and a general 7-question-count fact; thinner than Jun 2024/Jan 2022 despite appearing in three files.
Jan 20253 of 10 at the lesson level — but see belowVectors and connected-particles findings sit in three lesson files; separately, FORGE §1 carries this series' entire question-by-question mark table (all seven questions tagged by spec topic) and its own §2/§4 deep-read covers Q1, Q2, Q3, Q4, Q5, Q6, Q7 — every question's territory is named somewhere in this hub, even though only three of those findings have been folded into a curriculum lesson's own worked content yet.
Jun 2023, Jan 2024, Oct 2020, Oct 2018, Jan 2019, Jun 20191 of 10 eachEvery one of these single hits is paper-anatomy.ts's own question-count cross-check ("most series set 8 questions... Jan 2019 and Oct 2023 both set only 7") — a structural fact about the paper, not a worked question. No specific question content from any of these six series has been mined into any lesson.
Jun 20250 of 10Zero curriculum-lesson citations at all — but FORGE §1 carries this series' full eight-question mark table too, and its examiner-report finding about the final question ("by far the most demanding, with a modal mark of 0") is quoted directly. Structurally mapped in this hub; genuinely content-cold in every lesson.
Jan 2021, Jun 20210 of 10Genuinely closest to fully untouched. Jan 2021's mark scheme and examiner report were both downloaded and confirmed genuine, but the facts bank explicitly flags the examiner report as "not deep-read for topic content" (§8) — so nothing from it has entered any lesson. Jun 2021's own mark scheme is marked "Provisional" on its own cover (the globally disrupted 2021 series), and no examiner report for it was ever located — treat any self-mark against it as slightly lower-confidence than a "Results" (final) mark scheme.

Read this table for what it actually says. A high citation count means specific real content from that series has already been shown to you inside this course's own material — sitting that series whole is still useful (most of any paper stays genuinely untouched even at 9 of 10 files), but the named question(s) should be discounted when you self-mark, because a strong result on exactly that question may be testing memory of the lesson, not the technique cold. A "1 of 10" or "0 of 10" series is the closer thing to a genuinely blind sit this hub can currently offer — with Jan 2025 and Jun 2025 sitting in a genuinely different, in-between category: structurally previewed (you'll recognise the mark totals and spec-topic shape of each question going in) without having seen any specific worked answer for most of either paper.

3. A sequence across the study period, not one mock

Draw the first several mocks from the 1-of-10 / 0-of-10 rows — Jan 2021, Jun 2021, Jun 2023, Jan 2024, Oct 2020, Oct 2018, Jan 2019, Jun 2019, and (structurally previewed but content-cold) Jun 2025 — in any order; each is close to a genuinely cold test of the whole paper. Save the heavily-mined rows (Jun 2024, Jan 2022, Jan 2023, Oct 2022, Jan 2020) for later, and when you do sit one, review its already-cited question(s) separately afterward rather than folding a strong result on that one question into your overall read of the sitting.

A real ceiling worth stating plainly, the same way WMA11's own protocol states its own: 17 series are confirmed to have at least one genuine primary Pearson document somewhere in this course's research, and (per the dated note in §2) an 18th, October 2025, is worth checking for directly since enough time has plausibly passed for it to exist. That is a finite, countable supply, smaller than WMA11's own 17-series local archive in one important way — none of it sits in a local folder here, so every single mock on this list costs an active fetch from Pearson's own site before you can sit it, not just a file open. A study plan built on an assumption of unlimited easy cold papers for this specific unit will run out, or run into real friction sourcing each one, well before a Pure Mathematics unit's own plan would.

4. Setting up a real sitting

5. The moment the 90 minutes end, before opening anything

Before consulting any mark scheme: for every part you finished uncertain about, write a one-word guess in the margin at what might be wrong — "sign," "term," "vector," whatever comes to mind first. Don't look up the exact trap name yet. The value is an honest, un-primed first impression, captured before the mark scheme's own wording reshapes your memory of what you actually wrote on the page.

6. The self-mark order — sequencing FORGE's own checklist for a mock, not repeating it

FORGE §3 already gives a full self-mark checklist and §2 already gives the real M/A/B/DM conventions this checklist rests on — this section does not restate either. What it adds is an order to run them in when you've just finished a full mock rather than a single practice question, built around §1's own finding that this paper's dominant real risk is a correct method that stops one step short of the actual question:

1. Completion, first, before any content check. Was every question attempted? A blank answer scores zero with certainty; even a partial, structurally sound attempt has a real chance at an M mark (FORGE §5: "correct answers without working may not score all, or indeed any, of the marks available" runs both directions — a method shown without a final number can still bank real marks).

2. A fast, mechanical pass, done before opening the mark scheme at all, because each of these is self-checkable without it — this is FORGE §3's own "while you're working" and "before you finalise" lists, run retrospectively against a finished script rather than prospectively while writing one:

3. The literal mark-scheme pass — FORGE §2's M/A/B/DM conventions, applied against your own finished script as strictly as a real examiner would, not as leniently as you're tempted to. The honesty risk here runs toward giving yourself credit you didn't actually earn on the page — the specific things to check: "M0 A1 is impossible" (no accuracy mark stands without its method mark genuinely earned); ft tags only A and B marks, never M, so a carried-forward wrong value only rescues the marks that are allowed to follow through it; and a numerically "lucky" right-looking final answer built from a structurally broken equation (the missing-ma case from step 2) scores its M mark zero regardless of how the arithmetic afterward turns out.

4. Log every dropped mark, sorted by cause. FORGE §4 already maps named error patterns to the specific curriculum lesson file that owns each one in depth — route each loss there directly (§8 below repeats this routing briefly, it does not re-list FORGE §4's own map). Categorise each loss as method not shown (you knew the approach, the mark scheme wouldn't have credited how you wrote it — the cheapest fix), genuine content gap (you didn't know the method at all — worth a real re-teach, not a habit fix), or never reached (time ran out before the question or part was attempted — kept separate; §7 is specifically about these).

7. The timing audit, after the content audit

Compare your own checkpoint times (§4) against the two real, complete tables this course has ever built for this paper — the only ones that exist, so this is what "compare against a real series" currently means for WME01, not a stand-in for a fuller table this hub doesn't have:

January 2025 (WME01_01_2501, 7 questions, 75 marks) — FORGE §1:

QMarks≈ TimeTerritory
189.6 minVectors + N2L in vector form
21113.2 minKinematics, v–t graph, two unknown times
31214.4 minsuvat + friction + momentum/impulse combined
41012 minMoments, rod "on the point of tilting"
578.4 minVectors, position vectors, distance at a later time
61214.4 minFriction on an incline, "show that" then equilibrium-vs-motion
71518 minConnected particles then free motion — the final, heaviest question

June 2025 (WME01_01_2506, 8 questions, 75 marks) — FORGE §1:

QMarks≈ TimeTerritory
167.2 minMomentum/impulse
278.4 minVectors, relative position, bearing
389.6 minKinematics, suvat then a v–t sketch
478.4 minDynamics, two forces at angles, resolve then N2L
567.2 minMoments, several unknown forces on one rod
61113.2 minFriction on an incline, "show that," suvat, resolve
71315.6 minVectors/kinematics, relative motion, meeting condition
81720.4 minConnected particles then free motion — the final, heaviest question

Read the comparison in three different ways depending on what else happened on that question, rather than treating "over budget" as one undifferentiated signal — this three-way read is this document's own reasoned synthesis, flagged as such, not a Pearson-stated procedure:

A genuine, dated caveat on both tables above: they cover two consecutive series only. FORGE itself flags the "final question is the heaviest and is always this exact connected-particles-then-free-motion shape" finding as resting on two series, short of the three-plus this course otherwise wants before calling something a standing convention. Plan your own pacing around it as a strong prior — worth a specific time check near the end of any mock — but don't be shaken if a genuinely different series breaks the pattern; two data points is what this hub actually has.

8. Feeding the result back into revision

Route each loss-ledger entry from §6 to the resource that actually addresses its category:

9. When a mock surfaces something genuinely new

Here is the honest structural gap named in §0 again, in the place it actually matters: WMA11's own mock protocol routes a newly-surfaced pattern to a dedicated forge-error-pattern-tracker.md file with its own EP-code system and its own review cadence. No such file exists for WME01. The nearest real equivalent already built for this paper is FORGE §4's own "genuinely new patterns, found this pass, not yet in any lesson file" list — which is, in effect, exactly this mechanism already operating once (it holds the four Jan/Jun 2025 findings named in §1 above), just not yet given its own standing file or a name to call it by.

Until this hub builds a dedicated tracker, the honest working option is the same one FORGE §4 itself demonstrates: write the new pattern up in the same short, sourced, quoted form FORGE's own list already uses — what question, what series, what the examiner report or mark scheme actually says, verbatim where possible — and treat one instance on one of your own mocks as "seen once," not a confirmed pattern, the same discipline every document in this hub already holds itself to elsewhere. A pattern that recurs across two or more of your own mocks is real, disclosed evidence worth eventually proposing as an addition to FORGE §4 itself in a future pass — not something this document invents a new file for on a single sighting.

10. Honesty notes