Technique Masterclasses

Business Paper 1 — Marketing and People

Mock Paper Protocol

WBS11 — Mock Paper Protocol (Unit 1: Marketing and People)

Provenance (2026-09-28). Built from a full read of research/veridian/WBS11-verified-facts.md and every existing WBS11 technique-hub document — forge-exam-technique-guide.md, forge-forty-eight-hour-checklist.md, forge-battle-card.md, forge-error-pattern-tracker.md, forge-level-threshold-guide.md, forge-exam-day-protocol-extended.md, codex-definitions-and-application-bank.md, signal-frequency-and-boundaries.md — plus content/veridian/question-bank/wbs11.ts and the eight lesson files in content/veridian/curriculum/wbs11/. One piece of new research specific to this document: a direct listing of the local past-paper archive at ~/Downloads/PAPERI/IAL_Unit1_Complete_2024_2025/IAL_Materials/Business/ (19 series, January 2019 – October 2025, confirmed by directory listing this pass) cross-referenced against a citation sweep of every file named above, counting how many times each series is referenced anywhere in this course's own WBS11 material. 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 re-opened for this document beyond that directory listing — every technique or factual claim below traces to one of the files named above, cited at first use. Not affiliated with or endorsed by Pearson Edexcel.

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

This is the missing operational layer: not tariff-by-tariff technique (that's forge-exam-technique-guide.md §2), not how to place an essay answer on a real mark band (that's forge-level-threshold-guide.md), not a logging tool for a student's own mistakes (that's forge-error-pattern-tracker.md), not the real mechanics printed on the exam-day question paper itself (that's forge-exam-day-protocol-extended.md), and not the single specific mock this course already prescribes for the final 48 hours (that's forge-forty-eight-hour-checklist.md §3, Block B). This document answers four questions none of those five fully answer: which real past paper to actually sit, across more than one mock rather than just the final one; how to set the sitting up so it resembles the real thing rather than a relaxed read-through; in what order to run the self-audit afterward, and why that order; and what a mock on this specific paper is actually rehearsing for, per this paper's own real evidence — which turns out not to be what it's usually assumed to be.

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

forge-exam-day-protocol-extended.md §4 found something that reframes the whole point of a mock: across ten of the fifteen examiner reports it could read, Pearson's own examiners state directly that there is no real evidence candidates ran out of time on this paper — that finding recurs, close to verbatim, from January 2019 through January 2024. What those same reports name instead, repeatedly, as the actual reason marks are lost is a completed answer that missed the target: no counterbalance, the wrong stakeholder, extract copied rather than applied, a topic examined for the first time answered cold. A mock that finishes with ten minutes to spare but is riddled with those errors is not, on this paper's own record, a better result than one that ran out of time — it's a more representative rehearsal of the failure mode this paper actually produces most often.

That doesn't make the clock pointless. forge-exam-technique-guide.md §1's checkpoint table still exists because a section can silently burn 20 minutes on its first three questions and starve Discuss and Assess of the marks that decide most of that section's score — timing a mock for real is still how that specific failure gets caught. The point is what a mock should be read for afterward: not primarily "did I finish," but "did every finished answer land on what the question actually asked." §6 below builds the self-audit order around that priority directly.

2. Choosing which real paper to sit

Method. The local archive holds a genuine question-paper/mark-scheme/examiner-report triplet for most series from January 2019 to January 2025, plus question-paper-only folders for June 2025 and October 2025 (confirmed by direct directory listing this pass — ls ~/Downloads/PAPERI/IAL_Unit1_Complete_2024_2025/IAL_Materials/Business/). Separately, a keyword sweep across every WBS11 curriculum file, the question bank, and every technique-hub document counted how many times each series is named anywhere in this course's own material. That count doesn't measure whether a series has been exhaustively mined — most of it hasn't — it measures whether any specific question from that series 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 — sit for the other questions, treat the matching one as review, not diagnosis. Four series carry a full worked answer to one specific question inside this course's own material:

Sitting one of these four series whole is still useful — the other four or five questions in each paper are genuinely untouched — but skip or discount the one question already named above when scoring the result; you've already seen a complete worked answer to exactly that question, so a strong score on it tests memory of the model answer, not the technique.

Tier 2 — the general-purpose mocks. Every other series with a real question paper and mark scheme in the archive — January 2019, October 2019, January 2021, June 2021 (mark scheme present, no examiner report filed in this archive for that series), January 2022, June 2022, January 2023, June 2023, January 2024, June 2024, October 2021, January 2025, October 2024. Each of these is cited somewhere in this course's material — usually a single short quotation illustrating one named trap on one specific sub-question — but no full question from any of them has been turned into a worked model answer the way the four Tier 1 questions have. A handful of sub-questions inside any one of these may feel familiar if the matching trap has been closely drilled; the paper's other ten-or-so parts plus the essay have not been shown to a student as a complete answer. This tier is where most mocks in a study period should come from.

Tier 3 — timed dry run only, not a full self-mark. June 2025 and October 2025 hold a real question paper in the local archive but no mark scheme and no examiner report — confirmed by direct directory listing this pass, and independently confirmed the same way in forge-exam-day-protocol-extended.md's own provenance note. These are genuine, currently unpublished-mark-scheme series — fine for a realistic timed sit under §4's conditions below, not usable yet for the honest, mark-scheme-grounded self-mark §6 describes, because there is no real indicative content to check against. Hold these back until a mark scheme is actually published (no date is promised here, because none is known), or use them only to rehearse conditions and the paper-wide discrete-mark and level-descriptor language already verified in forge-exam-technique-guide.md and forge-level-threshold-guide.md — never to invent indicative content for a question these documents haven't seen a real mark scheme for.

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. A student who has independently worked through, say, the full June 2024 paper outside this course's material should treat June 2024 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 §5 already assumes at least five practice papers — its running tally has columns for "Paper 1" through "Paper 5" — but nothing in that document, or anywhere else in this course's material, says which real series should fill those slots. This document supplies that: draw the first three or four mocks from Tier 2, in any order — each one is a genuinely cold test of the whole paper. Save one Tier 1 series for later in the sequence, after its one already-modeled 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. Treat the Tier 3 series, once a mark scheme for either exists, as a bonus sixth or seventh sitting rather than part of the core five — there's no need to wait for them before starting.

forge-forty-eight-hour-checklist.md §3's own Block B mock — sat blind, in the T-30-to-T-14 window before the real exam — should be the last paper in this sequence, not the first time this protocol gets run. Running it cold, with no prior mock behind it, means the checklist's own diagnostic ("which self-mark box stays unticked across three or more papers is a habit, not a slip") has nothing to compare against yet. A student reaching for this document for the very first time inside that 48-hour window should still follow that document's own Block B guidance directly rather than trying to retrofit a multi-mock sequence into a window too short to hold one.

4. Setting up a real sitting

Concrete, not generic — grounded in what forge-exam-day-protocol-extended.md independently confirmed is actually printed on the real paper:

5. The moment the two hours end, before opening anything

Do this before consulting any mark scheme, per forge-error-pattern-tracker.md §2's own first step: for every question that feels like it lost marks, write a one-word guess in the margin at what went wrong. Don't look up the exact trap name yet — the point is capturing an honest, un-primed first impression before the mark scheme reshapes the memory of what was actually written.

6. The self-audit 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-forty-eight-hour-checklist.md §1 flags its own scheduling judgement. It's built from two things that are sourced: which errors are cheapest and fastest to check, and §1's finding that this paper's dominant real risk is a completed-but-off-target answer, not an unfinished one. Check in this order, not alphabetically through the paper:

  1. Completion, first, before any content check. Were all three sections attempted? This is the single most expensive, most avoidable loss on this paper — a blank section costs far more than any individual trap below, and forge-exam-day-protocol-extended.md §4 confirms the exam board's own stated floor is "try to answer every question," not answer every question well. Confirm this before spending time on anything else.
  2. Discrete-mark hygiene, next — fast and mechanical. Run forge-exam-technique-guide.md §3's per-tariff boxes for every Define, Calculate/Construct, Explain and Analyse answer: two distinct ideas on every Define, formula-or-diagram-before-numbers plus a unit/currency/% sign on every Calculate, two points of application on every Explain, two full chains with zero evaluative language on every Analyse. These are binary, checkable in seconds each, and catch the cheapest lost marks on the paper — forge-level-threshold-guide.md §4 confirms several of these are real, hard numeric caps (a missing PED sign costs an exact, confirmed mark; an incomplete Analyse pair caps at 3 of 6), not a matter of degree, so there's no judgement call to make here yet.
  3. The paper-wide top traps, next, on every Discuss/Assess/Evaluate answer. forge-battle-card.md §4's ranked list — missing or thin counterbalance, stakeholder substitution, copying the extract, repeating the Define stem word (already caught in step 2), dropping a sign/unit/% (already caught in step 2) — is the fastest way to catch the specific failure mode §1 above says is this paper's real, dominant risk. Check every extended answer against this list before attempting a full level placement; most real mark losses on this paper are one of these, wearing a different topic's clothes, and it's far faster to check five ranked patterns than to reason a level placement from scratch first.
  4. Level-of-response placement, last, because it's the slowest and most judgement-heavy step. For each Discuss/Assess/Evaluate answer, place it against the real boundary language in forge-level-threshold-guide.md §§2–3 — compare the actual answer to the closest real, verified "near-miss" and "what crosses the line" pair already documented there, or to the nearest of the three full L1–L4 ladders in content/veridian/question-bank/wbs11.ts, rather than guessing a mark cold. Doing this last means steps 2 and 3 have already caught and named the mechanical, discrete losses, leaving only the genuinely holistic judgement call for the step that actually needs one.
  5. Log everything, immediately, into forge-error-pattern-tracker.md §§3–4 — the eight structural categories where one fits, the named trap from forge-exam-technique-guide.md §4.1's index where a category is too broad, "other" where neither fits. Do this the same sitting, not later — the point of the tracker is a pattern becoming visible across mocks, which only works if every mock actually gets logged.

7. When a mock surfaces something genuinely new

If a mark loss doesn't match any named trap in forge-exam-technique-guide.md §4.1's index and doesn't fit one of forge-error-pattern-tracker.md §1's eight structural categories either, log it under that tracker's "other" column with a plain description rather than forcing it into a box that doesn't fit. One instance is a single data point, not a confirmed pattern — write it up as "seen in my own mocks," not as a new paper-wide rule, matching the discipline every source document in this hub already holds itself to (no invented likelihood, no claim beyond what's actually been observed). A genuinely new pattern that recurs across two or more of a student's own mocks is real, disclosed evidence worth eventually raising for a future pass to fold into forge-exam-technique-guide.md §4.2 or the facts bank's own §6 — not something this document does on a single sighting, and not something to silently discard either.

8. Honesty notes