Technique Masterclasses

Business Paper 2 — Managing Business Activities

Mock Paper Protocol

WBS12 — Mock Paper Protocol (Unit 2: Managing Business Activities)

Provenance (2026-09-28). Built from a full read of research/veridian/WBS12-verified-facts.md (1,222 lines — 16 series June 2019–October 2024, 15 mark schemes, 13 of 15 examiner reports) and every existing WBS12 technique-hub document — forge-exam-technique-guide.md, forge-forty-eight-hour-checklist.md, forge-battle-card.md, codex-definitions-and-application-bank.md, signal-frequency-and-boundaries.md, the six signal-topic-brief-*.md files and the six codex-deep-dive-*.md files — plus content/veridian/question-bank/wbs12.ts and all eight lesson files in content/veridian/curriculum/wbs12/, checked for their own trap-taxonomy and reference-card content so this document cross-references rather than repeats them. New primary-source work done specifically for this pass: a direct pdftotext -layout read of the real January 2025 WBS12/01 question paper (wbs12-01-que-20250115.pdf) — its front-cover instructions and all three section-opening lines, quoted verbatim and short below, not paraphrased from any other document's summary of them — and a direct directory listing plus spot-check of ~/Downloads/PAPERI/IAL_Unit2_Complete_2024_2025/IAL_Materials/Business/ (19 series, June 2019 – October 2025), which is this pass's own method for §2's tiering, not carried over from any prior document. That spot-check also surfaced a real filing quirk in that archive's own October_2024 folder, disclosed in §9. 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 a re-teach: not tariff-by-tariff technique (that's forge-exam-technique-guide.md §2), not a self-mark checklist for one already-written answer (that's the same document's §3), not the ranked list of this paper's top named traps (that's forge-battle-card.md §5), and not the final-approach revision plan (that's forge-forty-eight-hour-checklist.md). What none of those documents cover, and what this one does: which real past paper to actually sit, across more than one mock; how to set the sitting up so it resembles the real two hours rather than an open-book read-through; in what order to self-audit it afterward, using tools this hub already has; and what a mock on this specific paper is actually rehearsing for, per this paper's own evidence.

One honest gap to flag before anything else: WBS12's technique-hub is thinner than some sibling papers' in one specific way — there is no dedicated error-pattern-tracker document and no level-threshold "near-miss" guide for this paper the way some other Veridian papers have built. §6 and §7 below work around that gap by pointing at the real tools WBS12 does have (the verified level-descriptor tables, the two full level-exemplar ladders in the question bank, and the trap lists in FORGE and the battle card) rather than inventing references to documents that don't exist.

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

This paper's own record already answers this, and the 48-hour checklist and FORGE both state it: across the 13 examiner reports the facts bank could read in full, none records "candidates ran out of time" as a documented common error, and the January 2025 examiner report confirms the same thing directly for the most recent series checked [forge-exam-technique-guide.md §1; forge-forty-eight-hour-checklist.md §1]. What the same reports name repeatedly instead is a completed answer that missed what the question actually rewarded — the extract copied rather than used, a Discuss that only argues one side, an Analyse that develops one reason twice instead of two independently, a Calculate with the right number and no unit. A mock that finishes with time to spare but is full of those errors is not, on this paper's own record, a better rehearsal than one that runs close to the wire — it's a more accurate one.

That doesn't make the clock irrelevant. forge-exam-technique-guide.md §1's own sub-question timing table still matters, because a section can quietly burn its first three parts and starve the 8- and 10-mark questions of the minutes that decide most of that section's score. The point is what a mock should be read for afterward: not chiefly "did I finish," but "did every finished answer land on what the command word actually rewarded." §6 below orders the self-audit around that priority.

2. Choosing which real paper to sit

Method. A direct listing of ~/Downloads/PAPERI/IAL_Unit2_Complete_2024_2025/IAL_Materials/ Business/ this pass confirms 19 named series, June 2019 through October 2025. Cross-referencing that list against a grep sweep of every WBS12 curriculum, technique-hub and question-bank file for each series name gives a rough citation count per series — not a measure of how thoroughly a series has been mined, but of whether any specific real question from it has already been shown to a student as a worked answer, which is what actually compromises a mock's value as a cold test.

Tier 1 — a full worked level-exemplar already exists for one specific question. Two series:

Sitting either paper whole is still worthwhile — the other four sub-questions in that section, the whole of the other section, and the 20-mark essay are genuinely untouched — but discount or skip that one specific sub-question when scoring the result; a strong answer to a question you've already seen modeled in full tests recall of the model, not the technique.

Flagged partial exposure — one specific sub-question quoted at length, but not as a full level ladder. Four series carry a real, specific quote a student may already have seen:

None of these four is a full worked answer to the question — each is a single quoted mechanism, figure or line — so the rest of that series' paper is still a reasonably cold test. Treat them as a lighter-weight caveat than Tier 1, not a reason to exclude the series.

Tier 2 — general-purpose mocks, no known prior exposure in this course's material. Ten series: October 2019, January 2020, October 2020, January 2022, October 2022, October 2023, January 2024, October 2024, January 2025, June 2025. Each has a real question paper, mark scheme and (with the exceptions in Tier 3 below) a readable examiner report confirmed either in the facts bank's own 16-series review or, for the two 2025 series, in forge-exam-technique-guide.md's own direct pdftotext check. This tier is where most mocks in a study period should come from.

Tier 3 — incomplete official materials. Four series, each incomplete in a different, specific way:

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

WBS12 has no error-pattern-tracker document prescribing a numbered sequence of practice papers the way this hub does for at least one sibling paper, and — worth stating plainly — forge-forty-eight-hour-checklist.md itself never prescribes a full three-section, two-hour sitting inside its own 48-hour window; its §2 prescribes one timed section (45 minutes) in the T-48-to-T-24 window and one timed levels-based question in the T-24-to-T-2 window, not a full paper. That means a complete, realistic two-hour sitting of this paper has no home anywhere else in this hub — this document is where that has to happen, and it needs to happen earlier than the final 48 hours for the checklist's own partial drills to mean anything calibrated.

Draw the first three or four full mocks from Tier 2, in any order — each is a genuinely cold test of the whole paper. Fold in the two Tier 1 series later in the sequence, once their one already-modeled question has been reviewed separately on its own, so the rest of each paper still functions as a real test. Treat the Tier 3 series as extra sittings once a mark scheme exists for them (October 2025 has none yet), not as part of the core rotation. The 48-hour checklist's own partial-section and single-question drills in its final window should come after at least one full mock from this sequence, not instead of it — otherwise its own diagnostic value (recognising which traps are yours) has nothing built up behind it yet.

4. Setting up a real sitting

Grounded directly in the real January 2025 WBS12/01 question paper, checked this pass:

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

This is this document's own recommendation, not sourced to an existing WBS12 tool the way it would be if this paper had its own error-pattern tracker to feed: before consulting the mark scheme, write a one- or two-word note in the margin of any answer that felt weak, capturing an honest, un-primed first impression of what went wrong. The value is in doing this before the mark scheme reshapes the memory of what was actually written, not in the specific wording used.

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

This ordering is this document's own synthesis, flagged as such the same way forge-forty-eight-hour-checklist.md §1 flags its own scheduling judgement — built from which checks are cheapest and fastest, and from §1 above's finding that this paper's dominant real risk is a completed-but-off-target answer, not an unfinished one.

  1. Completion, first, before any content check. Were all three sections attempted, per the verified front-cover instruction in §4? This is the cheapest, most consequential check available — a blank section costs more than any individual trap below.
  2. Discrete-mark hygiene, next. Run forge-exam-technique-guide.md §3's own self-mark boxes for every Define, Calculate/Explain/Construct and Analyse answer — two distinct components on every Define, a unit or sign on every Calculate, two independently-developed reasons on every Analyse. These are binary and fast, and they catch the cheapest, most mechanical losses on the paper — already built and verified in this hub, not reproduced here.
  3. The paper-wide top traps, next, on every Discuss/Assess/Evaluate answer. forge-battle-card.md §5's ranked top-5 (quality-management term confusion; copying the extract; missing the unit/rounding instruction; writing a definition instead of the two direct reasons on Analyse; business-cycle under-preparedness) plus forge-exam-technique-guide.md §4's fuller trap map is the fastest way to catch the specific failure mode §1 names as this paper's real, dominant risk. Most real mark losses on this paper are one of these traps wearing a different topic's clothes.
  4. Levels-based placement, last, because it's the slowest, most judgement-heavy step — and the one step where WBS12's own hub genuinely has less to compare against than some sibling papers. For each Discuss/Assess/Evaluate answer, place it against the verified level-descriptor tables (the facts bank's own "Verified level descriptors" section, reproduced compactly in wbs12-paper-anatomy.ts's reference-card) and, where the topic matches, against the closest of the two full L1–L4 ladders in content/veridian/question-bank/wbs12.ts (Sew Sew for an 8-mark Discuss on legislation; Żabka for an 8-mark Discuss on an economic-influences topic). There is no dedicated near-miss/threshold guide for this paper the way there is for some others in this course — that's a real, disclosed gap, not something this document can fill by inventing threshold language that hasn't been verified against a real mark scheme. Where the topic doesn't match either existing ladder, placement has to rest on the level-descriptor wording alone; that's slower and more judgement-dependent than having a matched worked exemplar, and worth knowing going in.

7. Logging results — a real gap in this paper's hub, and a lightweight way around it

Unlike at least one sibling paper in this course, WBS12 has no dedicated error-pattern-tracker document with pre-built columns for a running multi-mock tally. Rather than pretend one exists, the honest recommendation is: keep your own simple running log — one row per mock, one column per named trap from forge-exam-technique-guide.md §4's compact map (grouped by lesson file) or forge-battle-card.md §5's top-5 — and tick which traps recurred each sitting. This is a suggested practice, not a sourced fact about this paper, and it's deliberately unelaborate: a spreadsheet or a sheet of paper with the trap names down the side does the job; building a dedicated tool for it is future work for this hub, not something to fabricate the appearance of here.

8. When a mock surfaces something genuinely new

If a mark loss doesn't match any named trap in forge-exam-technique-guide.md §4 or forge-battle-card.md §5, write it up plainly as "seen in my own mock" rather than forcing it into an existing category or asserting it as a new paper-wide rule. One instance is one data point. A pattern that recurs across two or more of a student's own mocks is real, disclosed evidence worth eventually raising for a future pass of this hub to formally fold in — not something this document does on a single sighting, and not something to silently drop either.

9. Honesty notes