What is a technical proposal in construction?
A technical proposal (mémoire technique in French) is the qualitative document submitted with a construction tender. It demonstrates the company's ability to deliver the project: organisation, methodology, resources, schedule, HSE approach and references.
It sits alongside the engagement letter (AE) and the price breakdown (DPGF). But unlike them, it has no fixed format: the company structures the narrative.
That is exactly what makes it decisive. At a comparable price, it is the technical proposal that wins or loses the bid.
Key takeaway
A technical proposal answers one simple question: « why should we pick you, specifically, for this exact project ? » Everything else flows from that.
What clients really expect
A public buyer or private client reads dozens of proposals every year. What makes them stop scrolling:
- Proof you have read and understood their tender (and not someone else's).
- A methodology that fits their project, not a copy-paste boilerplate.
- A named team, not a list of job titles.
- A justified schedule, not a decorative Gantt chart.
- Recent, comparable, verifiable references.
- A concrete, measurable, traceable HSE/CSR approach.
Standard structure of a technical proposal
There is no single legal structure, but a proven outline that matches client expectations and the most common scoring criteria:
- Company presentation : history, key figures, org chart, certifications (Qualibat, ISO 9001/14001/45001).
- Project understanding : rephrased stakes, site constraints, key risks identified in the tender.
- Execution methodology : phasing, work methods, justified technical choices, interface management.
- Human resources : named project team, CVs, site management, project org chart.
- Material resources : equipment, subcontractors, suppliers and co-contractors.
- Detailed schedule : sequencing, milestones, buffers, contingency management.
- HSE approach : prevention plan, waste management, environmental performance, CSR.
- Similar references : 3 to 5 recent and relevant projects with photos, contract values and client contacts.
- Annexes : certificates, datasheets, site safety plan, site layout drawings.
Pro tip
Follow the order of the sub-criteria from the tender rules (RC). If the RC lists safety before methodology, do the same. You make scoring easier : and you gain points.
How is a technical proposal scored?
In a public tender, the tender rules (RC) specify the weighting of each criterion. Technical value usually counts for 40% to 60% of the total score, with the remainder going to price.
Most common weightings observed in public works tenders:
- A generic proposal, even well written, will lose points against one that addresses each sub-criterion of the RC precisely.
- Personalisation is the number one success factor. More than layout, more than volume.
| Sub-criterion | Typical weighting | What the buyer looks for |
|---|---|---|
| Execution methodology | 25 – 35% | Clear phasing, work methods, justified technical choices |
| Human and material resources | 15 – 25% | Named team, allocated equipment, identified subcontractors |
| Schedule | 10 – 20% | Justified durations, milestones, buffers, contingency management |
| Environmental approach & CSR | 10 – 25% | Measurable commitments, waste traceability, carbon footprint |
| Safety (site safety plan) | 10 – 15% | Site-specific risk analysis, action plan |
| References | 5 – 15% | Recent, verifiable projects, comparable in size |
Indicative weightings : always refer to the RC of the specific tender.
Benchmark: average writing time for a technical proposal
How long does it take to produce a construction technical proposal? Numbers vary with project complexity, team maturity and tools used. Below are typical orders of magnitude observed on standard works tenders (€500k to €5M contract value).
- The main gain comes from tender analysis and the first structured draft, not from a 'magic prompt'.
- The expert stays in the loop: they validate every technical choice and adapt commitments to the project.
- The time saved is reinvested in personalisation : which is what gains points.
| Method | Average time | Estimated internal cost |
|---|---|---|
| Manual writing (Word, from scratch) | 2 to 3 days | €1,500 to €2,500 |
| With a well-organised internal library | 1 to 1.5 day | €800 to €1,200 |
| With Breek (analysis + assisted writing) | 2 to 4 hours | €150 to €300 |
Indicative estimates based on an average daily cost of €750 for a BTP bid manager (charges included).
Pre-submission checklist (12 checks)
Run through this systematically before any submission. A single unchecked box is a risk of lost points : or even disqualification.
- The tender rules have been read in full and the order of criteria respected.
- Every part of the tender package (specs, drawings, annexes) has been analysed.
- The project is named explicitly on the cover page.
- The team is named with CVs attached.
- Schedule durations are justified (no figures pulled out of thin air).
- References are recent (under 5 years) and comparable in size.
- Environmental commitments are measurable and traceable.
- The site safety plan is tailored to the site, not a template.
- Subcontractors are identified, with up-to-date certificates.
- File format and page count comply with the tender rules.
- The proposal is signed and dated correctly.
- A cross-review has been done by someone who did not write it.
The 7 mistakes that cost the most points
Across hundreds of proposals analysed, the same mistakes come back. And they are expensive.
Copy-pasting from a previous proposal
Coût : The buyer spots it in 30 seconds. Methodology score halved.
À faire : Rephrase every section, name the project, the site, the specific constraints.
Not following the RC order
Coût : The evaluator wastes time looking. They penalise as they go.
À faire : Use the RC sub-criteria as section titles.
Presenting the team as job titles ('a site manager')
Coût : No commitment perceived. Average score at best on human resources.
À faire : Name every person, attach CVs, specify the time allocation.
Schedule without justification
Coût : Suspicion of unrealism. Risk of questions during negotiation.
À faire : Justify every duration with a ratio (m²/day, lm/team), explain the buffers.
Vague environmental approach
Coût : Increasingly disqualifying. Some tenders require measurable commitments.
À faire : Precise commitments: % of waste recycled, kg CO₂ avoided, equipment certifications.
Polished form, empty substance
Coût : A beautiful but empty document scores lower than a sober but precise one.
À faire : Spend 80% of your time on substance, 20% on form. Not the other way around.
No cross-review
Coût : Typos, inconsistencies, outdated references. Credibility damaged.
À faire : Mandatory review by a non-author before any submission.
Reusable template and capitalisation
The best way to save time without losing quality is to build an internal library: company sheets, project sheets, CVs, HSE procedures, standard work methods. Each new proposal then becomes a tailored assembly, not writing from scratch.
Golden rule: reusable elements (company presentation, certifications, generic HSE approach) live in the library. Project-specific elements (project understanding, named team, schedule, work methods) are written case by case.
This is exactly what Breek automates: analysis of tender documents and drawings, requirement extraction, suggestion of content from your library, and generation of a first structured version that the expert validates and refines.