PMI Construction Professional (PMI-CP)™ Ultimate Cheat Sheet
Your Quick Reference Study Guide
This cheat sheet covers the core concepts, terms, and definitions you need to know for the PMI Construction Professional (PMI-CP)™. We've distilled the most important domains, topics, and critical details to help your exam preparation.
💡 Note: While this study guide highlights essential concepts, it's designed to complement—not replace—comprehensiv e learning materials. Use it for quick reviews, last-minute prep, or to identify areas that need deeper study before your exam.
About This Cheat Sheet: This study guide covers core concepts for PMI Construction Professional (PMI-CP)™. It highlights key terms, definitions, common mistakes, and frequently confused topics to support your exam preparation.
Use this as a quick reference alongside comprehensive study materials.
PMI Construction Professional (PMI-CP)™
Cheat Sheet •
About This Cheat Sheet: This study guide covers core concepts for PMI Construction Professional (PMI-CP)™. It highlights key terms, definitions, common mistakes, and frequently confused topics to support your exam preparation.
Use this as a quick reference alongside comprehensive study materials.
Contracts Management
50%Change-Order Control & Audit Trail
Auditable workflow to capture, evaluate, approve and close contract changes; update risk, contingency and baselines.
Key Insight
Every change order must trigger risk-register updates, contingency recalculation and baseline amendments; verbal sign-offs fail audits.
Often Confused With
Common Mistakes
- Accepting verbal or informal approvals as sufficient
- Skipping risk/contingency updates for 'minor' changes
- Assuming contingency must be spent before seeking a contract amendment
Contract Form & Delivery: Claims Drivers
How contract form, clauses and delivery model allocate risk and incentives—shaping who claims and how price/schedule are
Key Insight
Risk allocation sets incentives: aggressive transfer raises price or disputes; single-source reduces but doesn't eliminate claim triggers.
Often Confused With
Common Mistakes
- Assuming shifting all risk to the contractor prevents claims
- Believing lump-sum always yields the lowest price
- Thinking design‑build automatically eliminates claims
Risk Register — Living Risk Log
A living project record of threats and opportunities with owners, triggers, responses, and status for governance.
Key Insight
Must be updated and tracked: capture both threats and opportunities, assign owners/triggers, log responses and residuals.
Often Confused With
Common Mistakes
- Treating the register as a one‑time checklist created at kickoff.
- Logging only negative risks and ignoring opportunities.
- Assuming an entry equals 'managed'—no ongoing monitoring or acceptance recorded.
Probabilistic Risk Techniques (Monte Carlo, EMV)
Statistical methods (Monte Carlo, EMV, sensitivity) that quantify uncertainty as probability distributions for cost/s/
Key Insight
Generates probability ranges, not exact forecasts — results depend on quality of input estimates and expert judgment.
Often Confused With
Common Mistakes
- Expecting a single 'correct' number instead of outcome distributions.
- Dropping expert judgment—simulations don't replace qualitative insight.
- Trusting outputs when input estimates/distributions are poor (garbage in, garbage out).
Change Orders vs Claims — Entitlement First
Determine contractual entitlement (notice, causation, breach) before measuring remedy; variations often bypass claims.
Key Insight
Entitlement is the legal gate (strict notice + causation + breach); quantum and pricing come after and follow clause wording.
Often Confused With
Common Mistakes
- Relying on late or informal notices despite strict contract notice requirements
- Equating proof of causation with establishing the amount payable
- Treating every scope change as a claim instead of a processed variation/change order
Claims Lifecycle — Early Resolution Triggers
Use early notice, productive site meetings, contemporaneous records and staged negotiation to resolve claims before they
Key Insight
Early documented actions (notice + contemporaneous records + focused site meetings) preserve settlement leverage; negotiation ≠ admission.
Often Confused With
Common Mistakes
- Treating early negotiations as admissions of liability
- Waiting for a fully developed formal claim before attempting early settlement
- Skimping on contemporaneous records and losing bargaining leverage
Claims: Notice & Condition‑Precedent
Contract clause requiring timely, formal written notice and required proof before a claim can be decided or remedied.
Key Insight
A technically compliant notice preserves entitlement; late/defective notice usually bars relief even if loss is later proven.
Often Confused With
Common Mistakes
- Assuming a casual email or verbal remark satisfies the contract's formal notice.
- Believing late submission of supporting evidence cures a late or defective notice.
- Thinking commercial talks or interim relief waive strict notice or deadline rules.
Design‑Bid‑Build (DBB) — Split Contracts
Traditional delivery: owner completes design, then competitively bids a separate construction contract; design and build
Key Insight
Design and construction responsibilities are split: owner retains design risk and change exposure; contractor bears means/methods and construction‑phs
Often Confused With
Common Mistakes
- Assuming DBB guarantees final cost certainty once bids are received.
- Expecting the designer to control construction means and methods during build.
- Treating DBB as a single‑point responsibility model for both design and construction.
Latent Site Conditions (Differing Site Conditions)
Unforeseen physical site conditions (subsurface, contamination, utilities) that can change entitlement to time/cost at a
Key Insight
A DSC claim needs a material, unforeseeable difference from the contract baseline plus strict compliance with notice/claim clauses.
Often Confused With
Common Mistakes
- Not only geotechnical—includes contamination, unknown utilities and existing works.
- Surprise ≠ claim; must materially differ from contract baseline and be unforeseeable.
- Discovery doesn't remove the need to follow formal notice/claim procedures.
Delay & Extension of Time (incl. Concurrent Delay)
Analyse schedule impacts across packages, prove critical‑path causation, and establish entitlement to EOT/relief.
Key Insight
EOT entitlement rests on causal impact to the critical path plus compliant notice; concurrent delays need apportionment, not automatic cancelation.
Often Confused With
Common Mistakes
- Granting an EOT doesn't automatically waive the employer's right to liquidated damages.
- Ignoring cross‑package dependencies — local critical path alone can miss entitlement impacts.
- Assuming concurrent delays always cancel claims; you must analyse causation and criticality.
Change-Order Control & Audit Trail
Auditable workflow to capture, evaluate, approve and close contract changes; update risk, contingency and baselines.
Key Insight
Every change order must trigger risk-register updates, contingency recalculation and baseline amendments; verbal sign-offs fail audits.
Often Confused With
Common Mistakes
- Accepting verbal or informal approvals as sufficient
- Skipping risk/contingency updates for 'minor' changes
- Assuming contingency must be spent before seeking a contract amendment
Contract Form & Delivery: Claims Drivers
How contract form, clauses and delivery model allocate risk and incentives—shaping who claims and how price/schedule are
Key Insight
Risk allocation sets incentives: aggressive transfer raises price or disputes; single-source reduces but doesn't eliminate claim triggers.
Often Confused With
Common Mistakes
- Assuming shifting all risk to the contractor prevents claims
- Believing lump-sum always yields the lowest price
- Thinking design‑build automatically eliminates claims
Risk Register — Living Risk Log
A living project record of threats and opportunities with owners, triggers, responses, and status for governance.
Key Insight
Must be updated and tracked: capture both threats and opportunities, assign owners/triggers, log responses and residuals.
Often Confused With
Common Mistakes
- Treating the register as a one‑time checklist created at kickoff.
- Logging only negative risks and ignoring opportunities.
- Assuming an entry equals 'managed'—no ongoing monitoring or acceptance recorded.
Probabilistic Risk Techniques (Monte Carlo, EMV)
Statistical methods (Monte Carlo, EMV, sensitivity) that quantify uncertainty as probability distributions for cost/s/
Key Insight
Generates probability ranges, not exact forecasts — results depend on quality of input estimates and expert judgment.
Often Confused With
Common Mistakes
- Expecting a single 'correct' number instead of outcome distributions.
- Dropping expert judgment—simulations don't replace qualitative insight.
- Trusting outputs when input estimates/distributions are poor (garbage in, garbage out).
Change Orders vs Claims — Entitlement First
Determine contractual entitlement (notice, causation, breach) before measuring remedy; variations often bypass claims.
Key Insight
Entitlement is the legal gate (strict notice + causation + breach); quantum and pricing come after and follow clause wording.
Often Confused With
Common Mistakes
- Relying on late or informal notices despite strict contract notice requirements
- Equating proof of causation with establishing the amount payable
- Treating every scope change as a claim instead of a processed variation/change order
Claims Lifecycle — Early Resolution Triggers
Use early notice, productive site meetings, contemporaneous records and staged negotiation to resolve claims before they
Key Insight
Early documented actions (notice + contemporaneous records + focused site meetings) preserve settlement leverage; negotiation ≠ admission.
Often Confused With
Common Mistakes
- Treating early negotiations as admissions of liability
- Waiting for a fully developed formal claim before attempting early settlement
- Skimping on contemporaneous records and losing bargaining leverage
Claims: Notice & Condition‑Precedent
Contract clause requiring timely, formal written notice and required proof before a claim can be decided or remedied.
Key Insight
A technically compliant notice preserves entitlement; late/defective notice usually bars relief even if loss is later proven.
Often Confused With
Common Mistakes
- Assuming a casual email or verbal remark satisfies the contract's formal notice.
- Believing late submission of supporting evidence cures a late or defective notice.
- Thinking commercial talks or interim relief waive strict notice or deadline rules.
Design‑Bid‑Build (DBB) — Split Contracts
Traditional delivery: owner completes design, then competitively bids a separate construction contract; design and build
Key Insight
Design and construction responsibilities are split: owner retains design risk and change exposure; contractor bears means/methods and construction‑phs
Often Confused With
Common Mistakes
- Assuming DBB guarantees final cost certainty once bids are received.
- Expecting the designer to control construction means and methods during build.
- Treating DBB as a single‑point responsibility model for both design and construction.
Latent Site Conditions (Differing Site Conditions)
Unforeseen physical site conditions (subsurface, contamination, utilities) that can change entitlement to time/cost at a
Key Insight
A DSC claim needs a material, unforeseeable difference from the contract baseline plus strict compliance with notice/claim clauses.
Often Confused With
Common Mistakes
- Not only geotechnical—includes contamination, unknown utilities and existing works.
- Surprise ≠ claim; must materially differ from contract baseline and be unforeseeable.
- Discovery doesn't remove the need to follow formal notice/claim procedures.
Delay & Extension of Time (incl. Concurrent Delay)
Analyse schedule impacts across packages, prove critical‑path causation, and establish entitlement to EOT/relief.
Key Insight
EOT entitlement rests on causal impact to the critical path plus compliant notice; concurrent delays need apportionment, not automatic cancelation.
Often Confused With
Common Mistakes
- Granting an EOT doesn't automatically waive the employer's right to liquidated damages.
- Ignoring cross‑package dependencies — local critical path alone can miss entitlement impacts.
- Assuming concurrent delays always cancel claims; you must analyse causation and criticality.
Stakeholder Engagement
30%PMIS / Central Comm Platform (Compass)
Cloud hub that unifies chat, files, tasks, meetings, docs and dashboards for traceable project decisions.
Key Insight
Platform ≠ governance: policies, naming, access controls and audits make it a true single source of truth.
Often Confused With
Common Mistakes
- Assuming real‑time chat removes need for documented, versioned records.
- Centralizing data without access controls or segregation for sensitive info.
- Expecting the tool to auto‑fix data quality—skip governance and you get chaos.
Issue, RFI & Punch‑list Management
Log, categorize, assign, track and close RFIs/issues/punch items with SLAs, escalations and evidence‑based sign‑off.
Key Insight
Closure = owner + verifiable evidence + acceptance; a contractor 'marked complete' is not closed without re‑inspection.
Often Confused With
Common Mistakes
- Logging an RFI and assuming no active follow‑up or SLA tracking is needed.
- Treating punch lists as a final‑handover only task instead of continuous tracking.
- Accepting contractor completion without acceptance evidence or re‑inspection.
Claims Prevention — DRB & Early Intervention
Proactive contractual, documentation and behavioral tactics (DRB, FEP, mediation) to stop disputes early.
Key Insight
Early, continuous notice + neutral DRB + documented de‑escalation prevents escalation and costly claims.
Often Confused With
Common Mistakes
- Believing less documentation reduces claims.
- Equating occasional ad‑hoc meetings with a formal communication plan.
- Treating the Formal Early Warning Process (FEP) as a one‑time checklist.
RACI Matrix — Roles & Sign-offs
Responsibility chart mapping Responsible, Accountable, Consulted, Informed to prevent role overlap and ensure approvals.
Key Insight
One clear Accountable per task; Responsible executes; Consulted provides input; Informed receives outcomes.
Often Confused With
Common Mistakes
- Swapping or treating Accountable and Responsible as the same.
- Assigning multiple Accountables to one activity to 'share' ownership.
- Creating a RACI once and not updating it as teams or scope change.
Communication Feedback Loops
Closed‑loop, two‑way process that captures stakeholder input, KPIs and pulse checks to trigger corrective action.
Key Insight
Design as a closed loop: collect input → analyze context → trigger action/escalation → confirm outcome.
Often Confused With
Common Mistakes
- Counting only formal surveys as ‘feedback’.
- Reducing loops to periodic status reports, not two‑way dialogue.
- Assuming more frequent reports beat relevance or clear escalation triggers.
Mitigation Trio: Feedback, Targeted Comm, Action Plan
Integrate recurring feedback, focused high‑impact messages, and owned action plans to neutralize stakeholder resistance.
Key Insight
Map each resisting stakeholder to observable behaviours and root cause, then apply a tailored intervention with owner, deadline and success criteria.
Often Confused With
Common Mistakes
- Treating action plans as task lists without owners, deadlines, or success criteria.
- Viewing resistance only as active opposition and ignoring quiet non‑compliance.
- Relying on a single message or intervention instead of iterative feedback loops.
Stakeholder ID & Prioritization — Power/Interest + Salience
List stakeholders and rank by power, interest, legitimacy/urgency to focus engagement and risk controls.
Key Insight
Power ≠ interest — use Power–Interest to tailor contact and Salience (power, legitimacy, urgency) to set escalation priority; redo each phase.
Often Confused With
Common Mistakes
- Ignoring internal stakeholders (staff, subcontractors, suppliers).
- Treating identification as a one‑time kickoff task.
- Assuming more salience attributes automatically equals higher priority.
Stakeholder Engagement — Plan, Align, Prevent Claims
Ongoing tactics to elicit, negotiate, document and align expectations—used to prevent scope creep, disputes and claims.
Key Insight
Engagement is continuous and actionable: tailor methods by power, culture and feedback, document negotiated changes, and escalate when alignment fails
Often Confused With
Common Mistakes
- Only engaging external or senior stakeholders; ignoring low‑power but high‑impact parties.
- Confusing the stakeholder register (who) with the engagement plan (how/when).
- Treating engagement as static—failing to capture feedback, update plans, or document agreements.
Strategy and Scope Management
15%Scope Creep — Silent Scope Expansion
Undocumented scope growth — small asks or clarifications that cumulatively erode cost, schedule, quality, safety, and价值.
Key Insight
Creep often begins as tiny clarifications; the danger is cumulative effort/risk growth — treat clarifications like change requests.
Often Confused With
Common Mistakes
- Thinking scope creep equals only added features.
- Blaming only the client; internal teams, subs or regulators can cause creep.
- Relying only on change-control forms; weak scope/alignment lets requests bypass controls.
Scope Baseline — Approved scope: Scope Statement + WBS (Work Breakdown Structure
The approved scope documents (scope statement + WBS + WBS dictionary) used as the control reference for deviations.
Key Insight
The baseline is the active reference for variance — it does NOT auto-update; every change needs formal approval and a baseline revision.
Often Confused With
Common Mistakes
- Treating the current scope as the baseline; baseline only changes after formal approval.
- Mixing scope baseline with schedule or cost baselines — they are separate control documents.
- Assuming baseline forbids all changes; it governs controlled, documented revisions.
Change Order — Contract Amendment
Formal, signed contract amendment that records scope, cost, or schedule changes and authorizes new obligations.
Key Insight
A change order legally amends baselines and performance measurement — must document scope, price/time impacts and authorization to be enforceable.
Often Confused With
Common Mistakes
- Treating verbal or informal notes as a valid change order.
- Assuming every change order increases cost — time‑only or no‑cost orders exist.
- Believing a signature only changes scope and not contract baselines or performance measurement.
ADR — Mediation, Arbitration & Adjudication
Contract dispute routes that differ by formality, cost, speed and whether outcomes are binding.
Key Insight
Select ADR by enforceability and timing: mediation = facilitative/non‑binding; arbitration = private/binding; adjudication = fast interim relief; rule
Often Confused With
Common Mistakes
- Treating arbitration and mediation as identical processes.
- Assuming ADR clauses remove the need for precise, enforceable contract language.
- Believing all ADR methods are non‑binding — some produce binding, enforceable awards.
Scope Maturation & Governed Pivots
Iterative, governed scope changes using gap analysis, VE and CBA to align deliverables, cost and strategy.
Key Insight
A pivot is a governance-approved strategic change (not creep); always document decision rights and map cost/schedule/stakeholder impacts.
Often Confused With
Common Mistakes
- Treating VE/CBA as purely technical and bypassing governance approvals
- Assuming a scope is 'mature' after the first baseline
- Expecting schedule and cost to be unaffected by scope revisions
V&V, Acceptance & Commissioning (with BIM)
Planned tests, measurable acceptance criteria, BIM/model checks, training and docs to prove deliverables meet specs and运
Key Insight
Verification = spec conformity; Validation = fit-for-use. Formal acceptance needs measurable evidence plus commissioning outputs (tests, training, O&M
Often Confused With
Common Mistakes
- Relying on visual inspection alone for operational validation
- Using subjective acceptance criteria instead of measurable metrics
- Treating a clash‑free BIM model or signed handover as proof of full commissioning
Project Governance
5%Governance Models: Decision Rights & Assurance
Defines who decides, how oversight/audits run, and how assurance enforces delivery and compliance.
Key Insight
Governance sets decision rights and recurring assurance (audits, peer reviews) — it's the control layer, not the execution plan.
Often Confused With
Common Mistakes
- Equating the governance model with the project management plan
- Treating assurance/audit as day‑to‑day management instead of independent checks
- Assuming governance always eliminates flexibility rather than balancing control/delegation
Scope Governance: Boards, Thresholds & Escalation
Boards, charters and ToR that set approval thresholds, escalation paths, membership and scope decision authorities.
Key Insight
Tailor committees, ToR and approval thresholds to project size, contract type and regulatory risk; CCB is a forum, not the single sponsor.
Often Confused With
Common Mistakes
- Applying one governance model to every project without tailoring
- Treating the CCB as the same entity as the project sponsor or sole decision-maker
- Assuming a change control board alone provides complete scope governance
Interface Management — Boundaries, Boards, Register
Define, control and communicate where scopes/systems/contractors meet to stop gaps, overlaps and claims.
Key Insight
Interfaces are shared governance items — use an Interface Register + Interface Control Board and update through design, construction and handover.
Often Confused With
Common Mistakes
- Don't put all interface responsibility on one contractor — ownership is shared across client, packages and governance.
- Don't expect one central ‘interface manager’ to resolve unresolved package-level issues without package leads.
- Don't treat interfaces as design-only drawings — update contractual records and stakeholder communications through construction and handover.
Impact Analysis — Time‑Impact, Cost, Ripple Effects
Quantify cost, CPM/time‑impact, quality, safety and downstream effects to justify approvals and entitlement.
Key Insight
Always model direct + indirect impacts — critical path can change and entitlement may include time and cost, not just duration.
Often Confused With
Common Mistakes
- Don't assume consuming float automatically removes entitlement to a time extension.
- Don't assume resource reallocation that restores finish date removes entitlement to cost or time adjustments.
- Don't ignore indirect/downstream impacts — they frequently create additional delay or cost.
Scope Management Plan — Baseline & Configuration Controls
Defines how scope is defined, baselined, changed, tracked and approved across artifacts.
Key Insight
The plan prescribes governance/processes; the Scope Statement records the scope — both must align.
Often Confused With
Common Mistakes
- Treating it as a one‑time document and not updating during delivery.
- Equating the Plan with the Project Scope Statement (process ≠ documented scope).
- Assuming a baseline cannot be changed — change control can rebaseline with approvals.
100% Rule (WBS Completeness)
Each parent must represent 100% of its child work; children together must capture all parent work, incl. PM tasks.
Key Insight
Children collectively sum to 100% of the parent — not each child individually.
Often Confused With
Common Mistakes
- Reading the rule as each child must individually equal 100% of the parent.
- Omitting project management, quality or contract administration from the WBS.
- Believing it requires equal-sized or endless decomposition; stop at controllable work packages.