How to write a tender technical proposal: an outline and worked examples

Open the instructions and find the required response structure, technical criteria, attachments and page limits. Write down which part of your proposal will answer each criterion. If a form must be completed, start with that form.

One published CCI Mayotte tender separately assesses staffing, relevant references and methodology within its technical evaluation. It is a French procurement example, rather than a scoring system for every tender. The useful lesson is to build your structure around the requirements of the actual opportunity.

Where the buyer has not imposed a different format, these six sections provide a starting point. Keep the parts that answer the tender and add anything explicitly requested. This is a suggested drafting structure, not a legal checklist of mandatory documents.

Take each deliverable and work backwards through the actions needed to produce it. For a study, explain which data you will review, how you will obtain it and how you will handle missing information. For maintenance, explain how a request is received, who acts on it and how resolution is checked.

Use verbs that describe observable work: inspect, compare, test, correct, obtain approval. A sentence such as “we will provide rigorous monitoring” becomes useful when the reader knows who monitors what, when, and in which record.

Avoid attaching every CV in the company without explaining the roles. Identify who prepares the work, who delivers it, who reviews it and who communicates with the buyer. Check that people are available before committing them in your proposal.

A list of stages with an owner, duration and deliverable is enough to begin a work plan. Add dependencies on the client, such as site access, data delivery or approval of a draft. Review the plan with the person who would actually deliver the assignment.

A UNDP consultant notice published in June 2026 requests methodology and a timetable for deliverables. It illustrates the connection between approach and scheduling. That notice has closed, and its requirements should not be treated as universal rules.

For every important commitment, find something that helps the reader understand or verify it: an assigned role, a review procedure, comparable work or a sample deliverable you have permission to share. Point to the relevant annex rather than leaving the buyer to search.

Explain the context, your role, the work delivered and why a reference is relevant. If a project belonged to a former employer, distinguish your personal contribution from the experience of the firm now applying. Include only results and certifications you can support.

Follow the buyer’s format and page limit first. If no limit is stated, ask whether each section answers a requirement or makes your approach easier to understand. Remove repeated company background that adds no useful answer.

Check whether technical and financial material must be submitted separately. Keep pricing out of the technical document when separation is required. The tender instructions determine submission rules; the outline here does not.

Ask a colleague to locate the response to each criterion without your help. If they cannot find the delivery owner, the quality check or the basis for the schedule, improve that section. Check for names, dates and references left over from an earlier bid.

Finally, compare the proposal with your price and work plan. Every promised service should be reflected in your staffing and cost assumptions. To practise, choose a public offer on WTender, open the official documents and draft the outline first. Writing becomes easier once you know what each section needs to demonstrate.