Terminology management is the discipline of keeping an organisation’s important concepts accurately defined and appropriately named across languages, documents, software and media. Its gold standard is not a large glossary: it is trustworthy concepts, approved terms, traceable decisions and a practical system for detecting and repairing consequential mistakes.
This guide follows the fictional Estuary House science centre, whose translated content confuses a measuring instrument with a public flood-warning authority. The worked case demonstrates why terminology must govern meaning first, then wording, metadata and production systems.
Related specialist owners include Translation Memory Management Services for reusable bilingual segments, Multilingual Content Governance Services for published-language updates, and Translation and Interpretation Services for the wider language field. This article owns concept-oriented terminography and termbase governance.
Start with four decisions
- **Concept:** What does the item actually mean, and which neighbouring concept must it not be confused with?
- **Authority:** Which current source and subject specialist can validate the definition?
- **Language:** Which expressions and variants are accepted for each target audience?
- **Lifecycle:** Who approves, applies, tests and later changes that decision?
Choose a terminology-management route
23-chapter practical index
Concepts and authoritative definitions · chapters 1–7
- One term can change what a visitor believes a device does
- Start with concepts rather than matching words
- Specify the terminology domain and audience
- Give each concept its own stable identity
- Write definitions that distinguish neighbouring concepts
- Document preferred, admitted and deprecated expressions
- Use current terminology standards with the correct scope
Exchange, languages and workflow · chapters 8–15
- Treat TBX as an exchange format rather than a truth engine
- Separate TBX, XLIFF and translation memories
- Preserve source evidence for every disputed term
- Give subject experts and linguists different responsibilities
- Manage multiple target languages without assuming symmetry
- Separate abbreviations, symbols and units from ordinary terms
- Use terminology notes inside real content workflows
- Flag potential terminology errors without confusing them with proof
Errors, approvals and confidentiality · chapters 16–20
Testing, outcomes and stewardship · chapters 21–23
1. One term can change what a visitor believes a device does
A fictional science centre called Estuary House prepares an exhibit on coastal observation. Its English label distinguishes a tide gauge, which measures water level, from a public flood-warning service, which makes a separate decision about issuing information. In translated drafts, both are called ‘warning station’ in one language. A visitor may therefore think the physical gauge itself issues an official warning whenever water rises.
The gold standard of terminology management is not a spreadsheet containing thousands of bilingual words. It is a governed system that connects clearly defined concepts to approved expressions, subject expertise, audience context and real publication use. Estuary House is fictional, and the example is about language quality, not public warning instructions. It demonstrates why consistently reusing an incorrect term can be worse than an occasional visible inconsistency.
Back to chapter index · Continue to chapter 2
2. Start with concepts rather than matching words
A term is a designation for a concept within a domain, not simply a dictionary word waiting for an equivalent word elsewhere. A single expression can refer to different concepts in different industries, while one concept may have multiple acceptable designations. Terminology work begins by identifying the subject matter and what a thing means in that system.
ISO 704:2022 explains relationships among objects, concepts, definitions and designations. For Estuary House, a device that measures a level and an organisation that decides whether to publish a warning are separate concepts even if ordinary speech sometimes groups them. Before arguing over a translation, document what each concept actually is, what it is not, and which experts can confirm the distinction.
Back to chapter index · Continue to chapter 3
3. Specify the terminology domain and audience
A museum learning label, engineering procurement contract, software interface and clinical record all use specialist language differently. One term database covering all of them without domain boundaries can create false consistency. A terminology service should identify target audience, subject domain, reading level, jurisdictions and products in which its decisions will apply.
The science centre might need child-friendly labels for exhibits and more technical notes for educators. Both should remain scientifically consistent, but they need not contain identical phrasing. Document the accepted contexts and avoid forcing one preferred expression into every sentence. A technical word can be correct in a specialist glossary yet unsuitable for the public explanation if the resulting reader cannot understand it.
Back to chapter index · Continue to chapter 4
4. Give each concept its own stable identity
If a termbase uses a source-language spelling as the permanent identifier, a later name change may appear to create a new concept even when nothing substantive has changed. Stable concept IDs let the organisation manage multiple languages, names, variants and definitions against the same underlying meaning.
For the fictional exhibit, concept A could represent the water-level instrument and concept B the public warning service. Approved expressions, abbreviations and explanatory phrases can then be associated with each. A concept should not disappear when one language adopts a new preferred term. Stable identity also makes it easier to identify which translation memories, web pages and graphics require revision after a terminology decision.
Back to chapter index · Continue to chapter 5
5. Write definitions that distinguish neighbouring concepts
A useful definition should clarify the concept rather than merely restate the word or use another equally ambiguous term. For closely related concepts, define the distinguishing characteristic: what it measures, who operates it, what decision it represents, or which process it belongs to. Examples and notes can support but should not replace the definition.
At Estuary House, ‘a station that deals with tides’ would not distinguish a measuring device from a public information service. A more specific explanation links the device to measurement while reserving warning issuance for the appropriate decision process. Have the relevant subject expert approve the scientific meaning; the terminology team should not invent institutional authority. The definition must remain accurate when the display moves into another language.
Back to chapter index · Continue to chapter 6
6. Document preferred, admitted and deprecated expressions
A language may have one preferred term, acceptable alternatives for defined audiences, and expressions that should no longer be used. These statuses should be explicit and dated. A forbidden or deprecated term is not necessarily grammatically wrong in every context; its status reflects a controlled project or organisation decision.
An old exhibit might refer to ‘tide alarm’ colloquially while the new scheme chooses ‘tide gauge’ for the instrument. The termbase can preserve the legacy expression for searching or migration without recommending it in current copy. A reviewer needs to know why a term is deprecated and who approved the change. Merely removing the old spelling from the database may prevent editors from finding and repairing historical uses.
Back to chapter index · Continue to chapter 7
7. Use current terminology standards with the correct scope
ISO 12616-1:2021 sets requirements and recommendations for the fundamentals of translation-oriented terminography, particularly in low-complexity settings. Its abstract expressly excludes sophisticated management involving numerous roles and advanced terminological expertise. A multinational termbase may therefore need governance beyond what that part directly specifies.
ISO 704:2022 gives broader conceptual principles. ISO 30042:2019 defines TermBase eXchange, or TBX. As of October 2026, the proposed new edition remains ISO/CD 30042, a committee draft rather than a published 2026 standard. Use the actual published edition in the contract, and distinguish compliance with a data exchange format from competence in defining correct domain concepts.
Back to chapter index · Continue to chapter 8
8. Treat TBX as an exchange format rather than a truth engine
TermBase eXchange can represent structured terminological entries across tools, helping prevent manual copying and disconnected vocabularies. It does not automatically decide which definitions are scientifically right or who is authorised to accept a proposed term. Tools can exchange bad terminology perfectly.
ISO 30042:2019 explains TBX metamodels, data categories and dialects. Before exchanging a termbase, specify the applicable TBX profile or dialect, expected languages, fields and validation method. Test round trips between actual systems. Estuary House should not celebrate a successful import if the preferred expression, domain note or deprecated status has vanished during conversion. Interoperability and editorial authority must be reviewed independently.
Back to chapter index · Continue to chapter 9
9. Separate TBX, XLIFF and translation memories
TBX supports terminology data; XLIFF supports exchange of localisable content during production; translation memories typically store source and target segments for reuse. They serve related but distinct purposes. A translation memory may suggest an old sentence, while the termbase explains which current designation the sentence should use.
OASIS XLIFF Version 2.1 is a published OASIS Standard and can carry structured localisation content and relevant metadata. It does not replace ISO 30042 or make every imported segment terminologically correct. The eduKate Translation Memory Management guide addresses reuse governance. A professional workflow needs each resource to retain its own meaning, provenance and approval status.
Back to chapter index · Continue to chapter 10
10. Preserve source evidence for every disputed term
An editor may propose a term after reading a technical standard, an official agency page or a subject specialist’s explanation. The evidence should be recorded at a level sufficient for later review, including the source, date, edition and relevant limitations. A term copied from an anonymous forum is not equivalent to a designation accepted in an applicable regulatory document.
For Estuary House, the name of the instrument should be checked against the responsible scientific source and the exhibition’s educational scope. Store a source link or reference and its verification date. Do not assert that one country’s technical wording has legal authority in every destination market. A terminology service should give the client a way to inspect important decisions, not ask it to trust a hidden algorithm.
Back to chapter index · Continue to chapter 11
11. Give subject experts and linguists different responsibilities
Linguists understand meaning, grammar, usage and audience comprehension; subject specialists verify scientific, technical, financial or legal concepts. Neither expertise automatically substitutes for the other. Effective governance defines who proposes a term, who validates the concept, who decides local expression and who approves publication.
The museum curator may know how tide gauges work, while the Mandarin reviewer knows which phrase visitors will understand naturally. Where they disagree, record the underlying question and resolve it rather than letting the person with the highest job title override an unfamiliar language. A quality termbase shows both conceptual and linguistic approval. Assign accountable owners, not a single ambiguous checkbox called ‘reviewed’.
Back to chapter index · Continue to chapter 12
12. Manage multiple target languages without assuming symmetry
One concept may require a short noun in one language, a compound term in another and an explanatory phrase in a third. A good multilingual termbase represents those differences instead of requiring identical word counts or copying grammatical structures across languages. Some languages may have several accepted registers or variant spellings.
For the fictional exhibit, a compact English label might need more space in Malay or Tamil while preserving the same scientific meaning. Note accepted variants and audience context. A term should not be marked wrong merely because it uses more words than the source. The objective is concept consistency and usability, not visual symmetry across columns in a database.
Back to chapter index · Continue to chapter 13
13. Separate abbreviations, symbols and units from ordinary terms
Abbreviations and symbols can carry technical meaning, but a local reader may not recognise them. Some abbreviations remain unchanged internationally; others have different established conventions. Units, numerical values and codes may need precise preservation while surrounding explanations change.
A water-level figure in the museum could use a measurement unit that must remain mathematically accurate. Translators should not freely adapt an instrument code or change a unit without the authorised conversion and review. Store expansion, allowed short form and context as separate fields. A glossary of words alone may miss consequential symbols that appear in charts, annotations, equations and control labels.
Back to chapter index · Continue to chapter 14
14. Use terminology notes inside real content workflows
A termbase is most helpful when authors, translators and reviewers can reach relevant definitions where they make decisions. A detached spreadsheet emailed after translation has finished may do little to prevent mistakes. Tool integration should carry context, warnings and current versions rather than only show a preferred word.
W3C ITS 2.0 includes a Terminology data category that can identify terms and link to additional information in HTML or XML content. ITS 2.0 was published in 2013; it is not a 2026 substitute for TBX. The science centre can link a technical term in its content source to the correct concept entry, while still requiring a human reviewer to assess whether the suggested expression fits the sentence.
Back to chapter index · Continue to chapter 15
15. Flag potential terminology errors without confusing them with proof
Automated QA systems can identify use of deprecated expressions, inconsistent spelling or apparent disagreement with an approved termbase. They may also flag valid grammatical inflections, quotations of historical material or intentionally different senses of one word. Such flags need review by someone with sufficient subject and language context.
The W3C ITS 2.0 localisation-quality categories distinguish terminology issues from mistranslation, omission and other problems. An error flag is a hypothesis, not a final penalty. In the museum label, the wrong term is important because it turns a measurement device into a warning authority. A harmless grammatical variation should not be given the same severity merely because a string matcher does not recognise it.
Back to chapter index · Continue to chapter 16
16. Govern source-language writing, not only translations
Many downstream inconsistencies begin with ambiguous source content. If different writers call the same instrument by different names, translators may be forced to guess or create several target-language concepts. Terminology management should therefore inform source authoring and documentation before translation begins.
Give writers current terms, definitions and usage examples. When the source means different concepts, require authors to express the distinction rather than ask translators to conceal it. An editorial review of the original science script may reveal that a narrator uses ‘warning’ loosely. Repairing that source can improve all target editions at once. This is usually more responsible than fixing each translation independently after publication.
Back to chapter index · Continue to chapter 17
17. Create a lifecycle for proposing and approving changes
Terms evolve as products, regulations and audience language change. A service needs states such as proposed, under review, accepted, deprecated and withdrawn, with clear dates and approval rights. A change should not be allowed to propagate to all published content merely because a contributor edited one spreadsheet cell.
Record the reason, source and expected impact of each substantive decision. If the science centre changes its approved name for an instrument, identify affected website labels, audio scripts, translated graphics, learning sheets and stored translation segments. A current termbase is a managed decision system, not a static dictionary updated only before a major annual campaign.
Back to chapter index · Continue to chapter 18
18. Protect confidentiality and client-specific terminology
A termbase may contain unreleased product names, regulated technical details, internal project codes, customer identities and commercially sensitive definitions. Sharing entries across unrelated customers can create confidentiality breaches and intellectual-property disputes. Technical reuse must follow ownership, contractual permission and access boundaries.
A language vendor working for two different science publishers should not automatically merge private termbases to increase apparent efficiency. A shared public glossary and a restricted client-specific terminology database can have different rules. Establish roles, audit logs, export permissions and data retention. If generative AI or external terminology tools receive sensitive entries, verify that the client authorised the relevant processing and reuse before uploading them.
Back to chapter index · Continue to chapter 19
19. Resolve conflicting sources through a visible authority hierarchy
Several documents may give different expressions: an old approved brochure, a newly issued technical guideline, a translation memory and a staff member’s familiar phrase. The service must establish which evidence governs the target content, with the relevant client or domain owner deciding actual precedence.
Do not use ‘most recent’ as an automatic rule if the new document concerns another jurisdiction or a different technical object. For the fictional tide-gauge exhibit, check the current authoritative definition applicable to the display and keep historical names for search where useful. A dispute log should show the competing options, reasoning and approved conclusion. This prevents a reviewer from reopening the same disagreement on every page.
Back to chapter index · Continue to chapter 20
20. Measure terminology quality against meaningful risk
A termbase may contain thousands of entries while the most important safety or contractual terms remain undefined. A raw entry count cannot show quality. Useful indicators include approved concepts covering critical content, wrong-concept incidents, expired sources, unresolved decisions, usage of deprecated terms and successful fixes in live products.
Assess how serious an error is for the reader and the purpose. Misnaming a warning authority carries different consequences from using a slightly less elegant synonym in a decorative title. A review should identify which terms caused user misunderstanding and where. An executive dashboard should not average away one significant meaning error inside thousands of harmless style variations. Reliable terminology reduces consequential confusion, not merely the number of spelling differences.
Back to chapter index · Continue to chapter 21
21. Test in real layouts, audio and user journeys
An approved term can fail in a cramped mobile button, rapidly timed subtitle or unfamiliar voiceover. The language team must verify how terminology appears in the actual content medium. A correct dictionary entry does not prove that the product’s graphics, audio and navigation use it consistently.
For Estuary House, test the science explanation with actual exhibition visuals. Can the visitor distinguish the tide-gauge instrument from the official warning process after viewing the relevant labels, audio and diagram? If the answer is no, inspect the concept and presentation together. Correct terminology supports comprehension; it should not become jargon that only the project’s experts can decode.
Back to chapter index · Continue to chapter 22
22. Hand over a maintainable termbase and decision record
A professional service should deliver more than a proprietary database the client cannot open after a vendor contract ends. The agreement should specify export format, languages, concept IDs, definitions, status, sources, decisions and version history where relevant. It should also identify which information remains restricted by licences or client confidentiality.
Test a realistic export and import rather than assume a logo promising TBX support proves all fields will survive. Provide a concise guide explaining how to approve new entries and resolve conflicts. The client should be able to keep its public information current without asking a former contractor to reveal the only copy. Interoperability is useful only when it preserves enough context for continued responsible decisions.
Back to chapter index · Continue to chapter 23
23. The gold standard is one concept reliably understood in every edition
Return to Estuary House. Its revised display clearly distinguishes the measuring instrument from the authorised public information process. Each language uses suitable approved expressions, the glossary retains relevant historical variants, and a reader can find the underlying definition and verified source. Editors know how to request an update when the science or official terminology changes.
Terminology management earns its gold standard through precise concepts, appropriate language and governance that persists across publications. An enormous list of translations may look impressive, but real value appears when users make the right distinction and future teams can explain why a term was selected. The best termbase makes meaning dependable without pretending that all language is reducible to rigid substitution.
Worked case: one wrong designation changes a public explanation
Estuary House is fictional. The matrix is an illustrative governance test, not a scientific definition or operational flood-warning instruction.
| Object or idea | First terminology problem | Required control |
|---|---|---|
| Water-level measuring device | Called ‘warning station’ | Distinct concept, definition and preferred language expression |
| Official warning publication process | Conflated with the device | Separate subject-authority review and source evidence |
| Multilingual exhibit label | Consistent translation of the wrong concept | Concept-oriented review in every target language |
| Historical brochure | Old term still in searches and references | Deprecated variant linked to a stable concept ID |
| Future source update | Only one target language corrected | Impact mapping and verified published-language changes |
Client handoff: the controlled terminology entry
A useful entry must remain interpretable after another vendor receives it. The columns below provide a compact procurement and data-quality acceptance plan.
| Field | Purpose | Acceptance question |
|---|---|---|
| Stable concept ID | Keep meaning linked across revisions | Does identity survive a rename? |
| Definition and domain | Distinguish neighbouring ideas | Could a specialist verify the scope? |
| Terms by language | Preferred and accepted designations | Are register and use restrictions explicit? |
| Status and sources | Preserve authority and date | Can deprecated terms be traced? |
| Decision and ownership | Support responsible changes | Can another reviewer reconstruct why? |
| Exchange format | Enable tool portability | Do essential fields survive round trip? |
A practical termbase-governance checklist
- Define domain and audience before collecting terms.
- Give different concepts stable identifiers, accurate definitions and source evidence.
- Distinguish preferred, admitted and deprecated expressions per language.
- Follow ISO 704:2022, ISO 12616-1:2021 and published ISO 30042:2019 within their scope.
- Keep TBX terminology separate from translation memory and XLIFF content.
- Use subject expertise and target-language review before approval.
- Protect customer-specific terms, unpublished products and rights.
- Check real website, video and interface uses for meaningful outcomes.
- Export a maintainable termbase with open issues and future ownership.
Frequently asked questions
The answers below address edition confusion, client ownership, language variation and how to evaluate real terminology quality rather than vocabulary volume.
1. How is a termbase different from a bilingual dictionary?
A general bilingual dictionary offers possible meanings and language usage. A governed termbase identifies a defined concept within a subject domain and records approved, admitted or deprecated designations, context, sources and decisions. For translation projects, that distinction prevents a common word from being substituted where a technical concept requires something specific. A termbase should still be understandable to human users, not only software.
2. Is terminology management the same as translation memory management?
No. Translation memories preserve aligned source-and-target segments for reuse. Terminology systems govern specific concepts and their designations. A memory can contain an outdated term, while a termbase can instruct a reviewer to correct it. Integrations are helpful, but they must preserve approval status and recognise legitimate inflection or context variation. Neither resource replaces human subject expertise or current source content.
3. Which ISO terminology standards are current in October 2026?
ISO 704:2022 remains published for terminology principles; ISO 12616-1:2021 remains published for fundamentals of translation-oriented terminography in low-complexity settings. ISO 30042:2019 is the published TBX standard. Its planned replacement is a committee draft, not a published ISO 30042:2026 edition. Always confirm the contractual scope and current ISO record rather than substitute an anticipated edition.
4. Can a successful TBX import prove that a termbase is correct?
No. An import can prove that a file was accepted by software under certain conditions. It does not verify domain concepts, sources, cultural acceptability or approved statuses. Test whether definitions, languages, preferred terms, deprecated variants and identifiers survive exchange, then perform competent content review. A system can move wrong information without error while becoming more dangerous because the data looks standardised.
5. How should two departments resolve incompatible preferred terms?
Define the shared concept, the relevant domain, the audiences and the sources used by each department. A science team may approve a technical expression while a public communications team needs a readable explanatory label. Sometimes both can be accepted within their stated contexts. Record the decision and owner, rather than choose one term solely because the person proposing it holds a more senior position.
6. Should every organisation demand one term per concept in every language?
A concept should be identifiable consistently, but natural language allows context, register, inflection and multiple legitimate designations. Forcing one literal phrase into every sentence can harm clarity. A termbase should express which form is preferred where and which alternatives are allowed. Consistency of meaning matters more than mechanical repetition of identical words.
7. How can a termbase handle units and abbreviations?
Treat symbols, official codes, abbreviations and units as separately governed fields where necessary. State approved expansion, use case, measurement context and restrictions. A translation should not casually transform a numeric measurement or public authority code as though it were marketing wording. A qualified domain reviewer should examine conversions or legally fixed terms. Test their appearance in charts and interface labels, not just in paragraphs.
8. How does W3C ITS 2.0 relate to TBX?
ITS 2.0 can mark terms and other localisation metadata within HTML or XML content, potentially pointing to additional term information. TBX provides a structured exchange model for terminology databases. They address related but different data layers. ITS 2.0 is a W3C Recommendation from 2013; TBX’s published ISO edition remains 2019 as of October 2026. A production workflow can use both without suggesting one replaces the other.
9. What happens if an expert rejects an AI-suggested term?
Record the rejected expression and the approved reason where useful, then ensure the trusted termbase is not automatically overwritten by machine output. Determine whether affected source, memory and published assets need correction. AI can suggest candidates, but technical accuracy, audience comprehension and legal or client authority still need review. A rejection record can prevent the same unsuitable suggestion from repeatedly returning.
10. How should quality be measured without inflating entry counts?
Measure coverage of consequential concepts, the age and strength of source evidence, unresolved disputes, wrong-concept occurrences and improvements in actual materials. A database containing many trivial synonyms is not necessarily more useful than a smaller, well-reviewed one. Use error severity linked to reader harm and task completion. Do not disguise one misleading public warning label within a high average terminology-consistency score.
11. Can two clients’ termbases be merged by a vendor?
Only where contracts, confidentiality and intellectual-property permissions allow it. Entries may contain unpublished product information or client-specific terminology that should not be disclosed. Separate public standards-based terms from private approved preferences and confirm the rules for shared use. Technical convenience does not create a legal right to cross-reuse client data. The vendor should be able to explain access controls and export ownership.
12. What should be in a final terminology-management handoff?
Provide concept identifiers, approved definitions, applicable languages, term status, domain context, sources and review history in the agreed format, plus instructions for future updates. Test that the client can import and search the delivery and that relevant statuses survive. List open disputes, restricted entries and any untranslated concepts rather than marking every column complete. Name the person or role authorised to approve future changes.
Verified standards and eduKate ecosystem routes
- ISO 704:2022 — Terminology Work: Principles and Methods
- ISO 12616-1:2021 — Translation-Oriented Terminography
- ISO 30042:2019 — TermBase eXchange (TBX)
- ISO/CD 30042 — Committee Draft, Not Yet Published
- W3C Internationalization Tag Set 2.0 — Terminology Markup
- OASIS XLIFF 2.1 — Localisation Content Exchange
- ISO 11669:2024 — Translation Project Guidance
- eduKate — Translation Memory Management
- eduKate — Multilingual Content Governance
- Gold Standard Sectors & Services Directory
Standards note, 19 October 2026: ISO 30042:2019 remains the published TBX standard; the new edition is an ISO committee draft. ISO 12616-1:2021 has a specifically stated lower-complexity scope and cannot alone certify an enterprise terminology governance programme. Tool interoperability, content accuracy and regulatory authority are separate claims. This article is an educational service guide, not a certificate or public safety instruction.