ISO 9001 
ISO 17100 
ISO 18587 Translation memory and terminology management are practical assets in multilingual projects. They help that keep repeated content, product names, legal clauses, technical terms and preferred wording stay consistent across documents and languages. LinguaVox uses these resources for companies, public bodies, law firms, universities and corporate groups that manage recurring documentation and need reliable, consistent wording over time.
A translation memory is most useful when content is updated, reused or published in several versions. A terminology database is useful when the same concept should be translated consistently. Used well, both tools support the translator without replacing professional judgement.
How translation memories work
A translation memory stores previously translated segments in a bilingual database. When a new file is processed, the software identifies exact matches, partial matches and repeated segments. The translator can then review the previous wording, decide whether it still fits the new context and adapt it where necessary.
This is especially useful for technical manuals, legal templates, product catalogues, safety instructions, website updates, software documentation and recurring corporate reports. If a manufacturer revises one section of a manual, the approved wording from previous versions can be reused where it is still valid, reducing unnecessary retranslation and helping prevent avoidable inconsistencies between versions.
A memory match is not automatically correct. A repeated sentence may require a different gender, number, register or legal nuance in its new context. The translator therefore remains responsible for assessing each match rather than accepting it mechanically.
How terminology management works
Terminology management focuses on terms rather than full sentences. It covers product names, component names, department names, legal concepts, acronyms, regulatory references, drug names, software commands, menu labels and brand wording. Each approved source term is linked to one or more approved equivalents in the target languages.
This matters because most terms have several possible translations. Without a glossary, different translators may render the same product, function or clause in different ways. In technical, legal, medical, financial and software content, that inconsistency can confuse users and make documentation harder to maintain over successive updates.
A glossary can also specify terms that should remain untranslated, terms that follow a client preference, forbidden alternatives, acceptable abbreviations and notes on register or intended audience.
When these resources are most valuable
Translation memories and terminology databases are most effective in projects with repeated or evolving content: instruction manuals, standard contracts, tenders, HR policies, training modules, software strings, knowledge bases, ecommerce product sheets, medical device files and multilingual websites.
They are less dominant in creative copy, slogans, editorial writing or marketing campaigns where the translator needs greater freedom. Even in those cases, a glossary can still protect product names, brand vocabulary and preferred tone.
For long-term clients, these resources also simplify onboarding for new assignments. Future projects start from approved wording, and the same terminology applies consistently across departments, countries and suppliers.
Workflow and quality checks
The process begins with file analysis. If the client already has translation memories, glossaries, previous translations or style guides, we review them before quoting or starting work. Where no resources exist, we can build a basic glossary during the first project and expand it over time.
During translation, the linguist works in a CAT environment where memory matches and approved terms are visible. The reviewer then checks not only meaning and accuracy but also terminology consistency, numbers, names, formatting and suitability for the target audience. Where the service is contracted under an ISO 17100 workflow, bilingual revision by a second qualified professional is included. The project manager also confirms delivery requirements, file format and client instructions before the files are returned.
How to request a quote
Send the source files, target languages, deadline, intended use and any existing terminology resources. Previous translations are particularly useful, even if imperfect, because they show established wording and recurring structures. If certain terms are preferred and others should be avoided, include that information from the outset.
For multilingual projects, it is better to agree terminology before translation begins. Correcting terms after several languages have already been delivered is slower, more expensive and more prone to cascading inconsistencies.
Frequently asked questions
What is a translation memory?
A translation memory is a bilingual database of previously translated segments. It helps translators reuse approved wording where the same or similar text appears again, while still allowing them to adapt each match to the new context.
Is a glossary the same as a translation memory?
No. A glossary manages terms, product names, acronyms and preferred vocabulary. A translation memory stores full translated segments. In large projects, both resources work together and reinforce each other.
Can existing translations be converted into a translation memory?
Often, yes. If you have previous source files and their translations, they can sometimes be aligned to create a usable memory. The quality of the result depends on file condition, alignment accuracy and whether the previous translations are reliable.
Does using a translation memory reduce the price?
It can reduce cost where repeated segments or usable previous translations are present. The quote depends on the language pair, file format, match quality, review level required and whether the matches need substantial adaptation.
Who owns the terminology resources created during the project?
That depends on the agreement with the client. For ongoing corporate projects, terminology resources are normally managed for the benefit of future assignments and updated as products, departments or preferred wording evolve.
