The Procurement Plan in World Bank-Financed Projects: Where It Comes From and How to Keep It Current

In an earlier article in this series, the Procurement Plan was described as a formal instrument, not a planning convenience. A Project Implementation Unit that proceeds with a procurement activity not reflected in the current approved plan (even for legitimate reasons) must seek Bank approval to update the plan first. Proceeding without that approval is a compliance failure, regardless of the procurement outcome.

This article explains where the Procurement Plan comes from, what it must contain, and what is required to keep it current throughout project implementation. It also covers two instruments that practitioners consistently underestimate: the Project Procurement Strategy for Development (PPSD), which is the strategic foundation of the plan, and the Annual Work Plan and Budget (AWPB), which must be aligned with it.

The governing framework throughout is the World Bank’s Procurement Regulations for IPF Borrowers (7th Edition – September 2025). Section 4 of those Regulations covers the PPSD and Procurement Plan, and is the primary reference for what is discussed here.

The Project Procurement Strategy for Development

During project preparation, before the Financing Agreement is signed and before implementation begins, the Borrower is required to prepare a PPSD.

The PPSD is a strategic document. Its purpose is to analyze the procurement environment and determine the most appropriate procurement approach for the specific project. It considers the country and sector context, the capacity of the implementing agency, the condition of the relevant market, and the risks likely to affect procurement performance.

Based on that analysis, the PPSD identifies the procurement approaches, methods, and packaging strategies best suited to achieving the project’s development objectives.

The PPSD is not a list of contracts. It is the reasoning behind the decisions that produce that list.

It is reviewed and agreed with the Bank during project preparation. In practice, preparing a credible PPSD requires proper market analysis and an honest assessment of institutional capacity. It is not a template to be completed merely to satisfy a checklist.

Borrowers who treat the PPSD as a formality often produce procurement plans that do not reflect market reality, institutional capacity, or implementation risk. When that happens, procurement planning becomes weak from the start, and implementation suffers accordingly.

From Strategy to Plan: The First Procurement Plan

The Procurement Plan is derived from the PPSD. Where the PPSD identifies the strategic approach, the Procurement Plan translates that approach into an operational instrument. It sets out, contract by contract, what will be procured, which method will be used, which review arrangement applies, the estimated cost, and the expected timeline.

The first Procurement Plan covers the initial phase of project implementation, typically the first eighteen months. It is prepared during project preparation and must be approved by the Bank before it becomes effective.

The Bank uses the Systematic Tracking of Exchanges in Procurement (STEP) system to upload, review, and approve the plan. STEP is the Bank’s standard platform for new Investment Project Financing operations, and most active projects now use it. Once approved, the Procurement Plan is publicly disclosed through STEP.

Older projects that have not been onboarded to STEP may operate under separate tracking arrangements agreed with the Bank. However, the requirements for approval and disclosure still apply, regardless of the system used.

The contents of the Procurement Plan are not optional. For each contract package, the plan must specify the procurement method, whether the contract is subject to prior review or post review, the estimated contract value, and the expected timeline for key procurement milestones. These entries are not merely indicative. They are the authorized basis for proceeding.

A Project Implementation Unit that begins a procurement activity not reflected in the approved Procurement Plan, even if the activity is clearly necessary and within budget, is not operating under valid procurement authorization. The plan must first be updated and approved before the activity can proceed.

The Procurement Plan and the Annual Work Plan and Budget

One relationship practitioners often underestimate is the alignment between the Procurement Plan and the project’s Annual Work Plan and Budget, commonly referred to as the AWPB.

The AWPB sets out the project’s planned activities and expenditures for a given year and is typically submitted to the Bank as part of project supervision. The Procurement Plan sets out the contract-by-contract schedule through which goods, works, and services will be procured.

These two instruments must be consistent. A Procurement Plan that schedules contracts whose values do not align with the budgeted allocations in the AWPB is a warning sign that supervision missions will scrutinize and a common finding during post review. Equally, an AWPB that includes activities for which no corresponding procurement has been planned or authorized creates an accountability gap that is difficult to explain under audit.

In practice, Project Implementation Units (PIUs) preparing or updating either document should treat them as companion instruments. Changes to the AWPB that affect procurement scope, timing, or budget should trigger a corresponding update to the Procurement Plan. The reverse is equally true. Discrepancies between the two documents are not merely administrative. They are a signal that project management may lack adequate control over implementation.

Updating the Plan During Implementation

The Procurement Plan is a living document. The Bank’s Procurement Regulations require it to be updated at least annually, and more frequently when circumstances require. Updates are not discretionary. They are part of maintaining procurement compliance throughout project implementation.

Circumstances requiring a plan update include changes in contract packaging or scope, adjustments to procurement method or review arrangement, significant changes in estimated contract value, and changes in implementation timelines that affect the procurement schedule.

These changes cannot be implemented unilaterally. Each update must be submitted to the Bank, reviewed, and approved before the revised plan becomes operative.

In STEP-enabled projects, the update process is managed within the platform. This creates a traceable record of each plan version, each submission to the Bank, and each no-objection issued. That record is material during post review and implementation support missions.

The frequency of plan updates is often a signal of how well the project was prepared. Projects with well-grounded PPSDs and realistic initial plans tend to require fewer mid-course corrections. Projects where the PPSD was treated as a formality often generate repeated plan amendments from the outset, each one adding time, effort, and management burden.

What Practitioners Often Miss

Three points are often underestimated by practitioners moving from national procurement systems to donor-funded environments.

First, the relationship between the PPSD and the Procurement Plan. In many national systems, procurement planning often starts from a budget line, with method selection determined later and sometimes informally. In World Bank-financed projects, the strategic rationale for each procurement approach should be documented in the PPSD before the Procurement Plan is prepared. A weak or superficial PPSD produces a plan without a sound strategic foundation.

Second, the alignment between the Procurement Plan and the AWPB. The Procurement Plan is not a standalone document. It sits within the broader project management framework, and the AWPB is its closest companion instrument. PIUs that manage the two documents independently create audit exposure and implementation risk.

Third, the operational significance of prior review timelines. When a contract is subject to prior review, the Bank must review and issue a no-objection at key decision stages, including the procurement documents, the bid evaluation report, and the contract award recommendation.

The Bank’s standard turnaround for prior review submissions is typically five business days for straightforward cases, but this can extend depending on the complexity of the transaction, the Bank’s workload, and the mission calendar. Some project agreements specify review periods explicitly. Where they do not, PIUs should agree expected turnaround times with the task team at the outset of each major procurement.

A Procurement Plan that does not build in realistic Bank review periods will produce a schedule that cannot be met, regardless of how efficiently the PIU performs its own work. Prior and post review are addressed in detail in the next article in this series.

The Plan as a Management Tool

Beyond its compliance function, the Procurement Plan is a management instrument. When prepared carefully, updated promptly, and used actively by the PIU, it gives both the Borrower and the Bank a reliable picture of where each contract stands, where delays are emerging, and what corrective action may be needed.

Practitioners who treat the Procurement Plan as a document to be updated only when the Bank asks for it are missing its operational value. Used properly, it is the primary tool for keeping project procurement on track.

In this series:

1. When National Procurement Rules Are Not Enough
2. Public Procurement vs. Donor-Funded Procurement: Key Differences
3. The Procurement Plan in World Bank-Financed Projects: Where It Comes From and How to Keep It Current (this article)
4. Prior Review and Post Review in World Bank-Financed Projects
5. Procurement Methods in World Bank-Financed Projects (coming soon)