Which Defence Tender Documents Need Certified National-Language Translation
- 11 hours ago
- 6 min read
Five documents in a defence tender carry a certified national-language translation requirement: the tender response, the technical specifications, the qualification and exclusion documents, the compliance matrix, and the supporting certificates. Miss the language rule on any one of them and the contracting authority can set your bid aside as inadmissible before evaluation, regardless of price. Directive 2009/81/EC sets the procurement frame across the EEA, and each member state fixes the language its authority accepts.
AD VERBUM is an EU-hosted translation company that pairs a client-tuned LLM with certified defence linguists for tender documentation, certified to AQAP 2110, ISO 27001 and ISO 17100. We handle the five document types below through vetted linguists on EU infrastructure, with no public-cloud transit for restricted material. Below, each document, the language rule that applies, and what a gap costs.
How the language rule works
Directive 2009/81/EC governs defence and sensitive-security procurement across the EEA, and translation companies that handle EU defence tender work under Directive 2009/81/EC build around its language rule. Contract notices publish on Tenders Electronic Daily (TED), the EU's official tender portal, in all 24 official languages. The full tender documents and the submission itself run in the contracting authority's national language, because the directive leaves the language of the procedure to member-state law. A German authority evaluates in German, a French one in French. No single master version clears every market, and the European Commission lists language among the barriers that keep SMEs out of cross-border defence contracts.
1. The tender response
The tender response is the bid you submit: the technical and commercial offer, the cover letter, and any structured response forms the authority provides. The language rule is direct. You submit in the language the contract notice names, which is the authority's national language unless the notice explicitly allows another. A response in English to a Polish authority that required Polish is inadmissible, set aside before evaluation whatever its technical merit.
Certified translation here means a linguist who signs for the accuracy of the submission, not a machine draft skimmed the night before the deadline. If you want to know what certified translation actually covers, it is that signed accountability for the text, held to a defined process.
2. Technical specifications
The technical specifications describe what you offer against the requirement: system descriptions, performance data, drawings, and maintenance concepts. They carry the same national-language rule as the response, and they carry the highest error cost. A mistranslated tolerance, a unit converted wrong, or a term that drifts between sections can turn a compliant offer into a technical non-conformance.
Terminology has to hold across hundreds of pages. A defence term base built before production, not after, is the control that keeps the specification consistent from the first page to the last.
3. Qualification and exclusion documents
These prove you are allowed to bid: company registration, financial statements, proof of no relevant criminal conviction or unpaid taxes, and the self-declaration form the authority uses. Articles 39 to 46 of Directive 2009/81/EC set the qualitative selection and exclusion grounds. The authority reads these in its national language, so a certificate issued in your home country usually needs a certified translation attached. A missing or uncertified exclusion document is one of the most common reasons a technically strong bid never reaches evaluation.
4. The compliance matrix
The compliance matrix maps every requirement in the tender to your response, line by line, with a statement of comply, partially comply, or not comply. Evaluators score directly from it, so it has to read in their language and match the wording of the technical specification exactly. A matrix that says comply while the underlying specification, translated separately, uses a different term for the same component invites a clarification question at best and a compliance downgrade at worst. Translate the matrix and the specification together, against one agreed glossary, or they drift apart.
5. Supporting certificates and declarations
Quality certificates, security clearances, ISO and AQAP 2110 certificates, authorised-signatory declarations, and any consortium or subcontracting agreements round out the pack. Each is a short document with a high consequence: an authority that cannot read your ISO 9001 or AQAP 2110 certificate in its language may treat the requirement as unmet. Certified translation keeps the evidentiary chain intact, and the certified statement travels with the document into the authority's file.
Dual-use technical data changes the handling rules
Some of these documents contain controlled technical data, and that changes who may touch them. Regulation (EU) 2021/821 controls dual-use exports, and Article 2 treats transmission of controlled technology by electronic means as technical assistance, the EU analogue of a deemed export. Sending a maintenance manual for an Annex I or Annex IV item to an unvetted freelancer abroad can be an unlicensed transfer. National authorities enforce this: BAFA in Germany, DGA in France, UAMA in Italy.
Certified translation of controlled material has to run through vetted linguists on controlled infrastructure, which an open translation marketplace cannot promise. An NDA on its own does not meet the Article 2 technical-assistance test.
Where a certified translation gap costs you the bid
The rejections cluster around a few predictable gaps:
The response submitted in the wrong language, ruled inadmissible before evaluation.
An exclusion certificate attached without a certified translation, treated as not provided.
Terminology that drifts between the specification and the compliance matrix, downgraded on scoring.
Controlled technical data sent to an unvetted linguist, breaching Regulation (EU) 2021/821 Article 2.
Each is avoidable with certified linguists, one governed term base, and controlled handling from intake to submission.
Our defence translation services
Our translation services for regulated sectors run on ISO 27001 and ISO 42001 certified, EU-hosted infrastructure, with no reliance on public cloud tooling for core processing. Every project runs through our AI+HUMAN hybrid workflow: we ingest client Translation Memories and Term Bases first, our proprietary LLM-based LangOps System generates output constrained by client terminology on client-tuned open-weight models, and our certified subject-matter experts review for technical accuracy and regulatory compliance. Our QA is aligned to ISO 17100 and ISO 18587, with sector-specific requirements such as AQAP 2110 quality assurance and Regulation (EU) 2021/821 controlled-data handling applied where relevant. We serve Life Sciences, Legal, Finance, Defense, and Manufacturing clients across 150+ languages with 3,500+ subject-matter linguists. For teams managing audit-sensitive content, contact us to discuss your security and compliance requirements directly.
FAQ
Which language must a defence tender response be submitted in?
The national language the contract notice names, which is the contracting authority's own language unless the notice allows another. Directive 2009/81/EC leaves the language of the procedure to member-state law, so a Spanish authority can require Spanish. A response in the wrong language is inadmissible.
Does Directive 2009/81/EC require certified translation?
The directive does not use the words certified translation, but member-state procurement law and the authority's notice routinely require a signed, accurate translation of foreign-language documents. In practice, certified translation is how you prove a document in another language means what you claim. Uncertified drafts get set aside.
Do qualification certificates need certified translation?
Usually yes. Qualification and exclusion documents under Articles 39 to 46 of Directive 2009/81/EC, such as registration extracts and tax or criminal-record certificates, are read in the authority's national language. A foreign certificate typically needs a certified translation attached to be accepted as evidence.
Can I send controlled technical data to any translator?
No. Regulation (EU) 2021/821 Article 2 treats electronic transmission of controlled technology as technical assistance, so sending an Annex I or Annex IV maintenance manual to an unvetted linguist abroad can be an unlicensed transfer. Authorities such as BAFA, DGA and UAMA enforce it. Use vetted linguists on controlled infrastructure.
What if terminology differs between the specification and the compliance matrix?
Evaluators score from the compliance matrix against the technical specification, so a term that differs between them reads as a mismatch. At best it triggers a clarification question, at worst a compliance downgrade. Translating both against one term base under ISO 17100 review prevents the drift.
Does the UK still follow Directive 2009/81/EC after the Procurement Act 2023?
No. The UK moved to the Procurement Act 2023, in force 24 February 2025, which replaced the regulations that transposed Directive 2009/81/EC. UK bids run in English and publish on Find a Tender. Cross-border teams still need certified translation between EEA national-language source material and English.
