PMP Procurement Management: Contracts, Processes & Exam Tips

Procurement Management is one of the smaller knowledge areas (3 processes), but in my experience it is a frequent source of trick questions on the PMP exam. Contract types, buyer/seller risk, and source selection methods all show up regularly. The candidates I coach who know procurement cold reliably score these questions; the ones who skim procurement during prep often lose 5-8 questions to patterns I would call entirely predictable.

In this guide I cover the three procurement processes, the contract types I tell candidates they must know, the source selection methods, and the patterns that, in my view, distinguish strong procurement knowledge from surface familiarity. I also address the procurement scenarios that appear in agile and hybrid contexts.

The PMBOK 6 Close Procurements process was integrated into Control Procurements in PMBOK 7-aligned guidance.

Plan Procurement Management decides what to procure, when, how, and from whom. Outputs include the procurement management plan, procurement strategy, bid documents, source selection criteria, make-or-buy decisions, and procurement statement of work.

Conduct Procurements obtains seller responses, selects sellers, and awards contracts. Activities include holding bidder conferences, evaluating proposals, negotiating contracts, and signing agreements.

Control Procurements manages procurement relationships during the contract period, monitors performance, makes payments, and resolves issues. Closes contracts upon completion.

For exam questions, recognising which process is implicated is the first step. “We are deciding whether to build internally or buy from a vendor” -> Plan Procurement Management. “We are evaluating vendor proposals” -> Conduct Procurements. “Vendor missed a deliverable; what do we do?” -> Control Procurements.

The dominant exam pattern: given a scenario, identify the right contract type.

The contract types arrange on a risk spectrum from full seller risk (FFP) to full buyer risk (CPAF). T&M sits in the middle. The exam tests recognition of which contract type fits which scenario.

Patterns: - Well-defined scope -> Fixed Price (FFP usually). - Performance bonuses justified -> FPIF. - Long contracts in volatile markets -> FPEPA. - Short staff augmentation -> T&M. - R&D or vague scope -> Cost-reimbursable. - Performance metrics tied to fee -> CPIF. - Long partnerships with subjective evaluation -> CPAF.

For exam preparation, drilling on contract type scenarios builds reliable recognition. Doing 30+ contract type questions during prep produces fluency.

Risk shifts inversely with cost certainty.

• Fixed-price = highest seller risk, lowest buyer risk. The seller commits to a price; if costs exceed, the seller absorbs the loss.
• Cost-reimbursable = highest buyer risk, lowest seller risk. The buyer reimburses actual costs plus fee; cost overruns flow through to the buyer.
• T&M is in the middle. The buyer pays for time and materials at agreed rates; cost growth depends on duration.

When the question says “scope is unclear” or “we cannot define requirements”, cost-reimbursable contracts are usually the right fit. When the question says “scope is well-defined” or “we know exactly what we want”, fixed-price contracts are usually right.

The PMI mindset on contract type selection: match the risk allocation to the situation. Forcing fixed-price on uncertain scope produces vendor disputes when scope grows. Allowing cost-reimbursable on certain scope produces unnecessary cost overruns.

For exam questions about who bears risk, the candidate computes: in this contract type, who bears the cost overrun risk? The answer points to the contract type.

Methods include:

• Least cost: lowest qualifying bid wins. Used when quality differentiation is minimal.
• Qualifications only: cheapest qualified vendor wins, no competitive bidding. Used for standardised services.
• Quality-based: highest technical proposal wins. Cost is decided after vendor selection. Used when quality differentiation matters most.
• Quality and cost based (QCBS): weighted scoring of technical and cost. Used for most complex procurements.
• Fixed budget: vendor with best technical proposal within fixed budget wins. Used when budget is hard.
• Sole source: only one vendor available. Used when alternatives do not exist.

Exam tip: QCBS is the most common method for complex procurements. Recognise it when the scenario describes a weighted scoring approach.

The selection method matters because it shapes the procurement process. Least-cost methods can use simpler bid documents; QCBS methods require detailed evaluation criteria; sole-source methods may skip competitive bidding entirely.

For exam questions about source selection, the candidate identifies what the scenario emphasises. Cost-emphasis -> least cost or fixed budget. Quality-emphasis -> quality-based. Mixed emphasis -> QCBS.

Make-or-buy decisions consider:

• Cost (direct + indirect, vs vendor cost). Internal capacity has indirect costs (overhead, opportunity cost) that must be factored.
• Capability (do we have the skills, or does the vendor have them better). Specialist work often favours buying.
• Capacity (can we do it without disrupting other work). Even capable teams may lack capacity.
• Risk (vendor reliability vs internal execution risk). Vendor failure has different risk profile than internal failure.
• Strategic fit (is this core to our value proposition). Core capabilities often favour making; non-core favour buying.

The PMI mindset: choose make when capability is core; choose buy when it is non-core or vendor is materially better. The strategic fit

 consideration often dominates other factors for capabilities that define competitive advantage.

For exam questions, scenarios often present mixed signals. The candidate weighs the factors and applies the PMI mindset to select the right answer.

The make-or-buy analysis output (decision document) feeds into other procurement processes. Make decisions skip procurement; buy decisions trigger Plan Procurement Management.

Agile project procurement has specific patterns:

• Time and materials contracts suit agile work because scope evolves. The buyer pays for capacity; the team uses capacity flexibly.
• “Money for nothing, change for free” clauses allow scope swaps within fixed budgets without contract amendments.
• Master Service Agreements (MSA) with iterative SOWs establish overall terms once, then issue smaller SOWs per sprint or feature.
• Outcome-based contracts tie payment to results rather than effort. Increasingly common for AI and software services.
• Frame agreements in scaled agile environments cover multiple teams under shared procurement terms.

For exam questions about agile procurement, the right answer typically reflects scope flexibility. Fixed-price contracts can work for agile if the scope-flexibility mechanism is built in (money for nothing, change for free). Otherwise, T&M or cost-reimbursable better fit agile work.

• Confusing T&M with cost-reimbursable. T&M has hourly rates with material markups. Cost-reimbursable pays actual costs plus fees.
• Assuming the seller’s perspective. PMP exam questions are almost always from the buyer’s perspective unless stated otherwise.
• Skipping the bid/seller conference. When questions describe a vendor information meeting, the answer often references the bidder/seller conference.
• Mishandling change requests in procurement. All contract changes go through Perform Integrated Change Control plus Control Procurements.
• Missing the SOW vs Procurement Statement of Work. The Procurement SOW describes work for the vendor; the project SOW describes the broader project.
• Confusing procurement audit with closeout. Audit evaluates the process; closeout finalises the contract.
• Ignoring force majeure and similar clauses. When questions reference unusual circumstances (war, natural disaster), force majeure may apply.

The pattern: procurement traps often hinge on subtle distinctions. Slow reading and explicit identification of which contract type, process, or document is implicated prevents most traps.

Key procurement documents the exam tests:

• Procurement Management Plan: defines how procurement will be managed across the project.
• Procurement Strategy: high-level approach to procurement, including delivery method, contract types, and procurement phases.
• Bid Documents: documents sent to potential vendors. Include the SOW, evaluation criteria, contract terms, submission instructions.
• Procurement Statement of Work (SOW): detailed description of the work the vendor will perform, with deliverables and acceptance criteria.
• Source Selection Criteria: explicit criteria for evaluating vendor proposals. Weighted to indicate relative importance.
• Make-or-Buy Decisions: documented analysis showing why each procurement was decided in or out.
• Independent Cost Estimates: internal estimates of what procurement should cost, used to validate vendor proposals.
• Procurement Documents: catch-all term for the full set of materials supporting procurement.

For exam questions about which document applies, the candidate identifies the procurement stage and matches the document.

Vendor evaluation typically follows weighted scoring:

The weights vary by procurement context. Critical capability favours technical weight; cost-sensitive procurement favours cost weight.

For complex procurements, the evaluation includes: - Initial qualification (does the vendor meet minimum requirements). - Technical evaluation (how well does the proposal address technical requirements). - Cost evaluation (how the proposed cost compares to budget and to other proposals). - Risk evaluation (vendor stability, geographic considerations, dependency risk). - Best and Final Offer (BAFO): vendors invited to refine their proposals.

The PMI mindset on evaluation: rigorous, transparent, defensible. Documentation of the evaluation is mandatory; even more so in regulated or government procurement contexts.

Once a contract is signed, Control Procurements manages the relationship. Activities include:

• Monitoring vendor performance against SLA.
• Processing invoices and payments.
• Managing contract changes through Integrated Change Control.
• Handling disputes and escalations.
• Conducting performance reviews.
• Managing scope changes via amendments.

The PMI mindset on contract management: collaborative but disciplined. Adversarial relationships with vendors hurt project outcomes. Lax management produces scope creep and cost overruns.

For exam questions about vendor performance issues, the right answer typically involves: document the issue, engage the vendor for resolution, escalate within the contract framework, modify the contract via change control if needed.

Vendor performance issues that violate the contract may trigger: - Performance improvement plans. - Penalty enforcement (where contract supports). - Termination for cause. - Litigation (last resort).

Procurement closeout occurs at contract completion or termination:

• Verify all deliverables were received and accepted.
• Settle final payments and any retained amounts.
• Close out contract administration.
• Document lessons learned for future procurements.
• Archive contract documentation.
• Conduct procurement audit.

Procurement closeout happens whenever a contract ends, not only at project closure. Multi-vendor projects close out each contract as it completes.

For exam questions about closeout, the right answer typically involves following the formal closeout process even when the contract ended successfully and informally. Rigorous closeout produces institutional learning that informal closeout loses.