Short answer
Institutional buyers do not award on capability alone. They award the offer that is eligible, responsive, evidenced, understandable, deliverable and priced in a way the committee can defend. Treat the tender as a scoring and evidence exercise from the first page, and many avoidable losses disappear.
A capable firm can lose before the buyer has properly assessed its work. The failure is often in the submission process, not in the service.
Public and institutional buyers have to make decisions that can be explained to a committee, auditor, funder or public body. That means your bid must do more than sound confident. It must make eligibility, evidence, risk, method and price easy to check.
The World Bank’s guidance on rated criteria describes evaluation areas such as methodology, work plan, risk, performance capacity, key personnel and sustainability. It also makes an important point for vendors: the criteria, evidence and weighting should be visible in the bidding documents. Your first job is to understand that scoring instrument.
Read the tender as a scorecard
Do not begin by writing the company profile. Begin by extracting the buyer’s decision into a one-page matrix:
- Requirement: what must be submitted or demonstrated?
- Score: how many points or pass/fail gates apply?
- Evidence: which document, reference or named person proves it?
- Owner: who will produce and check the answer?
- Risk: what could make the response non-compliant or less credible?
Separate mandatory conditions from scored quality. A beautifully written methodology cannot rescue a missing form, an unsigned declaration, an ineligible consortium member or a late submission. The African Development Bank’s procurement guidance warns that bids may be rejected when required documents are missing and that the stated criteria govern evaluation.
1. Pass the compliance gate first
Before investing in a polished response, confirm that the firm can pass the basic gate:
- Legal registration, tax status, licences and eligibility are current.
- The firm, partners and proposed subcontractors meet conflict-of-interest and debarment requirements.
- Financial statements, turnover, insurance, bid security or other capacity evidence meet the stated thresholds.
- References cover the required client type, scope, value, geography and completion period.
- Every declaration, power of attorney, form and signature has the required format.
- The submission can reach the buyer through the required portal or channel before the exact deadline.
The AfDB eligibility guidance emphasises that conditions should test essential capability. Your response should therefore make the required capability easy to verify, not bury it in marketing language.
2. Prove the work with relevant evidence
Procurement committees do not need your entire history. They need evidence that is close enough to the assignment to reduce uncertainty.
For each reference, state the client, assignment, dates, value where permitted, your exact role, the team involved, the result delivered and a contact who can confirm it. If the work was delivered by a partner, say so. A long client list with no scope or outcome is less useful than three references the committee can understand.
Use the same discipline for people. Name the proposed project lead and critical specialists. Show availability, relevant qualifications, comparable assignments and the role each person will perform. Do not fill a tender with senior biographies of people who will disappear after award.

3. Answer the buyer’s risk, not only the scope
A tender may ask for a website, system, training programme, audit, construction package or advisory service. The committee is also asking what could go wrong and whether your method contains that risk.
Write the methodology around the buyer’s situation:
- What will you learn or confirm before implementation?
- What decisions must the buyer make, and when?
- What are the dependencies on data, approvals, suppliers, connectivity or staff time?
- How will progress, acceptance, quality and changes be recorded?
- What happens if a key person leaves, a dependency fails or the timetable moves?
The World Bank advises suppliers to demonstrate that they understand project risks, offer mitigations that can actually be delivered within the cost, and support claims with evidence. A generic method copied into several bids signals that the assignment has not really been understood.
4. Make the price defensible
Low price is not the same as good value, and a high price is not automatically a sign of quality. Your price should allow a reviewer to see what is included and why the resources are sufficient.
Show the logic behind the total:
- activities, deliverables and effort by phase;
- team roles, days or units and applicable rates;
- travel, taxes, licences, hosting, materials and subcontractors;
- assumptions, exclusions, validity period and currency;
- support, warranty, handover and change-control treatment.
Then check that the financial offer agrees with the technical offer. If the methodology promises five workshops but the price contains two days of facilitation, the committee sees a delivery risk. If tax treatment is unclear, the apparent low price may not remain low.
5. Show continuity before the buyer asks
Institutional buyers are buying continuity as well as an initial result. They need confidence that the contract will not stall because one consultant is unavailable, one supplier changes terms or one project file sits on a personal laptop.
Include a short continuity note covering:
- the deputy for each critical role;
- where working files, credentials and decisions are controlled;
- how subcontractors are managed and replaced;
- how incidents, delays and changes are reported;
- how data, confidentiality and handover will be protected.
This is especially important for small firms. Scale is not only headcount. It is the ability to keep commitments when circumstances change.
The bid review that prevents avoidable losses
Run two separate reviews. The first is compliance: forms, signatures, page count, format, naming, attachments, references, deadline and portal instructions. The second is quality: every scored criterion has a direct answer, evidence, owner, method and price connection.
Ask a reviewer who did not write the bid to mark it using the buyer’s own headings. They should be able to answer:
- What exactly is this vendor proposing?
- Why should the committee believe it can deliver?
- Which project risks has it understood?
- Where is the evidence for each important claim?
- Does the price make sense for the promised work?
Fix the answer, not just the wording. If a claim cannot be evidenced, reduce it, qualify it or attach the missing proof. Procurement committees are trained to distinguish a clear limitation from an unsupported promise.
Know when not to bid
A disciplined bid/no-bid decision protects both the firm and the buyer. Decline when a mandatory condition cannot be met, the delivery timetable is impossible, the reference profile is too far away, the cash requirement would endanger the business, or the requested work depends on capability you cannot name.
Bid when the opportunity fits your evidence, people, capacity, risk appetite and commercial model. A smaller firm can compete against a better-known name when its response is more relevant, more specific and easier to verify.
A ten-day submission plan
- Day 1: decide bid/no-bid and extract every gate and scoring criterion.
- Days 2–3: confirm references, people, partners, compliance documents and clarification questions.
- Days 4–6: write the method around the buyer’s risks, with deliverables, owners and acceptance points.
- Day 7: build the price from the method and test the technical-financial connection.
- Days 8–9: run independent compliance and quality reviews; resolve contradictions.
- Day 10: submit early enough to handle portal, signature or upload problems and save the final evidence.
Procurement rewards credible clarity
Good vendors lose when their capability is hidden behind generic prose, missing paperwork, untraceable claims or a price the committee cannot defend. Those are process problems, and process problems can be fixed.
Make the buyer’s work easier: show that you are eligible, understand the assignment, have done related work, know what could go wrong, have people who can deliver and have priced the work honestly. That is how a strong firm becomes a procurement-ready firm.
Frequently asked questions
Why do capable vendors lose institutional tenders?
Often because the bid fails a mandatory requirement, answers the scope rather than the evaluation criteria, provides weak evidence, contains unexplained pricing, or creates doubt about delivery risk. Good technical work is necessary but does not repair a non-responsive submission.
What should a procurement response prove?
It should prove eligibility, relevant experience, capacity, understanding of the buyer’s risks, a credible delivery method, qualified people, continuity arrangements and a price that follows from the proposed work. Each claim needs the evidence the tender asks for.
Should a small firm bid against a larger competitor?
Yes when the tender fits the firm’s evidence and capacity. A smaller bidder can compete through relevant references, named people, a clear method, local understanding, faster decisions and a credible risk plan. Do not bid where the mandatory conditions or delivery scale are beyond the firm.
How should we handle a tender question we do not understand?
Record the ambiguity, use the permitted clarification channel before the deadline, and keep the written response with the tender file. Do not quietly interpret a material requirement in the most convenient way.
What is the final review before submission?
Use a compliance matrix. Check every instruction, form, signature, page limit, file format, deadline, attachment, reference and price against the tender document. Have a second person review the final package against the scoring criteria, not just the prose.
Sources & the researchers worth crediting
External figures and recommendations are credited here so you can check the reasoning. The practical frameworks are Peter Bamuhigire’s analysis, not statistics presented as facts.
Read next
What Funders Check Before They Fund You
Prepare the operational evidence that institutional decision-makers ask for.
How to Run a Software Project So It Actually Finishes
Turn delivery promises into milestones, ownership and evidence.
Discuss a Tender or Delivery Challenge
Bring the requirement, timetable and bid questions into a structured review.
About the author
Peter Bamuhigire
Technology & Business Consultant
Peter Bamuhigire helps founders, consultancies and delivery teams turn their capability into clear, evidence-led proposals. His work connects procurement requirements with the people, controls and delivery plans behind them.

