Document template · Free
Technical method statement
Technical method statement
What this is
A concise description of the technical solution you propose to deliver, including how it meets the functional and non‑functional requirements of the contract.
When you need it
Required during the preparation of the tender dossier for contracts where the specification calls for a detailed description of the proposed method (e.g., construction works, IT system implementation, engineering services). It is usually mandatory when the award criteria include technical merit.
How to fill it in
- Identify the contract’s technical specifications (see Article 42 of Directive 2014/24/EU).
- Summarise your solution architecture or work plan, linking each element to a requirement.
- Provide any recognised standards, certifications or past‑project references that demonstrate compliance.
- State the resources (personnel, equipment) you will allocate and their qualifications.
- Indicate timelines for each major work package.
What wins points
Evaluators look for clear alignment with the technical specifications, demonstrable competence (certifications, past performance) and a realistic implementation schedule. Showing measurable outcomes (e.g., performance benchmarks, delivery dates) strengthens your bid.
How this gets you disqualified
- Missing reference to Article 42 requirements or omitting required certifications can trigger exclusion under Article 57 (exclusion grounds).
- Failing to provide sufficient detail may be deemed non‑compliant with the procurement specifications, leading to rejection at the selection stage.
Template
**Project name:** [Enter project title] **Technical solution overview:** [Provide a brief description of the proposed method] **Alignment with specifications (Art 42):** - Requirement 1: [Your approach] - Requirement 2: [Your approach] … **Standards & certifications:** - ISO 9001:2015 – Quality management (cert. No.) - CE marking where applicable **Personnel & qualifications:** - Project Manager – PMP certified, 10 y experience - Lead Engineer – [Qualifications] **Work package schedule:** | Work package | Duration | Start date | End date | |--------------|----------|------------|----------| | WP1 … | X weeks | DD/MM/YYYY | DD/MM/YYYY | …
What wins points
Demonstrate how your solution meets each technical specification (Art 42) and cite recognised standards or certifications, showing measurable performance targets.
How this gets you disqualified
Failing to reference Art 42 requirements or omitting required certifications can trigger exclusion under Article 57 and result in disqualification.
What an evaluator actually looks for
Check that each contract specification is explicitly addressed and that any cited standards (ISO, CE) are valid and relevant.
Sources
Get the daily EU tender brief
Free templates, plus the live tenders that match your capability — one email a day, no card required.