Terminology Management Services

What Terminology Management Services Cover

Terminology management is the discipline of deciding, once and in writing, what your products and processes are called in every language you sell into, then enforcing those decisions across every document and every linguist who touches your content. As a service, it has concrete deliverables: a structured multilingual termbase, definitions and usage notes for each concept, a validation workflow that puts approval in the hands of your engineers, and a maintenance cadence that keeps the asset current as your product line evolves.

The problem it solves is mundane and expensive. A hydraulic component called a "check valve" in your manual, a "non-return valve" in your spare parts list, and a "one-way valve" in your training slides will be translated three different ways, and your Mexican distributor will file three support tickets asking whether these are three parts. After 15 years of technical translation for US manufacturers, we can say plainly that inconsistent terminology causes more review cycles, more field confusion, and more rework than any other single factor. It is also entirely fixable. This page describes the fix as we deliver it; for how terminology plugs into the rest of our production, see the services overview.

Building Your Termbase: Extraction, Definition, Validation

We do not build termbases by asking you to fill in a blank spreadsheet. The raw material is documentation you already have, and the process runs in five stages:

1. Corpus assembly. We gather a representative slice of your content: manuals, datasheets, drawings, UI strings, and quality documents. Work we have already done for you, such as translating quality manuals, feeds straight into the corpus.
2. Term extraction. Extraction tools mine the corpus for candidate terms by frequency and termhood scoring; a terminologist then filters the candidate list, typically cutting 60–70% of it, because tools cannot tell a genuine term from a recurring phrase.
3. Concept entries. Each surviving term becomes a concept entry: definition, part of speech, context sentence from your own documents, source reference, and where relevant an image or part number.
4. Target-language equivalents. Specialist translators propose equivalents per language, flagging cases where two English terms collapse into one foreign term or vice versa, which is where most translation disputes actually start.
5. Client validation. Your engineers review and approve through a lightweight workflow: a shared review sheet or an online termbase portal, batched so no reviewer ever faces 800 terms at once. Nothing becomes binding until your side signs off.

A first working termbase of 300–500 concepts usually takes three to four weeks from corpus handover to validated delivery. That is deliberately modest. A validated 400-term base outperforms a speculative 4,000-term list every time, because linguists trust it.

Approved, Forbidden, Deprecated: Why Term Status Does the Heavy Lifting

A glossary that only lists correct terms solves half the problem. The other half is telling linguists, and increasingly MT engines and authoring tools, what they must not write. Every entry in a Techniwords termbase carries a status, and the statuses are enforceable in CAT tool QA checks, which means violations are caught mechanically before delivery rather than by an annoyed reviewer afterward.

Status	Meaning	Example
Approved	The one term to use for this concept in this language	"E-stop pushbutton" for the emergency stop device
Forbidden	Understandable but banned: legacy names, competitor trademarks, unsafe shorthand	"Kill switch" banned in operator-facing text
Deprecated	Formerly approved; being phased out, with a dated replacement note	Old product line name after a rebrand
Pending	Proposed, awaiting your engineers' decision; usable only with a query flag	New feature vocabulary during development

Forbidden terms earn their keep in regulated settings. In nuclear industry documentation, plant-specific component designations are contractual, and a synonym that would pass any ordinary review can fail a regulator's document audit. Terminology work in that sector often starts from the standards themselves, and our experience with ISO and ASTM standard translation means definitions get anchored to the normative source rather than to habit.

You Own Your Terminology: TBX and Portability

Some agencies treat the client's termbase as a retention device: it lives in their systems, exports are grudging or billed, and leaving them means starting over. We take the opposite position, in writing. The termbase we build for you is your property. You receive a full export in TBX (TermBase eXchange, ISO 30042), the vendor-neutral standard that loads into MultiTerm, memoQ, Phrase, XTM, and every serious terminology platform, plus Excel and CSV for people who just need to look terms up. Exports are free, on request, forever, including the day you decide to move your work elsewhere.

Portability also works in reverse. If you arrive with terminology scattered across old vendor glossaries, engineering spreadsheets, and a SharePoint folder nobody maintains, we consolidate, deduplicate, and migrate it into a single structured termbase, preserving whatever validation history exists. Combined with translation memory services, this gives you a complete, portable language asset package: the TM holds your sentences, the termbase holds your decisions, and both leave with you if you ever go.

Registers by Industry and by Client

The same word rarely means the same thing two industries apart, and a termbase that ignores this fails quietly. "Torque converter" belongs to drivetrains; "converter" alone means something entirely different in a steel mill or a power electronics lab. We structure termbases with registers: industry-level vocabulary shared across your sector, and client-level vocabulary that is yours alone, product names, internal abbreviations, part designations, brand voice rulings. A component supplier serving two sectors gets one commercial register and two technical ones, so the same sensor is described in IATF 16949 language for one buyer and in FDA language for another without cross-contamination.

Language pairs bring their own register problems. German technical writing compounds nouns aggressively, and deciding whether Drehmomentbegrenzungskupplung is rendered as one approved English term or a descriptive phrase is exactly the kind of ruling a termbase exists to record; our German technical translation team logs these decisions with justifications, not just equivalents. In automotive translation programs, registers additionally have to track customer-imposed vocabulary, because a Tier 1 supplier writing for two OEMs may be contractually required to call the same fastener by two different names.

The ROI of Managed Terminology, in Numbers You Can Defend

Terminology work is easy to postpone because its cost is visible and its benefit is diffuse. So we measure the benefit. On accounts where we run terminology management, we track three indicators quarterly: reviewer comments per 1,000 words, rounds of client review per document, and ramp-up time for linguists new to the account. A typical trajectory on a mature account: terminology-related review comments drop by 60–80% within two quarters, most documents settle at a single review round, and a new translator becomes productive in days instead of weeks because the termbase answers the two hundred questions they would otherwise ask your engineers.

One project from our files: a Midwest industrial equipment maker came to us with four target languages and a review process their German subsidiary described as hostage negotiation. Extraction across their manuals and ERP exports surfaced 214 concepts with two or more competing English source terms before translation even entered the picture. After an 1,800-concept termbase was validated, their engineering reviewers went from marking up roughly 40 terminology objections per manual to fewer than five, and their review cycle shrank from three weeks to four days. The termbase paid for itself inside the first documentation release. The people applying it day to day are the certified specialists described on this page, and terminology discipline is a standing requirement of our ISO 17100-compliant process, with independent revision checking term compliance on every job.

How the Termbase Is Enforced in Production

A termbase only earns its cost if it is wired into the tools where words actually get written. In our translation workflow, the termbase is loaded into the CAT environment on every project for your account, where active term recognition shows the approved equivalent to the translator as each segment opens. Compliance is then checked mechanically: the QA gate flags any segment where a source term appears but its approved target does not, and any use of a forbidden term, before the file can move to revision. The independent reviser sees the same term hits, so a disputed term triggers a query to you rather than a silent local decision by one linguist.

Enforcement extends beyond human translation. When an account uses machine translation with post-editing, the approved termbase is injected into the engine as a glossary constraint where the engine supports it, and post-editors are scored on term compliance in sample audits. On the authoring side, several clients load our exports into source-language checking tools such as Acrolinx or into their style guide tooling, so technical writers stop introducing new synonyms upstream. That closes the loop: the same 400 decisions govern the writer in Milwaukee, the translator in Stuttgart, and the MT engine in between.

• During translation: live term recognition in the CAT tool, per language, with definitions and usage notes visible in context.
• Before delivery: automated QA pass that blocks missed approved terms and any forbidden term, logged per file.
• During revision: term deviations surfaced to the second linguist, with client queries raised instead of improvised fixes.
• Upstream: optional source-terminology exports for your authoring and content teams, so consistency starts before translation.

Maintenance: a Termbase Is Fed or It Dies

An unmaintained termbase decays into a liability, confidently prescribing last year's names. Our maintenance service runs on a cadence matched to your release rhythm, usually quarterly for manufacturers and per-release for software clients. Each cycle covers: new term candidates harvested from recent projects and linguist queries, status changes (approvals, deprecations after rebrands or redesigns), conflict resolution when two departments have blessed different terms, and a compliance spot-check of recent deliveries against the current base. You receive a change log per cycle, so your documentation team always knows what moved and why.

Maintenance is priced as a modest per-cycle retainer scaled to termbase size and activity, not per term, so there is no incentive on either side to pad the base with junk entries. Initial construction is quoted as a fixed project fee based on corpus size and language count: a 400-concept base in two target languages sits at the low end, a 2,000-concept base across five languages with engineer workshops at the high end, and the quote itemizes extraction, entry writing, and validation support separately so you can see where the effort goes. Clients with active translation programs typically fold the retainer into their per-project pricing; standalone terminology engagements, for companies that translate in-house or elsewhere, are equally welcome and priced the same transparent way. As a member of ATA and GALA, and working from our Texas office across all US time zones, we run terminology programs for clients ranging from 200-concept startups to multidivision termbases north of 10,000 concepts. The structure is the same; only the scale changes.