Answer Validation Report

Rules applied: never treat marketing claims as fact; never manufacture consensus; preserve disagreements; a provider-supplied answer is "probable", not "verified", unless independently corroborated; no APM-published answer key exists publicly for any sample paper, so no answer in this corpus is labelled verified against an official key.

Answer status counts (148 raw occurrences)

What "probable" rests on

Independently corroborated answers (strongest evidence)

Question familyCorroboration
Thomas-Kilmann modesSP1 Q20 (current) + BoK7/QA Q12b + LO 11 syllabus
Risk management process orderSP2 Q29 (current) + BoK7/QA Q1a + LO 23
Resource smoothing vs levellingBoK7/QA Q7b + SP1 Q5 + LO 21d
Benefits management 5 stepsSP1 Q27 + SP2 Q27(b) + LO 9a
Configuration management stepsSP1 Q15 + BoK7/QA Q11a + LO 24
Projects vs BAU differencesBoK7/QA Q8a + Project Accelerator Q4 + LO 2

Long-response model marking points

answer_key.csv carries, for long-response questions with any answer treatment, a model marking-point summary (e.g. SP1 Q35 wind farm: 2 generic reasons + 3 scenario-specific reasons; SP1 Q7 business case: per-section contents). These are analyst/trainer-derived marking points, not APM examiner keys; each entry states its basis.

Explicitly NOT answered / flagged

Disagreements preserved

Where independent sources could disagree, no consensus was manufactured. The three disputed items above are the only places where the corpus found material ambiguity; if a downstream pass finds conflicting provider answers (e.g. a Scribd "model answers" document vs QA's), the disagreement should be added to 07_ANSWERS/disputed_answers.jsonl with both sides preserved.

Second pass update (2026-08-27)