An outline that departs from the RC
The buyer scores criterion by criterion. If your outline does not follow theirs, they have to hunt for the answer, and what they cannot find cannot be scored.
The required outline, an executive summary that fits on one page, and behind every claim the reference that proves it. Sentences that nothing supports are not written: they are flagged, because a technical proposal is contractual.
The technical proposal (mémoire technique) is the written document in which a candidate for a contract demonstrates how it will deliver the service. It is scored against the criteria in the tender rules and becomes contractual once the contract is awarded.
Definition as used on this page. See the glossary.
The buyer scores criterion by criterion. If your outline does not follow theirs, they have to hunt for the answer, and what they cannot find cannot be scored.
Describing your company is not describing how you will perform the contract. The criterion is about what you will do on this project, with these resources, these people, these timescales.
“We have an experienced team” is worth nothing without the CVs, comparable references and figures. Evidence is what turns an intention into a mark.
A vague timescale does not reassure; an unrealistic timescale becomes a contractual penalty. The proposal must commit to precisely what you can deliver.
Example structure for a services tender, with the weighting read from the tender rules.
One page: understanding of the need, the main commitment, the three proven points of differentiation.
Restatement based on the CCTP clauses, site constraints, interfaces with the other contractors.
Phases, deliverables, milestones, checkpoints, handling of contingencies, linked to references from comparable projects.
Project organisation chart, CVs linked to roles, equipment, declared subcontracting.
Certificates in force, dated indicators, improvement plan. The same evidence as your ESG questionnaires.
Reference sheets, certificates, detailed schedules: called from the body of the proposal, not piled up at the end of the file.
A public buyer expects proof of compliance, references to the clause, restraint. A key-account purchasing department expects measurable benefit and the transition plan. The substance, your evidence, does not change; the wording does.
No comparable reference for this type of service? The gap is flagged, with the option of writing the missing organisation note or reference sheet. See the mechanism.
The proposal is a text you review, correct and approve by name. What you gain is the time spent gathering and formatting, not editorial control.
Frequently asked
It follows the outline imposed by the tender rules when there is one. Otherwise, it follows the scoring criteria in their order of weighting, which puts the writing effort where the marks are won.
No: every claim comes from your indexed references — projects, resources, CVs, certificates — and cites its source. A sentence that nothing proves is flagged rather than written, which avoids the proposal that “sounds good” and falls apart at the first clarification.
Yes, except when the response template is imposed, in which case the buyer’s format applies, without modification.
It is taken into account as a writing constraint: pages are allocated according to the weighting of the criteria, and whatever is moved to an appendix is explicitly referred to.
It joins your knowledge base, with its sources and approvals. The next tender reuses what can be reused and flags what has changed since.
If the buyer asks, yes, and the answer is defensible: controlled use, answers sourced, scored and approved by name, traceability that can be produced. See the AI you can stand behind page.
We show, on your documents, which claims were not proven and what a proposal backed by your references would have said instead.