Key Concepts
Procurement basics appear on the PMP exam, and the project manager is almost always a critical stakeholder in procurement decisions, even when a separate team handles the mechanics. This task covers providing project-specific information, monitoring vendor performance for its impact on schedule and quality, and keeping procurement integrated with the rest of the project.
Managing procurement is a topic some project managers do not get much exposure to. Your organization may have a dedicated purchasing group that handles this work, or your projects may have been internal without external suppliers. Either way, procurement basics appear on the PMP exam, and the project manager is almost always a critical stakeholder in procurement decisions, even when a separate team manages the mechanics.
The project manager provides project-specific information, monitors vendor performance for its impact on schedule and quality, and keeps procurement activities integrated with the rest of the project plan. Even when someone else signs the contracts, procurement problems land on the project.
The terms “contract” and “agreement” are often used interchangeably in procurement.
2.5.1 Plan Procurement
Planning a procurement starts by understanding what the project actually needs and whether it should be built internally or acquired externally.
Procurement Strategy
Procurement Strategy encompasses planning the procurement process. This includes
- Performing make-or-buy analysis
- Making the make-or-buy decisions
- Creating a Procurement Management Plan
- Creating a Statement Of Work (SOW) for each procurement
Make-or-Buy Analysis
When analyzing scope, some work can be done by the project team, some can be built internally with additional resources, and some needs to be outsourced or purchased. Make-or-buy analysis is the evaluation that determines which work falls into which category. Factors that guide this decision include:
- Does the team have the skills to do the work to the required standard?
- Is there sufficient time to build internally, or is speed-to-capability more important?
- Is there an ongoing need for this skill set that justifies developing it internally?
- Are the required resources and skills available within the organization?
Statement of Work
A Statement of Work (SOW) describes a defined piece of work in enough detail for prospective sellers to determine whether they can deliver it. SOWs are developed from the project scope baseline and sent to potential vendors. They should be as clear and specific as possible: ambiguity in the SOW becomes a source of disputes during delivery.
When a vendor is interested in bidding, they respond to the SOW. The buyer evaluates those responses against defined criteria. The SOW forms the foundation of all subsequent procurement documents.
Bid Documents
Bid documents are used to request proposals or quotations from potential sellers. The form of the document depends on what is being procured:
- Request for Information (RFI): Used when more information about available goods or services is needed from the market before issuing a formal solicitation.
- Request for Quotation (RFQ): Used when price and delivery information is the primary need.
- Request for Proposal (RFP): Used when the solution is not straightforward and the buyer wants to evaluate the vendor’s approach alongside cost. The RFP is the most formal of the bid document types, with strict rules for content, timelines, and seller responses.
Bidder Conferences
Before vendors submit their proposals, organizations often hold a bidder conference to explain the requirements, terms, and conditions, and to answer questions. These sessions go by several names: pre-bid conference, pre-proposal conference, vendor conference, or contractor conference. Their purpose is to give all prospective sellers a common understanding of the requirements and reduce the risk of proposals built on different assumptions.
Source Selection Criteria
Source selection criteria define what the buyer is looking for when evaluating vendor responses. Common criteria include:
- Technical capability and approach
- Past performance and customer references
- Overall cost and life-cycle cost
- Delivery approach and milestone schedule
- Financial stability and capacity
- Warranty and support terms
- Compliance with intellectual property and proprietary rights requirements
Having clear, documented criteria before receiving responses keeps the evaluation consistent and defensible.
Qualified Vendors
Some organizations maintain a qualified vendors list: a set of pre-approved sellers that meet baseline standards for the type of goods or services being procured. Using a qualified vendors list shortens the evaluation process, since basic capability has already been verified. Where no qualified vendors exist, market research identifies candidates.
2.5.2 Execute a Procurement Management Plan
Once procurement planning is done, the plan has to be put into action. Executing the procurement management plan means running the solicitation process, evaluating vendor responses, and selecting a seller.
This phase covers communicating requirements to the market clearly and managing those communications carefully. Miscommunication with external parties is more costly than miscommunication internally, because the consequences are often contractual. The project manager should lean toward over-communicating objectives, needs, and success criteria with prospective vendors.
Practical steps during execution include:
- Add vendors and prospective sellers to the communications management plan and manage their information needs the same way you manage other project stakeholders
- Provide notifications of potential cost overruns, schedule changes, or scope issues to relevant parties
- Request acknowledgments from vendors to confirm their communications have been received and understood
- Provide formal written acceptance when contracted deliverables are received and verified
Communication
Once we know what we want to buy, we need to start communicating with prospective sellers.
When dealing with people, especially external ones, there is potential for miscommunication. This could lead to a costly mistake when working in the field of procurement, so we should err on the side of over-communicating our objectives, the project needs, and success criteria.
Some tips for managing procurement communications include:
- Add vendors and suppliers to the Communications Management Plan and administer their details and communication needs like all the other project stakeholders
- Provide periodic progress reports of supplier activities
- Share notifications of potential supplier cost overruns, schedule delays or issues with relevant stakeholders
- Provide acknowledgments back to suppliers when they communicate to verify the message was received and ask for the same to confirm that communication is occurring
- Provide formal acceptance of the supplier’s contracted deliverables.
2.5.3 Select Preferred Contract Types
Contracts
Contracts are mutually binding agreements. They obligate the seller to provide the specified product or service and obligate the buyer to pay for it. Contracts are typically customized for each agreement and vary in type.
Components of Contracts
- Description of the work being done, its deliverables, and scope
- Delivery dates or other schedule information
- Identification of authority and decision-making, where appropriate
- Responsibilities of both parties
- Management of technical and business aspects
- Price and payment terms
- Provisions for termination and dispute resolution
- Applicable guarantees and warranties
Common contract types include:
Fixed-Price Contracts
A fixed-price contract sets a defined price for a defined scope. The buyer’s cost risk is low: the price is agreed in advance and the seller absorbs overruns. These contracts work well when scope is well-defined and unlikely to change. The trade-off is that they require detailed specifications upfront. Sellers will pad their estimates to manage the risk they are absorbing, and ambiguous scope becomes a source of change orders.
- Pros – Provides maximum protection to the buyer
- Cons – Requires lengthy estimation and potential for padding by the seller.
Cost-Reimbursable Contracts
A cost-reimbursable contract pays the seller’s actual costs plus a fee representing profit or margin. The buyer carries the cost risk, because total costs are not capped. These contracts suit work where scope or parameters are uncertain, since the buyer retains control over what gets built. They require the seller to maintain an accounting system capable of tracking project costs separately.
Cost-reimbursable contracts can be structured with incentives for meeting schedule, cost, or technical performance targets, which partially aligns seller interests with buyer objectives.
- Pros – Can be structured to include incentives for meeting schedule, cost or technical performance targets.
- Cons – The buyer bears most of the cost risk because the total costs are unknown.
Time-and-Materials Contracts
A time-and-materials (T&M) contract pays an agreed hourly or daily rate plus material costs. It is a hybrid: the scope flexibility of a cost-reimbursable arrangement with rates fixed in advance. T&M suits short-term work or work where the level of effort cannot be determined upfront.
The risk for the buyer is that the seller’s profit is built into the hourly rate, so there is no incentive to finish early. T&M contracts typically include a not-to-exceed clause that caps the buyer’s total exposure.
- Pros – Good for projects that are difficult to estimate
- Cons – They can lead to cost and schedule overruns over long periods since the seller’s profit is built into the hourly rate. So, there is no incentive for them to finish early. To limit this, T&M contracts often come with a Not-to-Exceed clause.
Choosing the right type
This means matching the contract structure to the situation. A fixed-price contract on scope-uncertain work forces the seller to pad estimates or fight for change orders; neither serves the project. Cost-reimbursable on stable, well-understood work leaves the buyer exposed to cost risk with little benefit.
Different contract types favor the buyer or the seller in the ownership of financial risk. These are shown below.
Fixed-price contracts can be difficult on agile projects because requirements evolve. One approach is incremental delivery contracts, which break a large SOW into smaller work packages, each with its own fixed price. As work progresses, the vendor can re-estimate remaining packages based on new information, and the buyer can reprioritize remaining work based on evolving priorities and costs.
2.5.4 Evaluate Vendor Performance
Awarding a contract is not the end of procurement management: it is the beginning of an ongoing performance relationship. Vendors need to be monitored against the terms they agreed to, not trusted to deliver without oversight.
Performance evaluation should be structured and periodic, not reactive and ad hoc. Define the performance criteria before the contract is signed: delivery schedule, quality standards, defect rates, response times, reporting requirements, and any regulatory or compliance obligations. Build these criteria into the contract so both parties have the same understanding of what good performance looks like.
Procurement Performance Review
A procurement performance review is a structured evaluation of vendor performance against contractual requirements. It covers work completed to date, quality of deliverables received, schedule adherence, cost performance against agreed rates or budgets, and responsiveness to issues and change requests.
Reviews should be documented, shared with the vendor, and used to inform decisions about continuing the relationship, adjusting payment, or activating remediation clauses. A vendor who receives only informal feedback cannot improve systematically; formal documented reviews create a shared record and a basis for action if performance does not improve.
Procurement Audits
At the close of a procurement, some organizations conduct a procurement audit to review the full lifecycle of the contract. The audit identifies what went well and where the process could be improved, providing lessons for future procurement activities. It also confirms that the seller provided all required products or services, that all invoices and payments are settled, and that any outstanding issues have been resolved.
Agile teams working with vendor-supplied components often bring vendor representatives into the iteration review process, so performance is visible at the cadence of delivery rather than being reviewed quarterly. Shorter feedback loops allow course-correction before problems compound.
Due to the popularity and growth of agile approaches, the need and interest in conducting procurement aligned to agile projects have expanded. Organizations such as Lean and Agile Procurement (LAP) have sprung up to provide examples, case studies and training. Project managers tasked with procurement in these environments will likely find many valuable ideas.
2.5.5 Verify Objectives of the Procurement Agreement are Met
A contract specifies what the seller agreed to deliver and on what terms. Verifying those objectives are met means confirming delivered work satisfies the contractual requirements before final payment or contract closure.
This is procurement-specific acceptance, distinct from the general project scope acceptance process. The questions here are: does the deliverable conform to the statement of work? Were quality standards met? Were regulatory and compliance obligations satisfied? Are there any open claims, disputes, or unresolved issues?
Verification should draw on the documented acceptance criteria in the contract or SOW. Before accepting and closing a contract, the project manager should confirm that:
- All deliverables in the SOW have been received and inspected
- Any defects or non-conformances have been remedied or formally waived
- All payments are reconciled against work completed
- Documentation, warranties, and operating materials have been handed over
- No open purchase orders or invoices remain unresolved
Formal contract closure is not a formality. It protects the buyer from future claims and gives the seller a clean release from their obligations.
Closing Procurements
Contracts are closed when the terms and conditions have been fulfilled. A written notice is typically provided to the seller to confirm the agreement is complete. Procurements can be closed at any point in the project lifecycle, not only at the end. Because a project often involves multiple procurements running at different timelines, contract closure activities may happen well before the project itself closes.
2.5.6 Participate in Agreement Negotiations
Project managers may participate directly in procurement negotiations, and sometimes lead them. Understanding the negotiation process and participating effectively makes the difference between a contract that works for the project and one that creates problems throughout delivery.
The negotiation lifecycle moves through several stages. First, determine whether a negotiated agreement is actually needed. Sometimes, after examining the situation, it makes sense to accept the other party’s position or to use a standard arrangement. When negotiation is warranted, the next step is understanding the problem and defining the goals clearly before any discussion begins.
During negotiation, build cooperative relationships with the people on the other side of the table, even when the discussion is competitive. People make concessions more readily for those they like and trust. A positive, patient approach builds credibility and creates a better environment for finding workable options.
Listen to understand the other party’s interests, not just their stated positions. Positions are what people say they want; interests are why they want it. Understanding the underlying interest often reveals options that satisfy both sides without either giving up their core need.
Preparation matters as much as conduct at the table. Before any negotiation, the project manager should:
- Know the bottom line: what outcomes are acceptable and at what point it makes sense to walk away
- Research the other party’s constraints and likely priorities
- Float trial balloons to test options before making formal offers: “What if we structured this as two phases?” surfaces reactions without committing
- Know the opening position, but ask for theirs first if possible
Once agreement is reached, capture it in writing promptly. For formal contracts, this means legal documentation. For internal team agreements, it may be a shared document or charter. Both parties need the same record of what was agreed.
2.5.7 Determine a Negotiation Strategy
The approach taken in a negotiation shapes what is achieved. Three broad strategies apply.
Hard (Controlling) Strategy
A hard or controlling strategy treats the other party as an adversary. It assumes that gains for one side come at the expense of the other. Hard negotiation can secure short-term advantage but often damages the working relationship, which matters when the parties will be collaborating throughout a project.
Soft (Accommodating) Strategy
A soft or accommodating strategy prioritizes the relationship over the outcome. Conceding quickly to maintain goodwill can reach agreements faster, but they are often poor ones. Persistent softness invites the other party to push harder.
Principled Strategy
A principled strategy separates the people from the problem. It focuses on interests rather than positions and looks for options that create genuine mutual gain. Principled negotiation takes more effort to reach an agreement, but outcomes tend to be more durable, and the relationship is better preserved. This is generally the most effective approach for project agreements, where the parties need to work together after the contract is signed.
People often assume negotiation is win-lose. In practice, a third outcome is usually available: a result where neither party loses, where both get enough of what they need to commit to the agreement. Finding that outcome takes longer, but it pays off in the delivery relationship that follows.
When preparing for and conducting negotiations:
- Develop working relationships with the people across the table
- Listen to understand their interests, not just their positions
- Explore suggestions to find options that work for both sides
- Use external standards and benchmarks as objective reference points
- Develop your best alternative to a negotiated agreement (BATNA) before the conversation starts
BATNA
The BATNA (Best Alternative to a Negotiated Agreement) is what the project will do if the negotiation fails to produce an acceptable outcome. A strong BATNA gives the negotiator confidence to hold a position. A weak BATNA means accepting a poor agreement may be the rational choice, so improving the BATNA before entering negotiation is worthwhile preparation.
2.5.8 Manage Suppliers and Contracts
Signing a contract is the start of the supplier relationship, not the end of the procurement work. Once a vendor is engaged, their performance needs to be tracked, their work integrated into the project plan, and the relationship actively managed throughout delivery.
Control Procurements
The control procurements process covers managing procurement relationships, monitoring contract performance, handling changes and corrections, and eventually closing contracts. Procurement activities are integrated into the overall project plan to confirm that:
- The vendor’s work is authorized to begin at the right time
- Performance is reported against cost, schedule, and technical expectations
- Change control covers contract scope, not just project scope
- Quality controls are in place for vendor deliverables
- Risks associated with vendor work are monitored and managed
Vendors and suppliers should be treated as project stakeholders. Add them to the communications management plan and manage their information needs the same way you manage those of internal stakeholders. Provide periodic progress reports, acknowledge their communications, and give formal acceptance of contracted deliverables.
Contract Change Control System
The contract change control system is the process used to collect, track, and communicate changes to a contract. It may be part of the project’s integrated change control system or a separate mechanism. Standard contract change types include:
- Administrative changes: Minor, non-substantive updates, such as adjusting payment terms
- Supplemental agreements: New additions negotiated separately from the original contract
- Contract modifications: Substantive changes to scope, deliverables, or timeline
- Constructive changes: Changes caused by buyer action or inaction rather than a formal request
- Termination: A contract may be ended due to vendor default, poor performance, or at the customer’s request
Disputes and Legal Concepts
Even well-managed procurement relationships can produce disputes. Project managers need to be familiar with a few legal concepts:
- Warranty: A promise, explicit or implied, that goods or services will meet a defined standard
- Waiver: The giving up of a contract right, even if it occurs inadvertently
- Breach of contract: Failure to meet the terms of the agreement, which may result in damages or litigation
- Cease and desist letter: A formal signal that legal action is forthcoming if the alleged violation continues
When disputes arise, the first response should be to work toward resolution through the mechanisms defined in the contract. Most contracts specify a dispute resolution process that must be followed before legal action is permitted.
2.5.9 Plan and Manage the Procurement Strategy
The procurement strategy sets the framework for how all procurement on a project will be conducted. Where individual procurement plans focus on specific purchases, the strategy governs the overall approach. This covers which contract types will be used, how vendors will be selected and coordinated, and how the procurement process will be managed across the project lifecycle.
Procurement Management Plan
The Procurement Management Plan is a component of the project management plan. It describes how the project will acquire external goods and services. A useful procurement management plan defines:
- The timetable of key procurement activities
- The types of contracts to be used for different categories of work
- The process for obtaining, evaluating, and comparing bids
- Which procurement documents will be used and when
- How multiple providers will be managed alongside each other
- Any prequalified sellers that the organization has already approved
Once in place, the procurement strategy needs to be actively managed. As project conditions change, procurement plans may need to adjust: new needs emerge, vendor performance shifts, or scope changes alter what needs to be bought.
Agile approaches create challenges for traditional fixed-scope procurement because requirements evolve and rigid SOWs can quickly become inaccurate. The Lean and Agile Procurement (LAP) approach addresses this by bringing vendors into collaborative planning rather than asking them to respond to a fixed statement of work. Vendors contribute their expertise to shaping the scope rather than simply responding to it. Incremental delivery contracts, which split a large SOW into smaller fixed-price work packages, also help by reducing the risk of over- or under-estimating a large block of work and allowing reprioritization as the project progresses.
2.5.10 Develop a Delivery Solution
Before procurement can be completed, someone has to decide how the work will be done and who will do it. Developing a delivery solution means deciding the best combination of internal capability and external sourcing to accomplish the project’s objectives.
This is the make-or-buy question applied at the project level. Which components are best performed by the project team? Which should be outsourced to a specialist vendor? Which should be acquired off the shelf?
The make-or-buy analysis weighs several factors. First, the team’s current capacity and skill set. Second, the cost and lead time of building capability internally versus sourcing it externally. Third, proprietary or security considerations that affect what can be shared with external parties. Fourth, the long-term value of building internal capability for work the organization expects to repeat.
For complex deliveries, the solution may split work across multiple sources, with the project responsible for integration. In those cases, the delivery solution defines the boundaries between components, the interfaces between vendors, and the coordination mechanism that keeps separately procured work connected and aligned.
Developing this solution early, before procurement documents are issued, prevents the common problem of writing requirements for work that has not yet been scoped at the delivery level. Vendors respond better to clear, well-bounded requirements, and the project avoids rework when a procurement fails because the work was not understood before it was contracted.
Deliverables and Tools
Procurement Management Plan — Document defining how the project will acquire external goods and services, including contract types, evaluation criteria, and supplier management approach.
Statement of Work (SOW) — A document describing a defined piece of work in enough detail for prospective sellers to determine whether they can deliver it.
Request for Information (RFI) — A solicitation document used to gather information from the market about available goods or services.
Request for Quotation (RFQ) — A solicitation document used to obtain price and delivery information from vendors.
Request for Proposal (RFP) — The most formal bid document, used when the solution is not straightforward and evaluation of approach is as important as price.
Source Selection Criteria — The set of attributes used to evaluate and compare vendor responses.
Qualified Vendors List — A list of pre-approved sellers that have met baseline standards for the type of goods or services being procured.
Fixed-Price Contract — A contract that sets a defined price for a defined scope, with cost risk carried by the seller.
Cost-Reimbursable Contract — A contract that pays the seller’s actual costs plus a fee, with cost risk carried by the buyer.
Time-and-Materials Contract — A contract paying an agreed hourly rate plus materials, suited to work where the level of effort cannot be determined upfront.
Contract Change Control System — The process used to collect, track, and communicate changes to a contract.
Procurement Performance Review — A structured evaluation of vendor performance against contractual requirements, conducted at regular intervals.
Procurement Audit — A review of the full procurement lifecycle conducted at or near contract closure to identify lessons for future procurements.
BATNA — Best Alternative to a Negotiated Agreement: what the project will do if a negotiation fails to produce an acceptable outcome.
Related Topics
- 2.1 Develop an integrated project management plan and plan delivery
- 2.2 Develop and manage project scope
- 2.6 Plan and manage finance
- 2.9 Evaluate project status
- 3.3 Manage and control changes
- 3.5 Plan and manage risk
- 1.4 Engage stakeholders
- 1.8 Plan and manage communication
- 2.10 Manage project closure
- 2.4 Plan and manage resources
- PMP Mind Map
FAQ
Why do project managers need to know procurement?
Procurement basics appear on the PMP exam, and the PM is almost always a critical stakeholder in procurement decisions.
What is the project manager’s role?
Provide project-specific information, monitor vendor performance for its impact on schedule and quality, and keep procurement activities integrated with the project.
What if the organization has a dedicated purchasing group?
The mechanics may be handled elsewhere, but the project manager remains a key stakeholder in procurement decisions.
How does this task fit into the 2026 PMP exam?
Task 2.5 sits in the Process domain of the 2026 Exam Content Outline. The 2026 PMP Exam page has the domain and task breakdown and what changed in the new exam.
