PMI-CP common mistakes
PMI-CP · Understand the traps and how to avoid them.
When a scenario describes a contractor encountering differing site conditions, unexpected utility conflicts, or owner-caused delay, the candidate jumps straight to 'submit a claim for the additional cost and time' instead of selecting the step of giving formal written notice within the contract's stated notice period.
Candidates trained on generic project-management material think of claims as a documentation and cost-recovery exercise, so they pick the outcome they associate with 'getting made whole' rather than the contractual precondition that preserves entitlement.
What to do instead
For any question involving entitlement, delay, disruption, or extra work, first ask 'what does the contract require this party to do, and by when?' Look for the answer that preserves rights (notice, records, contemporaneous documentation) before any answer about money or time. Treat the time bar as a gate: no notice, no entitlement.
Candidate assumes the longest-duration activity or the path with the most activities is the critical path, and fails to re-run the forward and backward pass when a scenario states that a change consumed float or added a new activity.
The critical path is a computed result, not an intuition. Under time pressure, candidates substitute a visual shortcut ('the big activity must be critical') for the arithmetic, and they forget that float is a property of the whole path, not of a single activity.
What to do instead
Critical path = the continuous path with zero total float (or the least total float). Total float = LS - ES = LF - EF and is shared by all activities on that path. Whenever new information is given (added scope, revised duration, consumed float), recompute rather than reason from the original schedule, and check whether the critical path has moved to a different chain.
On a design-build, EPC, or turnkey project, the candidate assigns design responsibility and design-error risk to the owner because 'designers work for the owner' is the pattern they know from traditional design-bid-build.
Most candidates internalize one delivery model early and then apply its risk allocation to every scenario, even when the stem explicitly names a different delivery method with a single point of responsibility.
What to do instead
Before answering, write down the delivery method named in the stem and map three things to it: who designs, who holds the single point of responsibility, and who owns the interface risk between design and construction. In design-build/EPC the contractor carries design liability; in design-bid-build the owner retains it and bears the coordination gap; in CM at risk the CM holds the trade contracts and the GMP.
Candidate classifies insurance policies, surety bonds, and warranty-backed subcontracts as 'mitigation' or even 'avoidance' when asked to identify the risk response strategy being applied.
In everyday speech, buying insurance feels like reducing the danger, so the label 'mitigate' feels right. The formal taxonomy turns on where the financial consequence lands, not on how safe the team feels.
What to do instead
Memorize the response by mechanism, not by feel: transfer moves financial consequence to a third party (insurance, bonds, fixed-price subcontracts, warranties); mitigate reduces probability or impact on the project itself (redundant equipment, additional testing, early procurement); avoid eliminates the exposure by changing the plan or scope; accept retains it and funds it through contingency. If the project still absorbs the operational disruption and only the money moves, it is transfer.
Faced with a stakeholder who is blocking an approval or disputing site access, the candidate selects 'escalate to the sponsor or executive management' as the first and best action.
Escalation looks decisive and safe, so it becomes a default when the candidate cannot immediately see a technical solution. It also lets the candidate avoid the harder judgement of who actually holds influence over the blocker.
What to do instead
Escalation is a late-stage option, and usually a wrong answer when a constructive step remains available. Before escalating, expect the exam to reward: performing or updating the influence/interest analysis, meeting the stakeholder directly, adjusting the engagement approach, involving the party who has authority over the specific issue, or documenting the agreement. Choose escalation only when the stem shows the PM lacks authority and lower-level engagement has already failed.
When asked to identify stakeholders or plan engagement, the candidate lists only the contractual parties (owner, contractor, architect/engineer, subcontractors) and omits authorities having jurisdiction, utilities, adjacent property owners, community and interest groups, labor organizations, and lenders.
The construction industry's own language ('the parties') trains people to equate 'stakeholder' with 'signatory'. Candidates carry that habit into an exam where stakeholders are defined by impact and interest, not by contract privity.
What to do instead
Build the list by category rather than by contract: contractual parties, regulators and authorities having jurisdiction, utility and infrastructure providers, affected neighbours and community groups, financiers and insurers, and internal delivery functions. Then assess each for influence and interest. If an option names a non-contractual group that the stem shows is affected, it is very likely a correct answer, not a distractor.
The stem describes two bids with different capital cost, operating cost, maintenance burden, or schedule risk, and the candidate recommends award to the lowest-priced bidder.
Low-bid awarding is deeply embedded in public-sector construction culture and is the simplest comparison to make. Candidates also misread 'best value' questions as procurement-theory trivia rather than as a cost-comparison exercise.
What to do instead
Whenever the stem gives you differential operating, maintenance, energy, or schedule-risk data, the question is testing life-cycle or best-value evaluation. Compare total cost of ownership over the stated horizon, include the cost of the risk each bid carries, and pick the option that reflects evaluated best value. Choose lowest price only when the stem states the scope is fully specified, comparable, and price is the designated award criterion.
Candidate uses 'contingency' and 'management reserve' interchangeably, or states that the project manager may draw on management reserve to cover identified risks that have materialized.
Both are sums of money held for things that might happen, so the distinction feels academic. Candidates also blur 'identified risk' with 'unknown risk' and therefore blur which reserve applies.
What to do instead
Anchor on two questions: is the risk identified in the register, and whose baseline is affected? Contingency covers identified risks, sits inside the approved cost or schedule baseline, and is drawn by the project manager under defined authority. Management reserve covers unknown-unknowns, sits outside the baseline, and requires release by senior management or the owner. A related trap: an owner-held allowance or provisional sum in a contract is a commercial mechanism, not a PM reserve.
In a field scenario the candidate treats a verbal instruction, a site instruction, or a construction change directive as a fully priced and executed change order, or concludes that work must stop until a signed change order exists.
The candidate collapses several distinct instruments into one familiar term and does not distinguish which one authorizes work from which one settles price and time.
What to do instead
Separate the instruments by function: a change order is a signed, mutually agreed modification with price and time settled; a construction change directive (or equivalent) directs the work to proceed before agreement is reached, with price later determined by the contract's method; a field/site instruction typically conveys information and may need conversion into a formal change. On the exam, work directed under a change directive proceeds and is documented and priced afterwards, subject to notice requirements, rather than being refused.
Planning and sequencing questions are answered using generic phase order (initiate, plan, execute, monitor, close) without accounting for construction-specific constraints such as permitting and approvals, long-lead procurement, inspection and hold points, testing and commissioning, and the distinction between substantial completion and final completion.
Candidates revise process frameworks but not the physical and regulatory sequence of building, so they choose options that are logically tidy but impossible to execute in the stated order.
What to do instead
For any sequence question, ask what physically or legally must precede the activity: can the work be built before the permit or approval, before the long-lead item arrives, before the hold point is signed off, before the system is commissioned? Know that substantial completion triggers a defined set of consequences (owner use, warranty start, release of retention in part, liquidated damages stop) that differ from final completion, and expect questions to turn on that boundary.