How to prepare tender documents for a development bank bid

Requirements vary by procurement method and institution, but most development bank bids ask for the same building blocks. A complete package usually pairs a technical proposal with a financial proposal, adds consultant CVs in the required format, and includes the administrative and eligibility documents listed in the request for proposals. Prepare each part against the exact forms the bank provides, not a generic template.

• Technical proposal (technical envelope): methodology and work plan, evidence of similar experience, the proposed team, and the technical forms.
• Financial proposal (financial envelope): priced costs, staff rates, reimbursable expenses, and the financial forms.
• Consultant CVs in the bank’s format, such as World Bank Form TECH-6 or the ADB and EBRD templates.
• Eligibility and administrative documents: registration, references, powers of attorney, and any declarations the request for proposals lists.
• Signed forms and covering letters, named and numbered exactly as in the bid documents.

Many development bank assignments use a two-stage process, so it helps to know which stage you are at before you start writing. The expression of interest (EOI) comes first and is short: it shows the bank you are eligible and experienced enough to be shortlisted. Only shortlisted firms then receive the request for proposals (RFP) and prepare the full technical and financial proposal.

• An EOI is a qualification step. It typically asks for company background, similar assignments, and sometimes key staff, but not a full methodology or price.
• A full proposal is the detailed bid. It contains the methodology, work plan, staffing, CVs, and the priced financial offer.
• The EOI deadline is earlier and easier to miss, so treat it as the real first cut.
• Keep your EOI evidence reusable; strong project references and CVs feed directly into the later proposal.

Development bank proposals separate quality from price so that price cannot influence the technical score. You prepare two envelopes, a technical one and a financial one, and submit them so the financial offer stays sealed until the technical evaluation is finished. Mixing any pricing into the technical envelope can disqualify a bid, so check every technical form for stray cost figures before you submit.

• Technical envelope: methodology and work plan, similar-project experience, the staffing schedule, CVs, and signed technical forms.
• Financial envelope: the priced offer, staff rates and time inputs, reimbursable and other direct expenses, and taxes where required.
• How the two are scored depends on the method: QCBS weighs technical and financial together, while CQS and other quality-led methods lean on qualifications.
• Both envelopes must use the same currency rules, numbering, and file naming that the request for proposals specifies.

Never place cost information in the technical envelope. If a bank finds prices there, it can reject the whole proposal, however strong the technical content.

The terms of reference (ToR) define the tasks, deliverables, and evaluation criteria for the assignment, and evaluators score your technical proposal against them point by point. Structure your methodology to follow the ToR so a reviewer can find each required task and output quickly. A compliance matrix, mapping every ToR requirement to the page where you answer it, makes your proposal easy to score and shows you have read the assignment closely.

• List every ToR task and deliverable, then write a methodology section that answers each in the same order.
• Build a compliance matrix that points each requirement to the exact section, form, or CV that satisfies it.
• Match staff and CVs to the qualifications the ToR asks for, and highlight the exact experience the evaluators will look for.
• Answer the evaluation criteria directly; do not make reviewers infer that you meet a requirement.

Once the content is written, assembly and submission decide whether a strong bid actually arrives on time and complete. Work from a single checklist, keep the technical and financial envelopes separate, and give yourself a buffer before the deadline for signing, formatting, and upload.

1. Read the request for proposals in full and list every required form, document, and evaluation criterion.
2. Turn the requirements into a checklist, with an owner and an internal deadline for each item.
3. Draft the technical proposal: methodology, experience, staffing, and CVs in the bank’s format.
4. Complete the financial proposal on the required forms, kept separate from the technical envelope.
5. Review both envelopes against the checklist and the compliance matrix, and collect every signature.
6. Assemble submission-ready files and submit through the required channel before the deadline, then keep the confirmation.

A bid workspace such as Silka’s keeps the checklist, files, team, and both envelopes tied to one tender, and can generate consultant CVs and export documents in the formats banks expect, so the package stays complete from shortlist to submission.

Most rejected bids fail on compliance, not on ideas. A quick pass against these common mistakes protects weeks of work:

• Missing or unsigned forms, or forms filled in the wrong version or template.
• Putting price information in the technical envelope, which can disqualify the whole bid.
• A methodology that does not follow the ToR, so evaluators cannot find required tasks.
• CVs in the wrong format, over the page limit, or without the required signatures.
• Ignoring eligibility or conflict-of-interest rules, or missing the language and currency requirements.
• Leaving submission to the last hour, when upload, size, or portal problems can cost the deadline.