Preparing for World Bank, ADB, EBRD and IsDB-financed tenders

The most common mistake is treating World Bank, ADB, EBRD and IsDB procurement as one template with different logos. The institutions share principles, but the applicable process, evaluation method and document set change by project.

International financing can offer a more predictable procedure and stronger contract discipline, but it also demands a high standard of preparation. “Approximately” meeting a qualification criterion, describing a reference only in marketing language or searching for key experts in the final week rarely produces a competitive submission.

The financing institution is not always the direct purchaser. Procurement is generally conducted by the borrower, beneficiary or project implementation unit, while the financier applies its policy, review and eligibility framework. The financing agreement, procurement plan, standard document, project data sheets, addenda and national law can therefore be as important as the notice itself.

Read the procurement architecture first

Each opportunity should be reviewed across five layers:

1. Financing and project framework: the financing agreement, project procurement strategy/plan and the financier’s review arrangement.
2. Institutional policy: the applicable procurement policy, regulation, directive or guideline and its current edition.
3. Standard and project-specific documents: prequalification/initial selection, RFB/RFP, data sheets, evaluation criteria and conditions of contract.
4. National law and permits: company, tax, labour, licensing, security, foreign exchange, data and import requirements.
5. Addenda and clarifications: formal changes and answers issued during the tender.

Where there is ambiguity, bidders should use the clarification mechanism in the tender document rather than assume an interpretation. The operative project documents and addenda remain the binding source.

Current areas of focus across four institutions

This is a starting map, not a substitute for the project documents. Institutions update policies and standard forms, and projects under the same institution can use different methods and criteria.

Build the bid infrastructure before publication

1. Opportunity radar and institutional memory

Country strategies, pipelines, financing approvals, procurement plans, general procurement notices and specific notices should be monitored systematically. Each opportunity needs a record of sector, country, institution, anticipated timing, package, client and early-action owner.

2. Qualification evidence library

Project references should be kept as verifiable evidence—not only brochure copy—with contract value, scope, country, dates, participation share, completion certificate and client contact. Financial statements, corporate authorities, quality/ESG policies, litigation history and declarations should remain current.

3. Expert and partner network

Key-expert CVs should follow consistent formats and retain supporting evidence. Country and language experience must be matched realistically. A joint venture or subcontractor should be selected not only to fill reference gaps, but through clear roles, accountability, price, risk, exclusivity and decision rights.

4. Registration and portal readiness

Relevant e-procurement, consultant or supplier registrations should be completed early. User permissions, electronic signatures, file limits and upload rules need testing. Registration in a portal does not itself constitute prequalification or vendor approval.

5. Bid governance

Nominate the bid manager, technical lead, commercial lead, document controller, reviewer and authorised signatory. Document versions, clarification log, compliance matrix, risk register, pricing assumptions and submission plan should be governed centrally.

Pass the bid / no-bid decision through four gates

1. Strategic fit: do the country, client, sector and assignment size align with the company’s priorities?
2. Mandatory compliance: can eligibility, qualification, experience, experts, financial capacity and security requirements be evidenced?
3. Win probability: do client insight, competition, local position, technical differentiation and partnership create a real advantage?
4. Delivery economics: does the price cover tax, foreign exchange, security, travel, local staff, guarantees, cash flow and contractual risk?

Each gate should have explicit red lines. “We have already started, so we must continue” is sunk-cost thinking. The ability to make a no-bid decision when new facts emerge is a sign of institutional discipline.

How to build competitive advantage in the submission

Completeness through a compliance matrix

Map every requirement to its document section, owner, evidence, filename, status and review date. Signatures, powers of attorney, JV instruments, security wording and numerical/date consistency deserve separate control.

Project-specific thinking in the methodology

Replace generic company narrative with the client’s intended outcomes, critical risks, work packages, decision points and delivery plan. A proposal should demonstrate how it will deliver the ToR or Employer’s Requirements, not simply repeat them.

Role coherence, not just famous names

CVs should evidence the scored criteria, while organisation, person-month allocation, mobilisation and interfaces align with the methodology. A senior expert who is impressive on paper but unavailable in practice is a delivery risk.

Full-cost commercial modelling

Account for tax, withholding, currency conversion, price adjustment, payment delay, guarantees, insurance, local office, security, logistics and demobilisation. A low-priced contract with weak cash flow creates balance-sheet risk rather than growth.

Evidence behind integrity and ESG

Conflict of interest, sanctions, anti-corruption, environmental and social obligations, and supply-chain declarations are not box-ticking exercises. Corporate policies must align with actual practice and subcontractor controls.

Signals that may justify stopping the bid

• Attempting to interpret a mandatory similar-experience criterion into compliance,
• Unable to confirm a key expert’s eligibility or availability,
• A local partner will not commit to role, price and accountability,
• The required security wording cannot be issued by the bank,
• Tax and foreign-exchange impacts erode the target margin,
• The contract contains unlimited or uninsurable liability,
• The technical solution relies on unrealistic duration or staffing,
• Submission permissions and technical upload tests remain incomplete.

Twelve-question readiness check

1. Is the applicable institutional rule and edition identified in the project documents?
2. Are the procurement method, evaluation approach and mandatory pass criteria understood?
3. Are eligibility, conflict-of-interest and sanctions checks complete?
4. Is acceptable evidence available for every qualification criterion?
5. Have reference shares and scopes been calculated correctly?
6. Are JV/subcontractor roles and risks clear in writing?
7. Are key experts eligible, available and fully evidenced?
8. Does the methodology respond directly to the evaluation criteria and scoring?
9. Does the price include tax, currency, inflation, cash-flow and security costs?
10. Has management accepted the contract risks and non-negotiable conditions?
11. Have portal, electronic signature, file-format and submission rehearsals been completed?
12. Can the team and financing mobilise if the contract is awarded?

Development banks may update policies, standard documents and electronic systems. This article is a general readiness framework as at 26 July 2026. For each tender, rely on the financing agreement, applicable procurement plan, official procurement documents, addenda and governing law.