How to build a tender bid that wins.

Before reading the full tender documents, I look at three elements only. They decide whether the tender deserves any of my time:

• Submission deadline: do I realistically have time to prepare a clean bid?
• Expected deliverables: can I genuinely deliver what is asked, at the expected quality?
• Evaluation criteria: given the weight of each criterion, do I have a real chance of winning?

If the answer is no on any of the three, I pass. If it is yes, I read everything in detail:

• Instructions to bidders: selection criteria, weighting, deadline, submission format.
• General and special conditions of contract: contractual terms, penalties, payment schedule.
• Technical specifications: what must be delivered, how, and against which standards.
• Price schedule / bill of quantities: the pricing grid to follow line by line.

If a technical requirement is unclear, ask the official question through the procurement platform. Never guess.

Right after reading the documents, I write a response plan. It drives everything that follows: without one, you work blind and discover the gaps the day before submission.

The response plan lets me map out, on a single page:

• Information to collect: per stakeholder (management, HR, finance, technical), with an owner and a date.
• Documents to obtain externally: certificates, attestations, extracts. Who issues them, how long it takes, and how to request them.
• Partners to approach: subcontractors, joint venture partners and suppliers who strengthen the bid against the evaluation criteria.

The rule: anything that does not depend on me starts immediately. The earlier I launch external requests, the safer I am. Then I can focus calmly on what I control alone: the technical proposal and the pricing.

Most administrative documents are easy to gather. But a few, slow to produce or dependent on external approval, are the ones that sink bids. Handle these first, from day one:

• Bid bond / bid security: issued by a bank or an insurance company. Expect several working days.
• Professional liability insurance certificate: up to date and covering the scope of the contract.
• Credit line certificate: issued by your bank, often required to prove financial capacity.
• Proof of available liquidity: also issued by the bank, with a minimum amount set in the tender rules.
• Tax and social security clearance certificates: to request from the relevant authorities, sometimes with long lead times.
• Financial statements: balance sheets and income statements for recent years, certified as required.

The remaining documents (application letter, trade register extract, CVs, references, signatory authority) are usually easy to assemble in-house. Focus your energy on the six above, and start those processes on the first day.

The technical proposal usually carries a major share of the score. It must answer the technical specifications point by point, in the same order. The core structure, in this order:

• Understanding of the need: restate the buyer's context in their own words to prove you understood the problem.
• Proposed solution: describe the solution you offer before any implementation detail.
• Implementation methodology: how you will deploy the solution, step by step.
• Implementation team: dedicated profiles, roles, and experience relevant to the project.
• Schedule: key dates, milestones, interim deliverables.

That is the foundation. Additional sections (quality approach, CSR, safety, risk management, etc.) are added only if the tender documents explicitly ask for them.

Never change the structure of the price schedule provided. Every line must be filled in. A total that does not match the sum of the lines means a rejected bid. Check:

• Consistency between price schedule, bid form and technical proposal
• Correct application of VAT
• No missing line, no unjustified zero price

An evaluator reads dozens of bids. If yours is pleasant to navigate, they find your answers to each criterion instantly, and you score better. Get these right:

• Pagination: continuous, readable numbering at the bottom of each page.
• Table of contents: clickable in PDF, with headings aligned to the evaluation criteria.
• Headings and hierarchy: clear levels, consistent styles, no untitled section.
• Sober design: readable typography, generous margins, discreet branding, uniform headers and footers.
• Useful visuals: diagrams, summary tables, a visual schedule. Only when they clarify.

The evaluator must find their way around easily. If a criterion cannot be located in 10 seconds, it is lost.

• Every document listed in the tender rules is included
• Each document is signed and dated by the right signatory
• File formats comply with the rules (PDF, maximum sizes)
• The price schedule is consistent with the bid form
• Submission is done at least 24 hours before the deadline
• You kept the submission receipt