The most expensive word in translation is the one you define twice. Or worse – the one you never define at all.
Technical translation lives and dies on terminology. A valve is a valve is a valve – until one document calls it a “gate valve,” another calls it a “shut-off valve,” and a third simply says “valve.” Internally, your engineers know these terms are interchangeable for your product. Your German customers don’t. Your French distributors definitely don’t. And your translation costs just tripled because every inconsistency creates confusion, rework, and risk.
Terminology management isn’t glamorous. It doesn’t make presentations or win awards. But it’s the foundation that determines whether your multilingual documentation works as a coherent system or an expensive mess.
The hidden cost of inconsistent terminology
Most businesses discover terminology problems the hard way. A customer complains that the spare parts list doesn’t match the user manual. A distributor reports confusion about product specifications. An auditor flags inconsistencies in safety documentation. By then, the damage is done – not just to the documents, but to confidence in your brand.
The costs multiply quickly. Every inconsistent term requires translator research time. Every variation creates potential for misunderstanding. Every correction requires updating multiple documents across multiple languages. A single ambiguous term in English becomes multiple ambiguous terms across your language set, each requiring individual attention.
More seriously, inconsistent terminology creates compliance risk. Regulatory documentation requires precision. If your Declaration of Conformity uses different terminology than your user manual, auditors notice. If your safety instructions use terms that don’t appear in your training materials, that’s a gap that could matter when something goes wrong.
What terminology management actually involves
Terminology management is simply the practice of deciding what you call things and sticking to it. In principle, it’s straightforward. In practice, it requires deliberate effort.
The core is a termbase – a controlled vocabulary of approved terms and their definitions. For each concept, you define the preferred term in English, any acceptable alternatives, any terms that should not be used, and the approved translations in each target language. You might also include context notes, usage examples, and references to where the term appears in your documentation.
This sounds like creating a dictionary, but it’s more specific. A termbase isn’t trying to capture every possible meaning of every word. It’s capturing how your organisation uses particular terms in particular contexts. “Controller” might have dozens of meanings in general English. In your termbase, it has one meaning – the specific component in your product – and one approved translation in each language.
The termbase becomes the reference point for everyone involved in creating and translating documentation. Writers use approved terms. Translators use approved translations. Reviewers check against the termbase. Consistency becomes systematic rather than accidental.
Building a termbase that works
The temptation is to start big – to catalogue every term that might possibly need managing. This approach fails. You end up with thousands of entries, most of which nobody ever references, and the genuinely important terms get lost in the noise.
Start with the terms that matter most. Product names and model numbers. Key components and their functions. Safety-critical terminology. Industry-standard terms where precision matters. Regulatory terms with specific meanings. This core vocabulary – perhaps fifty to a hundred terms for most businesses – delivers most of the value.
For each term, capture more than just the word itself. Include a clear definition that distinguishes this term from similar terms. Note the context where it applies. Identify any terms that are explicitly wrong – the variations you don’t want used. This context helps translators make good decisions even when the termbase doesn’t cover every possible situation.
Source your translations carefully. The approved German translation for a technical term should come from someone who knows both the language and the subject matter. Ideally, it should align with how your customers and industry actually use the term in that market. A technically correct translation that nobody in the target industry recognises is worse than useless.
Making terminology management stick
A termbase that sits in a folder helps nobody. Terminology management only works when it’s embedded in how you actually create and translate documentation.
For writers, this means making the termbase accessible and expected. If your technical authors are writing in isolation, consulting the termbase when they remember, consistency will be patchy. If the termbase is integrated into your authoring environment – flagging unapproved terms, suggesting approved alternatives – consistency becomes the path of least resistance.
For translators, the termbase should be part of the translation brief. Professional translation tools can integrate termbases directly, flagging when source terms have approved translations and warning when those translations aren’t used. This isn’t about constraining translators – it’s about giving them the information they need to make good decisions.
For reviewers, the termbase provides an objective reference. Instead of subjective debates about whether a particular translation “sounds right,” reviewers can check whether approved terminology has been used. This makes reviews faster and more consistent.
Governance and maintenance
Terminology isn’t static. Products evolve. New features require new terms. Industry usage shifts. Regulations introduce new requirements. A termbase that isn’t maintained becomes a historical document rather than a working tool.
Someone needs to own terminology. In most organisations, this sits with technical documentation or quality – someone close enough to the products to understand what terms mean, with enough authority to make decisions stick. Without clear ownership, terminology decisions become consensus exercises that never conclude.
New terms need a defined process for addition. When a product manager introduces a new feature name, that needs to flow into the termbase before documentation starts. When a translator encounters an untranslated term, there needs to be a route to get it approved rather than making an ad hoc decision that may or may not stick.
Regular review keeps the termbase current. Terms that are no longer used can be archived. Translations that have proven problematic can be revised. New terms from recent projects can be formally added. Annual review is minimum; quarterly is better for active documentation programmes.
The translation workflow connection
Terminology management and translation memory work together. Translation memory captures how you’ve translated content before. Terminology management captures how you’ve decided terms should be translated. When they’re aligned, consistency compounds. When they’re not, you get systematic inconsistency – the same wrong term used correctly every time.
The integration matters. When your translation memory suggests a previous translation, your termbase should validate whether that translation uses current approved terminology. When your termbase specifies a translation, your translation memory should learn it for future use. This alignment isn’t automatic – it requires deliberate setup and maintenance – but it’s what transforms terminology management from a reference document into an active quality system.
The business case for getting this right
Terminology management requires investment. Someone needs to build the termbase. Someone needs to maintain it. Your translation workflow may need adjustment to use it properly. This isn’t free.
But the returns are concrete. Translation costs reduce because translators spend less time researching terminology and less time on rework. Review time reduces because there’s an objective standard to check against. Quality improves because consistency is built in rather than hoped for. Risk reduces because safety-critical terminology is controlled.
Perhaps most importantly, your documentation works as a system. User manuals match spare parts lists. Training materials match operating procedures. Specifications match marketing claims. Your customers experience coherent communication rather than a collection of documents that happen to be about the same product.
At Bubbles, we help clients build and maintain terminology that works across languages. We understand that terminology management isn’t about creating perfect dictionaries – it’s about creating practical systems that make consistency achievable and sustainable.
