English guides. The UzTender.com catalogue, plans and account pages are in Russian and Uzbek.
← All English guides

World Bank Procurement in Uzbekistan: A Supplier Guide

Updated 3 November 2026

To pursue World Bank-financed procurement in Uzbekistan, identify the project, the contract package and the organisation buying the goods or services. Then establish whether the record is a planning signal, an invitation requesting a response, or an award. These distinctions determine what your company should prepare and where it should send it.

UzTender is an independent aggregator for discovering covered opportunities. It does not approve World Bank suppliers or submit bids. Use the original notice and current purchaser documents to verify the opportunity before committing translation, engineering or bank-guarantee costs.

World Bank notices in the UzTender catalogue →(in Russian / Uzbek)

Are you supplying a borrower project or the Bank itself?

A borrower-executed project and a purchase for the World Bank Group's own operations are different routes. The project supplier hub describes companies supplying government borrowers. For such a package, establish the implementing agency and contracting purchaser from the project and invitation.

The separate corporate vendor page currently directs new corporate applicants to its Vendor Management Portal. It also explains that an application does not automatically make the company a registered WBG vendor. Completing that process is not a substitute for a borrower project's instructions.

Write the legal purchaser's name at the top of your working file. A project implementation unit may manage communications, while another named entity signs the contract. Resolve that relationship before addressing your proposal or requesting a guarantee.

What do current, upcoming and potential opportunities mean?

The World Bank opportunities page separates three discovery categories. Current opportunities contain specific notices with response deadlines. Upcoming opportunities contain general notices anticipating later invitations. Potential opportunities come from procurement plans and can change or never proceed.

Turn these into different internal actions:

RecordUseful supplier actionWhat it does not establish
Potential packageResearch capacity, references and delivery optionsThat a bid can be filed now
General noticeIdentify the project and monitor package publicationA final specification or submission window
Specific invitationObtain the complete package and assess the requested responseAutomatic qualification
Award informationReview the result and comparable scopeA remaining invitation to compete

A planned date is a forecast for your watchlist. Only the operative invitation and its amendments establish the response timetable you should work against.

How do you track one package without confusing it with the project?

Keep a package record rather than a folder named only after the programme. One project can buy equipment, construction and consulting services through separate procurements with different requirements. Project financing totals are not individual contract budgets.

Record the following fields in one working record per package:

  • Project title and project identifier.
  • Package reference and lot, where applicable.
  • Purchaser and implementing contact.
  • Source URL, publication date and date checked.
  • Document type, response required and current stage.
  • Deadline, stated time zone and submission destination.
  • Applicable documents, unresolved issues and next action owner.

Use the same identifiers when matching an aggregator record to the original notice. Similar wording is insufficient if the package reference, lot or purchaser differs. Keep an amended notice attached to the existing record instead of counting it as new demand.

What should an expression of interest contain?

Prepare the response requested by the invitation, not a generic complete tender. For a consulting expression of interest, first establish whether the opportunity concerns a firm or an individual and what evidence is requested for consideration. A later invitation to submit a proposal is a separate stage.

Map each requested capability to evidence: relevant assignment, the entity that performed it, scope, dates and the proposed team's role. State whether experience belongs to the bidder, an affiliate or a prospective partner. Do not relabel a manufacturer's delivery as your company's completed consulting assignment.

Use concise, verifiable descriptions. “Designed a maintenance programme for comparable equipment” becomes useful when the response identifies equipment scope, responsibilities and an available reference. Include prices, experts or prescribed forms at the stage and in the manner requested; an unsolicited commercial offer does not replace missing qualification evidence.

Which documents should control bid preparation?

Obtain the complete issued package and any amendments, then identify the instructions, data sheet, qualification requirements, specifications or terms of reference, response forms and contract conditions. Record the governing framework and edition cited for that procurement. The World Bank project procurement hub links the relevant borrower, supplier and framework resources.

Build a requirement matrix with separate columns for mandatory eligibility, technical compliance, evaluated quality and contractual obligations. For every row, record the document clause and your evidence. This prevents a strong technical proposal from hiding a missing authorisation or an unacceptable delivery commitment.

Check the requested language and translation arrangements in the package. An English invitation does not establish that every supporting certificate can be filed untranslated. Likewise, importing another procurement's document list can create unnecessary work or omit a decisive requirement.

How should amendments and clarification be managed?

Assign one person to maintain the source record and circulate changes. Save each amendment with its date, affected requirements and required action. If a specification changes, review the technical offer, price, manufacturer commitment and delivery plan together.

Send focused clarification through the channel specified for the procurement. Identify the package and clause, explain the practical ambiguity and ask a question the purchaser can answer. For example: does the stated installation requirement include testing at every delivery site? A generic request to “confirm compliance” offers little guidance.

Treat a support enquiry, clarification, account registration and bid submission as different events. Record the actual response and any formally revised document. Do not assume that a question extends the deadline or that an informal conversation changes the issued conditions.

What does a practical supplier decision look like?

Consider this fictional exercise: an overseas pump supplier finds a planned Uzbekistan water-project package, later followed by a specific invitation. The company initially has product brochures and manufacturer support, but lacks a confirmed commissioning arrangement.

At planning stage, it collects relevant references and estimates delivery constraints. Once the invitation appears, the bid manager checks whether commissioning is mandatory, who may perform it and what evidence the bidder must provide. The technical lead maps performance requirements to a named model. Finance checks freight, installation costs, payment timing and any required security.

The decision remains “clarify” until responsibility for commissioning is supported. A low factory price cannot resolve that gap. If the issued conditions require capabilities the company cannot demonstrate, a documented no-bid decision is more useful than an unsupported claim.

What proves the response reached the right recipient?

Before filing, reconcile the package reference, bidder identity, authorised signatory, document versions and submission destination. Check whether the instructions require electronic submission, physical delivery or another permitted method. A discovery website is not necessarily the receiving system.

Keep evidence appropriate to that route: the final submitted files, transmission or delivery record, timestamp and the recipient's available acknowledgement. An uploaded draft or a completed corporate vendor application proves a different action.

After the deadline, monitor official communications and record the next stage. Keep the project, package and contract references connected so later result analysis remains reproducible.

Sources

More guides in English

All English guides →