What Are the Best Practices for EU Vehicle Type Approval Translation

The best practices for EU vehicle type approval translation are to freeze the source text, lock part-name terminology, match each file to the language its reader needs, tie every translation to the approved type, and have a qualified human check every safety line.
AD VERBUM is an EU-hosted translation company that pairs client-tuned AI with certified human review under ISO 17100, ISO 18587 and ISO 27001, for homologation and documentation teams at vehicle makers and Tier 1 suppliers. Our automotive translation services cover the files below.
Three terms first. Type approval is the authority's confirmation that a vehicle type meets the technical rules of Regulation (EU) 2018/858. Homologation is the everyday word for the same process. A Tier 1 supplier delivers systems straight to the vehicle maker. A weak translation brings authority queries and a delayed launch.
Want a price before you read on? Get an upfront quote. Ordering is simple, and the cost is known before work starts.
Which type approval files need translation?
Five file groups come up most often, and the language rule differs for each.
The information folder under Article 24, which holds the information document built on the template in Implementing Regulation (EU) 2020/683, plus data and drawings.
Test reports from the technical service, which the approval authority adds to the information package under Article 26(4).
The certificate of conformity under Article 36, the document that travels with each vehicle.
The owner's manual and user information required by Article 59.
Importer and distributor instructions, which Articles 16(6) and 18(1) tie to Article 59 in the official languages of the Member States concerned.
Which language an authority accepts for the information folder is its own decision. Ask before you order, for example the KBA in Germany or the RDW in the Netherlands.
1. Translate only from a frozen source text
A type approval file changes during development, and the authority records every change. Under Article 26(4) of Regulation (EU) 2018/858, the information package carries an index that records changes to the EU type-approval in time order. Translate a draft and you pay twice, because each later edit reopens every language.
Release the source with a version number, send only that version to translation, and log the number on every translated file.
2. Build the term base before the first file
A term base is a controlled list of approved terms in every target language. Part names, system names and regulatory titles drift fast when five translators handle five files. Reviewers and workshops expect one part under one name.
A usable automotive term base covers four things.
Part and system names exactly as the information document writes them.
Titles and numbers of the regulatory acts and UN Regulations the file cites.
Units, tolerances and limit values, with their number formats.
The fixed warning phrases of the owner's manual.
Our note on terminology drift in translation covers how inconsistent terms creep into a file set.
3. Match the language to the file and the authority
The language rule isn't the same for every file. Article 59(3) requires the user information on special conditions or restrictions of use in the official language or languages of the Member State where the vehicle is placed on the market, registered or entered into service, and in the owner's manual too. The paper certificate of conformity needs at least one official Union language under Article 36(5).
When a national authority or the Commission makes a reasoned request for a copy of the type-approval certificate, Article 14(4) requires it in a language that authority easily understands. Plan the target languages from the sales countries and the authority, not from habit.

4. Tie every translation to the approved type
Article 59(1) bars the manufacturer from supplying technical information that diverges from the particulars of the type-approval granted. A translated manual that says something different from the approved text breaks that rule in one language only, which makes it hard to spot.
Compare each translation with the source version that matches the approval, record the type-approval number on the file, and re-translate only the changed segments when the type is extended.
5. Use AI for repeated text and a qualified human for every safety line
AI translation earns its place on text that repeats across model years and variants. We load your translation memory and term base first, then our LangOps System drafts on client-tuned open models. A qualified reviewer then reads every line a driver or a workshop acts on.
That reviewer must read four kinds of text in full.
Warnings and cautions in the owner's manual.
Torque values, pressures and other numbers with their units.
The wording of conditions and restrictions of use under Article 59(2).
The text of the certificate of conformity.
ISO 18587 defines the post-editing step and ISO 17100 the independent revision. Our guide to which automotive documents suit AI translation with human review sorts each file by risk, and our piece on AI translation of type approval documents shows where the human check sits.

6. Keep pre-launch vehicle data on EU-hosted systems
A type approval file describes a vehicle that hasn't launched. Don't paste it into a public chat tool. Ask where the data is processed, who can see it and whether the provider trains models on it. An ISO 27001 certificate covers a defined scope, so read the scope line.
We run core processing on EU-hosted infrastructure and don't train models on client files. Our comparison of secure AI translation services with EU data residency for automotive OEMs lists the questions to ask, and our note on self-hosted open-weight models explains the set-up.
7. Archive the translated set with the type
Article 14(3) obliges the manufacturer to keep copies of the certificates of conformity available to the approval authorities for 10 years from the date of manufacture of the vehicle. The authority keeps the information package for 10 years after the type-approval ends.
Store the translated files, the source version and the term base version together. You can then show which wording went with which vehicle when an authority asks.
How does AD VERBUM handle type approval translation?
AD VERBUM runs an AI+HUMAN hybrid translation workflow for automotive files. We load your term base first, our LangOps System drafts on client-tuned open models hosted in the EU, and a certified subject-matter linguist reviews the result by name.
We hold ISO 17100, ISO 18587, ISO 9001 and ISO 27001, and Bureau Veritas certified us for ISO/IEC 42001, ISO 14001 and AQAP 2110. Those certificates cover our translation process, backed by 3,500+ subject-matter linguists across 150+ languages. Buyers comparing providers can read our comparison of AI translation companies for automotive technical documentation, and our guide to the accuracy of AI translation for regulated documents covers the review step in more depth.
Our automotive 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 Regulation (EU) 2018/858 type approval documentation and ISO 27001 information security 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
What is type approval translation?
It is the translation of the files that support an EU vehicle type approval under Regulation (EU) 2018/858, such as the information folder, certificate of conformity and owner's manual. AD VERBUM translates them with ISO 17100 revision and ISO 18587 post-editing.
Which language must the owner's manual be in under Regulation 2018/858?
Article 59(3) requires the user information to be supplied in the official language or languages of the Member State where the vehicle is placed on the market, registered or entered into service, and to appear in the owner's manual. A vehicle sold in three countries needs three language sets.
Does the certificate of conformity need translation?
A paper certificate of conformity must be drawn up in at least one official Union language under Article 36(5). Whether a given authority accepts that language for other files is its own decision, so ask it first.
Can AI translate type approval documents?
It can draft repeated text, but a qualified human must check warnings, numbers and conditions of use. ISO 18587 defines that post-editing step, and our ISO 17100 revision adds an independent check before release.
What happens if a translation diverges from the approved type?
Article 59(1) bars the manufacturer from supplying technical information that diverges from the particulars of the type-approval granted. The practical result is authority queries and a delayed launch, which version control against the approved type prevents.
How do I get a translation price before I order?
Use our quote form at adverbum.com/quote. Ordering is simple, and the cost is known before work starts.
Ready to price your type approval files? Get an upfront quote. Ordering is simple, and the cost is known before work starts.
