Mock Paper Protocol

Provenance: compiled 2026-09-29. Built from a full read of research/veridian/WMA11-verified-facts.md and every other WMA11 technique-hub document already in this folder at the time of writing — forge-exam-technique-guide.md, forge-forty-eight-hour-checklist.md, forge-battle-card.md, forge-error-pattern-tracker.md, forge-exam-day-protocol-extended.md, codex-formula-and-method-bank.md, signal-frequency-and-boundaries.md and the fourteen signal-topic-brief-*.md files — plus content/veridian/question-bank/wma11.ts and a grep-based citation sweep of the nineteen lesson files in content/veridian/curriculum/wma11/. Two pieces of new checking specific to this document: (1) a direct directory listing of the local past-paper archive at ~/Downloads/PAPERI/IAL_Unit1_Complete_2024_2025/IAL_Materials/Mathematics/, confirming exactly which files exist for each of its sixteen series; (2) a grep sweep of every WMA11 curriculum and question-bank file for each series name found in the facts bank, counting how many files cite it, to separate "used as a full worked anchor somewhere in this course" from "named in passing" from "never touched." That sweep is this document's own method, stated in full in §2, not a hidden or invented count. No new primary-source PDF was opened for this document — every formula, mark-scheme rule and trap below traces to one of the files named above, cited at first use. Not affiliated with or endorsed by Pearson Edexcel.

#WMA11 — Mock Paper Protocol

#Pearson Edexcel IAL Mathematics, Unit 1: Pure Mathematics P1

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

This is the operational layer that sits on top of seven existing documents, not an eighth re-teach of any of them. It answers three questions none of the other seven fully answer: which real series to actually sit, across more than one mock rather than just the single one this hub already schedules; in what order to self-mark the result once the 90 minutes end, and why that order catches the paper's real, documented failure mode fastest; and how to read the timing data a mock produces so it tells you something more specific than "finished" or "didn't finish."

What this document does not do: it does not re-explain why the mark scheme works the way it does (that's forge-exam-technique-guide.md §2), it does not re-derive the per-question timing budget or the cumulative-checkpoint tables (that's forge-exam-technique-guide.md §1 and forge-exam-day-protocol-extended.md §3), it does not re-list the formulae or worked-method recipes (codex-formula-and-method-bank.md), it does not re-catalogue named error patterns (forge-error-pattern-tracker.md §1's EP-codes), it does not repeat the last-look summary (forge-battle-card.md), and it does not repeat the single 90-minute mock this hub already schedules inside the final 48 hours (forge-forty-eight-hour-checklist.md §1, T-30 to T-14). Where any of those is the right place to look, this document names it and moves on rather than restating it.

---

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

forge-battle-card.md §5 ranks, as the single most repeated failure shape in this paper's documented history, something that is not "ran out of time" and not "didn't know the method": solving the intermediate step and stopping there, without finishing the thing the question actually asked for. Four independently-verified instances of exactly this shape already sit in this hub — hidden-quadratic substitution (solves for the substituted variable, never solves back for x — Jan 2023 Q5, Jan 2025 Q4(b)); simultaneous equations (finds x, forgets to substitute back for y — Jan 2023 Q7(d)); two-stage integration (defers both constants to the very end instead of fixing each as it's found — Jan 2023 Q11(b)); and a zero-gradient tangent (computes f′(⅓) = 0 and stops, never writes the tangent equation — Oct 2021 Q6(c)). Each of those already has its own dedicated worked treatment in a curriculum lesson file. What a mock adds that a single worked example can't is the chance to catch this shape live, on a question you have never seen the trap named for — because the whole point of the pattern is that it doesn't announce itself; the algebra up to the stopping point is genuinely correct.

That reframes what a mock should be read for afterward. A mock that finishes with time to spare is not, by itself, a better result than one that runs out of time — it is only a better result if what got written down actually answered what each question asked. §6 below builds the self-mark order around checking that specific thing early, not last.

The clock still matters for a second, separate reason that is genuinely about time, not completion: forge-exam-day-protocol-extended.md §2 documents a real, low-mark, high-failure-rate question (January 2023 Q9, 4 marks, "more than half of all candidates scored no marks") sitting in the same paper as genuinely hard, high-mark questions that still pay out real partial credit for a correct first step (June 2022 Q5(a), "1 out of 4 was a very common score" but a real method mark was still there to take). A mock run under a real clock is the only way to find out, for yourself and not just from a cited examiner report, whether you're the kind of candidate who over-invests in a small, high-failure-rate question at the cost of a large one you were merely stuck on rather than lost on.

---

#2. Choosing which real paper to sit

Method. Two local archives hold genuine WMA11 question-paper/mark-scheme/examiner-report triples — WMA11-verified-facts.md §7 confirms both, and separately confirms one of them (~/Documents/SOL/Papers/IAL_Paper1_Complete/IAL_Materials/Mathematics/) holds PDFs for 16 series: Jan 2020–2025, June 2019–2024, Oct 2019–2024 — missing only Jan 2019, June 2020, Oct 2023 and June 2025. A direct directory listing of the other archive (~/Downloads/PAPERI/IAL_Unit1_Complete_2024_2025/IAL_Materials/Mathematics/), done for this document, confirms the same 16 folders, with two gaps worth flagging separately, because they are not the same kind of gap. June_2021 genuinely holds only a question paper and mark scheme in both archives — no examiner-report file of any kind — confirmed directly by listing both folders for this document; a mock on that series can be self-marked against the real scheme in §6 below but not cross-checked against examiner commentary afterward. October_2020 is a narrower, different problem: both archives' own file named Mathematics_Unit 1_ER_October_2020.pdf is not actually a PDF — a file check and a raw byte read (done for this document) confirm it is a saved Pearson "page not found" HTML error page mislabelled with a .pdf extension, the exact corruption the facts bank's own §7 already documents and worked around by re-fetching the real report directly from qualifications.pearson.com (confirmed genuine: WMA11_01_2010_ER, header reads "Examiners' Report ... October 2020 ... In Pure Mathematics 1 (WMA11)"). That real report is not missing from this hub — it is already fully read, quoted, and built into the facts bank (§4) and into sector-area-and-arc-length.ts's own trap-taxonomy — so a mock on October 2020 genuinely can be cross-checked against real examiner commentary; the only thing that doesn't work is opening the local archive's own file expecting it to be that report. Separately, Jan 2019's own examiner report was fetched live and is fully built into this hub (facts bank §4) — it is not in either local archive at all, so a genuinely blind timed sit of the real Jan 2019 paper needs sourcing directly from qualifications.pearson.com or an equivalent mirror, not either local folder.

A grep sweep of every curriculum lesson file and the question bank, done for this document, counted how many files cite each series by name — not a measure of how exhaustively a series has been mined, but of whether any specific real question from it has already been shown to a student as a worked example, which is the thing that actually compromises a mock's value as a cold test.

Tier 1 — already mined into this course's own material. Sit the rest of the paper, treat the named question(s) as review, not diagnosis.

Sitting a whole Tier 1 series is still useful — most of each paper is genuinely untouched — but discount the named question(s) when scoring the result; a strong self-mark on exactly that question tests memory of the lesson's own worked example, not the technique cold.

A named gotcha inside Tier 1: the local archive's own "June_2024" folder holds the WMA11/01R reserve paper, not the real WMA11/01 — confirmed by the paper's own printed reference, and independently caught by this hub's surds research when a full-paper grep for "surd" first flagged that folder and then found the mismatch (signal-topic-brief-surds-manipulation-and-exact-answers.md; codex-deep-dive-surds-manipulation-and-exact-answers.md, row 6 of its frequency table). The lesson content above is built from the real Summer 2024 paper, located separately on pmt.physicsandmathstutor.com, not from that local folder. If you pull "June 2024" from the local archive expecting a cold mock, you are actually sitting the reserve paper — which, as far as this hub's research has checked, is itself untouched by any WMA11 lesson content beyond that one mismatch note, so it is usable as a genuinely cold sit in its own right. The point of naming this explicitly is only that you should know which paper you are actually sitting, not assume the label on the folder is the paper this hub has already partly used.

Tier 2 — a confirmed-genuine primary document, structurally checked, but no specific question mined into any lesson. January 2024 (its per-question mark totals — 5,5,7,6,10,6,9,9,10,8 — are already visible in two existing timing tables, and its General Marking Guidance boilerplate was directly cross-checked against January 2023's, but no actual question content from it appears anywhere in a lesson) and October 2022 (confirmed as a genuine mark scheme with matching structure, zero content citations found anywhere in the grep sweep). Both are close to cold for content purposes — the January 2024 caveat is narrow: you will recognise the shape "10 questions, 75 marks" and each question's printed mark value going in, which is structural information, not a worked answer.

Tier 3 — genuinely untouched by any pass of this course's own WMA11 research, per the facts bank's own "series actually reviewed" table (§4) and confirmed by this pass's grep sweep returning zero hits. January 2020, January 2021, January 2022, June 2019 and October 2024 each hold a full real QP/MS/ER triple in the local archive and are named nowhere in the facts bank or any lesson file — the best available full-paper cold mocks this course has access to. October 2019 is very nearly in this tier: only its Q8 (a surd-simplification side-finding on a hidden-quadratic question) has been read at all, and even that finding was logged as "adjacent... not stretched to cover" the surds lesson's own core skill (WMA11-verified-facts.md, Lesson-audit log, surds-manipulation-and-exact-answers.ts entry) rather than built into a worked example — the rest of that paper is cold.

A caveat this tiering can't fully account for. This tiering reflects what this course's own written material cites, not what any individual student has personally read. Someone who has independently worked through, say, the full January 2020 paper outside this course's material should treat it as partially seen regardless of what tier it sits in above.

---

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

forge-error-pattern-tracker.md §3's own log template has eight blank rows, clearly built to hold more than one sitting — but nothing else in this hub says which real series should fill them. This document supplies that: draw the first several mocks from Tier 3 (or Tier 2, once Tier 3 is exhausted), in any order — each is a genuinely cold test of the whole paper, content and timing both. Save the Tier 1 series for later, after each one's already-seen question has been separately reviewed on its own, so the rest of that paper still functions as a real test even though one question doesn't.

forge-forty-eight-hour-checklist.md §1's own T-30-to-T-14 mock should be the last paper in this sequence, not the first time this protocol gets run. That document's own pile-(a)/pile-(b) sort (genuine content gap vs. a presentation gap the mark scheme wouldn't have credited) is far more informative when there's already a pattern from two or three earlier mocks to compare it against — a single sitting with no prior baseline can't tell a real recurring weakness from one bad day on one paper. If there is only one real, unseen series left by the time the 48-hour window opens, that is exactly the series that checklist's own T-30-to-T-14 block should use; don't spend it earlier in the sequence "to get ahead," and don't manufacture a second timed sit on a paper you've already marked once — you already know the answers, so it can no longer test anything but memory (the 48-hour checklist's own §1 makes the same point about re-sitting a paper twice).

A real ceiling worth naming plainly: across both archives plus the one externally-sourced real Summer 2024 paper, at most 17 distinct real WMA11 series exist that this course has any access to at all (16 in the local archive, plus the one genuinely live-fetched Jan 2019 series — Summer 2024's real paper replaces, rather than adds to, the mislabelled local "June 2024" folder). A study plan built on an assumption of unlimited cold past papers will run out before the exam does; sequencing matters precisely because the supply is finite and countable, not because of any received wisdom about spacing practice.

---

#4. Setting up a real sitting

• Exactly 90 minutes, one continuous sitting, no pausing. If a real interruption happens, log the actual elapsed time honestly in the timing audit (§7) rather than pretending the clock stopped — a mock's diagnostic value depends on the timing record being real.
• Constrain your own formula sheet to the real one, physically, before you start — not a general reminder to "know your formulae," which forge-exam-technique-guide.md §5 and forge-forty-eight-hour-checklist.md §3 already give, but a concrete mock-setup action neither of those documents asks for: write out, or photocopy, only the real formula booklet's actual P1 section — sphere and cone mensuration, and the cosine rule (codex-formula-and-method-bank.md §0.2, verified against the real booklet, Issue 2, January 2021) — and have nothing else in front of you. A mock sat with a fuller personal formula sheet available measures a different, easier skill than the real paper does, because the quadratic formula, the sine rule, area = ½ab sin C, arc length, sector area and both power-rule formulas are not there on the day (forge-battle-card.md §1–§2) — the whole point of drilling them from memory is defeated if a mock quietly lets you look them up.
• Check your calculator is Pearson-compliant before this sitting, not just before the real exam. The same restriction forge-forty-eight-hour-checklist.md §1 (T-8 to T-1) tells you to check the night before the real exam — no symbolic algebra, no symbolic differentiation/integration, no retrievable stored formulae (spec Appendix 6; the real Jan 2023 cover rubric, WMA11-verified-facts.md §2) — applies with equal force to a mock: sitting a mock with a non-compliant calculator (or with stored formulae you'd have to clear before the real exam) inflates the mock's score relative to what the real sitting will produce, which defeats the point of the diagnostic before you've even finished it.
• Use a real question paper, sourced from qualifications.pearson.com directly or from one of the two local archives named in §2 — never a paper reconstructed from this hub's own short, attributed trap-taxonomy quotes, which are fragments, not full questions.
• Write your checkpoint numbers at the top of the script before starting, taken from forge-exam-day-protocol-extended.md §3's cumulative-checkpoint method (running mark total × 72 seconds = the clock reading you should be at or ahead of) rather than either of that section's two worked example tables verbatim — the question count on this paper isn't fixed (10 or 11 in every series checked, WMA11-verified-facts.md §2), so the method, not a memorised table, is what actually transfers to whichever real series you're sitting. The one fixed anchor that holds regardless of question count is the halfway point: 45 minutes is exactly half of 90, and is worth a glance at the clock on any sitting (forge-exam-day-protocol-extended.md §3).
• Answer every question, in printed order, by default. This paper has no Section A/B/C structure to navigate — it's one flat, compulsory sequence — and "students must answer all questions" is a rubric requirement printed on the real paper, not encouragement (WMA11-verified-facts.md §2). A mock that skips a question "to save time" is not testing the actual paper's own rules.

---

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

Do this before consulting any mark scheme: for every question you feel uncertain about, write a one-word guess in the margin at what went wrong — "substitution," "period," "sign," whatever comes to mind first. Don't look up the exact trap name yet. The point is capturing an honest, un-primed first impression before the mark scheme's own wording reshapes your memory of what you actually wrote — a margin guess written after reading the scheme is retrofitted, not diagnostic.

---

#6. The self-mark order — what to check first, and why

This ordering is this document's own synthesis, not a Pearson-stated procedure — flagged as such, the same way forge-exam-day-protocol-extended.md and forge-forty-eight-hour-checklist.md each flag their own non-sourced judgement calls. It's built from two things that are sourced: §1's finding that this paper's dominant real risk is a correct method that stops short of the actual question, and the fact that some losses are cheap and mechanical to self-check while others genuinely need the mark scheme in hand. Check in this order, not question-by-question through the paper:

1. Completion, first, before any content check. Was every question attempted? This is the cheapest, most avoidable loss on this paper — a blank answer scores zero with certainty, while even a wrong attempt at a formula-and-substitution has a real chance at a method mark (forge-exam-day-protocol-extended.md §4, point 5). Confirm this before spending time on anything else.

2. A fast, mechanical pass for the highest-frequency confirmed losses — done before you open the mark scheme at all, because these are self-diagnosable without it:

• Every indefinite integration: is there a +c? This is the single most-repeated "silly" loss in the whole corpus, independently confirmed in four series (forge-error-pattern-tracker.md §2, EP5c).
• Every question asking for an exact value, or where surds are clearly in play: is the final answer still exact, or did it become a decimal partway through? (EPXb; the general Pure-Mathematics principle, WMA11-verified-facts.md §3.)
• Every inequality or region answer: is it stated in the actual variable, never "in terms of R" or any other region label? This is a real M0 — a lost method mark, not just a lost accuracy mark (EP1j, forge-exam-technique-guide.md §2.7).
• Every question carrying a printed "solutions relying on calculator technology are not acceptable" warning (or a close variant of it): does your working show a genuine algebraic line, not just a start line and an end line? (EPXa.)
• Every question you solved via a substitution (p = 3ˣ, a quartic-in-x², a two-stage integration, a zero-gradient tangent): did you actually finish — solve back for the original variable, find both coordinates, fix both constants, write the tangent equation — or does your working stop at the intermediate result? This is §1's own dominant pattern, and it is the one item on this list that is a genuine re-read of your own working against the question stem, not a one-glance check.
• Every inexact numerical answer: 3 significant figures, unless the question states otherwise (verbatim general instruction, every series checked).

forge-error-pattern-tracker.md §2 names EP5c and EP1g specifically as the two patterns with a stated cross-series count, which is why they anchor this pass — but the whole list above is worth running mechanically, in minutes, before the slower work in step 3 begins.

3. The literal mark-scheme pass — applying the M/A/B conventions to your own script as strictly as a real examiner would, not as leniently as you're tempted to. forge-exam-technique-guide.md §2.6 already explains what each convention means for writing a solution; self-marking is the same conventions applied the other way, against your own finished script, and the honesty risk runs in the opposite direction — toward giving yourself credit you didn't actually earn on the page:

• "M0 A1 is impossible" (WMA11-verified-facts.md §3, verbatim) — if you can't point to the specific line where a method mark was genuinely earned, don't award the accuracy mark that depends on it, even if your final number happens to be right.
• ft only ever tags A and B marks, never M (forge-exam-technique-guide.md §2.6) — if you carried forward an earlier wrong value, check whether the mark in question is A/B (which can credit "correct ft" working from your own wrong number) or M (which stands or falls purely on the method shown against whatever you were actually working with, ft or not).
• cso marks require, in the mark scheme's own words, "no errors in this part of the question" (WMA11-verified-facts.md §3) — stricter than cao; don't award yourself a cso-flagged mark for a derivation that had a slip you happened to correct later, even if the final answer under it is right.
• Rule 5 — a genuine misread that doesn't materially simplify the question costs exactly two A/B marks in the affected part, not a blanket zero and not full credit; apply the actual deduction rather than rounding it either way.
• isw protects work written after a correct answer; it does not restore one you've since crossed out (forge-exam-technique-guide.md §2.6) — if your script shows a correct value followed by further working that changes it, mark the version you actually submitted, not the earlier correct one you "really meant."
• An answer with no working gets no credit beyond what "could be done 'in your head'" (WMA11-verified-facts.md §3) — don't award a method mark because you know what you meant to do; if the working the scheme is looking for isn't on the page, it isn't earned.

4. Log every dropped mark into a loss ledger, sorted by cause, using the existing tracker rather than a fresh sheet. For each mark lost in steps 2–3, record it in forge-error-pattern-tracker.md §3's practice log, using the matching EP-code from §1 where one fits, or a self-named code per that document's own §4 where it doesn't. Categorise each entry as it goes in:

• Method not shown — you knew the approach but the mark scheme wouldn't have credited how (or whether) you wrote it. These are the cheapest to fix and the ones step 2 above should have already caught most of.
• Genuine content gap — you didn't know the method at all. These are the ones worth flagging for a real re-teach, not a quick habit fix (see §8).
• Never reached — the question, or the part, was never attempted because time ran out. Keep these separate from the two categories above; §7 below is specifically about them.

---

#7. The timing audit, after the content audit

Compare the checkpoint times you actually wrote down during the sitting (§4) against forge-exam-day-protocol-extended.md §3's running-total method. This document's own addition — a reasoned categorisation, not a Pearson-sourced convention, flagged as such — is to read the comparison in three different ways depending on what else happened on that question, rather than treating "over budget" as one undifferentiated signal:

• Over budget, but the answer was right. This is a fluency gap, not a knowledge gap — you have the method, it just takes you longer than the paper's own 72-seconds-per-mark rate allows. The fix is targeted speed drilling on that specific spec point (the matching curriculum lesson's own chain-drill), not re-learning the technique.
• Under budget, but the answer was wrong. This is a carelessness flag, not a time-pressure one — you finished with time to spare and still lost the mark, which means the loss belongs in §6's content audit, not in a "give myself more time" plan. Cross-check it against the loss-ledger categories above before assuming more time would have helped at all.
• Never reached in the time available. This is the one genuinely timing-caused loss, and the only category where "practise pacing" is actually the right fix rather than a guess. If the same position in the paper (not the same topic) keeps being where you run out of time across two or more mocks, the problem is more likely to be cumulative overspend on everything before that point than any one question.

---

#8. Feeding the result back into revision

Route each loss-ledger entry from §6 to the resource that actually addresses its category, rather than re-reading the whole hub after every mock:

• Method-not-shown / presentation entries → re-read forge-exam-technique-guide.md §2's matching sub-section (the formula-first habit, the three named 3TQ routes, per-term diff/int marks, dependent-mark chains, the abbreviations) — these are about how you wrote it, and that section is where the "how" lives.
• Genuine content-gap entries tied to a named EP-code → the specific curriculum lesson file named in that code's See column in forge-error-pattern-tracker.md §1 — re-work that lesson's own marked-solution and trap-taxonomy block, not just the one question you got wrong on the mock.
• Formula-recall failures → codex-formula-and-method-bank.md Part 1, or the condensed version in forge-battle-card.md §1–§2.
• Fluency (over-budget-but-correct) entries from §7 → the matching lesson's own chain-drill, repeated for speed, not for correctness you already have.
• Never-reached entries from §7 → forge-exam-day-protocol-extended.md §4's "if you are running behind" sequence, rehearsed specifically for the position in the paper where the overspend accumulates.

forge-error-pattern-tracker.md §5's own review protocol (tally codes every 3–4 practice sets, target the top 3 by count, re-check for two consecutive sets before retiring a code) is the mechanism this feeds into — this document's own job ends at getting each mock's result logged there correctly, not at re-describing that review cycle a second time.

---

#9. When a mock surfaces something genuinely new

If a mark loss doesn't match any EP-code in forge-error-pattern-tracker.md §1, log it under that document's own §4 mechanism — a short, self-named label, tracked the same way — rather than forcing it into the nearest code that doesn't quite fit. One instance on one mock is a single data point, not a confirmed pattern; write it up as "seen in my own mocks," matching the discipline every source document in this hub already holds itself to. A pattern that recurs across two or more of your own mocks is real, disclosed evidence worth eventually raising for a future pass to fold into the facts bank's own §6 or the error tracker's §1 — not something this document does on a single sighting, and not something to silently discard either.

---

#10. Honesty notes

• No grade boundary and no likelihood percentage appears anywhere above — signal-frequency-and-boundaries.md §2 documents the one unverified figure this course's research has ever surfaced (October 2022) and why it isn't repeated anywhere in this hub, this document included.
• §2's tiering measures this course's own citation footprint as of 2026-09-29, on the files actually swept — it is not a claim about what any individual student has personally studied, and it says nothing about which series will feel easier or harder; a Tier 1 series is "partly seen by this course's own material," not "predicted" or "easier."
• The June 2021 examiner-report gap, the October 2020 corrupted-local-file issue (real report available elsewhere in this hub, just not from that file — §2), and the June 2024 reserve-paper mismatch (§2) are disclosed exactly as found, not smoothed over to make the tiering look tidier than it is.
• This document's own new contribution, stated plainly: the archive-tier sourcing sweep in §2 (a directory listing plus a citation grep, both done for this document); the pre-mark-scheme mechanical triage list in §6 step 2 (a resequencing of already-verified patterns, not a new one); the explicit self-marking-honesty framing of the M/A/B conventions in §6 step 3 (applying already-sourced writing conventions to a marking-yourself use case this hub hadn't separately addressed); and the overspent/underspent/never-reached timing categorisation in §7 (reasoned synthesis, flagged as such). Every fact those sections rest on — every quoted mark-scheme rule, every named series, every EP-code — is inherited from one of the seven source documents named in the provenance note above, not re-derived from a primary PDF independently for this pass.