Responding to a tender: a concrete example
Responding to a tender means assembling two blocks: the application (who you are, your capacities) and the bid (what you propose, at what price). Here is the usual list of documents and the structure of a winning technical memo. We do not hand out a ready-made PDF (every contract differs), but the outline below is directly reusable.
The documents to provide
- Application letter (DC1)
- Candidate declaration (DC2): capacities, turnover
- Deed of commitment (ATTRI1 / DC3): your signed bid
- Price schedule (DPGF / BPU): the detail of your prices
- Technical memo: the document that makes the difference
Structure of a winning technical memo
| Section | What the buyer wants to read |
|---|---|
| Understanding the need | You read the specifications and grasped the constraints |
| People and equipment | Dedicated team, equipment, subcontracting |
| Methodology | How you deliver, step by step |
| Schedule | Deadlines met, milestones, handling of hazards |
| Quality, safety, environment | Your concrete, measurable commitments |
The mistakes that cost the contract
Responding at the last minute, missing a required document, copying a generic memo without quoting the specifications, or offering a price so low it becomes abnormally low. The best habit is to spot the right contracts early: exactly what the Tendveo radar does.
Frequently asked questions
Is there a free tender-response template?
No universal template: every contract has its own specifications. The technical-memo outline above is reusable and free, to be adapted to each consultation's specifications.
What is the most important document in a response?
The technical memo. Price matters, but technical value often decides, since the price criterion rarely weighs 100 %.
Related guides
Source : BOAMP/DILA · Licence Ouverte 2.0 · as of 25/06/2026