Terminology Management and Glossary Development

In most organisations the problem grows quietly. A product name is translated in one document and left untouched in another; a single technical term circulates in three different forms across three separate manuals. To the reader, this is a sign of an organisation that is not in command of its own language. Terminology management first makes that disorder visible, then ties it to a single approved source.

When is it needed?

Terminology management makes sense for organisations that produce translations regularly and through more than one channel. Those with a product catalogue under constant revision, those publishing documents in several languages, and those working with a range of translators and agencies gain the most from it. Setting up a terminology project for a single short document is unnecessary; but as volume grows, so does the cost of inconsistency.

The need usually announces itself through a problem: a customer complaint, two manuals that contradict each other, or the same argument about the same term being had again with every new translation. That recurring friction is the sign that the terminology now needs to be written down.

How the process works

A terminology project is less about filling in a glossary than about discovering an organisation’s own language and putting it in order; that is why the work starts from existing documents rather than imposing a template from outside. The distinguishing step in the sequence below is approval: no equivalent enters the glossary until someone with authority inside the organisation has approved it. Skip that step and the glossary loses its binding force. Nor does the process end with a single delivery; maintenance, the final step, keeps the terminology a living resource. The same framework serves both for building a glossary from scratch and for putting an existing one in order.

1. Term extraction. Candidate terms are gathered from existing documents; both the concepts that recur most often and those that cause confusion are collected.
2. Filtering. The candidate list is narrowed down, separating the terms that genuinely need managing from ordinary vocabulary.
3. Equivalents and approval. A target equivalent is proposed for each term and confirmed by a specialist within the organisation. Without the approval step, a glossary carries no authority.
4. Style guide. Rules on tone of voice, forms of address, capitalisation and abbreviation are set out alongside the terms.
5. Maintenance. The glossary is updated as new products and concepts appear; terminology is a living resource, not a frozen one.

How it is delivered

Terminology is delivered both as a glossary a person can read and as data that can be loaded into translation tools. The readable version is a document teams and writers can consult; the tool version prompts the approved terms automatically while translation is under way. The style guide is an inseparable part of the resource. On subsequent translation work the glossary comes into play directly and secures consistency from the outset.

Points specific to this service

The most critical step is approval. A glossary that the organisation’s own specialist has not approved is only a list of suggestions and binds no one. The success of a terminology project therefore depends on someone inside the organisation taking part who is able to decide. A glossary built from outside but never owned inside soon ends up on the shelf.

The second point is keeping it current. Terminology is not a document to be drawn up once and forgotten; it has to be updated as the organisation brings out new products and new concepts. A glossary left unmaintained turns within a few years into an archive that no longer reflects reality. For organisations with a regular need for translation, terminology is the common ground beneath everything covered by our translation services, which is why sustaining it as part of a corporate workflow is the soundest approach.

Who owns it, and how it stays alive

The value of a terminology resource shows less in building it than in keeping it alive, and that calls for a named owner inside the organisation: a person or a unit who approves new terms, has the last word on disputed equivalents and sees that the glossary stays current. Where this responsibility is left undefined, even the most carefully prepared glossary soon falls behind reality and stops being used.

Terminology survives by being built into everyday working practice. Terms being suggested automatically during translation, writers being able to reach the glossary easily as they draft, and new terms being recorded in an orderly way as they arise are the habits that keep the resource alive. The glossary should be a natural part of the work, not an archive forgotten in a file of its own.

Once that is in place, terminology produces a value beyond individual translations: a coherence in which the organisation is in command of its own language and shows the same consistency in every document. This becomes plainly visible in organisations that produce content in several languages and through several channels.

What determines the price?

The first factor in the cost of a terminology project is the volume of material to be scanned and the number of terms to be extracted. The second is the number of languages; each additional language brings its own equivalents to find and approvals to obtain. The third is the scope of maintenance: a one-off glossary, or a service kept continuously up to date? Ongoing maintenance is assessed separately, as regular work. A price therefore cannot be given without first seeing the volume of material and the range of languages.

You can share your documents and target languages through the quote form. The pricing logic is set out on the pricing page and the languages we work in on the language pages.

Situations that come up often

• An unapproved glossary. A list drawn up without a decision-maker from inside the organisation; it binds no one and goes unused.
• Neglect. Terminology set up once and never updated; it soon falls out of date.
• Over-reach. Trying to take every last word into the glossary; this leaves the terms that actually matter in the shade.
• No route into the tools. A glossary that stays on paper; it cannot come into play automatically while translation is under way.

This page is for general information; translation, approval and delivery requirements may vary by document type. Confirming the current requirement before you apply saves time.