Procurement and Stakeholder Engagement Planning

Who Bears the Risk When Something Goes Wrong

Before a single contract is signed, the project has already made its most consequential procurement risk decision: who absorbs the cost when the work turns out to be harder, longer, or more expensive than expected? That question is not answered at the negotiating table. It is answered by the contract type chosen during planning, and the contract type is determined by one variable above all others: how clearly the scope is defined at the time of contracting. Get that match right and the procurement relationship works. Get it wrong and the consequences surface during execution as cost disputes, deliverables that are technically complete and practically wrong, or a vendor who bids low on unclear scope and then fights every change the project needs to make.

This chapter covers the two planning activities that close out the project management plan. Procurement planning defines how the project will acquire what it cannot or should not build internally, which contract structures fit which situations, and what the project commits to in writing before a vendor relationship begins. Stakeholder engagement planning takes the stakeholder register built during initiation and asks what it will take to move each person or group from where they are now to where the project needs them to be. Both activities are built during planning so that execution does not have to improvise the most relationship-critical decisions in the middle of the work.

The Make-or-Buy Decision

Every project need that sits outside the team's current capability or capacity represents a choice between building internally and procuring externally. The case for keeping work in-house is strongest when the team has both the relevant capability and the bandwidth to absorb the additional load, when the work involves sensitive or proprietary information that should not leave the organization, or when tight quality oversight and deep integration with other project activities make an external handoff genuinely risky. The strongest in-house case is when the work is central to what the organization does well and the team can take it on without pulling critical people from other priorities that the project also depends on.

The case for external procurement is strongest when the team lacks a specific skill set, when the timeline does not leave room to develop the capability internally, or when the organization simply cannot absorb the additional workload. Specialist contractors exist precisely for work that surfaces rarely in the project mix. Building an internal competency for a one-time engagement rarely makes financial sense when that competency will sit unused after the project closes. Cost can cut either way, and the analysis should model both options rather than assume the outcome before the numbers are examined. The make-or-buy decision must be documented. Record what was evaluated, what factors drove the choice, and what the implications are for cost, schedule, and risk. That documentation becomes load-bearing when the project is reviewed, when a vendor relationship changes mid-project, or when someone asks eighteen months later why a particular capability was contracted rather than built internally.

The Statement of Work — Defining What Is Being Purchased

If the decision is to procure, the next step is defining exactly what is being bought. The statement of work describes the scope the vendor must deliver: what work is included, what the timeline requires, what acceptance criteria the deliverable must meet, and any applicable standards or technical specifications. It becomes the foundation of the contract, the basis for the vendor's price, and the standard against which the project will hold the vendor accountable once the work begins.

A vendor cannot price work accurately without a clear statement of work, because they cannot know what they are committing to. The project cannot hold a vendor to a standard that was never written down, because there is no written standard to reference. Vague procurement begins with a vague statement of work, and the consequences arrive during execution as scope disputes over work that was always implied but never specified, and deliverables that are technically finished and functionally inadequate. A statement of work that is complete, specific, and testable is not a legal formality. It is the document that makes the vendor relationship manageable once the pressure of execution begins, and it is the project's only meaningful defense when a vendor argues that something outside the original scope is their problem to solve.

A complete SOW covers:

• Purpose and business need.
• Work included in scope.
• Work explicitly excluded from scope.
• Deliverables and acceptance criteria.
• Applicable standards, specifications, and technical constraints.
• Assumptions and dependencies.
• Vendor responsibilities.
• Buyer and project responsibilities.
• Milestones and reporting expectations.
• Change control path.

Contract Types — Who Bears the Risk

Three contract structures cover most procurement relationships, and each distributes financial risk differently between buyer and seller. The governing principle across all three is the same: the less defined the scope, the more financial risk the buyer carries. Contract type is not a payment preference. It is a risk allocation decision, and it should match the actual level of scope clarity the project has at the time of contracting.

Fixed Price Contracts

A fixed price contract exchanges a defined price for a defined scope. The seller commits to delivering exactly what the contract specifies at the agreed price and absorbs any cost overrun on that scope. That risk transfer is the appeal for buyers: the cost ceiling is set before work begins. The catch is that fixed price only delivers that protection when the scope is complete enough to price reliably. When a seller bids fixed price on uncertain scope, the bid either includes a large risk premium to cover what cannot be planned, or the delivery suffers when reality exceeds what the price covers. A fixed price contract is not inherently low-risk for buyers. It is only low-risk when the scope is genuinely well-defined.

Fixed price contracts come in three main forms. A Firm Fixed Price contract is the simplest version: one price for one fully defined set of deliverables, with no adjustment unless the contract is formally changed by mutual agreement. The seller absorbs all cost risk. Sellers can accept that risk comfortably only when their scope is well-understood and predictable. A Fixed Price Incentive Fee contract keeps a fixed price ceiling, which protects the buyer on cost, but layers in incentive payments tied to specific performance metrics such as early delivery, cost efficiency, or technical outcomes. The ceiling keeps buyer cost risk contained while making the contract more attractive to sellers whose work carries some uncertainty in approach. A Fixed Price with Economic Price Adjustments contract is designed for multi-year or cross-border engagements where currency fluctuations, inflation, or volatile material costs would otherwise make a locked price impractical over time. The price adjusts by a pre-agreed formula tied to specific economic indicators, rather than at either party's unilateral request.

Cost-Reimbursable Contracts

Cost-reimbursable contracts reverse the risk structure entirely. The buyer pays the seller's actual costs, and the profit is the part that is negotiated and fixed in advance. Both parties agree on what qualifies as a billable cost, how costs are documented and verified, and how the seller earns their margin above those costs. This structure fits situations where scope is genuinely uncertain: research and development, early-phase design, feasibility work, or any engagement where the full extent of the work becomes clear only by doing it. The buyer carries the financial risk of how expensive the work turns out to be. Active cost oversight from the buyer is not optional in these contracts.

Cost-reimbursable contracts come in several forms, and the difference between them matters considerably for how risk is distributed. Cost Plus Percentage pays the seller their actual costs plus a percentage of those costs as profit. This is the highest-risk structure for buyers: the seller's profit grows as costs grow, which eliminates the financial incentive to control costs efficiently. Cost Plus Fixed Fee pays actual costs plus a fixed fee that does not change with cost variation. The seller's profit is set regardless of whether the project runs over or under estimate, which creates a modest incentive to manage costs without rewarding inefficiency. Cost Plus Incentive Fee pays actual costs plus a base fee with additional incentive payments for meeting or beating defined targets on cost, schedule, or technical performance. The seller earns more by performing well, which aligns incentives more directly than a flat fixed fee does. Cost Plus Award Fee pays actual costs plus a fee structure where the majority of the profit is discretionary, awarded by the buyer based on a subjective performance assessment. This requires close collaboration and a rigorous evaluation process to function as intended. Without that structure, award fee decisions become arbitrary and the contract loses its motivating effect.

Time and Materials

Time and materials contracts pay the seller for hours worked at an agreed rate and for materials consumed at cost. The contract defines what constitutes a billable material or expense and sets the service rate. Scope is estimated, not fixed. That estimate is the buyer's only cost reference, and it carries no contractual force. For this structure to work without generating unpleasant surprises, there must be either a high level of trust built from a long prior relationship, or enough project controls to substitute for that trust: a not-to-exceed ceiling, weekly timesheet approval, defined work packages for each engagement period, and a named approver who can stop hours before spending exceeds authorization. Without those controls, hours accumulate at the agreed rate and the final cost is discovered rather than planned. Time and materials makes practical sense for short, closely monitored engagements where scope is still emerging. For larger, longer efforts, the buyer's exposure grows with every hour that passes without converting uncertain discovery work into defined, bounded deliverables.

Other Agreement Types

Not every procurement relationship is governed by a formal contract. A Memorandum of Understanding is a documented agreement on how parties intend to proceed, typically used to establish mutual expectations before a formal contract is finalized. It is not legally binding in the same way a contract is, but it creates a shared reference when work needs to begin before all terms are fully executed. A Service Level Agreement defines the performance standards for an ongoing service rather than a deliverable: response times for different support priority levels, uptime commitments, and the remedies that apply when those standards are not met. SLAs are common for IT services, facilities management, and any ongoing relationship where consistent service quality is what is being purchased, not a one-time output. Staff augmentation provides contracted personnel with specific skills to work within the project team, with no guaranteed outcome. The buyer directs the work; the seller provides the capability. This structure suits situations where the project needs a specific technical skill for a defined period and does not require the seller to take ownership of a deliverable or result.

Buyer and Seller Risk — Side by Side

Every contract type places a different burden on each party. The pattern holds consistently: as scope definition increases, risk shifts from the buyer toward the seller. As scope uncertainty increases, risk shifts back to the buyer. The table below maps each contract type against buyer and seller risk levels, with the key driver that explains the distribution. Choosing the wrong contract type for a given scope situation does not just create administrative problems. It creates misaligned incentives that compound throughout the relationship, producing disputes, cost overruns, or quality failures that a better-matched contract would have avoided.

Rows shaded red indicate highest buyer exposure. Yellow indicates shared or moderate risk. Green indicates risk has shifted substantially to the seller.

Selecting Vendors — The RFx Family

When a project needs to procure from an external vendor, the method used to solicit and select that vendor should fit the procurement situation. The RFx family covers the main options. A Request for Proposal invites vendors to propose how they would approach the work, not just what it would cost. It is appropriate when the project has a clear requirement but an open technology or methodology choice: the vendor's approach and fit matter as much as the price. A Request for Quotation is used when scope is defined and selection is based primarily on price: vendors quote against the same specification and selection is based primarily on the lowest compliant price. A Request for Information is used before the formal solicitation to gather market intelligence: understanding what vendors offer, what typical price ranges look like, and whether the intended procurement approach is realistic. An Invitation for Bid is a formal solicitation used primarily in government procurement, where a sealed bid process and public accountability requirements govern how work is awarded.

The method selected shapes the relationship from the start. An RFP process produces a vendor who has thought through the problem and proposed a solution the project evaluated and selected. A quotation process produces a vendor who priced work to a specification and was selected on cost compliance. The expectations that follow from each are different, and the contract type that fits each is usually different as well. A vendor selected through an RFP typically works on a more collaborative basis with some flexibility in approach; a vendor selected through a rigid quotation process is typically held to the precise specification that was quoted.

Evaluating vendor responses requires an explicit set of criteria applied consistently across all submissions. Without a defined evaluation framework, selection decisions are hard to defend and easy to challenge. The weights below reflect a typical balance; any specific procurement should adjust them to reflect what matters most for that contract.

One practical rule that projects routinely learn the hard way: every external procurement with a meaningful lead time must appear in the schedule as work, not as a note in the margin. Solicitation, vendor questions and responses, evaluation, contract review, approval, ordering, delivery, inspection, and acceptance can each consume days or weeks. Procurement is a schedule dependency, and a schedule that does not reflect it is already wrong at the moment it is baselined.

From Register to Engagement Plan

Procurement planning determines how the project manages its contractual dependencies. Stakeholder engagement planning addresses a different category of dependency entirely: the people whose behavior, decisions, and cooperation the project relies on but cannot simply contract for. A vendor can be directed through a statement of work. A department head who has concerns about the relocation cannot. A regulatory contact whose quiet resistance could delay a permit approval cannot be managed with a fixed-price contract and acceptance criteria. The stakeholder engagement plan is how the project handles those relationships deliberately, before execution creates conditions where there is no longer time to build them.

The plan begins with the stakeholder register built during initiation. That register identifies who the stakeholders are, what their interests are, and what influence each carries over project outcomes. It is the starting point, not the destination. Planning stakeholder engagement takes each person or group on that list and asks two questions: where is their engagement level now, and where does it need to be for the project to succeed? The gap between those two positions is the planning problem. The engagement plan specifies what the project will do to close it.

The Five Engagement Levels

Stakeholder engagement exists on a spectrum of five levels. Unaware means the stakeholder does not know the project exists or what it will mean for them. Resistant means they are aware and opposed. Neutral means they know about the project and neither support nor oppose it. Supportive means they are aware and in favor. Leading means they are actively championing the project and helping drive its success.

These levels are not fixed categories, and treating them as such is one of the most common mistakes in stakeholder management. A stakeholder who is currently resistant can move to neutral, and then to supportive, with the right engagement at the right time. A stakeholder who is currently at Leading can drift back toward neutral if the relationship is not maintained as the project progresses and their attention moves elsewhere. The engagement plan is built around managing those movements: creating the conditions that accelerate the changes the project needs and preventing the backslides that create friction and delay during execution.

The Engagement Matrix — Mapping the Gap

The engagement matrix maps each stakeholder group against the five levels and marks two positions: C for their current level of engagement and D for their desired level. When C and D are in the same column, engagement is where it needs to be, though that position still requires active maintenance rather than neglect. When they are in different columns, there is a gap, and the gap is exactly what the engagement plan commits the project to addressing. The matrix makes the planning problem concrete. "The operations director needs to move from neutral to supportive before the move window" is a solvable planning problem. "We need better stakeholder buy-in" is not.

C = Current engagement level. D = Desired engagement level. Each gap between C and D represents a planned engagement action.

The RtR matrix surfaces several distinct situations. Warehouse and Office staff are currently unaware the relocation is happening, which means the first engagement action is simply informing them, followed by the work of moving them toward active support before their cooperation is needed during the move itself. Residential Teams are resistant; moving them to neutral requires understanding what is driving that resistance before designing any engagement response. Commercial Teams are neutral but represent the project's primary business justification: the relocation exists to serve their growth, and the desired level is Leading rather than merely Supportive, because their active championing of the project's success is part of what makes it work. The Service Department is already at its desired level and needs maintenance, not movement.

Mapping the gap is analysis. Closing it requires planned action. The engagement plan pairs each gap with a specific response, an owner, and a timing target before execution begins.

The Power-Interest Grid — Prioritizing Engagement Effort

Not every stakeholder can receive equal engagement attention, and attempting to treat them all identically is both inefficient and counterproductive. The power-interest grid provides a practical framework for prioritizing where the project's relationship-building effort goes. It maps each stakeholder on two dimensions: their authority to affect project outcomes, and their level of interest in those outcomes.

The grid does not replace the engagement matrix. It helps decide where to concentrate effort when the project cannot give every stakeholder equal time. A high-power, low-interest executive needs periodic high-level briefings and a clear path to reach the PM when a decision requires their input, not a weekly status report they will never read. A high-interest, low-power employee group needs regular updates in a format they can actually consume, and acknowledgment that their perspective was heard, without being pulled into decision-making forums where they have no authority. The misallocation that creates the most project risk is neglecting the high-power stakeholder with low current interest: a sponsor who has been kept satisfied but not closely engaged can become a blocker at the moment the project most needs their support, precisely because the relationship was treated as maintenance rather than management.

The salience model offers a more nuanced alternative when the power-interest grid alone is not sufficient to prioritize a complex stakeholder landscape. Where the grid maps authority against interest level, the salience model evaluates three dimensions: power (the ability to impose will on the project), legitimacy (whether the stakeholder's involvement is appropriate and justified), and urgency (how time-sensitive their claims are). Stakeholders who score high on all three warrant the highest priority; those who score high on only one dimension may hold authority or urgency without the legitimacy or power to act on it directly. The model is most useful on large, politically complex projects where different stakeholders hold very different combinations of authority and time sensitivity, and where the two-axis grid is too coarse to guide engagement decisions with the specificity the project needs.

Closing the Gap — Influence, Not Broadcast

A stakeholder gap does not close by sending more reports. The method of closing the gap depends entirely on what is driving it. Moving a stakeholder from resistant to neutral requires understanding what the resistance is actually about: what they stand to lose, what concern has not been addressed, what they need to feel heard before their position can shift. Sending a resistant stakeholder the same communication package that works for a supportive one is not engagement planning. It is communication planning applied to the wrong problem.

Moving a stakeholder from neutral to supportive often means demonstrating that their interests are genuinely reflected in the project, not that the project needs their support but that the project has already accounted for their needs in the decisions it has made. Moving a stakeholder from supportive to leading requires finding the specific reason that person would personally invest their credibility in the project's success, which is usually tied to how the project's outcome connects to something they care about beyond the project itself. The goal is not to maneuver people toward a predetermined position. It is to understand their legitimate concerns, address what the project can address, and build support through transparency, involvement, and demonstrated respect for their interests. The engagement plan specifies the actions, conversations, and involvements that will be used to close each identified gap. It is an influence strategy built around specific people and specific dynamics, not a communication broadcast schedule. The distinction is sharpest when a stakeholder's current position directly affects a project decision that cannot wait: a department head whose approval is needed at a critical milestone, or a regulatory contact who has the authority to delay a permit. Those gaps must be closed before the milestone is reached, not during it.

Handling the Plan With Discretion

The stakeholder engagement plan contains honest assessments of real people: their current position on the project, the concerns driving their resistance or passivity, and the project's strategy for shifting that position. That is not information for wide distribution. Sharing it carelessly can damage the very relationships it was built to protect. A stakeholder who discovers that their resistance has been formally catalogued and that a strategy for moving them exists may respond in ways that make the engagement harder, not easier. Keep the plan with the people who need it to act on it, and handle it with the discretion appropriate to any document that includes frank assessments of individual motivation and behavior. The value is in the thinking and the action it guides, not in the artifact itself being widely visible.

Planning Is Complete — Execution Begins

With procurement and stakeholder engagement planning complete, the project management plan is ready for the approval process. Every subsidiary plan has been developed: scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement. The three baselines are approved through the project's governance process, and changes after that point are managed through formal change control rather than informal adjustment. The project now has documented answers to the questions that will govern everything that happens during execution: what was planned, who is accountable for what, what the project will do when things go differently than expected, and how the project will communicate and manage its key relationships. The planning phase does not disappear when execution begins. The plans become the reference points against which every decision, variance, and adjustment during execution is measured. They are what makes the difference between a controlled project and a reactive one.

What's Next

The next chapter, Executing, covers what happens when planning transitions to delivery: directing and managing the work, acquiring and developing the team, managing quality and knowledge, and responding to the reality that no plan survives contact with execution exactly as written. Planning describes what the project intends to do. Executing is the test of whether the planning was good enough to guide the work through what actually happens.

Reflect

• In a current or recent project, how was the make-or-buy decision made? Was it documented, or did it disappear into a conversation that no one can reconstruct six months later?
• When you last selected an external vendor, did the contract type match your actual level of scope clarity at the time of contracting? What was the consequence if it did not?
• Which stakeholders in your current project have the largest gap between their current and desired engagement level? What is driving that gap, and what would it take to close it?
• Where in your experience has a high-power, low-interest stakeholder become a blocker at a critical moment because the relationship was treated as maintenance rather than active management?