Business Paper 1 — Marketing and People

Error Pattern Tracker

#WBS11 — Error Pattern Tracker (Unit 1: Marketing and People)

Provenance (2026-09-28). Built from research/veridian/WBS11-verified-facts.md §4 (cross-cutting patterns verified across 3+ series) and §6 (flagged issues), cross-referenced against content/veridian/technique-hub/wbs11/forge-exam-technique-guide.md §4 (the full trap-taxonomy cross-reference index and its §4.2 new-evidence entries) so nothing below restates what those two documents already say in full. Also checked against content/veridian/technique-hub/wbs11/signal-frequency-and-boundaries.md (topic-frequency table) and content/veridian/question-bank/wbs11.ts (the three full worked real anchors). Not affiliated with or endorsed by Pearson Edexcel. Every specific claim below traces to one of those two source documents' own already-verified citations — this pass did not re-open any primary PDF. Short quotes (under ~15 words) carry their original attribution; everything else is paraphrase. No likelihood percentage or grade boundary is stated anywhere in this document — where a frequency is given, it is "seen in N of M series checked," exactly as the source documents phrase it, never a predicted probability.

What this is. The two documents above already built the taxonomy — every individual trap, named and filed against a lesson. This document does not repeat that list. It is the missing third piece: a tool for logging a student's own mistakes against that taxonomy while doing timed practice, so a pattern becomes visible across sessions instead of being re-discovered (or forgotten) each time. Photocopy or re-type the tables in §3 and §4 before each timed-practice sitting; fill them in during the 10-minute self-mark that should follow every paper, not during the paper itself.

#1. The eight paper-wide categories (pre-populated, not a student's to invent)

These are not the full trap list — they are the eight structural patterns the facts bank found repeated across three or more of the series it checked, which makes them the categories worth tracking as a group rather than the ~40 individual, topic-specific traps the FORGE guide already indexes one at a time. A single practice paper's mistakes should mostly sort into these eight; if an error genuinely doesn't fit any of them, log it under "other" in §4 rather than forcing it.

#	Category	What it actually is	Confirmed in (series checked)	Full detail
1	Stem-echo	A 2-mark Define answer restates the term itself with no second, distinct idea added	Jun19, Jun22, Jun23, Jun24, Jan24 (6 separate terms)	`forge-exam-technique-guide.md` §2 Define; facts bank §4.1
2	Extract-copy	Quoting or paraphrasing the source extract as if the quotation itself were the analytical point	Jun22, Jan23, Jun23, Jun24	facts bank §4.2; `promotion-pricing-and-distribution.ts` trap `dont-just-copy-the-extract`
3	Stakeholder substitution	The question names a specific stakeholder (employees, passengers, a named individual); the answer defaults to impact-on-the-business instead	Jun19 (Superdry), Jun22 (passengers), Jun24 (Coffee House)	`motivation-and-leadership.ts` trap `stakeholder-substitution`
4	Missing counterbalance	A Discuss/Assess/Evaluate answer builds only one side of the argument	Every one of the 6 series reviewed, without exception — the single most-repeated finding in the whole dataset	facts bank §4.4; multiple lesson files' own `missing-counterbalance` entries
5	Thin Explain	A 4-mark Explain gives one point developed twice instead of two genuinely distinct points	Jun19 (Q2b), Jan23 (Q2b)	facts bank §4.5
6	Calculation hygiene	Correct method, but no workings shown, or the answer is missing the unit/currency/% sign the question specified	Jun22, Jun23, Jan24, Jun24	facts bank §4.6
7	Flat conclusion	A 20-mark Evaluate essay's conclusion repeats body points rather than weighing significance and making an actual recommendation	Jun22, Jun23, Jun24	facts bank §4.7
8	First-appearance cold spot	A spec sub-point examined for the first time in a series scores disproportionately badly, precisely because it has no exam history to prepare against	PED–TR relationship (Jan23, first examination); entrepreneur-to-leader transition (Jun23, first examination); B2B/B2C strategy (Oct22, first examination); opportunity cost (Oct24, first examination in the archive checked)	facts bank §4.8; `forge-exam-technique-guide.md` §4.2

Categories 1, 2, 4 and 6 are, by the facts bank's own count, the highest-frequency of the eight — worth checking first when a paper comes back with marks missing and no obvious reason why.

#2. How to self-mark in a way this tracker can actually use

Five minutes, immediately after finishing a timed paper, before checking any mark scheme in detail:

For every question that lost marks, write in the margin which of the eight categories above it looks like, in one word. Don't look up the exact trap name yet — a rough guess is enough to start.
Open the mark scheme (or, for the paper's own worked real anchors, the level-exemplar cards in content/veridian/question-bank/wbs11.ts) and check the guess against what was actually credited.
Log it in §3 (if it's one of the eight structural categories) or §4 (if it's a narrower, topic-specific trap — check the FORGE guide's §4.1 index first for the exact name; if it isn't there, it may be new evidence worth a plain "other" entry rather than a forced fit).
After three or more papers, total the tally columns in §5. A category with three or more entries by a student's own log is a stronger, more personal signal than any paper-wide frequency figure above — it's this student's actual weak spot, not the cohort's.

#3. Structural-category log (the eight from §1)

Fill one row per mistake, one table per practice paper. Leave the "Fix applied" column blank until the next paper, then go back and tick it once that fix has actually been tried.

Date	Paper/series practiced	Question (e.g. "Q2d")	Category (1–8)	What I actually wrote (one line)	What the mark scheme credited instead	Fix applied next time?

#4. Topic-specific trap log (cross-referenced, not restated)

For a mistake that's really a named trap from the FORGE guide's §4.1 index (stem-echo's cousins like market-share-is-not-a-percentage, demand-is-not-want, boston-matrix-is-a- snapshot-not-a-forecast, and the ~35 others indexed there) — write the trap's own name, not a fresh description of it. The point of using the existing name is that it links straight back to the lesson file that drills it, so a repeated entry here is an instruction to re-open a specific page, not just a note that something went wrong.

Date	Question	Trap name (from FORGE §4.1, or "new" if not listed there)	Lesson file to revisit	Fix applied next time?

If a mistake doesn't match any named trap in the FORGE index and doesn't fit one of the eight structural categories in §3 either, log it here anyway as "other," with a one-line description. A repeated "other" entry across two or more papers is real, disclosed new evidence — exactly the kind of finding that should be raised for the FORGE guide's own §4.2 or the facts bank's §6 to absorb later, not quietly discarded because it doesn't fit an existing box.

Date	Question	Description (since no existing name fits)

#5. Running tally (fill in after every third paper)

Category	Paper 1	Paper 2	Paper 3	Paper 4	Paper 5	Total
1. Stem-echo
2. Extract-copy
3. Stakeholder substitution
4. Missing counterbalance
5. Thin Explain
6. Calculation hygiene
7. Flat conclusion
8. First-appearance cold spot
Named trap (§4), specify:
Other (§4), specify:

Read this table across, not down, after the fifth paper. A category that appears in four or five of the five columns is not bad luck on one paper — it is this student's own single most valuable thing to fix before the next attempt, ahead of anything else in this document.

#6. Two worked example entries (real, sourced, filled in to show the format)

These are not a student's own mistakes — they are the paper's own confirmed error instances, entered here once each to show exactly how a completed row should look. Delete or leave them in place as a reference; either is fine.

§3 example (category 4, missing counterbalance):

Date	Paper/series practiced	Question	Category	What was written	What the mark scheme credited instead	Fix applied next time?
(example)	June 2019	Q1(d), profit share, 8-mark Discuss	4 — Missing counterbalance	Financial-incentive benefits only, no drawback	The real mark scheme separately credits that profit share is role-weighted, so junior staff "may feel less motivated than those higher in the organisation" — a second, distinct limitation, not a restatement	—

§4 example (named trap):

Date	Question	Trap name	Lesson file to revisit	Fix applied next time?
(example)	June 2019 Q1(d)	`stakeholder-substitution`	`motivation-and-leadership.ts`	—

Both rows draw on the real June 2019 examiner report's own finding for this question: "the majority of students did not answer the question fully as they focussed on the impact of the profit share scheme on [the business], rather than the impact on the employees" — the same quote already cited, with full context, in motivation-and-leadership.ts's own trap-taxonomy entry.

#7. What this document deliberately leaves out

No grade boundaries and no predicted-likelihood figures appear anywhere above, in line with this course's standing rule and because neither exists in any source checked for this paper (see signal-frequency-and-boundaries.md §2 for the grade-boundary gap specifically). This document also does not re-print the ~40 individual trap descriptions the FORGE guide already indexes in full at §4.1 — duplicating them here would drift out of sync with that index the first time either document is next updated. Use §4's trap-name column to look them up in place instead.