PMI-CP — PMI Construction Professional Quick Review
Quick Review for PMI Construction Professional (PMI-CP) candidates covering construction delivery, contracts, scope, schedule, cost, risk, quality, safety, stakeholders, and practice focus.
Quick Review purpose
This Quick Review is for candidates preparing for PMI’s PMI Construction Professional (PMI-CP) exam, code PMI-CP. It is designed to help you refresh the most testable construction project management ideas before moving into topic drills, mock exams, and detailed explanations.
Use it as an PM Mastery practice guide: review the decision rules, then test yourself with original practice questions in a question bank. The exam is not only about memorizing terms; it often tests how a construction professional should respond when schedule, cost, contract, safety, quality, stakeholder, and field realities conflict.
High-yield exam mindset
For PMI-CP questions, assume you are expected to act as a professional construction project leader who:
- Protects safety and ethical conduct first.
- Uses the contract, project management plan, and governance process instead of informal shortcuts.
- Integrates design, procurement, construction, commissioning, and handover.
- Documents facts before escalating claims or disputes.
- Communicates early with the right stakeholders.
- Looks for root causes, not just symptoms.
- Balances owner value, constructability, risk, quality, cost, and schedule.
- Prevents field problems through planning, interface management, and clear responsibilities.
A strong answer is often not the fastest action. It is the action that preserves safety, follows governance, aligns stakeholders, and maintains project control.
Fast review map
| Area | Know cold | Common exam trap |
|---|---|---|
| Delivery strategy | How delivery model affects risk, collaboration, design maturity, procurement, and change control | Assuming one delivery model is always best |
| Contracts and procurement | Contract type, risk allocation, notice, change orders, claims, payment, closeout obligations | Treating verbal direction as approved scope |
| Scope and change | Baselines, WBS, RFIs, submittals, field changes, change log, approvals | Doing extra work before documenting impact |
| Schedule | Critical path, float, constraints, lookahead planning, delays, acceleration, recovery plans | Compressing the schedule without analyzing risk |
| Cost | Estimate basis, contingencies, earned value, forecasting, cash flow, cost control | Confusing budget variance with earned value variance |
| Risk | Risk identification, qualitative analysis, responses, ownership, triggers, contingency plans | Managing an issue as if it were still a risk |
| Quality | QA vs QC, inspections, test plans, nonconformance, corrective action, commissioning | Inspecting quality only after work is complete |
| Safety and environment | Hazard controls, stop-work, permits, incident response, environmental protection | Prioritizing schedule over unsafe conditions |
| Stakeholders | Owner, designer, contractor, subcontractors, authorities, utilities, community | Communicating late or with the wrong party |
| Interfaces | Physical, contractual, technical, organizational, and schedule handoffs | Assuming another party is coordinating the interface |
Construction project lifecycle essentials
Construction projects move through overlapping phases. Exam scenarios often test whether you understand what should be controlled at each point.
| Phase | Main focus | Candidate decision point |
|---|---|---|
| Initiation / business need | Owner objectives, project justification, funding, high-level risks | Clarify value drivers before locking in scope |
| Planning and design | Requirements, design development, constructability, estimates, permits, procurement planning | Detect ambiguity before it becomes field rework |
| Procurement | Bid packages, contract strategy, supplier selection, long-lead items | Align contract type with risk and design maturity |
| Construction execution | Mobilization, field coordination, production, safety, quality, schedule, cost | Control work through approved plans and records |
| Commissioning / turnover | Testing, systems integration, punch list, documentation, training | Verify readiness before acceptance |
| Closeout | Final payment, claims resolution, warranties, lessons learned, demobilization | Do not treat physical completion as administrative completion |
Key lifecycle traps
- Design is not automatically “complete” because construction has started. Many construction projects require ongoing design clarification, submittal review, and field coordination.
- Procurement decisions affect schedule risk. Long-lead equipment, specialized labor, customs, logistics, and supplier capacity can become critical path drivers.
- Turnover is not just the punch list. It may include commissioning records, as-builts, operations manuals, training, warranties, spare parts, and acceptance documentation.
- Closeout starts early. Waiting until the end to collect records causes delay, disputes, and payment issues.
Delivery models and risk allocation
The delivery model influences who controls design, who carries coordination risk, how early contractors are involved, and how changes are handled.
| Delivery approach | Typical strengths | Typical risks / watchouts |
|---|---|---|
| Design-bid-build | Clear separation of design and construction; competitive bidding | More owner design risk; higher potential for RFIs and design-related changes |
| Design-build | Single point of responsibility for design and construction | Owner must define performance requirements clearly; changes can be costly |
| Construction management approach | Early construction input and phasing support | Role clarity and responsibility boundaries must be managed |
| EPC / turnkey-style delivery | Integrated engineering, procurement, and construction; strong single-party accountability | Owner needs strong requirements and change discipline |
| Alliance / collaborative models | Shared risk, joint problem solving, early integration | Requires trust, transparency, and mature governance |
Decision rule
When a question asks what delivery or contract strategy is best, look for:
- Design maturity.
- Owner’s need for control.
- Schedule urgency.
- Risk tolerance.
- Market capability.
- Interface complexity.
- Need for early contractor involvement.
- Regulatory, permitting, or operational constraints.
Avoid answers that select a delivery model based only on lowest initial price.
Contracts, procurement, and commercial control
The exam may test whether you understand contract intent, not legal minutiae. Read contract-related questions by asking: Who accepted the risk, what process applies, and what documentation is required?
Common contract types
| Contract type | Cost risk tendency | Best fit | Watchout |
|---|---|---|---|
| Lump sum / fixed price | More risk to contractor | Well-defined scope and design | Changes and ambiguities can become disputes |
| Unit price | Shared based on measured quantities | Repetitive measurable work; uncertain quantities | Quantity growth affects total cost |
| Cost reimbursable | More risk to owner | Uncertain scope; need for early start | Requires strong cost transparency and controls |
| Guaranteed maximum price | Shared depending on terms | Collaborative planning with cost ceiling | Assumptions and exclusions matter |
| Time and materials | More risk to owner if uncontrolled | Emergency, small, or undefined work | Needs caps, approvals, and daily records |
Procurement review points
- Procurement is not only purchasing; it includes sourcing strategy, bid evaluation, contract award, expediting, inspection, logistics, and supplier performance.
- Long-lead items must be integrated into the schedule early.
- Bid evaluation should consider technical compliance, capacity, schedule, quality, safety, commercial terms, and risk—not price alone.
- Changes to procurement packages can create scope gaps or duplicate scope.
- Supplier delays may become project delays if they affect the critical path.
Claims and change control
| Term | Meaning in exam scenarios |
|---|---|
| Change request | Proposed modification to scope, cost, schedule, quality, or contract requirements |
| Change order | Approved contractual change |
| Claim | Demand for time, money, or other relief when entitlement or responsibility is disputed |
| Notice | Formal communication required by contract or governance process |
| Entitlement | Basis for receiving time, cost, or other relief |
| Quantum | Amount of time or money being requested |
| Mitigation | Reasonable action to reduce impact |
Contract scenario decision rule
If a contractor receives direction that may change scope:
- Confirm safety and immediate site conditions.
- Review contract requirements and authority limits.
- Document the instruction, facts, dates, quantities, and potential impact.
- Provide required notice through the correct channel.
- Request clarification or approval before proceeding when practical.
- Update schedule, cost, risk, and stakeholder communications after approval.
Do not choose an answer that ignores documentation or assumes verbal direction automatically authorizes cost recovery.
Scope, requirements, and change management
Construction scope control depends on clear requirements, design documents, specifications, contract boundaries, and disciplined field execution.
Key scope artifacts
| Artifact | Why it matters |
|---|---|
| Project scope statement | Defines what is included and excluded |
| WBS / work packages | Breaks work into manageable deliverables |
| Drawings and specifications | Define technical requirements |
| Basis of design | Explains design assumptions and intent |
| RFI log | Tracks clarification requests and responses |
| Submittal log | Tracks shop drawings, product data, samples, and approvals |
| Change log | Records proposed, pending, approved, and rejected changes |
| As-built records | Capture actual installed conditions |
| Punch list | Tracks incomplete or deficient items before final acceptance |
Scope traps
- RFI responses can create changes. If clarification modifies requirements, evaluate cost and schedule impact.
- Submittal approval is not a blanket approval of contract deviations. Exceptions must be clearly identified and accepted.
- Field directives may need later formalization. Emergency work still requires documentation.
- Scope gaps often occur at interfaces. Examples: utility tie-ins, controls integration, temporary works, testing responsibility, access, and commissioning support.
- Gold plating is still a problem. Adding unapproved features can increase cost, complexity, and risk.
Construction issue decision path
Use this mental model for many scenario questions.
flowchart TD
A[Field issue occurs] --> B{Immediate safety or environmental risk?}
B -->|Yes| C[Stop or make safe, follow emergency procedures, notify required parties]
B -->|No| D{Potential scope, cost, schedule, quality, or contract impact?}
C --> D
D -->|Yes| E[Document facts, review contract and project controls, issue required notice]
D -->|No| F[Resolve within approved plan and record outcome]
E --> G{Design or technical clarification needed?}
G -->|Yes| H[Submit RFI or technical query through approved channel]
G -->|No| I{Approval required before work proceeds?}
H --> I
I -->|Yes| J[Obtain authorization or change approval]
I -->|No| K[Proceed within authority, monitor impact]
J --> L[Update logs, schedule, cost forecast, risk register, and stakeholders]
K --> L
Schedule management essentials
Construction schedules are logic-driven planning and control tools. Exam questions often test whether you can identify the correct response to delay, constraint, sequencing, or acceleration problems.
Terms to review
| Term | Meaning |
|---|---|
| Activity | A defined task with duration and relationships |
| Milestone | Significant zero-duration event or decision point |
| Critical path | Longest path through the network; determines project finish date |
| Total float | Time an activity can slip without delaying project completion |
| Free float | Time an activity can slip without delaying its immediate successor |
| Constraint | External or imposed limitation on work sequence or timing |
| Lookahead plan | Near-term planning window used to remove constraints and coordinate crews |
| Baseline schedule | Approved schedule used for performance comparison |
| Recovery schedule | Plan to regain lost time |
| Schedule compression | Shortening duration through crashing or fast tracking |
Crashing vs fast tracking
| Technique | What it does | Main risk |
|---|---|---|
| Crashing | Adds resources, overtime, shifts, equipment, or subcontractors | Higher cost, congestion, productivity loss |
| Fast tracking | Performs activities in parallel that were planned sequentially | Rework, quality issues, coordination failures |
Delay analysis mindset
When a delay appears, ask:
- Is it on the critical path?
- Was it caused by the owner, contractor, designer, supplier, weather, authority, or another party?
- Is it excusable, compensable, both, or neither under the governing documents?
- Is there concurrent delay?
- Was timely notice given?
- What mitigation actions were reasonable?
- Is the schedule update reliable and contemporaneous?
Do not assume every delay deserves time or money. The facts, contract, critical path, causation, notice, and mitigation all matter.
Cost, estimating, and earned value
Cost questions often require distinguishing estimating, budgeting, forecasting, cost control, and commercial entitlement.
Cost management review table
| Concept | Exam focus |
|---|---|
| Direct costs | Labor, materials, equipment, subcontractors directly tied to work |
| Indirect costs | Site overhead, supervision, temporary facilities, insurance, support costs |
| Contingency | Amount reserved for identified project risks within the project budget approach |
| Management reserve | Reserve for broader unknowns, if used in the governance structure |
| Escalation | Cost growth due to market or time-based price changes |
| Cash flow | Timing of inflows and outflows, not just total cost |
| Forecast | Expected final cost based on current performance and known trends |
| Commitment | Contracted or obligated amount |
| Accrual | Cost incurred but not yet invoiced or paid |
Earned value formulas
Know the interpretation more than the arithmetic.
\[ \begin{aligned} CV &= EV - AC \\ SV &= EV - PV \\ CPI &= \frac{EV}{AC} \\ SPI &= \frac{EV}{PV} \end{aligned} \]Where:
- PV = planned value.
- EV = earned value.
- AC = actual cost.
- CV less than 0 means cost overrun against earned value.
- SV less than 0 means behind planned earned value.
- CPI less than 1.0 means cost inefficiency.
- SPI less than 1.0 means schedule inefficiency against the plan.
Candidate mistakes
- Confusing actual cost with earned value.
- Treating a low invoice amount as good performance without checking earned progress.
- Ignoring committed costs that have not yet appeared as actuals.
- Forgetting that cost forecast should include known changes, trends, risks, and remaining work.
- Assuming contingency can be spent without governance.
Risk and opportunity management
Risk management is proactive. Issue management is reactive. PMI-CP scenarios often test this distinction.
| Item | Risk | Issue |
|---|---|---|
| Timing | May happen | Has happened |
| Tool | Risk register | Issue log |
| Response | Avoid, mitigate, transfer, accept, exploit, enhance, share | Assign action, resolve, escalate, document |
| Focus | Probability and impact | Actual consequence and recovery |
Common construction risks
- Incomplete design or unclear requirements.
- Subsurface or site condition uncertainty.
- Long-lead equipment delays.
- Labor shortages or productivity loss.
- Permit or authority delays.
- Utility conflicts.
- Interface gaps between trades.
- Weather impacts.
- Material escalation or supply chain disruption.
- Safety incidents.
- Quality failures and rework.
- Commissioning integration failures.
- Stakeholder opposition or access restrictions.
Risk response review
| Response | Use when |
|---|---|
| Avoid | Change the plan to remove the threat |
| Mitigate | Reduce probability or impact |
| Transfer | Shift or share financial responsibility through contract, insurance, bond, or warranty mechanism |
| Accept | Monitor and prepare contingency if active acceptance is appropriate |
| Exploit | Ensure an opportunity occurs |
| Enhance | Increase probability or benefit of an opportunity |
| Share | Allocate opportunity ownership to a party best able to capture it |
A strong answer assigns a risk owner, trigger, response, and follow-up action. A weak answer simply “monitors the risk” when active mitigation is needed.
Quality management and commissioning
Quality in construction is built into planning, procurement, installation, inspection, testing, and turnover. It is not only final inspection.
QA vs QC
| Concept | Focus | Example |
|---|---|---|
| Quality assurance | Process confidence and prevention | Reviewing procedures, supplier qualifications, inspection and test plans |
| Quality control | Product verification and detection | Inspections, tests, measurements, punch list verification |
Quality tools and controls
- Inspection and test plan.
- Method statement or work procedure.
- Material receiving inspection.
- Mockups and first-work inspections.
- Hold points and witness points.
- Nonconformance report.
- Corrective and preventive action.
- Root cause analysis.
- Calibration records.
- Commissioning plan.
- Systems completion and turnover packages.
Nonconformance decision rule
When defective work is found:
- Protect safety and prevent further defective installation.
- Document the nonconformance with objective evidence.
- Notify responsible parties through the approved process.
- Evaluate technical impact and disposition: repair, rework, use-as-is, or replace, as allowed by governance.
- Identify root cause.
- Implement corrective action.
- Verify effectiveness.
- Update lessons learned and quality records.
Avoid answers that jump directly to blame or payment withholding without first documenting, evaluating, and following the quality process.
Safety, environment, and site control
Safety is a high-priority decision filter. In exam scenarios, if a condition creates imminent danger, the correct first response is usually to stop or control the unsafe work, make the area safe, and notify appropriate parties.
Safety review points
| Topic | What to remember |
|---|---|
| Hazard identification | Find hazards before work starts, especially during planning and daily briefings |
| Job hazard analysis / job safety analysis | Break work into steps, hazards, and controls |
| Permit-to-work | Controls high-risk activities such as hot work, confined space, energized work, lifting, or excavation where applicable |
| Stop-work authority | Work should stop when conditions are unsafe |
| Incident response | Provide aid, secure area, notify, investigate, preserve facts |
| Leading indicators | Inspections, observations, training, near-miss reporting |
| Lagging indicators | Injuries, incidents, lost time, damage after the fact |
| Environmental controls | Waste, erosion, spill response, dust, noise, water, protected areas |
Safety traps
- Choosing to continue work to protect the schedule.
- Treating near misses as unimportant because no injury occurred.
- Waiting for a formal meeting while an immediate hazard remains uncontrolled.
- Assuming safety responsibility belongs only to the safety manager.
- Failing to integrate safety with planning, sequencing, access, temporary works, and subcontractor coordination.
Stakeholder and communication management
Construction projects are stakeholder-heavy. Good answers usually identify the right stakeholder, communicate through the right channel, and preserve a record.
Stakeholder groups
| Stakeholder | Typical concerns |
|---|---|
| Owner / client | Value, cost, schedule, performance, risk, acceptance |
| Designer / engineer | Design intent, technical compliance, clarifications |
| Contractor | Means, methods, production, coordination, commercial recovery |
| Subcontractors | Access, prerequisites, sequencing, payment, information |
| Suppliers | Specifications, approvals, manufacturing, logistics |
| Authorities having jurisdiction | Permits, inspections, code compliance |
| Utilities | Shutdowns, tie-ins, protection, relocation |
| Operations / end users | Maintainability, training, turnover, access |
| Community | Traffic, noise, safety, environmental impact |
Communication decision rules
- Use informal discussion to clarify, but use formal channels for decisions, approvals, changes, and notices.
- Escalate when authority, risk, cost, schedule, safety, or stakeholder impact exceeds the team’s level.
- Tailor communication: executives need exceptions and decisions; field teams need clear work instructions; technical teams need complete information.
- Do not hide bad news. Report facts, impacts, options, and recommendations.
- Record decisions and assumptions.
Interface and integration management
Interface failures are a major source of construction disputes and delays. Interfaces can be physical, technical, contractual, schedule-related, organizational, or operational.
Interface examples
| Interface type | Example |
|---|---|
| Physical | Two trades working in the same space |
| Technical | Mechanical system must integrate with controls system |
| Contractual | Scope boundary between contractor and utility provider |
| Schedule | One contractor’s completion is another contractor’s access condition |
| Information | Designer response needed before fabrication |
| Operational | Shutdown window needed in an active facility |
Interface management actions
- Create an interface register for complex projects.
- Assign interface owners.
- Define deliverables, dates, dependencies, and acceptance criteria.
- Use coordination meetings, BIM/clash detection where appropriate, and field walkdowns.
- Track open interface issues to closure.
- Align interface risks with schedule and change control.
- Verify commissioning and turnover dependencies early.
A common wrong answer is to assume the project manager can solve every interface personally. The better answer often assigns clear ownership, creates a coordination mechanism, and tracks closure.
Lean construction and production planning concepts
PMI-CP candidates should be comfortable with practical production control ideas often used in construction.
| Concept | Practical meaning |
|---|---|
| Pull planning | Plan backward from milestones based on handoffs and commitments |
| Last Planner-style thinking | Use reliable short-term commitments from those performing the work |
| Constraint removal | Clear prerequisites before work starts |
| Percent plan complete | Measures reliability of planned commitments completed |
| Takt planning | Creates rhythm and flow across locations or work zones |
| Visual management | Makes work status, constraints, and safety issues visible |
| Continuous improvement | Uses lessons learned and root cause analysis to improve performance |
Lean trap
Lean does not mean “work faster no matter what.” It means improving flow, reliability, coordination, constraint removal, and value delivery while reducing waste.
Ethics and professional responsibility
For PMI-related exams, professionalism matters. Expect answer choices that test integrity under pressure.
Choose actions that:
- Provide truthful status reporting.
- Disclose conflicts of interest.
- Follow procurement and contract rules.
- Protect confidential and proprietary information.
- Avoid favoritism, bribery, and improper influence.
- Respect safety, environment, and community obligations.
- Escalate serious issues appropriately.
- Preserve accurate records.
Avoid answers that hide problems, manipulate progress data, bypass governance, retaliate against whistleblowers, or ignore unsafe conditions.
High-yield “if you see this, think that” table
| Scenario clue | Think first |
|---|---|
| Unsafe condition | Stop or control work, make safe, notify |
| Verbal direction to perform extra work | Document, confirm authority, follow change process |
| Design ambiguity | Submit RFI / technical query; assess impact |
| Subcontractor delay | Check critical path, contract responsibility, mitigation |
| Cost overrun | Analyze earned value, commitments, forecast, root cause |
| Behind schedule | Identify critical path drivers before accelerating |
| Quality defect | Document NCR, evaluate disposition, corrective action |
| Stakeholder complaint | Understand impact, communicate plan, update register |
| Long-lead equipment issue | Integrate procurement, logistics, schedule, risk response |
| Interface conflict | Assign ownership, coordinate, track closure |
| Claim threat | Preserve records, follow notice process, analyze entitlement |
| Commissioning failure | Verify system integration, test records, readiness, corrective actions |
Common wrong-answer patterns
Watch for answer choices that:
- Take action outside authority.
- Ignore the contract or project management plan.
- Skip documentation.
- Prioritize cost or schedule over safety.
- Blame a party before facts are established.
- Escalate too early without analysis, or too late after damage grows.
- Approve changes without impact assessment.
- Treat all delays as compensable.
- Use contingency without approval.
- Confuse quality assurance with quality control.
- Communicate only informally when formal notice is required.
- Focus on one trade while ignoring project-wide interfaces.
- Accept a low bid without checking technical compliance and capacity.
Quick calculation and interpretation drill
Use original practice questions to make these interpretations automatic.
| Given | Correct interpretation |
|---|---|
| CPI below 1.0 | Cost performance is unfavorable |
| SPI below 1.0 | Schedule performance is unfavorable against planned value |
| Negative CV | Earned value is less than actual cost |
| Negative SV | Earned value is less than planned value |
| Activity has zero total float | It is on the critical path in that schedule model |
| Delay on noncritical activity within float | May not delay project completion |
| Added resources to shorten duration | Crashing |
| Overlapping sequential work | Fast tracking |
| Risk has occurred | Move from risk response to issue management |
| Approved change affects baseline | Update applicable baseline through change control |
How to use this Quick Review with practice questions
- Scan this page once without stopping. Mark topics that feel weak.
- Do focused topic drills. Use original practice questions on contracts, change, schedule, cost, risk, quality, safety, and stakeholders.
- Review detailed explanations. Do not only check whether you were right; identify why the best answer is better than the tempting answer.
- Build a mistake log. Track whether errors come from content gaps, misreading, overreacting, or ignoring governance.
- Move to mixed sets. PMI-CP scenarios combine multiple areas, so practice switching between contract, schedule, cost, safety, and stakeholder thinking.
- Finish with timed mock exams. Build pacing and decision discipline.
Final review checklist
Before exam day, make sure you can confidently answer:
- What is the safest first action?
- What does the contract or governance process require?
- Is this a risk, issue, change, claim, or nonconformance?
- Who has authority to decide?
- What documentation is needed?
- Does this affect the critical path?
- Does this affect cost forecast, cash flow, or earned value?
- What stakeholder communication is required?
- Is there an interface dependency?
- What update is needed to the log, register, baseline, or plan?
Practical next step
Use this Quick Review as your final concept pass, then move into PMI-CP topic drills and mixed question-bank practice with detailed explanations. Focus especially on scenario questions where safety, contract process, field execution, and stakeholder communication all compete for attention.
Continue in PM Mastery
Use this Quick Review as a final concept map, then move into PM Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original PM Mastery practice items; they are not official PMI questions, copied live-exam content, or exam dumps.