Last Updated on June 16, 2026 by Jorge Lynch
The previous article in this series explained that prior review timelines must be built into every realistic procurement schedule. A Procurement Plan that does not account for Bank review periods will produce a schedule that cannot be met, regardless of how efficiently the implementing agency performs its own work.
This article explains what prior review and post review mean, when each applies, what the Bank examines under each arrangement, and what the practical consequences are for Project Implementation Units (PIUs) that need to keep procurement moving while maintaining audit-ready files.
The governing framework throughout is the World Bank’s Procurement Regulations for IPF Borrowers (7th Edition – September 2025). Paragraphs 3.1 through 3.10 of those Regulations address the Bank’s review of procurement decisions.
What Prior Review Means
Prior review means that, before the PIU can proceed to the next stage of a procurement process, it must submit the relevant documents to the Bank and receive the Bank’s no-objection.
A no-objection is not an automatic step. It is a substantive review. The Bank examines the documents submitted and determines whether the procurement has been conducted in compliance with the Procurement Plan and the Procurement Regulations. If the Bank identifies deficiencies, it will not issue a no-objection until those deficiencies are addressed.
In a typical prior review procurement, three stages commonly require a no-objection. The first is the procurement documents stage. Before the PIU issues the request for bids, request for proposals, or request for quotations to the market, the Bank reviews and clears the draft documents. The second is the evaluation report stage. After bids or proposals are received and evaluated, the Bank reviews the evaluation report before the PIU communicates the result to bidders or proposers. The third is the contract award stage. Before the contract is signed, the Bank reviews and clears the award recommendation.
A PIU that proceeds beyond any of these stages without a valid no-objection is not in compliance with the financing agreement. That remains true even where the underlying procurement decision may have been sound.
When Prior Review Applies
Prior review does not apply to every contract. It applies to contracts that the Bank has designated as subject to prior review in the Procurement Plan, based on value thresholds and risk considerations.
The specific thresholds are set for each project. They reflect the Bank’s assessment of the project’s procurement risk, the implementing agency’s capacity, and the nature of the contracts involved. High-value contracts are typically subject to prior review. The Bank may also designate lower-value contracts for prior review if the risk profile warrants closer scrutiny.
The review arrangement for each contract is recorded in the Procurement Plan in the Systematic Tracking of Exchanges in Procurement (STEP) system. That entry should not be treated as permanent. If circumstances change and the Bank determines that a particular contract warrants closer scrutiny, the review designation can be changed. PIUs should therefore check the current approved Procurement Plan, not an earlier version, before beginning any procurement.
Factors that can cause prior review thresholds to change
Several factors can cause prior review thresholds to change during implementation. This matters because a threshold change is not merely administrative. It can significantly affect how much of a PIU’s procurement workload becomes subject to Bank scrutiny.
The most common driver is a change in the project’s procurement risk rating. Thresholds are tied directly to the Bank’s assessment of that risk, which is generally classified as High, Substantial, Moderate, or Low. Post review exercises support this process because one of their objectives is to provide a basis for updating the project’s procurement risk rating. If a post review reveals poor performance or systemic weaknesses, the risk rating may be increased, which can lower the financial thresholds and bring more contracts under prior review. The reverse is also possible. A project that demonstrates consistently sound procurement performance may see its risk rating reduced, with thresholds adjusted accordingly.
The Bank’s Accredited Practice Manager also has formal authority to request a change in prior review thresholds for a specific project, subject to approval by the Chief Procurement Officer. This mechanism can be used to address a Borrower’s capacity constraints, situations of fragility, or other project-specific vulnerabilities that make standard thresholds inappropriate.
In emergency situations involving natural or man-made disasters or conflict, standard prior review thresholds may not apply in the usual way. The Chief Procurement Officer can provisionally increase the accreditation thresholds granted to procurement staff, allowing clearances to be expedited in support of a rapid response.
The No-Objection and What It Does Not Mean
A no-objection from the Bank is an authorization to proceed. It is not a guarantee of correctness, and it is not a transfer of responsibility for the procurement outcome.
The Bank’s Procurement Regulations are explicit on this point. A no-objection does not relieve the Borrower of responsibility for the accuracy and adequacy of the information submitted, or for the soundness of the procurement decision. If the PIU submitted documents that were inaccurate or incomplete, a no-objection issued on that basis does not protect the Borrower from later scrutiny.
This matters because some PIU staff treat a no-objection as closing the file on a given stage. It does not. The records must still support the decision. If a post review or audit later reveals that the documents on which the no-objection was based were misleading, incomplete, or incorrect, the fact that a no-objection was issued provides no protection. This is why the Bank’s standard no-objection language usually begins with words to the effect that, “based on the information provided,” the no-objection is granted. That wording is a clear signal that the review is conditional on what the PIU submitted. It is not an independent verification of the accuracy or completeness of the procurement records.
Building Prior Review Time into the Procurement Schedule
The Bank’s standard turnaround for prior review submissions is often shorter for straightforward cases under simplified procedures and longer for complex transactions or submissions requiring technical review by Bank sector specialists. Some project agreements specify review periods explicitly. Where they do not, PIUs should agree expected turnaround times with the Bank’s task team at the outset of each major procurement.
The practical implication is that every stage in a prior review procurement has two lead times: the time the PIU needs to prepare and finalize the documents, and the time the Bank needs to review them. Procurement schedules that plan only for the first lead time will consistently miss their targets.
A realistic procurement schedule for a prior review contract might include sixty days to prepare and finalize the procurement documents, ten working days for Bank review at that stage, ninety days for the bidding period and evaluation, ten working days for Bank review of the evaluation report, and a further ten working days for Bank review of the award recommendation before the contract can be signed. That is a minimum schedule of approximately six months from the decision to go to market to contract signature, before accounting for any resubmissions required.
In practice, even that estimate may be conservative. It covers Bank review windows but does not account for delays in the Borrower’s own internal approval processes, which frequently extend the overall timeline beyond what the procurement calendar alone would suggest. Internal authorizations, committee approvals, and sign-off requirements within the PIU or line ministry can add weeks at each stage, and those delays accumulate.
The schedule also depends on the procurement method in use, which determines how the solicitation is structured, how long the bidding period must be, and what evaluation procedures apply. Procurement methods in World Bank-financed projects are the subject of the next article in this series.
PIUs that plan for three months on a process that realistically requires six months should not be surprised when they miss the target by three months.
What Post Review Means
Post review is conducted after the procurement process is complete and the contract has been awarded, or in some cases after the contract has been implemented. The Bank examines a sample of contracts that were not subject to prior review to assess whether they were procured in compliance with the Procurement Plan and the Procurement Regulations.
Post review is not a lower standard of scrutiny. It is different timing, not a lower bar. The documentation requirements for a post review contract are the same as for a prior review contract. The PIU must be able to demonstrate, on the basis of its procurement file, that the method selected was appropriate, the process was competitive, the evaluation was conducted fairly and in accordance with the stated criteria, and the contract was awarded to a qualified and compliant bidder or proposer.
The Bank’s task team typically selects the sample for post review during supervision missions, although the Bank may also conduct stand-alone post review exercises. The selection is not purely random. The Bank may give additional attention to contracts where supervision data, complaints, delays, amendments, or other signals suggest procurement risk.
What the Bank Looks at During Post Review
During post review, the Bank examines the procurement file for each selected contract. That file should contain, at minimum, the approved entry in the Procurement Plan authorizing the procurement; evidence that the procurement method was applied correctly, including any required market survey or quotation documentation; the procurement documents, where applicable; records of any advertisement or solicitation; the bids or proposals received; the evaluation report; the award notification and any required standstill period documentation; and the signed contract.
If the file is incomplete, the Bank cannot verify compliance. An incomplete file is itself a finding, regardless of whether the underlying procurement was in fact conducted properly. PIUs that rely on staff memory to reconstruct what happened, rather than on contemporaneous documentation in the file, will not survive post review.
The Bank’s findings from post review are reported through project supervision and implementation reporting channels. A pattern of weaknesses across multiple contracts will typically result in a request for a procurement action plan and may affect the Bank’s assessment of the overall procurement risk rating for the project.
In serious cases, where the Bank determines that a contract was not procured in compliance with the Financing Agreement and the Procurement Regulations, it may declare the contract misprocured. The consequences of misprocurement can include ineligibility of the contract expenditure for financing, meaning the Borrower bears the cost.
A Common Misunderstanding About Post Review
Perhaps the most common misunderstanding about post review is that it applies to lower-risk contracts and therefore requires less care. That is not accurate.
Post review contracts are below the prior review threshold, meaning the Bank does not review them before they proceed. But that is a function of value and risk tiering, not a signal that documentation standards are relaxed. The Procurement Regulations apply to all procurement under the project, regardless of review arrangement.
The practical consequence is that a PIU may conduct and close dozens of post review contracts over the life of a project, with no Bank scrutiny at any stage. Then, during a supervision mission, the Bank selects a sample and reviews the files. If those files do not support the procurement decisions they purport to record, the PIU faces findings across a body of completed work, some of which may date back months or years.
Maintaining documentation discipline on post review contracts from the moment the procurement begins, not after the fact, is the only reliable protection against this outcome.
What Practitioners Should Know
Three points stand out for practitioners managing procurement in World Bank-financed projects.
First, the review arrangement is contract-specific and can change. Do not assume that the prior or post review designation in the initial Procurement Plan is permanent. If the Bank adjusts the designation for any contract, the change will be reflected in the updated plan in STEP. PIUs should check the current plan before beginning procurement.
Second, a no-objection is not an approval of the procurement outcome. It is an authorization to proceed based on the documents submitted. The Borrower retains responsibility for the completeness and accuracy of those documents and for the soundness of the procurement decision they support.
Third, post review applies to a high volume of contracts, and the documentation bar is the same as for prior review. PIUs that give post review procurement less systematic attention than prior review procurement are building a risk exposure that typically becomes visible at the worst possible moment: during a supervision mission or an audit.
The next article in this series addresses procurement methods in World Bank-financed projects: when each method is available, what conditions must be met to use it, and where practitioners most often go wrong in method selection.
In this series:
- When National Procurement Rules Are Not Enough
- Public Procurement vs. Donor-Funded Procurement: Key Differences
- The Procurement Plan in World Bank-Financed Projects: Where It Comes From and How to Keep It Current
- Prior Review and Post Review in World Bank-Financed Projects (this article)
- Procurement Methods in World Bank-Financed Projects (coming soon)