Mock Paper Protocol

Provenance: written 2026-09-29, against research/veridian/WMA13-verified-facts.md (read in full — the primary provenance-checked source for the assessment-structure, mark-scheme-convention and cross-topic-pattern facts below), the three standing technique-hub documents for this paper already in this folder (forge-exam-technique-guide.md, forge-forty-eight-hour-checklist.md, signal-frequency-and-boundaries.md, each read in full so this document does not re-derive what they already cover), and a direct grep audit of this course's own WMA13 materials — content/veridian/curriculum/wma13/*.ts (11 lesson files) and content/veridian/technique-hub/wma13/*.md (the technique-hub documents that predate this one) — run this pass specifically to build the exposure table in §2, methodology stated in full there so it can be re-run and checked. content/veridian/question-bank/wma13.ts was also read in full (189 lines, 2 questions, both from October 2024) to confirm which real questions it currently reproduces.

#WMA13 (Pure Mathematics 3) — Mock Paper Protocol

#What this document is, and isn't

This is the protocol for running a real, timed WMA13 mock and self-marking it honestly — sourcing, sequencing, timing, and post-sitting audit. It is not a repeat of material that already exists elsewhere in this technique hub:

• forge-exam-technique-guide.md §2 already defines the M/A/B mark-coding system, dM1/ddM1, ft/bod/cao/isw, and the "quote the formula first" rule in full, with verbatim sourcing. This document does not re-derive those definitions — it cites them and adds the order of operations for applying them to your own script honestly (§6 below).
• forge-exam-technique-guide.md §6 already gives the exam-day, in-the-moment protocol (what to do question-by-question while sitting the real thing). This document is about the mock as a rehearsal-and-diagnostic tool, not the final sitting.
• forge-forty-eight-hour-checklist.md already tells you when, in a revision countdown, to run or avoid a full past paper (e.g. not starting a fresh one inside the last day). It assumes the how-to described here.
• signal-frequency-and-boundaries.md already carries the verified topic-frequency and grade-boundary data. Calibrate a mock score against that document, not against anything invented here.

#1. What counts as a real mock for this paper

A WMA13 mock is a genuine past series' question paper, sat under real conditions, marked against that same series' genuine mark scheme. It is not a generic "Pure Maths 3 practice test" from a third-party bank — those don't carry Pearson's own M/A/B/ft/bod/cao/isw/dM1/ddM1 conventions, and self-marking against anything else teaches you to grade yourself by a system you won't be marked against.

This course's own research has independently source-verified 13 real WMA13 series (per WMA13-verified-facts.md §2, plus the October 2024 series added during later lesson audits — see that file's §5, 4.4 entry and forge-exam-technique-guide.md's provenance line). What's actually available for each varies:

"Not reviewed in this course's research" means this course's own archive did not read or verify an examiner report for that series — it does not mean Pearson never published one. If you can source a report for January 2023, October 2023 or June 2024 yourself, you can still self-mark those series against their real mark schemes (below) without one; the report is a cross-check on why marks are commonly lost, not a requirement for marking.

Sourcing rule: use a mark scheme and question paper you can verify are genuine Pearson documents — the real publication code on the cover (WMA13_01_...), not a retyped or "reconstructed" version. A mark scheme with the wording paraphrased loses the exact M/A/B lines you need to self-mark against.

#2. Choosing which series to sit, and in what order

A mock is only a valid timing-and-technique rehearsal if you sit it cold. If you have already read a detailed worked walkthrough of a series' specific questions in this course's own lessons or technique-hub documents, sitting that series "cold" no longer measures what a mock is meant to measure — it measures recall of material you've already studied, not live exam performance.

To make that concrete rather than a vague warning, this pass ran a direct count of how often each series is named across this course's own WMA13 materials: grep -irc for each series' month/year (both abbreviated and full month name) across the 11 lesson files in content/veridian/curriculum/wma13/*.ts, and separately across the technique-hub markdown files that predate this one. Combined counts:

Read this as a proxy, not a precise measure. A raw substring count picks up every mention of a series name, including a passing citation ("also confirmed in Jan 2022") as well as a full worked exemplar quoted line-by-line — so it can overstate exposure for a series cited often in passing, and it can understate exposure for a question referenced mainly by its own question number after the series is named once. It is, however, a real, reproducible number, not a guess — re-run the same grep -irc commands over the same files and you get the same counts.

Practical sequencing: sit June 2024, October 2023, and October 2022 first, while they're least likely to have been spoiled by this course's own worked material — in that order, since June 2024 has effectively zero curriculum-lesson exposure. Save January 2022, October 2020, and June 2023 — the three most heavily mined for worked examples across this course's lessons and technique-hub — for open-book review or for re-marking practice (checking your own understanding of a mark scheme against a paper you already know) rather than for a timed, blind sitting.

One specific exception, not covered by the counts above: October 2024's Q7(a) and Q8(c) are reproduced as complete, real questions — full text, mark scheme, and examiner-report commentary — in content/veridian/question-bank/wma13.ts. If you have drilled that question bank, those two questions specifically are spent regardless of the series' middling exposure score; the rest of that paper is unaffected.

#3. Before you start: replicate the real conditions

Grounded directly in the verified assessment structure (WMA13-verified-facts.md §3):

• 90 minutes, 75 marks, every question compulsory — there is no section structure to skip or reorder around; sit the whole paper, in order, in one sitting.
• Calculator: an ordinary scientific calculator only. Appendix 6 (verbatim) bans "Calculators with a facility for symbolic algebra, differentiation and/or integration" — no CAS, no graphing calculator with symbolic calculus. Using one for a mock teaches a habit you cannot use on the day.
• Formula sheet: only the real Mathematical Formulae and Statistical Tables booklet (Issue 2, January 2021) — its P1/P2/P3 sections are listed in full in WMA13-verified-facts.md §3. Nothing memorised beyond what that section documents as "not in the booklet" should be written on a crib sheet for the mock; if you need a crib sheet to pass, that's diagnostic information the mock should surface, not something to mask.
• No notes, no open lesson files. The point of a cold sitting is to find out what you can do without them.
• Watch for the per-question calculator rubric. Some questions on a real paper carry their own instruction above them — verified verbatim, printed directly on the January 2023 paper above Q5: "Solutions relying entirely on calculator technology are not acceptable." This is printed on the paper itself, not a general reminder — read every question stem before answering it, exactly as you would in the real exam.

#4. Timing the sitting

forge-exam-technique-guide.md §1 already gives the real planning figure — 72 seconds per mark (90 minutes ÷ 75), demonstrated against January 2023's own hand-checked mark breakdown — and the caveat that marks are not spread evenly across questions. Don't re-derive that here; use it. What's specific to a mock rather than exam day is generating your own timing data to audit afterward:

1. Before starting, write your own per-question time budget in the margin of your answer booklet — each question's own printed mark tariff × 1.2 (the 72-second figure, expressed in minutes), running as a cumulative clock time (e.g. "Q1 by 0:07, Q2 by 0:14…") rather than a countdown, so a glance at a wall clock tells you instantly whether you're ahead or behind.
2. Check the clock only at the boundary between questions, not mid-question. A mid-question glance measures anxiety, not pace; a between-question glance measures the number you actually need — write the real elapsed time next to your written budget for that question as you move to the next one.
3. Do not set a per-question alarm. The real exam has no bell between questions — an alarm trains a stop-and-panic reflex the exam doesn't reward and manufactures pressure that isn't really there. A single visible clock or stopwatch is enough.
4. If a question is running well past its budget, mark where you are in the margin and decide deliberately whether to push on or move to the next question — but only decide this at a question boundary, using the number from step 2, not as a mid-question guess.

The point of steps 1–2 is to produce real per-question timing data, because §7 below needs it to separate "ran out of time" from "got it wrong" when auditing the result.

#5. The moment time is called

• Stop writing exactly at 90 minutes. Finishing "just this line" corrupts the very timing data the mock exists to produce, and it isn't available to you in the real exam either.
• Mark, in the margin, exactly where you were — which question, and roughly how far into it — before you do anything else. This is the raw material for telling a timing failure apart from a technique failure once you mark.
• Set the script aside before opening the mark scheme. Do not mark from memory of what you meant to write. The real exam marks what's on the page; a self-mark that marks your intentions instead is marking a different candidate.

#6. Self-marking honestly

The definitions — M/A/B, dM1/ddM1, ft/bod/cao/isw, "quote the formula first" — are already documented in full, with verbatim sourcing, in forge-exam-technique-guide.md §2. What follows is the order of operations for applying them to your own script without quietly being generous to yourself, plus the specific leniency traps this course's research has found are easiest to fall into when you already know what you meant.

Order of operations:

1. Mark every M line first, straight through the whole script, before looking at any A mark. A/A-marks are dependent on the M mark that precedes them — the general marking guidance states plainly that M0 A1 is impossible (WMA13-verified-facts.md §4) — so marking A first, on a line where the working "looks about right," tempts you to award the accuracy mark for an answer you recognise rather than checking the method mark it depends on was actually earned.
2. For any dM1/ddM1 line, count how many independent method marks genuinely precede it in your own script before deciding it's earned — don't copy the depth from a different question you remember. WMA13-verified-facts.md §4 documents this exact mistake happening in real drafted material (a real ddM1 quote grafted onto a simpler single-technique example that didn't actually have two preceding method marks) — it's a real, confirmed error mode, not a hypothetical one.
3. Check the whole line for a cso ("correct solution only") mark, not just its final number. The convention is explicit: no errors anywhere in that part of the question. A correct final value reached via a script with an earlier slip does not earn a cso mark just because the number is right.
4. Only apply isw after a correct answer has already appeared. "Ignore subsequent working" protects a correct answer from being undone by what comes after it — it does not let you skip past an error that occurs before the correct value shows up.
5. Never mark an M line "ft." Follow-through only ever applies to A or B marks — forge-exam-technique-guide.md §2.4 documents that this course's own lesson drafts mislabelled a follow-through method mark "M1 ft" three separate times before the error was caught. If you write "M ft" while self-marking, treat that as a signal to re-check, not a valid mark.
6. Re-check every calculator-flagged question against what your script actually shows, not what you know is true. If a question carried the "show all stages... calculator technology" rubric (§3 above), any M/dM/A mark chained to a step your script shows only as a bald final value is wrong, regardless of whether the value itself is correct — this is precisely what the real October 2024 Q8(c) mark scheme does, scoring a numerically perfect final answer 1,1,0,0,0 because the solving steps were never shown (forge-exam-technique-guide.md §3). This is the single easiest place to over-credit yourself, because you already know your number is right.
7. Apply exact-value, unit, and notation rules literally. Specific, real, named traps to check your own script against: a range written in $x$-notation instead of $y$/$f(x)$-notation loses the mark even with the right number (Jan 2023 Q1(a)); a correctly derived inverse attached to the wrong function's letter scores zero despite flawless algebra (Jan 2023 Q1(c)); a modelling answer missing a unit or a direction word ("increasing," "decreasing," "loss") loses the mark even with the right number (confirmed across 5+ series — WMA13-verified-facts.md §6); an angle given in the wrong unit on a construction mark like $R$/$\alpha$, not just the final solved angle, loses the mark (Oct 2020 Q7(a)). Self-marking with "I clearly know what I meant" is exactly the leniency the real mark schemes refuse — mark what's on the page, in the notation the scheme actually requires.
8. Check for an "ONLY" answer. If a question asks for a specific solution ("the smallest," "the first"), finding every solution and not rejecting the extras costs the mark even though you did strictly more correct mathematics (Jan 2022 Q2(b), verified verbatim — the accuracy mark is "ONLY," not "at least").

#7. What to check first, before you trust a total

Mark the whole script (§6), then audit in this order — this order matters, because it checks the most probable explanation for a dropped mark before the least probable one:

1. Write your score question-by-question, not just a final total. A single number hides whether marks were lost in one place or spread across the paper.
2. For every question you dropped marks on, check it first against the four cross-topic patterns already confirmed across three or more series and documented as general exam-technique, not one sub-topic (WMA13-verified-facts.md §6): incomplete "show that" working, a missing unit or context word on a modelling answer, a calculator-only method with no working shown, and a missing or wrong-notation domain/range on a function question. These four are independently confirmed across at least three series each, which makes them the single most probable explanation for a dropped mark on almost any topic — cheaper to rule in or out than a topic-specific check.
3. Only then, check the topic-specific trap table already built in forge-exam-technique-guide.md §5.1 for the specific spec areas the sat paper actually tested — that table names the lesson file and trap id for each confirmed pattern; don't re-diagnose from scratch what's already named there.
4. Calibrate the resulting total against real grade boundaries only through signal-frequency-and-boundaries.md, which sources its boundary figures directly from Pearson's own published grade-boundary PDFs. Do not estimate a boundary, and do not treat one mock's raw score as more precise than the boundary data itself supports.
5. Cross-check your timing log from §4 against where marks were actually lost. A question you ran far over budget on and also lost marks on points at a pacing problem; a question you finished on time and still lost marks on points at a technique gap the cross-topic or topic-specific checks (steps 2–3) should already have caught.

#8. Logging the result

Keep this minimal and consistent across mocks, so one sitting can be compared to the next rather than read in isolation. Per mock, record:

• Date sat; series used (and whether it was a "least-exposed" or "already-studied" choice, per §2).
• Raw score, question-by-question, out of the paper's real total.
• Which of the four cross-topic patterns (§7.2) recurred, and on which question(s).
• Which named topic-specific trap(s) from forge-exam-technique-guide.md §5.1 recurred, and on which question(s).
• Per-question time budget vs. actual, from the margin notes made during the sitting (§4).

The point of the log is to turn a single mock into evidence about which specific, already-named trap is actually live for you — not a generic "practice more" takeaway. If the same cross-topic pattern or the same named trap shows up on two or more separate mocks, that is real, specific evidence about where the next revision session should go; a single occurrence is not yet a pattern.

#Flagged gaps

• The exposure table in §2 is a proxy built from this course's own materials, not a claim about what any individual student has personally read. A student who has skipped the lessons and technique-hub entirely would find no series contaminated by this course's own writing, regardless of the counts above.
• No independent search was run for real Pearson examiner reports for January 2023, October 2023, or June 2024 beyond what WMA13-verified-facts.md already documents as reviewed. "Not reviewed in this course's research" (§1) should not be read as "does not exist."
• This document does not restate the M/A/B/dM1/ddM1/ft/bod/cao/isw definitions, the 72-second-per-mark timing table, or the per-topic trap table — each is cross-referenced to the existing document that already carries it, to avoid two documents drifting apart on the same fact over time.

#Sources

• research/veridian/WMA13-verified-facts.md — §2 (source archive and series list), §3 (assessment structure, calculator policy, formula-booklet contents), §4 (mark-scheme conventions, verbatim), §6 (cross-topic patterns), §5 (Jan 2023 Q1, Jan 2022 Q2 and Q7, Oct 2020 Q7, Oct 2024 Q8(c) — specific verbatim findings cited above).
• content/veridian/technique-hub/wma13/forge-exam-technique-guide.md — §1 (timing table), §2 (mark-code definitions), §3 (calculator-only-method penalty, incl. the real Oct 2024 Q8(c) 1,1,0,0,0 breakdown), §5.1 (topic-specific trap table), §6 (exam-day protocol).
• content/veridian/technique-hub/wma13/forge-forty-eight-hour-checklist.md — read in full for scope-boundary purposes (when to sit or avoid a full paper in a revision countdown).
• content/veridian/technique-hub/wma13/signal-frequency-and-boundaries.md — read in full; source of record for grade-boundary calibration, not reproduced here.
• content/veridian/curriculum/wma13/*.ts and content/veridian/technique-hub/wma13/*.md — direct grep -irc series-mention audit for §2's exposure table (methodology stated in full there, reproducible).
• content/veridian/question-bank/wma13.ts — read in full (189 lines); confirms the two real questions it currently reproduces (Oct 2024 Q7a, Q8c).