A detailed procurement plan can execute the wrong commercial idea with great efficiency.
Projects often use the words strategy and plan as though they describe different levels of the same document.
They do not.
The Week 1 procurement framework distinguishes corporate procurement strategy, project procurement strategy and procurement planning. Corporate strategy links procurement activity to organisational objectives and policies. Project procurement strategy connects sourcing choices to the operating environment of a particular project. Procurement planning then identifies what should be procured, how, how much and when.
That distinction is more than terminology. Strategy defines the logic of the choice. Planning organises the execution of that choice.
When leaders confuse the two, procurement teams can become extremely busy without resolving the decisions that matter.
The Strategic Context
Consider two projects that both need a specialist engineering package.
Project A decides that the work contains proprietary knowledge and should remain largely internal, using an external specialist only for a narrow verification task.
Project B decides that speed and access to scarce expertise matter more than retaining the work internally, and sources an integrated external package with knowledge-transfer requirements.
Both projects may create procurement plans. Both may have schedules, tender documents, approval gates and contract registers.
But the plans are implementing fundamentally different strategies.
The distinction matters because procurement strategy answers questions about boundaries, relationships, risk and value before planning answers questions about sequence and process.
What Leaders Commonly Misread
A procurement schedule is a strategy
A schedule shows timing. It does not explain why one sourcing route is preferable to another.
A sophisticated spreadsheet can conceal an unresolved commercial decision.
A standard contract equals a standard strategy
Templates improve consistency, but contract form should follow the nature of the work. High uncertainty, complex interfaces or collaborative innovation may demand different commercial behaviour from a simple, well-specified purchase.
Using the organisation’s familiar contract does not prove that the strategy fits the requirement.
Procurement strategy belongs only to procurement specialists
The source material presents corporate procurement strategy as connected to organisational objectives and project procurement strategy as connected to the project environment. That requires input beyond the procurement function.
Project leaders know schedule and integration. Engineering knows technical uncertainty. Operations knows lifecycle requirements. Finance understands funding and affordability. Procurement understands market structure and commercial mechanisms.
Strategy emerges from the interaction of these perspectives.
Reframing the Issue
A useful distinction is:
Procurement strategy decides how the organisation wants the market to help create value. Procurement planning decides how that intention will be executed and controlled.
This provides a hierarchy.
At enterprise level, policy may define probity expectations, delegated authority, preferred sourcing principles, sustainability conditions or rules for competitive tendering.
At project level, leaders decide the delivery and sourcing model, packaging, supplier relationship, market approach, risk allocation and evaluation logic.
At planning level, teams build the procurement schedule, documentation, approvals, tender activities, evaluation process, negotiation steps and contract-management arrangements.
Each level constrains the level below it.
Strategic Analysis
Strategy starts with the outcome
Before asking what to buy, identify the project outcome and the role external capability must play.
If the outcome is uncertain, strategy may need to preserve flexibility. If the product is highly standardised, strategy may prioritise efficient competition. If the work creates long-term operational dependency, supplier continuity and exit options may deserve more weight.
Strategy determines packaging
Breaking work into packages can increase competition, reduce dependency or provide specialist access. It can also create more interfaces, more contracts and more coordination burden.
Bundling work can simplify accountability but may reduce market competition or place the organisation into a more dependent relationship.
Packaging is therefore a strategic choice about integration and control.
Strategy determines the relationship model
The supplied framework notes traditional lump-sum contracts alongside collaborative arrangements, partnering and early contractor involvement.
The important lesson is not that newer models are better. It is that different project conditions require different commercial behaviours.
Where scope is stable and interfaces are simple, price competition may work well. Where scope is evolving and parties must solve problems jointly, aggressive risk transfer can create defensive behaviour and claims rather than value.
Planning turns choices into control
Once the strategy is explicit, procurement planning can answer practical questions:
- What needs to be procured?
- When must the market be approached?
- What documentation is required?
- Which suppliers are eligible?
- What evaluation criteria will be used?
- Who approves each stage?
- What information must be available before release?
- How will changes and supplier performance be controlled after award?
Planning is indispensable. It is simply not a substitute for strategy.
A Hypothetical Test: The Same Requirement, Two Different Strategies
Consider a hypothetical manufacturer planning a new automated inspection cell.
The project needs cameras, software, mechanical integration and ongoing support. One team immediately develops a procurement schedule: specification in March, tender in April, award in May, installation in August. The plan is clear, but it says nothing about the commercial architecture.
A second team begins with strategy. It determines that image-processing knowledge could become important to future product development, while mechanical fabrication is mature and readily available in the market. It therefore retains software architecture and data ownership internally, competitively tenders the mechanical package, and uses a specialist vision supplier under a model that includes knowledge transfer and access to configuration data.
Both teams can produce excellent procurement plans. Only the second has first decided what capability should remain internal, what can be commoditised and what relationship is needed with the market.
This is the practical difference between strategy and planning.
At program and portfolio level, the distinction becomes even more important. If several projects independently outsource similar specialist capabilities, the organisation may create a strategic dependency without ever making an explicit enterprise decision. Portfolio governance should therefore look across project procurement strategies to identify repeated sourcing patterns, common suppliers, competing demand and capabilities that may deserve enterprise investment.
Decision Framework
Leaders can test whether they have a strategy or merely a plan by asking two sets of questions.
Strategic questions
- Why is external supply preferable?
- What value must the commercial model protect?
- How should the work be packaged?
- What supplier relationship is required?
- Which risks should each party control?
- What capability or knowledge must be retained?
- How reversible is the sourcing decision?
Planning questions
- What procurement activities are required?
- In what sequence?
- By which dates?
- With which approvals?
- Using what documents and evaluation process?
- Who owns each activity?
- How will progress and compliance be reported?
If the project can answer the second set but not the first, the procurement process is operationally prepared but strategically weak.
From Strategy to Execution
Immediate action: separate the procurement strategy from the procurement plan in governance reviews. Require a concise strategy statement that explains the sourcing logic before approving the detailed procurement schedule.
Medium-term capability: develop a small number of strategic sourcing archetypes rather than one universal process. Examples could include commodity purchase, specialist professional service, integrated work package, collaborative high-uncertainty delivery and long-term outsourced service.
Long-term positioning: use completed procurements to test whether strategies produced the intended outcomes. Capture not only contract compliance but value, claims, supplier behaviour, internal workload, knowledge transfer and lifecycle effects.
Related article: From Lowest Price to Best Value: The Economics Leaders Miss in Procurement
Signals to Monitor
A project may lack procurement strategy when different team members give different answers about why a supplier is being engaged, when the delivery model is chosen primarily because a template already exists, or when evaluation criteria are created after the market approach has already been selected.
Another signal is a procurement plan that tracks dozens of milestones but contains no explicit statement of retained capability, risk allocation or supplier relationship.
That is administration without commercial intent.
Questions for the Leadership Team
- What is the procurement strategy trying to achieve beyond completing the sourcing process?
- Which enterprise objectives or policies constrain the project’s sourcing choices?
- Is the proposed packaging reducing risk or simply moving coordination work somewhere less visible?
- Which supplier behaviours does the contract model encourage?
- What assumptions must be true for the strategy to outperform the alternatives?
- How will the project know whether the strategy, not just the tender process, succeeded?
Closing Perspective
Planning answers how.
Strategy answers why this commercial arrangement, why this boundary, why this market approach and why this allocation of control.
A mature organisation needs both. But the order matters.
When strategy is absent, procurement planning can turn into disciplined execution of an unexamined assumption. When strategy is clear, planning becomes what it should be: the mechanism that converts a deliberate commercial choice into controlled action.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.