Terminology people can rely on

Glossary & Termbase

Record the words your organisation has already decided on, enforce them during translation, and turn terminology found in real documents into a reviewed language asset.

Capabilities

What you can do here

Quality controls

The controls shown on this page are part of the working product, with plan access noted in the documentation.

Create terms or import them

Add source-target pairs by hand or upload CSV, XLSX, or TBX terminology, with a sample file available when you need the expected structure.

Only relevant terms are applied

DeepReference finds glossary entries that occur in the current source and sends those decisions with the translation instead of flooding every request with the full list.

Two layers of enforcement

The translation receives the approved term as an instruction, then a deterministic check verifies the result and restores terms that were dropped or changed.

Strict or preferred behaviour

Force the exact approved wording when consistency is absolute, or prefer the term while allowing an inflected form when grammar requires it.

Terminology extraction

Extract candidate terms from a source document or a source-translation pair, including proposed translations and occurrence counts.

A reviewed termbase

Approve or reject extracted candidates, promote useful terms into a glossary, and use approved termbase entries in smart suggestions.

Non-translatables and forbidden terms

Protect brand names, product codes, and custom never-translate items, and keep words that must not appear in the target on a separate control list.

Several assets for teams

Business and Enterprise workspaces can separate named termbases and glossaries by client, product, language pair, or confidentiality requirement.

Where it helps

Glossary & Termbase

  • Legal and regulatory terminology
  • Medical and pharmaceutical vocabulary
  • Product names, parts, and model codes
  • Brand language and approved marketing terms
  • Technical concepts across manuals and specifications
  • Client-specific terminology that must stay separate

A practical workflow

How the work moves

01

Create, import, or extract

Start from an existing terminology file, add decided translations yourself, or extract candidates from documents you already work with.

02

Review what belongs

Approve useful candidates, correct their target wording, reject noise, and promote finished terms into the glossary that should enforce them.

03

Activate the right asset

Choose the glossary for a text or document job. Team workspaces can select the appropriate named termbase or memory for the client.

04

Check and maintain

Use editor QA and smart suggestions during review, then update or remove entries as products, regulations, and client decisions change.

Put it to work

Open the dashboard to start a translation, or read the detailed guide first.