Business Paper 2 — Managing Business Activities
Error Pattern Tracker
Provenance (written 2026-09-28): built primarily from research/veridian/WBS12-verified-facts.md
(read in full, 1,221 lines — 16 series June 2019–October 2024 text-extracted; 15 mark schemes; 13 of
15 examiner reports read in full, denominator stated per-claim below exactly as that file states it).
Two patterns not in the facts bank's own window are carried across from
forge-exam-technique-guide.md in this same folder (also read in full first), which independently
cites the January 2025 and June 2025 examiner reports directly — flagged inline wherever used, since
this document did not itself re-open those two PDFs. codex-definitions-and-application-bank.md and
signal-frequency-and-boundaries.md were also read in full to check for overlap; neither builds a
loggable template, so there is none to duplicate. content/veridian/question-bank/wbs12.ts was
checked too — its two real past questions (Sew Sew, Żabka) are both already cited as primary sources
in the facts bank and are referenced here under the same two categories they informed
(235-3, 232-1/DIS-1), not re-derived independently.
What this document adds that nothing else in this folder does: forge-exam-technique-guide.md §4
already lists this paper's 40 verified trap-taxonomy entries as a compact, static reference map. This
document does not restate any of those explanations — it turns the underlying confirmed patterns into
something a student logs their own timed-practice mistakes against, attempt by attempt, so the
patterns stop being a reference list someone reads once and start being a record of what a specific
student actually keeps doing. Where a pattern already has a named trap-taxonomy entry in a curriculum
file, its ID is given here as a cross-reference for the full mechanism-level explanation — that
explanation is not repeated.
Citation key: quotes under ~15 words, attributed inline, are the primary-source examiner report or
mark scheme's own wording, checked against WBS12-verified-facts.md's own verification of that PDF.
Anything longer is paraphrased. "Confirmed in N of M series reviewed" always uses the facts bank's own
stated denominator (13 examiner reports, Oct 2019–Oct 2024) unless a pattern is sourced to FORGE's
January/June 2025 addition, marked [FORGE] where that applies. No likelihood is stated for any
pattern beyond "seen in N of M series checked" — this paper has no grade-boundary or percentage data
attached to individual error types, and none is invented here.
WBS12 FORGE — Error Pattern Tracker
Managing Business Activities (Unit 2). A fillable log for timed-practice mistakes, pre-populated with this paper's own confirmed, primary-source-verified error patterns so you log your mistakes against real categories from the start, not invented ones.
How to use this
- After every timed practice question or paper, look at what you actually lost marks on. Find the
closest-matching category in the key below (Part 1 for command-word/technique mistakes, Part 2 for
topic-content confusions). If nothing matches, log it anyway under
OTHERwith your own short label — a real gap this document doesn't have evidence for yet is still worth tracking. - Add one row to the log in Part 3 for each mistake, using the next free row number. The pre-filled
SEEDrows above the blank ones are not your mistakes — they show Pearson's own confirmed version of that category, so you know what you're matching against. Leave them in place; add your own rows below them. - Every few papers, tally Part 4. A category with three or more of your own entries is a genuine, personal recurring weakness — not a guess, a count from your own log — and belongs at the top of your next revision session.
- When you run out of blank rows, copy the table header and keep going. This is a template, not a fixed-length form.
Part 1 — Technique / command-word categories
These are mistakes in how you answer a given tariff, independent of topic. Full mechanism-level explanations for the ones with a trap-taxonomy ID live in their named curriculum file; this table only gives the one-line identifying cue and the confirmed source.
| Code | Category | Confirmed source |
|---|---|---|
DEF-1 | Define (2): extract reference given, earns zero | Examiner reports, near-identically worded from Oct 2020 onward |
DEF-2 | Define (2): only one of the two required components given, or an example substituted for it | June 2023 (franchising); Jan 2022 (social enterprise) |
CALC-1 | Calculate (4): unit/% sign missing or wrong, caps the mark below full | Confirmed in every series with a Calculate question reviewed, June 2019–Oct 2024 |
CALC-2 | Calculate (4): total figure asked for, per-unit (or vice versa) given | Oct 2022, Q2(b) |
EXP-1 | Explain (4): knowledge point stated with no direction of change | Jan 2023, Q1(b) |
ANA-1 | Analyse (6): tried to apply or analyse the definition itself | 7 of 13 examiner reports reviewed (Oct 2019, Jan 2020, Oct 2020, Jan 2021, Oct 2021, Jan 2022, Oct 2022) |
ANA-2 | Analyse (6): one reason developed twice, not two genuinely distinct reasons | General AO-structure rule, confirmed across every series' AO breakdown |
APP-1 | Application (any tariff): extract quoted or copied standalone, not built into reasoning | Near-verbatim in all 13 examiner reports reviewed; explicit in Oct 2022 and Jan 2023 |
DIS-1 | Discuss (8): one-sided only, or an unrewarded conclusion added where none is required | Confirmed in 10 of 13 reports reviewed; independently restated June 2023 (Żabka) and Oct 2023 (Arditi Tours) |
ASS-1 | Assess (10): no stated, reasoned judgement by the end | Derived from the paper's own Level 4 descriptor, not a specific candidate-error quote — see seed row |
EVAL-1 | Evaluate (20): no stated recommendation/solution by the end | Derived from the paper's own Level 4 descriptor — see seed row |
GEN-1 | A memorised list of advantages/disadvantages applied without checking it fits the actual business in the extract | Oct 2022 (plc-type advantages given to a business that had only just become Ltd); Oct 2022 Q1(e), ASV |
VAR-1 | An external economic variable (2.3.5.1) confused with something the business itself decided | January 2025 examiner report, Q1(c) [FORGE] |
Part 2 — Content-confusion categories, by spec section
Topic-specific misunderstandings — the content was wrong or muddled, not just the technique.
2.3.1 Planning a business and raising finance
| Code | Category | Confirmed source |
|---|---|---|
231-1 | Leasing's meaning not understood at all | Oct 2019, Q3 |
2.3.2 Financial planning
| Code | Category | Confirmed source |
|---|---|---|
232-1 | Sales forecasting confused with market research | Oct 2019, Q2(c) |
232-2 | Inflation assumed automatically "good" for a business | Jan 2020, Q2(d) |
232-3 | Margin of safety: an averaged/whole-period figure treated as if it applies to every component, hiding one already running below break-even | Oct 2023, Q1(d) — Arditi Tours |
2.3.3 Managing finance
| Code | Category | Confirmed source |
|---|---|---|
233-1 | Profit confused with profitability | Jan 2020, Q2(e) |
233-2 | A liquidity ratio judged in isolation, with no comparator (prior year, or a similar business) | Jan 2023, Q3 — AvN |
233-3 | Acid test ratio: intangible assets wrongly included in current assets | Oct 2021 mark scheme |
233-4 | Raising price to raise profit, without assessing the PED-driven demand-fall risk | Oct 2022, Q2(e) |
233-5 | More marketing spend assumed automatically to mean more profit, ignoring that the spend is itself a cost | Oct 2022, Q2(e) — Dapaah Chocolates |
233-6 | Factoring — meaning not understood, guessed at | Oct 2024, Q3 |
233-7 | A below-"ideal-range" liquidity ratio treated as an automatic crisis, regardless of the business's own inventory/payment cycle | Jan 2023, Q3 — AvN (a nuance in the model answer, not a quoted candidate error — see seed row) |
2.3.4 Resource management
| Code | Category | Confirmed source |
|---|---|---|
234-1 | Total Quality Management mistaken for "quality" in a general sense | Oct 2020, Q1(d) |
234-2 | Quality circles confused with quality assurance or quality control | June 2022, Q1(d) |
234-3 | Quality assurance confused with quality control | Oct 2021, Q3 |
234-4 | Waste-minimisation/give-away strategies assumed to carry no cost to the business | Oct 2024, Q2(d) |
234-5 | Short lead-in times (or quality management) discussed without linking either back to competitive advantage | Jan 2024, Q3 — Freewing |
2.3.5 External influences
| Code | Category | Confirmed source |
|---|---|---|
235-1 | Business cycle confused with the product life cycle | Jan 2023, Q2(c) |
235-2 | Currency appreciation and depreciation effects reversed | June 2023, Q2(d) — Wilson |
235-3 | Legislative duties (e.g. health & safety) assumed to apply uniformly, regardless of business size/employee count | Jan 2021, Q2(d) — Sew Sew |
235-4 | Copyright protection over-estimated — assumed unlimited in time, or assumed to protect the underlying concept, not just its specific expression | June 2022, Q2(d) — Cruise & Go |
235-5 | An interest-rate "customer disposable income" channel assumed to apply even to customers who aren't exposed to that rate | Oct 2020, Q1(e) — Lotus Garments Co. |
(2.3.4 quality-management note, not a separate row: 234-1–234-3 together are the single strongest
repeated pattern in the whole archive — three independent series confirm candidates confusing these
terms with each other: Oct 2020 (TQM vs quality generally), Oct 2021 (QA vs QC), June 2022 (quality
circles vs QA/QC). If you log two or more entries across these three codes, treat it as one
underlying weak spot — a single side-by-side re-read of control/assurance/circles/TQM, not three
separate revision sessions.)
Part 3 — The log
SEED rows are Pearson's own confirmed pattern for that category, quoted or closely paraphrased with
its source — not your mistake. Add your own rows below them, numbered onward. "Root cause" is your own
one-word-or-phrase diagnosis: term confusion, misread the ask, missing mechanic, technique/AO structure, over-generalised a rule, or your own label.
| # | Code | Series / date (SEED = source paper) | What went wrong | What was actually needed | Root cause | Fixed next time? |
|---|---|---|---|---|---|---|
| S1 | DEF-1 | SEED — Oct 2020 onward | Definition answer built around a detail from the extract | "reference to information in the extract(s) is not required" — extract references earn zero on Define | term confusion | — |
| S2 | DEF-2 | SEED — June 2023 | "Franchising" defined as one vague idea ("expanding," "selling on its behalf") | Vague references to "expanding" or "selling products on its behalf" were explicitly not accepted — needs both parts: franchisor allows franchisee to trade under its name | missing mechanic | — |
| S3 | CALC-1 | SEED — June 2019, Q1(b) | 41.7% given with no working, or 41.67 with no % sign | Real graduated penalty on this exact question: 41.67% → 4/4; 41.7% (rounded) → 3/4; 41.67 with no % → 3/4; 41.7 with no % → 2/4 | technique/AO structure | — |
| S4 | CALC-2 | SEED — Oct 2022, Q2(b) | Variable cost calculated per unit | Question asked for total variable cost per month | misread the ask | — |
| S5 | EXP-1 | SEED — Jan 2023, Q1(b) | "The break-even point would be affected" | "it was necessary to say it would increase" — a stated direction, not just an assertion of change | technique/AO structure | — |
| S6 | ANA-1 | SEED — 7 of 13 reports | Definition of a term written out, then "applied" | "it is not possible to apply or analyse the definition" — the two knowledge marks must be two distinct, applicable points | technique/AO structure | — |
| S7 | APP-1 | SEED — 13 of 13 reports (general); Jan 2020 Q3 (extreme case) | A sentence from the extract copied in as if that were application | "Application marks will not be awarded for simply repeating evidence in the extracts"; Jan 2020 Q3 candidates who "copied much of it" scored very low | technique/AO structure | — |
| S8 | DIS-1 | SEED — 10 of 13 reports; independently restated June 2023 (Żabka) and Oct 2023 (Arditi Tours) | A conclusion written for an 8-mark Discuss; or only one side argued | "A conclusion is not required for an 8 mark discuss question"; "The command word 'discuss' requires a two-sided argument" | technique/AO structure | — |
| S9 | ASS-1 | SEED — mark scheme, Level 4 descriptor | Two sides given, no final judgement stated | Level 4 (8–10) requires "...leading to a supported judgement" | technique/AO structure | — |
| S10 | EVAL-1 | SEED — mark scheme, Level 4 descriptor | Both sides weighed, essay ends without a recommendation | Level 4 (15–20) requires "an effective conclusion that proposes a solution and/or recommendations" | technique/AO structure | — |
| S11 | GEN-1 | SEED — Oct 2022, Q1(e) — ASV | Public-company advantages (raising large capital internationally) given to a business that had only just become a private Ltd | "it is unlikely he would have grown to become a leading business internationally" — check which advantages actually fit this business, not the form's memorised full list | over-generalised a rule | — |
| S12 | VAR-1 | SEED — Jan 2025, Q1(c) [FORGE] | Something the business itself decided (a pricing or staffing choice) named as an economic variable | 2.3.5.1's five variables are specifically the ones set outside the business — inflation, exchange rates, interest rates, taxation/government spending, the business cycle | term confusion | — |
| S13 | 231-1 | SEED — Oct 2019, Q3 | Leasing's meaning not known | Access to higher levels blocked on a 20-mark loans-vs-leasing question without knowing what leasing is | missing mechanic | — |
| S14 | 232-1 | SEED — Oct 2019, Q2(c) | Sales forecasting written about as if it were market research | "Sometimes candidates confused market research for sales forecasting" | term confusion | — |
| S15 | 232-2 | SEED — Jan 2020, Q2(d) | Inflation assumed to simply help a business — "they could make more profit" | Inflation raises a business's own costs, and can squeeze customers' real spending — not an automatic gain | over-generalised a rule | — |
| S16 | 232-3 | SEED — Oct 2023, Q1(d), Arditi Tours | Whole-day margin of safety (8 passengers, from a 76 total vs. a 68 break-even total) read as safe across the board | Two of the four individual services (15 and 11 passengers against a 17 break-even) were separately running at a loss | over-generalised a rule | — |
| S17 | 233-1 | SEED — Jan 2020, Q2(e) | Methods to raise more profit given, for a "profitability" question | "do not know the difference between profit and profitability" — profitability is a margin, not an absolute amount | term confusion | — |
| S18 | 233-2 | SEED — Jan 2023, Q3, AvN | A liquidity ratio stated and left to speak for itself | "lacked understanding of liquidity and working capital" — higher marks needed a stated comparator (a prior year, or a similar business) | missing mechanic | — |
| S19 | 233-3 | SEED — Oct 2021 mark scheme | Acid test ratio calculated with intangible assets left in current assets | "mistakenly including intangible assets in the calculation" — acid test excludes inventory (and, per this note, is not the place for intangibles either) | missing mechanic | — |
| S20 | 233-4 | SEED — Oct 2022, Q2(e) | A price rise proposed to increase profit, with no demand-side caveat | "failed to assess how this may deter many and reduce demand" — a price rise can lower profit if demand is elastic | missing mechanic | — |
| S21 | 233-5 | SEED — Oct 2022, Q2(e), Dapaah Chocolates | More advertising spend treated as a pure profit gain | Advertising only raises profit if the resulting revenue gain exceeds what the advertising itself costs | over-generalised a rule | — |
| S22 | 233-6 | SEED — Oct 2024, Q3 | Factoring skipped, or guessed at | "lacked understanding of factoring" — candidates ignored that part of the question rather than risk a wrong guess | missing mechanic | — |
| S23 | 233-7 | SEED — Jan 2023, Q3, AvN (mark scheme nuance, not a quoted error) | A ratio below the rough 1.5:1–2:1 current / 1:1 acid-test benchmark assumed automatically unsafe | Fast inventory turnover (e.g. clothing manufacturers) can make a below-range ratio genuinely fine — always compare, don't just check against the benchmark alone | over-generalised a rule | — |
| S24 | 234-1 | SEED — Oct 2020, Q1(d) | TQM answered as "quality" in general terms | "did not understand its meaning" — TQM is a specific, named system, not a synonym for caring about quality | term confusion | — |
| S25 | 234-2 | SEED — June 2022, Q1(d) | Quality circles described as if they were quality assurance/control | "confused quality circles with quality assurance or quality control" | term confusion | — |
| S26 | 234-3 | SEED — Oct 2021, Q3 | Quality assurance and quality control used interchangeably | "lacked understanding of either quality assurance or quality control" | term confusion | — |
| S27 | 234-4 | SEED — Oct 2024, Q2(d) | Giving away food before its use-by date assumed to have no downside | "no negative implications for the business" was the wrong assumption — waste minimisation still carries a real cost | over-generalised a rule | — |
| S28 | 234-5 | SEED — Jan 2024, Q3, Freewing | Lead-in times and quality management each discussed on their own | "lacked understanding of short product lead-in times" — and where they were discussed, not tied back to the actual question, competitive advantage | missing mechanic | — |
| S29 | 235-1 | SEED — Jan 2023, Q2(c) | Business cycle question answered with product life cycle content | Examiner report (verbatim, as printed — see note below): "no understanding of a business plan, instead making reference to a product life cycle" | term confusion | — |
| S30 | 235-2 | SEED — June 2023, Q2(d), Wilson | Currency appreciation and depreciation effects mixed up | "some were confused about the effects of a currency depreciation" — question was actually about the Thai baht's appreciation | term confusion | — |
| S31 | 235-3 | SEED — Jan 2021, Q2(d), Sew Sew | A sole trader with no staff assumed to carry the same legal duties as a large employer | "does not need to comply with health and safety legislation" — until the business actually takes on employees | over-generalised a rule | — |
| S32 | 235-4 | SEED — June 2022, Q2(d), Cruise & Go | Copyright assumed to be permanent and to cover the underlying idea, not just its specific form | "copyright is usually only given for a limited time"; "does not protect the concept itself" | over-generalised a rule | — |
| S33 | 235-5 | SEED — Oct 2020, Q1(e), Lotus Garments Co. | An interest-rate change assumed to hit customer demand for every business, regardless of who its customers are | "the customers would not be affected by the Egyptian interest rate" — Lotus Garments Co. exports most of its output, so its export customers aren't exposed to the Egyptian rate at all | over-generalised a rule | — |
| 1 | ||||||
| 2 | ||||||
| 3 | ||||||
| 4 | ||||||
| 5 | ||||||
| 6 | ||||||
| 7 | ||||||
| 8 | ||||||
| 9 | ||||||
| 10 | ||||||
| 11 | ||||||
| 12 | ||||||
| 13 | ||||||
| 14 | ||||||
| 15 |
Note on S29's quote: this is presented exactly as the primary-source examiner report states it, per
WBS12-verified-facts.md's own flag — the question itself is entirely about the business cycle, so
"business plan" in the source is very likely a Pearson-side typo for "business cycle." It is quoted
verbatim rather than silently "corrected," because an earlier, unrelated document in this course's own
research history quietly changed this exact word and presented the result as a direct quotation —
exactly the error this course's sourcing discipline exists to prevent.
Note on S30: the same appreciation/depreciation confusion was, in an earlier draft of this course's
material, wrongly attributed to June 2022 as well as June 2023. Re-checked directly against both
primary sources: June 2022's own Q2(d) is a copyright question (Cruise & Go, the source for 235-4
above) with zero exchange-rate content anywhere in its examiner report. Only June 2023 (Wilson) is a
confirmed instance of this pattern — logged here as one series, not two.
Part 4 — Your tally
Fill this in after every few practice papers by counting your own numbered rows in Part 3 (not the
SEED rows) against each code. Leave a category blank until you've actually logged something against
it — an empty cell here means "not yet tracked," not "not a risk."
| Code | Times logged | Code | Times logged | Code | Times logged |
|---|---|---|---|---|---|
DEF-1 | 233-2 | 234-3 | |||
DEF-2 | 233-3 | 234-4 | |||
CALC-1 | 233-4 | 234-5 | |||
CALC-2 | 233-5 | 235-1 | |||
EXP-1 | 233-6 | 235-2 | |||
ANA-1 | 233-7 | 235-3 | |||
ANA-2 | 231-1 | 235-4 | |||
APP-1 | 232-1 | 235-5 | |||
DIS-1 | 232-2 | GEN-1 | |||
ASS-1 | 232-3 | VAR-1 | |||
EVAL-1 | 234-1 | OTHER | |||
233-1 | 234-2 |
Reading this table honestly: three or more entries against one code, from your own timed practice,
is a real personal pattern — go re-read that code's full mechanism in its cited lesson file (via the
trap-taxonomy cross-reference in forge-exam-technique-guide.md §4, where one exists) before your next
paper. One or two entries against many different codes is normal variance, not yet a pattern worth a
dedicated session. This document does not, and cannot, tell you which of your own future mistakes will
matter most — only your own filled-in count can do that.
Sources
research/veridian/WBS12-verified-facts.md (16 series June 2019–October 2024; 15 mark schemes; 13 of
15 examiner reports read in full — June 2019 and June 2024 reports unreadable, noted inline in that
file). content/veridian/technique-hub/wbs12/forge-exam-technique-guide.md §4, for the two
January/June 2025 additions marked [FORGE] above, which that document cites directly to those two
examiner reports. Real per-question figures (the June 2019 Q1(b) penalty table; the Arditi Tours
passenger counts) are reproduced from those same verified sources as numeric data, not exam-board
prose. No content in this document was carried over from the old, pre-audit Veridian build — three
confirmed misquotations and one wrong set of mark boundaries were found in that material during the
facts-bank pass and are documented in that file's own "Errors found in old material" section; none of
that material was reused here.