Technical translation services translate specialized content, such as user manuals, specifications, safety data sheets, and software text, using linguists who know the subject. A reliable process fixes terminology in a glossary first, then has a second linguist revise every translation, as ISO 17100 requires, before final QA. That is how SEAtongue runs
human translation for technical content.
Key takeaways
- Under ISO 17100, every translation is revised by a second linguist before delivery.
- ISO 17100 accepts translators with a translation degree, a degree in another field plus 2 years of translation experience, or 5 years of full-time translation experience.
- Terminology is settled before translation starts, in a glossary checked by subject-matter experts and, where needed, the client.
- From 20 January 2027, the EU Machinery Regulation requires instructions for use in a language users can easily understand, as each Member State decides. They may be supplied digitally.
- Machine translation with post-editing is a separate workflow with its own standard, ISO 18587. Decide per content type, not per project.
What counts as technical content?
Technical content is any text a reader acts on to build, operate, maintain, or stay safe around a product. Errors introduced in translation cost more than style: a torque value copied incorrectly or a warning softened in the target language is a product problem, not a language problem. For
manufacturing translation, the work usually covers these types.
| Content type | Examples | What goes wrong without a technical process |
| Manuals and guides | User manuals, maintenance guides, installation instructions | Steps and part names translated differently across chapters |
| Safety content | Safety data sheets, hazard warnings, safety handbooks | Warnings that are softened, reordered, or unclear |
| Engineering documents | Specifications, engineering reports, CAD drawings, and schematics | Units, tolerances, and callouts misread or reformatted |
| Software and systems | ERP and MES screens, production dashboards, UI strings | Text that overflows buttons or loses its placeholders |
Technical manual translation
Technical manual translation covers user manuals, installation guides, maintenance and service manuals, and safety instructions. Manuals change release after release, so the glossary and translation memory matter most here: approved wording is reused in every update, and only new or changed text is translated again.
How SEAtongue handles technical translation
SEAtongue runs every technical project in five steps: terminology is fixed before the first sentence is translated, and a second linguist checks every file. Each step maps to a standard we are certified to, so you can verify the process, not just the promise.
1. Terminology comes first
Before translation begins, our terminologists build a custom glossary and termbase from your source files. Subject-matter experts help create it, and you validate it when required. Every linguist on the project then works from the same approved terms.
2. Native, industry-specialized translators
Translation starts only once terminology is settled, and it is done by native translators who specialize in your industry. Every linguist is selected and tested in line with ISO 17100:2015 before being assigned to a project. Our translation management system then matches linguists to each job by qualifications, availability, and past performance.
3. Revision by a second linguist
A second linguist checks every translation for grammar, terminology, glossary consistency, and cultural fit. This is the revision step ISO 17100 requires, and it applies to every file, not a sample.
4. Subject-matter review where it matters
For technical content, an industry expert can add a review on top of revision. Our specialists bring domain knowledge in fields such as software, mechanical engineering, and medical content, and they validate translations where a linguist alone cannot.
5. Automated checks, then final QA
Automated checks for terminology consistency, formatting, and linguistic errors run before the final human review, so issues are caught early. Our quality team then validates technical terms and numbers, corrects any remaining inconsistencies, and confirms your style and formatting requirements are met.
Final QA confirms that every number, unit, and term in the translation matches the source. It does not verify the engineering accuracy of the source itself, so any source errors should be raised with your technical team.
Who you work with
| Role | What they do |
| Account manager | Your main point of contact |
| Project manager | Oversees the project from kickoff to delivery |
| Local language manager | Appointed per project, with expertise in the target language |
After delivery, we ask for your feedback and fold it into our process. Our system also scores each linguist’s performance after every project, which decides who is assigned next time.
Certified at every step
SEAtongue holds four ISO certifications that cover the technical translation process end to end. See the full list on our
quality certifications page.
| Certification | What it covers in a technical project |
| ISO 17100:2015 | Translator qualifications, revision by a second linguist, project management |
| ISO 18587:2017 | Post-editing of machine translation output, and post-editor training |
| ISO 9001:2015 | Documented quality management across all operations |
| ISO 27001:2022 | Information security for your files: encryption, secure platforms, role-based access |
Our linguist network covers over 50 countries. Read more about our
quality process.
What does ISO 17100 require?
ISO 17100:2015 sets requirements for the translation process itself: who may translate, who must check, and who manages the job. For a buyer, it is a way to confirm a vendor’s process without auditing it yourself.
| Requirement | What the standard asks for |
| Translator qualifications | One of: a recognized translation degree; a degree in another field plus 2 years of translation experience; or 5 years of full-time professional translation experience |
| Revision | Every translation revised by a second linguist before delivery |
| Review | Optional subject-matter review, and proofreading for layout and formatting |
| Project management | A project manager assigned to oversee each job |
Source:
TÜV SÜD, ISO 17100 certification.
Which regulations affect technical translation?
Product regulations decide which languages your documentation must ship in, and the EU Machinery Regulation is the next big change. Regulation (EU) 2023/1230 applies on a mandatory basis from 20 January 2027. Machinery placed on the EU market before that date must still comply with the Machinery Directive 2006/42/EC.
Under Article 10(7) of the Regulation:
- Instructions for use must be in a language users can easily understand, as determined by the Member State concerned.
- Instructions may be provided in digital format.
- If a user asks at the time of purchase, the manufacturer must provide paper instructions free of charge within one month.
For manufacturers exporting from Asia to Europe, this means planning every EU target language before launch, not after a market asks for it. Sources:
EUR-Lex, Regulation (EU) 2023/1230;
European Commission, Machinery.
Human translation or machine translation with post-editing?
Choose per content type: the two workflows follow different standards, and one project can use both.
| Human translation | Machine translation with post-editing (MTPE) |
| How it works | A qualified linguist translates, a second linguist revises | A machine translation engine drafts, a trained post-editor corrects |
| Standard | ISO 17100 | ISO 18587 |
| Usually suited to | Safety content, regulated documentation, new terminology | Large, repetitive documentation with a stable glossary |
| What to check | Revision step and translator qualifications | Post-editing level and post-editor training |
What should you send your translation vendor?
Send everything that fixes meaning before translation starts, so translators decide less on their own.
- Source files in their editable format, not PDFs exported from them.
- Any existing glossary, termbase, or translation memory.
- Your style guide and approved product names.
- Reference material: earlier translations, drawings, screenshots of the product.
- Exact target locales, for example Simplified or Traditional Chinese, Bahasa Indonesia or Bahasa Malaysia.
- The regulations the documents must meet and who signs off on the translation.
- A subject-matter contact who can answer translator queries.
Frequently asked questions
How is technical translation different from general translation?
Technical translation carries content a reader acts on, so accuracy is measured against the product, not just the language. It needs translators with subject knowledge, a fixed glossary, and a revision step. General translation can allow more freedom in wording; technical text usually cannot, because one term must mean one thing everywhere.
Do technical translators need an engineering background?
Not always, but they need working knowledge of the field. Ask vendors how they match translators to subjects, and whether an engineer or subject-matter expert reviews the translation. That optional review adds a technical check that a linguist alone cannot give.
Can you translate CAD drawings and schematics?
Yes. SEAtongue translates text in CAD files, blueprints, and schematics. Send the native, editable files where you can: text locked inside a PDF export is harder to extract and to put back cleanly.
Is machine translation acceptable for technical documents?
It can be, with trained human post-editing. ISO 18587 covers that workflow. It tends to suit large, repetitive documentation with a stable glossary. Safety warnings, regulated content, and text with new terminology are safer with full human translation and revision.
How do you keep terminology consistent across languages?
Build a glossary before translation starts and store approved translations in a translation memory. The glossary fixes each technical term once per language. The translation memory reuses approved sentences in later updates, so a revised manual keeps the same wording as the version already in use.
Planning manuals or safety documentation for new markets?
Tell us about your project, and our team will review your requirements and respond with a clear, commitment-free analysis of the right approach, scope, and timeline.
Contact our team.