Last Updated on May 11, 2026 by Jorge Lynch
In public procurement practice, evaluation is often treated as the decisive stage of the process. That is understandable. Evaluation is the point at which bids or proposals are examined, ranked, and a recommendation for award is made. It is also the stage most likely to attract scrutiny when there is a complaint, a challenge, or an audit review.
But in many public procurements, one of the most consequential decisions is made much earlier.
It is the decision on the procurement method.
More Than a Procedural Step
That point is sometimes overlooked because method selection is often treated as an early procedural step. In reality, it is much more than that. The selected method helps determine the scope of competition, the procedural path, the expected lead-time, the applicable transparency requirements, and the broad structure within which evaluation will later take place. In some cases, it also affects implementation directly, especially where one procurement depends on the completion, results, or deliverables of another.
In public procurement, of course, method selection is not simply a matter of preference. The applicable legal, regulatory, or donor framework defines the methods that may be used and the conditions for their use. In most systems, those conditions are tied to the procurement category, the estimated monetary value, and the nature and complexity of the requirement. In some cases, they also extend to specific circumstances, such as emergencies, limited competition, or other defined exceptions.
The Framework Sets Limits – Judgment Fills the Space
But that does not make method selection mechanical.
The framework sets the boundaries. It does not remove the need for judgment. Before the method can be chosen properly, the requirement must be correctly understood and classified. Estimated value must be realistic. Complexity must be assessed honestly. Risks must be considered in context. The practitioner must also decide whether the requirement should be procured on its own, combined with similar needs, or approached through some other arrangement permitted by the applicable rules.
Packaging, Consolidation, and Recurring Needs
This is where procurement planning becomes decisive.
A requirement that appears simple when viewed in isolation may call for a different approach when looked at more broadly. The purchase of one vehicle for one unit, for example, may fall within a relatively simple procurement approach under the applicable rules. But if similar vehicle needs across several departments are pooled into one requirement, the value, market interest, and procurement strategy may change significantly. What might have been handled one way as a stand-alone purchase may properly require a more competitive process once the requirement is consolidated.
The same is true of recurring needs. Repeated one-off procurements are not always the best answer simply because each individual purchase is small or familiar. Where the requirement recurs over time, and where the framework allows it, a framework agreement or similar arrangement may be more efficient, more economical, and more consistent with sound procurement planning than a series of disconnected procurements.
Emergencies illustrate the same point from another direction. Most frameworks recognize that exceptional circumstances may justify a different procurement method. But the existence of an emergency does not eliminate the need for discipline. The facts must genuinely support the use of the exception. Time pressure alone is not enough, especially where the urgency was foreseeable or arose from weak planning. A method that departs from normal competition may be legally permissible in exceptional circumstances, but it still requires careful justification.
Lead-Time, Sequencing, and Implementation Dependencies
Method selection also has direct implications for procurement lead-time, and therefore for implementation. Different methods involve different process durations, approval steps, advertising periods, evaluation burdens, and contract finalization requirements. Sometimes that affects only administrative efficiency. In other cases, it affects the viability of implementation itself.
That becomes especially important where procurements are dependent on one another. One procurement may need to be completed before another can begin. The deliverables under one contract may define the scope, technical approach, or timing of the next. In such cases, method selection is not merely a matter of procedural design. It is part of implementation planning. A method may be legally available and superficially defensible, yet still be poorly chosen if its likely lead-time is inconsistent with the sequencing needs of the project.
This does not mean that shorter methods should be chosen simply to accelerate implementation. Public procurement does not permit that kind of reasoning. The governing framework still controls what methods are available and under what conditions. But it does mean that procurement planning should take realistic lead-times and procurement dependencies into account from the outset. Where that is not done, delay is often built into implementation from the beginning.
For all these reasons, method selection should not be treated as a routine administrative step.
Yet that is often exactly how it is treated.
A requirement is classified too quickly. Complexity is understated. Estimated value is treated casually. Similar needs are not considered together. Recurring requirements are handled through repeated one-off purchases without asking whether a framework arrangement would be more suitable. An exception is invoked because time is short. Lead-time is considered too late. Dependent procurements are planned as though they were independent. In such cases, the chosen method may satisfy a superficial reading of the process while resting on weak planning and weak reasoning.
That is a serious weakness in public procurement practice.
Once the method has been selected, the rest of the process proceeds within the logic and constraints of that choice. If the selected method is poorly matched to the requirement, the market, the level of risk, the implementation sequence, or the governing framework, the procurement may be weakened from the outset. The process may still appear orderly. The file may still be complete. Evaluation may still be carried out properly. But the foundation may already be weak.
What Sound Method Selection Requires and Why It Must Be Recorded
This is why method selection deserves more disciplined attention than it often receives.
A sound choice of method in public procurement requires, at a minimum, correct classification of the requirement, correct application of the governing framework, a realistic assessment of value, complexity, lead-time, and relevant risks, and a clear justification for why the selected method is appropriate in the circumstances. In many cases, it also requires sound judgment on packaging, consolidation, recurring needs, procurement sequencing, and whether exceptional circumstances truly exist.
That justification does not need to be lengthy. But it does need to exist. It should be clear, specific, and placed on file before the process begins. It should show that the method was selected deliberately and on stated grounds, not adopted by habit or defended later for convenience.
That last point matters more than many practitioners admit.
Too often, the rationale for method selection is not recorded properly at the start. It is reconstructed afterward, usually when someone asks why competition was limited, why requirements were aggregated or divided in a particular way, why a framework agreement was not considered, why an exception was used, or why implementation was delayed by a procurement sequence that should have been anticipated. At that stage, the exercise is no longer one of procurement planning. It is an exercise in retrospective defense.
That is not good public procurement practice.
A well-managed procurement file should show that the method was selected prospectively and for stated reasons linked to the requirement, the estimated value, the complexity, the procurement strategy, the implementation sequence, and the applicable rules. This is not merely a matter of documentation. It is a matter of defensibility. When method selection is properly reasoned and recorded at the beginning, later scrutiny is easier to withstand. When it is not, even a procedurally correct process may appear arbitrary.
None of this means that evaluation is unimportant. It remains a critical stage. Nor does it mean that method selection is the only early decision that matters. Requirement definition, packaging, specifications or terms of reference, qualification criteria, evaluation criteria, contract structure, and implementation planning are also fundamental. A procurement can still fail if those elements are weak, even where the chosen method is appropriate.
But method selection is one of the earliest strategic decisions in public procurement. It is governed by rules, but it still requires judgment. It affects competition, transparency, lead-time, and implementation. For that reason, it should be treated with corresponding seriousness.
Practitioners who want to strengthen procurement quality do not always need to begin with evaluation forms or additional approval layers. In many cases, the better starting point is more basic. They should examine how procurement methods are being selected, on what grounds, and with what regard for the realities of implementation.
If methods are being selected through superficial classification, casual valuation, weak packaging decisions, poor sequencing, administrative convenience, or time pressure, that is one of the first practices that deserves closer scrutiny.
Because weak public procurement outcomes do not usually begin at evaluation.
They often begin much earlier.
—
Method selection — including its treatment under different regulatory and donor frameworks — is addressed in depth in Public Procurement: Principles, Categories, and Methods, 2nd Edition.