PMP Procurement Management: Contract Types, Negotiation and Vendor Management

Procurement management is the work of obtaining products, services or results from outside the project team: deciding what to buy, choosing a seller and a contract type, negotiating the agreement, managing the seller while the work is done and formally closing the agreement when its objectives are met. In PMI's PMP Examination Content Outline (July 2026) it is Task 5 of the Process domain, with ten enablers:

1. Plan procurement.
2. Execute a procurement management plan.
3. Select preferred contract types.
4. Evaluate vendor performance.
5. Verify objectives of the procurement agreement are met.
6. Participate in agreement negotiations.
7. Determine a negotiation strategy.
8. Manage suppliers and contracts.
9. Plan and manage the procurement strategy.
10. Develop a delivery solution.

Two ideas run through all of them. First, the contract is the governing document: what the seller must deliver, how performance is judged, how changes and disputes are handled and what remedies apply are all decided by its terms, not by informal conversations. Second, the project manager participates but usually does not hold contract authority; in most organizations a procurement or contracting officer is the only person who can legally bind the buyer. The project's own change control process, finance reserves and closure of the whole project belong to sibling tasks; this lesson covers the procurement side of each.

Procurement planning starts with a make-or-buy analysis: before any bid document is written, the team compares doing the work in-house with buying it from a seller on cost, risk, capability, schedule and control. The decision belongs before solicitation because it decides whether there is anything to procure at all.

A sound analysis counts the whole cost of each path:

• Direct costs such as purchase price, lease rate, labour, operation and maintenance.
• Opportunity cost: if the internal team builds something, the work they would otherwise do is delayed. When those people are on revenue-generating work, the value lost from that delay belongs in the cost of the "make" option. An internal estimate that looks cheaper can lose once this is added.
• Non-cost factors: skills the organization lacks, intellectual property and long-term ownership, confidentiality, and how much control the buyer needs over the work.

Lease or buy: the break-even calculation

For equipment, a one-step break-even calculation compares a daily lease with a purchase plus running cost. Break-even days = purchase cost ÷ (daily lease cost − daily running cost if bought). If the item is needed for longer than the break-even point, buying is cheaper on cost alone; for a shorter period, leasing is. For example, with a $9,000 purchase, $150 per day to run it and a $450 all-in daily lease, break-even is 9,000 ÷ 300 = 30 days. Always check what the lease price includes, and treat cost as one input alongside the non-cost factors above.

Once the decision is to buy, the buyer issues bid documents that match what it needs back from sellers. The choice depends on how well the need is defined and how sellers will be compared.

The procurement statement of work (SOW) describes the work being bought in enough detail that prospective sellers can decide whether they can do it and price it. Its quality shows up in the bids: if sellers each read the scope differently, their offers cannot be compared like for like, and the fix is to tighten the SOW so every seller prices the same thing. The SOW is also later the yardstick for acceptance, performance evaluation and disputes about scope, so ambiguity in it becomes a cost later.

The procurement management plan records how procurement will be run: the contract types to use, who holds authority, the source selection criteria and their weightings, the independent estimates, and the documents and timetable.

The right contract type follows from how well the scope is defined and who should carry the cost risk. Well-defined scope lets the seller price the work and carry the risk; poorly defined scope forces the buyer to carry it, because no seller can responsibly fix a price for unknown work.

The general rule: the less precisely the deliverable can be described today, the further the contract moves from fixed price toward cost-reimbursable terms, and an incentive fee keeps a cost-reimbursable seller motivated to save. When the buyer is really buying capacity (hours or people) rather than a defined deliverable, T&M fits, ideally with a not-to-exceed limit.

Incentive contracts: share ratios, fees and ceiling prices

Incentive contracts share any difference between the target cost and the actual cost between buyer and seller using a share ratio written buyer/seller. The seller's portion adjusts its fee: an overrun reduces the fee, an underrun increases it.

1. Variance = actual cost − target cost.
2. Seller's share = variance × seller's percentage.
3. Fee = target fee − seller's share of an overrun (or + seller's share of an underrun).
4. Total paid = actual cost + fee.
5. Fixed price incentive only: the buyer never pays more than the ceiling price; any cost above it falls entirely on the seller.

Worked example (FPIF): target cost $50,000, target fee $5,000, share ratio 70/30, ceiling price $60,000, actual cost $56,000. The overrun is $6,000; the seller bears 30% = $1,800, so the fee is $3,200 and the price is $59,200, under the ceiling, so that is what the buyer pays. Had the formula produced more than $60,000, the buyer would pay the ceiling.

Worked example (CPIF): target cost $80,000, target fee $8,000, share 80/20, actual cost $70,000. The underrun is $10,000; the seller earns 20% = $2,000 extra, so the fee is $10,000 and the buyer pays $70,000 + $10,000 = $80,000. Cost-plus contracts have no ceiling price; the buyer reimburses allowable cost.

Source selection means choosing a seller by scoring proposals against the weighted criteria agreed in the procurement management plan, not by price alone or by gut feel. A low-priced bidder with no relevant experience may still win if the weights favour price, or lose if technical approach and past performance carry more weight; the point is that the agreed method decides.

• Independent cost estimate: the buyer's own estimate of what the work should cost. A bid far below it (or far above it) is a signal that the seller may have misunderstood the SOW. An outlier bid is something to investigate before any award decision, typically by confirming what the seller understood the scope to be.
• Fairness: every prospective seller must have the same information. A question from one bidder is answered and the answer shared with all bidders, typically through a bidder conference or a written clarification. Private answers give one seller an advantage and can invalidate the process.
• Conflicts of interest: anyone with a personal interest in a bidder (for example a relative who owns the firm) discloses it to the procurement lead and steps aside from evaluating proposals, following the organization's procurement policy.
• Best and final offers: if the solicitation allows another pricing round, it is offered to every shortlisted seller on equal terms.

A negotiation strategy is prepared before meeting the seller. It ranks the buyer's objectives into must-haves and tradeable terms, sets a walk-away point, and decides the stance to take with the other party.

• BATNA (best alternative to a negotiated agreement): what the buyer will do if no acceptable deal is reached, such as turning to another qualified seller or a different sourcing route. A strong BATNA sets a realistic walk-away point. It is part of preparation, so the team can judge any offer against it the moment it is made.
• Collaborative stance: with strategic, long-term vendors the aim is a mutually workable agreement that preserves the relationship after signing, rather than winning every point.
• Decision authority: confirm beforehand who on each side can agree terms. A seller representative who must refer everything to head office (a limited-authority tactic) can reopen agreed points later; establishing authority up front prevents it.

On the buyer's side, the project manager participates in negotiation, bringing knowledge of the scope, schedule and risks, but commitments that bind the organization are made by whoever holds procurement authority, normally the procurement or contracting officer who signs the agreement. Anything proposed at the table that would change price or terms binds the buyer only once the authorized signatory agrees it, so the project manager's role is to analyse proposals and route them to that person.

Once the agreement is signed, the buyer manages the seller against the contract's terms. Vendor performance evaluation uses the measures the contract defines: performance reviews, inspections and audits, acceptance testing, and KPIs or service-level agreements (SLAs).

• Shortfalls: review the performance data with the vendor and apply the remedy the contract specifies (service credits, rework at the seller's cost, withheld payment). Remedies are applied as the contract sets them out and in proportion to the shortfall; ending the agreement is reserved for serious or persistent breach.
• Payment: pay what the contract's payment terms earn. When the payment terms tie money to accepted deliverables, the trigger for payment is the acceptance record, not any other indicator of progress.
• Needs the contract does not cover: a contract can only enforce what it states. When a business need emerges that the agreed measures do not capture, that is a gap in the terms, addressed with the vendor in a performance discussion and then through an amendment or renegotiated terms, because the seller is bound only to what it agreed.
• Privity of contract: the buyer's contract is with the seller, not the seller's subcontractors. Requests from a subcontractor are redirected through the seller.
• Integrating vendor staff: when vendor people work inside an agile team, the team events they must attend (reviews, retrospectives) should be in their SOW; changing the SOW goes through procurement.

Contract change control

Changes to what a seller must deliver go through the contract change control process and are recorded as an amendment, even on a firm fixed price contract. A new regulation that adds work outside the contracted scope is agreed as a priced amendment. When someone on the buyer side informally directs a seller to do extra work, the buyer has created a constructive change; the seller's request for payment is then handled as a claim under contract change control: the work and its value are assessed and, if valid, agreed as an amendment. Agile contracts with a dynamic-scope option allow equal-sized backlog items to be swapped within the agreement, but anything that changes price or end date, such as extra paid iterations, is still a contract change for procurement.

Claims and dispute resolution

A claim is a seller's (or buyer's) formal assertion that it is owed compensation or a change because of a disputed change, for example extra payment for work it believes was outside the contracted scope, or for cost caused by a buyer delay. Claims are documented, assessed on their merits and settled through the contract.

1. Assess the claim. Check the records against the contract. A fixed price covers the agreed scope under the agreed conditions; where the buyer's own action or inaction changed those conditions, the seller can be entitled to compensation or time even under a fixed price. Entitlement and amount are separate questions: first decide whether the claim has merit, then negotiate the amount.
2. Negotiate first. Direct negotiation between the parties is the preferred settlement.
3. Alternative dispute resolution (ADR). If negotiation fails, follow the contract's dispute clause, typically mediation or arbitration.
4. Litigation is the last resort; termination is a separate remedy for serious breach, not a way to settle a disagreement.

Claims should be settled before a procurement is formally closed; any that cannot be resolved are carried forward under the contract's dispute terms.

A procurement is closed when the buyer has verified that the objectives of the agreement are met: every deliverable has been accepted against the SOW and acceptance criteria, outstanding claims are settled (or, if they cannot be, handled under the contract's dispute terms) and final payment is made.

Closing a procurement then includes:

• Formal written notice to the seller that the contract is complete, normally issued by the person with procurement authority.
• Procurement audit: a structured review of the whole procurement process, from planning to administration, to find what worked and what didn't.
• Lessons learned and a record of the seller's performance for future source selection.
• Archiving the contract file.

A contract may also end early through termination for convenience or for cause, as its terms allow. Closing the whole project is a sibling task; procurement closure is one input to it.

The procurement strategy decides how each part of a purchase is packaged, contracted and delivered. The rule of thumb is to match each package to how well-defined it is: fixed specifications get fixed price; emerging requirements get T&M or cost-reimbursable terms. One project can, and often should, use different contract types for different packages.

• Phased procurement: when requirements are unclear today but a short discovery phase will define them, contract discovery separately (often T&M), then procure the build at a fixed price; each phase is a separate award decision.
• Delivery methods: design-bid-build keeps design and construction under separate contracts and gives the buyer control of design; design-build puts both under one contract, so one party is accountable for both and the phases can overlap, which usually shortens delivery; the trade-off is that the buyer specifies required performance instead of steering the detailed design.

Agile contracting techniques

Each technique answers one constraint, so the right combination follows from listing the buyer's constraints: a spending limit is answered by a cap, funding released in tranches by increments, a need to exit by a cancellation clause, and a long relationship with changing work by a master agreement. For example, a buyer expecting to use one vendor for several years on different work each year would keep the legal terms in a master agreement and put each year's work in its own schedule.

Developing a delivery solution means choosing who will produce the result and in what form: build in-house, outsource, form a mixed vendor-internal team, or buy and configure a commercial off-the-shelf (COTS) product. The choice is driven by the deadline, the capabilities the organization has, how standard the need is, and who must own and maintain the result afterwards.

Ownership after go-live is often the deciding condition: ask who will support, change and fix the result. An option that delivers quickly but leaves no internal capability moves the problem to after launch. Constraints such as data residency, security or integration with internal systems also shape where a bought product is hosted and run.