CPSP common mistakes
CPSP · Understand the traps and how to avoid them.
Treating 'supply management' as a synonym for procurement/tactical buying and answering questions about internal stakeholder needs, specification development, or make-vs-buy from a pure purchasing-transaction lens.
Candidates with buying or expediting backgrounds map every scenario onto purchase-order mechanics and miss that the Supply Management Core domain tests the broader management discipline (needs identification, specification, total cost of ownership, internal customer alignment).
What to do instead
Before answering, classify the scenario: is the question about defining the need and specification, about market engagement, or about transaction execution? Build a one-page map of the supply management process steps and rehearse placing 15 sample scenarios onto that map until the classification is automatic.
Choosing the 'best price' or 'lowest bid' option in sourcing scenarios that explicitly mention lifecycle costs, switching costs, or risk exposure, instead of applying total cost of ownership and weighted evaluation criteria.
Price is the most visible and quantifiable number in the stem, and candidates under time pressure anchor on it rather than reconstructing the evaluation model the question implies.
What to do instead
When a stem contains any cost beyond unit price (freight, tooling, warranty, disposal, downtime, transition), force yourself to list at least three cost elements before looking at options. Practise converting a price-only comparison into a TCO comparison for three categories you know well.
Confusing category management with sourcing events: answering strategy, segmentation, or category plan questions with a tender/RFQ process description.
Sourcing is the most familiar and concrete activity, so candidates default to it whenever a question mentions suppliers or spend, even when the question asks about segmentation, demand levers, or multi-year category strategy.
What to do instead
Memorise the distinction explicitly: category management decides what to do with a spend pool over time (segmentation, demand management, supply base design, value levers); sourcing executes a market engagement. For each practice question, write one line naming which of the two the stem is asking about before selecting an answer.
Treating negotiation as a single distributive haggling event and picking the option that 'holds firm' or 'anchors aggressively' in integrative, multi-issue, or long-term relationship scenarios.
Many candidates' real-world negotiation experience is price haggling, so they import a win-lose frame into questions about interests, tradeables, and joint value creation.
What to do instead
Drill the interest-versus-position distinction and the concept of trading across issues of differing value to each side. In every negotiation stem, identify each party's underlying interest and at least two non-price variables (volume, payment terms, lead time, specification, risk allocation) before evaluating options.
Selecting contract types or clauses by name recognition rather than by risk allocation: for example choosing fixed-price for a poorly specified, high-uncertainty scope, or missing which party bears a described risk.
Candidates memorise contract labels without the underlying logic of who carries cost and performance risk, so they cannot transfer the concept to a scenario that describes uncertainty, volume swings, or performance incentives.
What to do instead
Build a two-column table for each contract form (fixed price, cost-plus, time and materials, incentive, framework) listing who bears cost risk, who bears performance risk, and when it fits. Answer contract questions by first naming the dominant uncertainty in the stem, then matching the form that puts that uncertainty on the party best able to manage it.
Reducing supplier relationship management to supplier performance scorecards and treating segmentation, governance cadence, joint improvement, and escalation design as interchangeable.
Scorecards are the most tangible SRM artefact, so candidates reach for them even when the question is about which relationship model fits a strategic supplier, how to structure governance, or how to handle a relationship that has become transactional.
What to do instead
Learn an explicit segmentation logic (strategic, collaborative, transactional, and where relevant bottleneck or leverage) with the governance and engagement each implies. For SRM questions, first assign the supplier to a segment from the stem's evidence, then select the governance or development action consistent with that segment.
Treating risk management as risk identification only, and failing to distinguish likelihood from impact, mitigation from contingency, or single-supplier dependency from general market risk.
Risk registers are usually presented as lists, so candidates learn to spot risk names but not to reason about exposure, residual risk, or which response (avoid, reduce, transfer, accept) fits a described situation.
What to do instead
Practise a two-step method on every risk stem: (1) name the specific exposure and whether the question is about probability, consequence, or response; (2) choose the response type that matches the described capability and cost. Separately rehearse mapping tools (dependency analysis, multi-tier visibility, dual sourcing, buffer strategy) to the risk they actually address.
Answering sustainability and ethics questions with aspirational statements ('commit to net zero', 'engage suppliers on ESG') instead of the concrete mechanism the scenario requires, such as due diligence, traceability, audit rights, code-of-conduct enforcement, or conflict-of-interest handling.
Sustainability language is familiar and sounds correct, so candidates pick the option with the most virtuous wording rather than the one that creates an enforceable control or a defensible ethical decision.
What to do instead
For each sustainability or ethics stem, ask 'what makes this verifiable or enforceable?' and prefer options that create evidence, contractual obligation, or a documented decision process. Study the difference between supplier codes, audits, certifications, and traceability systems, and which one addresses which failure mode.
Treating analytics tools as answers: choosing 'implement a dashboard', 'use AI for forecasting', or 'adopt a spend analytics platform' when the question is about data quality, master data, measurement design, or interpreting a described metric.
Tool familiarity and vendor messaging create a bias toward technology solutions, and candidates skip the diagnostic step of asking whether the underlying data, definitions, or process can support the tool.
What to do instead
Adopt a fixed sequence for technology and analytics questions: what decision is being made, what data is required, is that data available and clean, what metric or model applies, and only then what tool. Practise identifying data-quality and definition problems (duplicate supplier records, inconsistent units, missing lead times) as the root cause in scenario stems.
Ignoring the stem's constraints and selecting the textbook-ideal option that the scenario has ruled out (for example recommending competitive tender when the stem states sole-source, single-source, emergency, or long-qualification conditions).
Candidates pattern-match on keywords to remembered best practice and skip the qualifiers that define the actual decision space, which is exactly where exam writers place discriminating detail.
What to do instead
Before evaluating options, underline every constraint in the stem (time, capacity, regulation, existing contract, capability, budget) and eliminate any option that violates one, even if it is otherwise best practice. Then choose among the remaining feasible options and confirm your choice respects each underlined constraint.