PDCA CPC common mistakes
PDCA CPC · Understand the traps and how to avoid them.
Treating the exam as a generic project-management test and answering scheduling questions with textbook critical-path logic instead of the contract's specified schedule requirements, float ownership, and time-extension entitlement rules.
Candidates with PMP-style backgrounds assume universal best practice and skim the scenario's contract clauses, missing that the exam tests how the specified contract allocates risk and time.
What to do instead
Before answering any scheduling item, identify who owns float, what the contract says about delays and extensions, and whether the scenario involves excusable, compensable, or concurrent delay; build a one-page decision tree mapping each delay type to notice, entitlement, and documentation requirements, and drill it against past scenario stems.
Computing bid prices or change-order values without adding the correct markups in the correct order - omitting overhead, contingency, bond, and profit, or applying them to the wrong base.
Candidates memorize formulas but not the sequence, and under exam time pressure they apply a single multiplier to direct cost instead of building the price up layer by layer.
What to do instead
Practice a fixed buildup sequence: direct cost, then field/general conditions, then home-office overhead, then contingency, then bonds and insurance on the marked-up subtotal, then profit; write the sequence on scratch paper at the start of the exam and reconcile each answer against it.
Confusing the roles and authority of the owner, architect/engineer, construction manager, and contractor when answering contract-administration questions, attributing inspection authority or directive power to the wrong party.
Real-world titles vary by project and candidates import their own employer's organizational chart rather than the standard AIA or EJCDC allocation assumed by the exam.
What to do instead
Build a comparison table of the standard delivery models and contract forms listing who issues instructions, who certifies payment, who approves substitutions, and who bears design responsibility; answer role questions by first naming the delivery model in the stem.
Reading a specification or drawing-interpretation scenario for the general intent and selecting the 'reasonable' answer instead of applying the order of precedence and the strict language of the document.
Practitioners are used to resolving conflicts informally in the field and underestimate how literally the exam tests precedence clauses, 'shall' versus 'should', and the contractor's duty to report discrepancies.
What to do instead
For every documents question, first state the order-of-precedence hierarchy in the stem, then locate the specific conflicting clause; practice items that hinge on a single word such as 'shall', 'or equal', or 'as directed by the engineer'.
Answering safety items with the control that would have prevented the incident in hindsight rather than the control the standard requires at that step of the hierarchy of controls or the specific regulatory trigger.
Candidates reason from experience and pick the most effective engineering control even when the question asks what the competent person must do first, or what notification threshold applies.
What to do instead
Memorize the hierarchy of controls order and the specific numeric and procedural triggers (inspection intervals, competent-person duties, recordkeeping, reporting timelines) as discrete facts; for each scenario, ask what the regulation requires now, not what would be ideal.
Choosing the ethically 'nice' answer on professional-practice and ethics items instead of the one that follows the licensing law, the duty to report, and the obligation to notify the client in writing.
Candidates conflate general business ethics with the specific professional obligations of an architect or engineer, and they avoid answers that seem confrontational or that escalate to an authority.
What to do instead
Learn the standard sequence for ethical dilemmas: document, notify the responsible party in writing, decline to certify noncompliant work, escalate to the licensing board only where required; practice distinguishing confidentiality duties from mandatory reporting duties.
Skipping the computation on estimating and cost-control items and guessing from the answer choices, or making arithmetic errors because units and waste factors are not converted consistently.
Time pressure and discomfort with quantity takeoff math lead candidates to pattern-match numbers rather than calculate, and mixed units (cubic yards versus cubic feet, tons versus pounds) cause silent errors.
What to do instead
Do the arithmetic on paper with units written at every step, and sanity-check magnitude before selecting; drill takeoff problems with waste and compaction factors until unit conversion becomes automatic.
Treating leadership and communication items as personality questions and picking the most agreeable or most decisive option rather than the behavior that matches the situational-leadership or team-development principle being tested.
Candidates answer from personal style and miss the underlying construct - delegation versus direction, task versus relationship behavior, or the correct escalation path for a performance problem.
What to do instead
Study the named frameworks the exam draws on (situational leadership, team stages, conflict modes, communication models) and for each practice item identify which construct is being tested before reading the options; prefer answers that gather information and address the person directly over those that escalate or avoid.
Answering pre-construction planning items as if the project were already underway, selecting execution-phase actions when the question concerns constructability review, permitting, or procurement strategy.
The pre-construction domain overlaps heavily with field operations, and candidates default to the action they would take on site rather than the action appropriate before mobilization.
What to do instead
Tag every scenario with its project phase before evaluating options; build a phase-by-phase checklist of deliverables and decision gates from programming through mobilization and eliminate any option that belongs to a later phase.
Ignoring quality-control specifics - inspection and test plan requirements, hold points, first-work verification, and nonconformance disposition - and answering with general 'check the work' language.
Candidates treat QC as common sense and do not memorize the formal mechanics of ITPs, witness points, and rework versus accept-by-concession decisions that the exam tests precisely.
What to do instead
Learn the QC document set and the disposition options for nonconforming work, including who has authority to accept, reject, or require rework; practice scenario items that require choosing the correct hold point or the correct party to approve a deviation.