2025-11-19 · Baduno Editorial Team · 7 blog.readMin · Blog & Knowledge
Five Steps to Your First Terminology Database
When the same product has four names in three texts, it's time for a termbase. A pragmatic start without a software project.
Steps 1–2: Collect and Review
Extract recurring technical terms from your website, catalog, and contracts – a simple spreadsheet is enough. Mark duplicates and variants: this review alone reveals most inconsistencies.
Step 3: Decide
Define one preferred term per concept – and just as important: document prohibited variants. This decision belongs to the subject-matter departments, not to translation; they know the impact on the customer.
Step 4: Have It Translated
Only now do languages come into play: one binding equivalent per target language, reviewed by native speakers with domain expertise. Twenty core terms translated properly beat two hundred unchecked ones.
Step 5: Enforce
A term base only works if it is embedded in the workflow: as a checklist in editing, as a specification in the translation pipeline, as an appendix in every service provider briefing. Maintain it like your price list – it is just as business-critical.
Step 6: Institutionalize Terminology Maintenance
Define who can propose changes and who approves them. A three-tier model has proven effective: any employee can suggest entries, an editor checks for formal correctness, and a subject matter expert makes the final decision. Document the date of each change and maintain a change log. Schedule quarterly reviews of the most common error sources: evaluations from editing show where the termbase has gaps or is outdated. Without regular maintenance, any terminology degrades within 18 months—for example, a manufacturer of industrial components defined "guide rail" in 2020, but by 2023, three departments were using "slide rail" and "profile guide" in parallel. The review took four hours, correction in eight languages two days. Institutionalize maintenance as an integral part of your quality management system, not as a post-project activity.
Step 7: Integrate Terminology into Your Translation System
The best termbase is useless if your translators have to browse it manually. Integrate terminology into your translation management system (TMS) or computer-aided translation (CAT) tool. Modern systems automatically display the preferred term while typing and highlight deviations in color. To do this, export your table as TBX (TermBase eXchange)—the ISO standard for terminology data. The import routine automatically checks for duplicate entries. For example, a medium-sized machine manufacturer loaded 500 terms in six languages into their TMS via a TBX file. The consistency of their operating manuals increased from 68% to 94% within one quarter. Plan the integration effort realistically: an IT test with three terms and one language takes half a day; the full roll-out across all target languages takes two to three days.
Step 8: Define KPIs for Terminology Quality
Measure whether your terminology work is having an impact. Three proven KPIs are: terminology consistency (proportion of correctly used preferred terms per document), terminology coverage (proportion of terms in the termbase relative to total vocabulary), and error recurrence rate (proportion of previously recorded errors that reappear). Measure monthly and transparently share the values with product areas. A medical technology company increased consistency from 72% to 95% after introducing these KPIs by incorporating the three most common violations into its editorial guide. Important: Never link KPIs to sanctions, but to improvement suggestions. A high error recurrence rate usually indicates that terminology is not findable in the workflow – in that case, the integration in step 7 is too weak.
When the same product has four names in three texts, it's time for a termbase. A pragmatic start without a software project.
Step 9: Anchor terminology as part of the content strategy
Terminology must not live isolated in the translation process. Integrate it early into content creation: editors should access the termbase when writing, not just translators. Ideally, a central glossary in the content management system (CMS) automatically suggests the correct term when creating new pages. A manufacturer of solar modules required its German-language editorial team to have every new term reviewed by technical editing before publication. Result: The number of subsequent corrections in translations dropped by 60%. Also plan for the decommissioning of product names: when you discontinue a product, archive the entries – do not delete them, otherwise historical references in old documents will be missing. Take responsibility for terminology as a strategic asset, not a tedious chore.
Terminology in Agile Content Workflows
In agile development processes, content is created iteratively and often decentralized. A lightweight terminology process that prioritizes speed over completeness has proven effective here. Instead of a large termbase, at the start of each sprint you define the five to ten most important terms for the current feature and record them in the shared team glossary. This list grows with each sprint and is transferred to the main termbase at the end of the quarter. Ensure that terminological decisions are not left to the developer or writer: the Product Owner or a designated subject matter expert specifies the preferred term. Integrate terminology checks into the definition of done: each user story undergoes a brief terminology review before being sent for translation. A software manufacturer reduced the number of terminology corrections by over 40% using this method, without slowing down the agile flow. The key lies in focusing on essentials and clear accountability per sprint. Avoid trying to manage all terms at once – that blocks content production.
Cost-Effectiveness of Terminology Work
Terminology work incurs costs before it generates benefits. Therefore, plan a realistic cost-benefit analysis that compares the effort for collection, decision-making, maintenance, and integration with the savings. The main benefits are: reduced translation costs due to fewer post-edits, faster time-to-market through consistent documentation, and lower liability risk through clear product names. A mechanical engineering company found that 20 hours of initial terminology work saved 120 hours of editorial time over six months. Be conservative: assume savings of 10 to 15 percent of translation costs when maintaining a termbase with 100 to 200 terms in five languages. Important: document the savings transparently by measuring the time for correction cycles before and after introducing terminology. This builds a case for the budget for the next maintenance round. Also consider opportunity costs: an inconsistent product confuses customers and ties up support resources. Terminology is not a pure cost factor but an investment that pays for itself within a year when properly maintained.
Terminology and Legal Certainty: Minimizing Liability Risks
In regulated industries such as medical technology, pharmaceuticals, or mechanical engineering, consistent terminology is not just a matter of quality, but of legal compliance. An incorrectly translated safety warning or an inconsistent product designation in the instructions for use can lead to product liability cases. The EU Product Liability Directive and the Machinery Regulation require clear, traceable terms in all languages. A terminology database addresses this by establishing binding designations and excluding variant forms. Proceed systematically: Store the respective legal basis (e.g., ISO standard, EU directive) as metadata for each term. This allows your translator to immediately recognize the regulatory binding nature. Example: A manufacturer of insulin pumps legally defined the terms "dosage" vs. "dose" and entered them into the termbase. After a product defect, the company was able to prove that the translation exactly matched the normative requirement – averting liability. Also maintain a change log with dates and approvers to present a complete history in case of dispute. Consider archiving: Old product designations remain in the termbase so that legacy contracts can be referenced with legal certainty. A term-based legal documentation is not overhead but an investment in your legal position.
Terminology for Multilingual SEO: hreflang and Keyword Consistency
For international websites, terminological consistency is a crucial SEO factor. Search engines evaluate whether titles, descriptions, and headings are aligned across all language versions. A central termbase ensures that, for example, "product configurator" uses the same word choice in all target languages – otherwise you confuse crawlers and users. Even more important is the connection with hreflang tags: These tell Google which language version is relevant for which market. If the terms do not match, user experience suffers and bounce rates increase. Therefore, define a canonical term per language for each product family and store it in your CMS. For instance, a cloud software provider standardized "dashboard" in five languages and simultaneously optimized its hreflang implementation. The result: click-through rate from organic search increased by 15 percent, measurable without warranty limitation. Integrate your termbase into the SEO review: Before launching new landing pages, have the target pages checked by a native speaker with SEO expertise for terminological accuracy. Also document regional variants (e.g., "Handy" vs. "Mobiltelefon") and store them as regional preferences in your termbase. This avoids duplicate rankings for the same term in the same language.
blog.faqT
Can I manage a terminology database without special software?
Yes, for starters, a simple spreadsheet in Excel or Google Sheets is sufficient. Columns: Term, Preferred Term, Forbidden Variants, Definition, Source, Status, Last Change. It is important that you maintain the table regularly and that all parties use a binding version. As the number of terms or languages grows, it is advisable to switch to a specialized terminology tool with TBX export.
How often should I review and update my terminology?
At least once per quarter, you should evaluate the most common errors from your editorial reviews and supplement the termbase. New products or legal changes require immediate updates. Additionally, conduct an annual review of all entries to archive or correct outdated terms. A well-maintained terminology evolves with your products and markets – otherwise it loses its value.
