Why Does Term Consistency Matter? The Return on Corporate Terminology

When a concept goes by a different name from one document to the next, the organisation pays a silent cost. Term consistency means naming the same concept with the same preferred word in every document, by every translator and in every language. It looks simple, but achieving it takes discipline; and when it is missing, a text loses its credibility without anyone noticing.

Contents

Hann’s dictionary stresses that the traditional alphabetical approach breeds inconsistency, and counters it by organising terms along the axes of concept and field. In this article we look at why term consistency matters, what inconsistency costs and how corporate terminology secures it.

What Does Term Consistency Secure?

Consistency lets the reader see, without a moment’s doubt, that the same thing is being referred to. If a component appears as “gasket” on one page of a technical manual, “packing” on the next and “seal” on a third, the reader cannot tell whether these are the same part or different parts.

That uncertainty is no luxury worry in a technical text. In an assembly instruction or a safety warning, a slip in terminology can lead straight to the wrong action. This is exactly why Hann sets precision and clarity as the priorities of technical translation; consistency is the precondition for both.

Consistency also protects the voice of the brand. When every document in the same product family uses the same terms, the organisation appears to speak with one mouth. Scattered terminology, by contrast, turns the text into a patchwork stitched by different hands and damages the perception of professionalism.

This assurance carries over into searching and reference. If users know they will always find the part they are looking for under the same name in a manual, their trust in the document grows and support requests fall. Inconsistent terms force users to search for one concept under several different words; that is both a waste of time and a source of error. Consistency is a quietly working component of the user experience.

Where Does Inconsistency Come From?

The most common source of inconsistency is synonymy. When a concept has more than one acceptable name, different translators pick different names. Nobody has made a mistake; the result is scattered all the same. Managing synonyms therefore sits at the centre of consistency.

The second source is time. An organisation’s term preferences drift over the years without anyone noticing. A new translator joins and brings their own habits; older documents are never updated. The termbase then starts to carry several accumulated names for the same concept.

The third source is the flip side of synonymy: the same word being used for different concepts. If “load” stands for both an electrical load and a mechanical load in one text, the reader cannot work out which is meant. Consistency covers not only “the same name for the same concept” but also “a different name for a different concept”.

The fourth source, and the one most often missed, is the source text itself. If the source document is inconsistent, the translation inherits that inconsistency. Term management must therefore begin not only in the target language but on the source side as well. Fixing the terms of the source text in advance heads off the disorder that would otherwise surface during translation.

The Unseen Cost of Inconsistency

The cost of term inconsistency usually shows up late. At first nobody notices; but as the document grows and the languages multiply, the confusion compounds. The table below compares the outcomes of a consistent and an inconsistent term system.

Dimension	Consistent system	Inconsistent system
Reading	Clear	Confusing
Translation memory	High match rate	Low match rate
Review	Short	Long and costly
Brand perception	Trustworthy	Scattered

Inconsistency is particularly expensive on projects that use a translation memory. When the same concept is stored in different forms, the memory takes them for separate items; the match rate falls, reuse declines and cost rises. Here consistency turns directly into a budget line.

The cost of review grows quietly too. In an inconsistent document the reviser has to check every term one by one and decide which form is the right one; that pushes up the time spent per page. In a consistent document, checking amounts to confirming whether a term matches the termbase. On large projects the difference can run to days.

How Is Corporate Terminology Built?

The route to consistency runs through settling on a single preferred term per concept. That term is gathered in a termbase; its synonyms are recorded as admitted as well, but the preferred one is clearly marked. Everyone then looks at the same source and makes the same choice.

The termbase has to sit where translators, and any translation tools, can reach it. A term list nobody can reach is useless, however well it has been prepared. Even the best termbase cannot deliver consistency if it is not open on the translator’s desktop. The corporate terminology material in our knowledge centre explains how a termbase is shared and kept up to date.

Finally, consistency is reinforced by a checking step. Before delivery, the terms in the document are checked against the termbase. This check can be done by hand or with a tool; what matters is that consistency stops being a wish and becomes a measured criterion. Consistency that is never measured melts away in time.

Keeping terminology in one person’s memory is the most fragile solution of all. When that person leaves or hands the work over, the accumulated preferences go with them. Making the termbase a written and shared resource frees the organisation’s linguistic memory from any individual. A newly arrived translator can then work with the organisation’s preferred terms from the first day.

Balancing Consistency and Flexibility

Consistency does not mean rigid uniformity. Some contexts call for a different term: a warmer word may suit a marketing text, a precise one a technical manual. A good termbase records this contextual distinction too, noting which term is to be preferred where.

That flexibility does not weaken consistency; on the contrary, it makes it realistic. A blind “one term everywhere” rule produces unnatural texts. The aim is to preserve the identity of the concept while respecting what the context requires. Consistency is not sameness but predictability. Once readers see that the same concept is named consistently within the same product, the small nuances that shift with context will not strike them as odd.

The way to strike that balance is to document the decisions. Once it is written down why a term is preferred and in which context it changes, future debates get shorter. The termbase then becomes not merely a list but the linguistic memory of the organisation.

How Consistency Relates to Translation Memory

Term consistency and the productivity of a translation memory are directly linked. A translation memory stores sentences that have already been translated and offers them again in similar sentences. But if a concept appears under different words from one document to the next, the memory cannot see those sentences as similar; the match rate falls and reuse declines.

This is the point at which the termbase and the translation memory complete each other. The memory manages sentences, the termbase manages terms. When the termbase enforces consistent terms, the sentences entering the memory come out consistent as well, so the two tools feed one another. An inconsistent term system, by contrast, lowers the productivity of both tools at once.

This relationship shows why consistency is not merely a linguistic concern but also a question of cost. A high match rate means less retranslation and a lower invoice. The initial effort put into corporate terminology comes back multiplied by the return on the translation memory. Thinking of the two systems separately means getting less out of both; whereas when the termbase and the translation memory are built together, consistency and productivity come out of the same investment.

The Türkiye context

In Turkish, term consistency calls for an extra effort because of the language’s rich stock of synonyms. For one and the same concept, both a word of Turkish origin and one of foreign origin are in circulation: “bilgisayar/kompüter” (computer), “sıklık/frekans” (frequency), “iletişim/haberleşme” (communication). Unless it is settled which of them is the corporate standard, the text will swing back and forth between the two.

Another local factor is that Turkish technical terms have not yet settled down. When a new technology arrives, several candidate equivalents are in use at the same time; for the sake of consistency the organisation has to move early and choose one. At our office in Ankara Kızılay we recommend drawing up a short list of preferred terms on corporate projects before the work begins. That list keeps the language of the organisation the same even when the translator changes, and it brings review costs down. Because most organisations in Türkiye skip this step and go straight to translation, inconsistency is usually noticed not at the first delivery but as the documents pile up; a short list drawn up early, on the other hand, heads off much of that accumulated problem from the outset. Built with a small investment, such a list turns in time into one of the most valuable linguistic assets an organisation has.

What does this mean for you?

If yours is an organisation that produces documents regularly, term consistency feeds straight into the credibility of those documents and into your translation costs. To secure consistency:

1. Set a single preferred term for each of the concepts you use most often.
2. Record the synonyms as well and mark clearly which one is preferred.
3. Keep the termbase where your translators and your tools can reach it.
4. Make the pre-delivery term check a fixed step in the process.

These four steps turn consistency from a good intention into a measured assurance. On corporate projects we build the preferred term list together with you and check consistency at every delivery; our translation services include that assurance. To have us assess the terminological drift in your existing documents, write to us from the contact page.

Frequently asked questions

What does term consistency mean?

It means naming the same concept with the same preferred term in every document, by every translator and in every language. Consistency lets the reader see, without a moment’s doubt, that the same thing is being referred to.

What harm does term inconsistency do?

It confuses the reader, reduces trust and leads to misunderstanding in technical texts. It also lowers the productivity of the translation memory, because the same concept is stored in different forms.

How is consistency achieved?

By settling on a single preferred term per concept and gathering it in a termbase. Once translators and tools are connected to that termbase, the same concept appears in the same form everywhere.

Is term consistency needed in a small organisation?

Yes. Even in an organisation working with a single translator, preferences drift over time. A short list of preferred terms preserves the accumulated knowledge when the team grows or the translator changes.

Sources

• Hann, M. (1992). The Key to Technical Translation, Vol. 2. John Benjamins.
• ISO 17100:2015. Translation services – Requirements for translation services.
• Bowker, L. (2015). Terminology and Translation. Handbook of Terminology, John Benjamins.