Complete Timing Guide

Provenance (checked 2026-09-29): this document verifies and extends a raw, unverified source file — ~/Downloads/FINSTO/WBS12 — COMPLETE TIMING GUIDE.md — against three layers of real evidence: (1) research/veridian/WBS12-verified-facts.md read in full (1,221 lines — 16 series June 2019–October 2024, 15 mark schemes, 13 of 15 examiner reports read directly); (2) content/veridian/curriculum/wbs12/paper-anatomy.ts, the standing verified mark/time reference page for this paper; and (3) content/veridian/technique-hub/wbs12/forge-exam-technique-guide.md, which already derives a sub-question timing table and — critically — already checked the primary sources for whether time pressure is a real, documented problem on this paper. This document does not duplicate any of those three; it exists specifically to check the FINSTO source's granular, minute-by-minute claims against them and report what survives. Per this course's own standing rule, and per the specific caution this task was issued under — that this material family has a documented history of only roughly a quarter of spot-checked "verbatim" claims actually checking out — every specific minute figure below is either traced to the verified 1.5-minutes-per-mark arithmetic already established in paper-anatomy.ts and forge-exam-technique-guide.md, or is explicitly labelled as this document's own derived arithmetic, never presented as a Pearson-published rule. Not affiliated with or endorsed by Pearson Edexcel.

#WBS12 Complete Timing Guide — Minute-by-Minute Pacing

#What this document is, and isn't

forge-exam-technique-guide.md §1 already establishes the only verified timing model this course has for WBS12: a flat 1.5-minutes-per-mark rate (120 minutes ÷ 80 marks), applied down to each sub-question, giving a 45/45/30-minute split across Sections A/B/C. This document takes that verified arithmetic one level further — a full elapsed-time checkpoint schedule across the entire two hours — which is genuinely new (that file stops at the per-section running total; it does not lay out a 0:00→2:00 clock). It does not re-derive the AO splits, level descriptors or trap taxonomy already verified elsewhere; those are cited, not repeated.

It was commissioned to verify a specific outside source — a "COMPLETE TIMING GUIDE" file claiming exact minute allocations for every sub-question, a four-paragraph essay template for Q3 with per-paragraph timing, elapsed-time pacing checkpoints, and a set of "emergency protocols" for falling behind. Almost none of that granular structure survived verification. The headline finding, established independently in forge-exam-technique-guide.md §1 from the January 2025 examiner report and confirmed across all 13 readable examiner reports in the verified-facts file: no examiner report reviewed for this course records "candidates ran out of time" as a documented problem on this paper. A minute-by-minute survival guide built around the premise that this paper is a tight time race is answering a question the primary sources don't actually raise. What the sources do raise, repeatedly, is command-word technique — which is why the pacing table below is offered as a planning aid, not a countdown to panic over.

---

#1. The verified base layer — nothing new, restated so the rest of this page has a foundation

From paper-anatomy.ts and forge-exam-technique-guide.md §1, both already verified: 120 minutes, 80 marks, flat rate 1.5 min/mark, applied per sub-question within each section's identical five-part climb (Define 2 → Calculate/Explain/Construct 4 → Analyse 6 → Discuss 8 → Assess 10):

Section B repeats this unchanged against a fresh extract. Section C is a single 20-mark Evaluate at the same flat rate: 30 minutes, no sub-parts. 45 + 45 + 30 = 120. This table, and the disclosure that the flat rate is this course's own study heuristic rather than a Pearson instruction, is unchanged from forge-exam-technique-guide.md — restated here only as the arithmetic everything below is built from.

---

#2. The elapsed-time schedule (the genuinely new part)

Extending the table above into a running clock across the full two hours — arithmetic only, no invented reallocation:

This is the actual, defensible minute-by-minute plan this course can stand behind. Two things about it are deliberately different from the FINSTO source's version:

• No separate "extract reading" line item. No primary source, and no already-verified Veridian material, carves out a fixed number of minutes for reading the extract as distinct from answering the question — the flat rate already absorbs whatever reading takes. The FINSTO source's 3/3/4-minute reading allowances are not derived from anything checkable; they were dropped, not incorporated.
• No separate "buffer" line item. The front cover's own instruction — verified in forge-exam-technique-guide.md §5 — is to check your answers if time remains at the end, not to reserve a fixed number of minutes for it in advance. The next section explains where any real spare time is likely to come from instead.

#An optional adjustment layer — labelled as optional, because it is

forge-exam-technique-guide.md §1 makes one verified, evidence-based case for spending less than the flat allocation on one specific sub-question: Define. A well-drilled two-component definition needs no extract reading, no application and no analysis, and genuinely takes under a minute to write once drilled — the source cites the January 2025 examiner report's own standing tip that extract reference isn't required on Define questions. If you bank roughly 2 of Define's 3 minutes on each of Q1(a) and Q2(a), you free up to 4 minutes across the paper — organically creating the check-your-work margin the front cover asks you to use, without a separate invented "buffer" row. Treat this as a technique refinement on top of the checkpoint table, not a replacement for it — the checkpoint table above is the one to plan against; this is what to do with any time it leaves spare.

---

#3. Tariff-by-tariff stop cues — verified technique, correct minute attached

Each rule below is already verified in research/veridian/WBS12-verified-facts.md and/or forge-exam-technique-guide.md §2; only the minute figure and the framing as a "stop cue" are new here.

---

#4. Section C (Q3) — what's verified about its shape, and what genuinely isn't

The FINSTO source proposes a fixed four-paragraph template for the 20-mark Evaluate — Planning (2 min) → P1 main argument (7 min) → P2 "evaluate P1" (4 min) → P3 competing argument (7 min) → P4 + conclusion (4 min) — and states P2 specifically is "worth 2–3 marks."

None of this paragraph structure or per-paragraph timing exists in any primary source, or in any already-verified Veridian material for this paper. A direct search of research/veridian/WBS12-verified-facts.md, content/veridian/curriculum/wbs12/, and every file in content/veridian/technique-hub/wbs12/ for this vocabulary — "bilateral," "P1/P2/P3/P4," a named paragraph count — returned nothing. This isn't a minor gap; it contradicts something that is verified. forge-exam-technique-guide.md §2 states directly, from the January 2025 examiner report: levels-based marking works by an examiner reading the whole response and placing it at its best-fit level — there is no per-paragraph sub-mark tally to assign "2–3 marks" to a middle paragraph. Presenting a specific mark value for one paragraph of a holistically-marked essay misrepresents how the marking actually works, not just an unverifiable detail.

What is verified, and worth keeping: a two-sided treatment of the question, evidence drawn from the extract and used (not quoted standalone), and ending on a stated recommendation rather than a summary — all directly traceable to the level descriptors and the January 2025/June 2025 examiner-report findings already written up in forge-exam-technique-guide.md §2 and §3. Where Q3 names two specific factors to weigh against each other, giving each its own developed treatment before synthesising is a real checklist item there too. None of that requires, or has ever been shown to require, exactly four paragraphs at exactly those minute counts.

No fixed number of minutes for Q3's internal shape is offered here, because none is derivable from a real source — inventing one would repeat exactly the error being corrected. Plan Q3's 30 minutes around the verified requirements above (two-sided development, extract used as evidence, a stated recommendation with time left to write it), not around a specific paragraph clock.

---

#5. Verification log — the FINSTO source, claim by claim

Structural claims (marks, sections, AO splits, conclusion requirements) — verified, because they restate facts already established elsewhere:

Granular timing claims — not verified. This is the part the document exists to check, and it is where almost everything fails:

One internal arithmetic problem found independently of comparing to primary sources: the source's own "Full Paper Summary" table lists Q1 = 39 min, Q2 = 39 min, Q3 = 28 min (summing to 106), then adds two further rows — "Extract reading (built in) — 10 min" and "Buffer — 4 min" — to reach its stated total of 120 min. But the 10 minutes of extract reading are already counted inside the 39/39/28 figures (3+3+4=10, matching exactly). Adding them again as a fifth row double-counts them: the table's own numbers only genuinely reach 110 minutes of accounted-for time (106 + the real 4-minute buffer), not 120. This is a self-consistency failure in the source's own arithmetic, independent of whether the underlying minute allocations are otherwise credible — which, per the row above, they aren't either.

---

#6. If you are genuinely behind schedule

Offered as ordinary technique judgement, not as a documented response to a risk the primary sources show is common — per §5 above, they don't:

• Finishing a stuck calculation at "good enough" rather than perfecting it is real, verified advice (paper-anatomy.ts), because a correct method with visible working still earns most of the marks even with a wrong final figure.
• On a Discuss or Assess answer running long, cutting it off to preserve time for the next question is a defensible trade given the verified fact that Discuss needs no conclusion and Assess's top band needs a stated judgement rather than a lengthy build-up — but no source states a specific number of minutes at which this trade becomes correct, and none is invented here.
• On Q3, if a conclusion is genuinely at risk of being skipped, writing it before finishing every point is a reasonable prioritisation given the verified finding that some conclusion — however underdeveloped — is what every real Level 4 exemplar reviewed for this course actually has, and Level 3 only "may" have one. This is a judgement call, not a Pearson-documented instruction.

---

#7. Scorecard

Of the source document's claims that could be independently checked: roughly 18–19 structural claims (marks, AO splits, section shape, conclusion requirements) verified — but these are claims the source shares with already-verified Veridian material, not new information the source itself contributed. Of the specific granular timing content that is this document's actual subject matter — the per-question minute allocations, the extract-reading allowances, the pacing checkpoints, the Q3 paragraph template, and the emergency-protocol thresholds (over 50 distinct figures across the source) — effectively none were independently derivable from a primary source or from this course's own already-verified arithmetic; nearly all were dropped and replaced with the verified flat-rate model in §§1–2 above. One claim (Hard Stop 3's instruction to check Discuss-question conclusions) is not merely unverified but directly contradicts a fact verified across 10 of 13 examiner reports, and a second (Q3's per-paragraph mark value) misstates how levels-based marking works at a mechanical level. Treating the source's structural claims and its granular timing claims as one pool, on the order of a quarter of its total distinct claims survive verification — consistent with the documented base rate for this material family, and the reason this pass verified line by line rather than transcribing.