Before a Procurement Strategy Is Fixed
In many organisations, the first substantive procurement question asked is which strategy to use. Should the work go to a single contractor, an alliance, a design-and-construct arrangement, a managing contractor, a panel, a two-stage engagement, or something less conventional?
That question is important. It is also, in almost every case, being asked too early.
Procurement strategy is a downstream decision. The choice of model works only when a set of prior questions has been answered clearly. When those questions have not been answered, or have been answered by default rather than by design, the strategy is chosen against an incomplete picture of what it is meant to achieve. The organisation may still arrive at a contract. It rarely arrives at the outcome it set out to secure.
The failure mode is familiar. A strategy is selected early on the basis of what the organisation is used to, what the market seems to expect, or what senior stakeholders find comfortable. Downstream decisions then get shaped around the strategy rather than around the outcome. By the time the mismatch becomes visible, the tender has issued, the market has responded, and the room for correction has narrowed sharply.
Before the strategy question can be usefully answered, five earlier questions have to be resolved. Some of them will feel too basic to warrant discussion. That impression is usually the signal that they have not been resolved at all.
1. What is the organisation actually trying to secure?
This is the question most often assumed to have been answered when it has not.
Every procurement produces two things: a contract and an outcome. The contract is the visible artefact. The outcome is the reason the contract exists. When these two are treated as identical, the procurement is being organised around the wrong deliverable.
An organisation running a design-and-construct procurement to build a piece of infrastructure is not, ultimately, procuring a design and a construction. It is procuring an operational asset that has to work reliably for decades, integrate with adjacent systems, meet regulatory obligations that will evolve, and be maintainable by whoever operates it. The procurement strategy must be chosen against that outcome, not against the immediate deliverable.
Where this distinction is not held clearly, the procurement optimises for the delivery moment. Cost certainty at contract award. Programme certainty at execution. Assurance that the contract is signed cleanly. Each of these is legitimate. None of them is the outcome the organisation is trying to secure.
The clearest test is a simple question. If the contract were signed exactly as planned but the outcome the organisation intended was not delivered, would the procurement be considered successful? Where the honest answer is uncertain, the organisation has not yet defined what it is trying to secure.
2. What risks does the organisation actually need to allocate, and to whom?
Risk allocation is often described as a downstream question, settled inside the drafting of contract terms. It is not. It sits at the heart of the strategy decision, because the choice of model is largely a choice about who carries which risks under what conditions.
Every procurement model implies a particular risk architecture. Alliance models retain risk with the owner and share upside and downside collectively. Design-and-construct models transfer design and construction risk to a contractor. Managing contractor models retain some risk with the owner and pay the contractor to manage the rest. Panel arrangements distribute risk across multiple providers. Two-stage models defer risk allocation until later in the process, when more is known.
These are not neutral choices. They shape everything that follows: contractor selection, pricing behaviour, contingency setting, dispute exposure, and the organisation’s own delivery burden.
The prior question is which risks the organisation actually needs to allocate, and to whom. Some risks are best carried by the party with the greatest control over them. Some are best carried by the party best able to price them. Some can only be carried by the owner because no other party has the information or the authority to manage them. And some are better left uncovered, because insuring or transferring them is more expensive than accepting them.
When an organisation moves to strategy selection without this analysis, it usually inherits the risk architecture of the model it chose rather than choosing the model that produces the risk architecture it needs. The consequences appear later, in disputed variations, unexpected contingency drawdowns and gaps in responsibility no one anticipated. By that point, the risk allocation has already been made. It was made when the model was chosen.
3. What does the market need to see, and when?
Every procurement is also a communication with the market. The strategy chosen, the timing of its release, the way it is briefed, and the sequence of engagement all send signals that shape how respondents prepare.
Well-managed procurements pay attention to these signals. They understand that a market briefed six months early on an ambiguous scope will respond differently to the same procurement briefed clearly at the point of release. They understand that early informal engagement can strengthen the eventual field of respondents or, if handled poorly, contaminate it. They understand that the market’s read of the organisation’s intent influences whether the best respondents will invest in a compliant bid or a strategic one.
Signal management is not manipulation. It is honest communication of what the organisation intends, calibrated to the timing and format the market can act on. Where it is neglected, the field of respondents is narrower and less well prepared than it might have been. Where it is handled well, the organisation attracts the responses it actually wants.
Strategy selection made without regard to signalling risks producing a technically sound procurement that the market does not respond to well. The most common result is a smaller-than-expected field, more caveats than expected in the responses received, and evaluation panels asked to choose between a group of respondents none of whom have understood the procurement in the way the organisation intended.
4. Have the evaluation foundations been established before the strategy is fixed?
Evaluation criteria are often treated as a downstream decision, developed after the strategy has been chosen and refined during the tender preparation. This sequencing is defensible administratively. It is a strategic error.
The evaluation criteria are not just how respondents will be assessed. They are the operational definition of what the organisation is trying to secure. Until the criteria are drafted, the outcome the procurement is seeking exists only as intent. Once drafted, the criteria commit the organisation to a specific interpretation of that intent, expressed in a form respondents can meet, panels can score, and probity can defend.
Attempting to establish this after the strategy has been chosen exposes two problems. First, the strategy has already committed the procurement to a certain kind of respondent, a certain kind of offer, and a certain range of prices. The criteria are then drafted to fit what the strategy has already assumed. Second, weaknesses in the criteria are much harder to correct once the strategy is public, because doing so appears to change the terms of engagement mid-process.
The remedy is to establish the evaluation foundations before the strategy is fixed. Not the full criteria in final form, but the material questions the organisation will ask, the standards it will apply and the evidence it will require. Where these are settled early, the strategy can be chosen against them rather than in ignorance of them. Where they are not, the strategy is chosen against assumptions that may or may not survive contact with the criteria the organisation eventually adopts.
The Selection Decision essay addresses what makes evaluation criteria defensible. The point here is different. Defensibility begins with timing.
5. Is the governance authorised to make the decision the strategy will require?
Every procurement strategy implies a series of downstream decisions the organisation will have to make: shortlisting, tender evaluation, negotiation limits, award, contract execution and change management during delivery. Each of these requires an authority to be exercised at the right level.
Where governance and authority have been aligned to the strategy before it is chosen, these decisions can be made cleanly when they arise. Where they have not, the procurement encounters a series of authority questions during execution, each of which slows the process and dilutes accountability.
The prior question is whether the governance framework has the authority to make the decisions the chosen strategy will require, in the timeframes it will require them, at the levels of financial commitment involved. Where the answer is no, either the governance needs to be adjusted before the strategy is chosen, or the strategy needs to be chosen with the governance’s actual authority in mind. The one thing that should not happen is a strategy chosen against a governance framework that cannot support it.
Procurement strategy is not the first question. It is the culminating question. It becomes answerable once the organisation has resolved what it is trying to secure, which risks need to sit where, what the market needs to see, what the evaluation will actually test, and whether governance can carry the decisions the strategy will produce.
Strategy chosen without those foundations may still lead to a contract award. It cannot reliably lead to the outcome the organisation set out to secure.
