A translation glossary in a law firm should be scoped to the matter, not the firm, because every agreement defines its own vocabulary in its own definitions clause and those definitions do not carry across deals. Affiliate turns on an ownership threshold that changes from transaction to transaction; a firm-wide entry that fixes one rendering will enforce the wrong meaning everywhere else. The workable structure is layered: a firm base for durable house terminology, a client layer for that client's names and preferences, and a matter layer built from the agreement's own definitions before translation begins. The matter layer takes precedence, travels with the matter on handover, and is archived with the matter file at close.
This guide covers how to populate a matter glossary from the definitions clause, how inheritance and precedence should work, and why the confidentiality properties of a matter glossary rule out a firm-wide list.
Every Agreement Ships With Its Own Dictionary
Clause 1.1 is a dictionary. The drafters take ordinary words, assign them stipulated meanings, capitalise them, and then build obligations on top. Material Adverse Effect means what this agreement says it means, and the parties negotiated exactly that.
Two consequences follow for translation. First, the defined term must be recognisable as a defined term throughout — a reader has to be able to follow every occurrence back to clause 1.1, and that link is severed by any variation, including a variation that is a perfectly good synonym. Second, the rendering cannot be inherited from another matter, because the underlying definition is different. Reusing last deal's rendering imports last deal's negotiated meaning.
This is why the useful unit is the matter. A firm base can hold jurisdictional standards and house style; only the matter layer can hold what this agreement actually decided, which is the part that carries legal risk.
Harvesting the Definitions Clause Before Translation Starts
The extraction is mostly mechanical, which is why it is worth doing properly rather than leaving to whoever opens the file first.
Pull every term in quotation marks followed by means or shall mean from the definitions clause. Then sweep for inline definitions, which are the ones people miss: parentheticals like (the "Escrow Agent") scattered through the operative provisions, and terms defined for the first time inside a schedule. Add the parties as drafted, including legal-form suffixes, the governing law and jurisdiction references, and any deal code name.
Word documents give you a shortcut here: defined terms are frequently cross-referenced with REF and other field codes, so the field list is a second index of what the drafters treated as load-bearing — and those fields also need to survive translation intact, which is a separate test worth running.
Do this before the first sentence is translated. Retrofitting terminology onto a completed draft means re-reviewing all of it.
The Freeze-or-Translate Decision, Made Once Per Matter
Each harvested term takes one of two treatments, and the choice belongs to the fee earner running the document.
Freeze. The defined term stays in the source language, usually with a target-language gloss on first use. This is common where the agreement is governed by English law and the translation is for a client's internal understanding rather than execution — the English capitalised term remains the operative one, and freezing it keeps the link to the executed document unambiguous. Party names, standard references and citations are always frozen; the do-not-translate list guide covers the mechanics.
Translate and lock. The term is rendered once in the target language, capitalised in the same way, and enforced everywhere. This is right for execution copies, bilingual instruments and any document a local court will read.
What matters is that the decision is made once, recorded per term, and applied to every document in the matter — the agreement, the schedules, the side letters, the disclosure letter. Mixed treatments inside one matter are the failure this whole process exists to prevent.
Three Layers and a Precedence Rule
The layers do different jobs and should be maintained by different people.
Firm layer. House style, your own entity names, standing counterparties, jurisdiction-standard renderings validated by local counsel, and forbidden terms the firm will not use. Owned by knowledge management, changes rarely.
Client layer. That client's registered entity names across jurisdictions, product and brand names, their in-house preferences, and any rendering their local counsel has already blessed. Owned by the client relationship partner.
Matter layer. The defined terms from this agreement, the deal code name, and any decision taken during this transaction. Owned by the associate running the document.
Precedence runs matter over client over firm, deterministically. The non-negotiable requirement is attribution: when a term renders a particular way, the system must be able to say which layer supplied it. Without that, a partner asking why a clause reads as it does gets an answer nobody can verify, and the glossary stops being trusted.
Confidentiality Makes a Firm-Wide List the Wrong Container
This is the argument that usually settles the structure question, and it is not primarily about translation quality.
A matter glossary contains the deal code name, the target's registered entities, the names of individual signatories, and often terms that reveal deal structure. Put that in a firm-wide list and you have published confidential matter information to every fee earner with glossary access, across information barriers that exist precisely to prevent it. A code name appearing in a shared dropdown is a conflicts problem that no amount of good terminology makes acceptable.
There is a data protection dimension too: named individuals in a glossary are personal data under GDPR, with the retention and access obligations that follow. A matter glossary should inherit the matter's access controls, ethical walls and retention schedule automatically — the same posture applied to the underlying documents in a data room, not a looser one because it is "only a word list".
Handover Between Fee Earners
Matters change hands. Associates rotate, work follows the sun to another office, and a dispute team inherits a document a corporate team translated three years earlier.
The glossary has to survive that, which means it lives with the matter file rather than on someone's laptop or in a personal account on a translation platform. Every entry needs three pieces of metadata to be useful to the next person: who approved it, when, and on what authority. Client instruction, email of 3 June and local counsel advice, Madrid, 12 May are entries with standing. An unattributed row is a rumour, and the next fee earner will either re-litigate it or, worse, rely on it.
Include the glossary and the enforcement reports in the handover pack alongside the drafts. The entries most likely to be lost — and most expensive to recreate — are the ones somebody paid local counsel for.
Multi-Jurisdiction Matters and Local Counsel Decisions
A deal running across five jurisdictions produces five sets of terminology decisions against one set of concepts, and the storage model determines whether that is manageable.
Concept-oriented term bases under ISO 30042 hold one concept with a section per language, so a Spanish local counsel decision attaches to the concept without disturbing the German or Japanese renderings, and the definition everyone is working from stays shared. Pairwise spreadsheets give you five files that drift, and no way to see that they were ever meant to agree.
Where documents move between the firm's systems and a vendor's, XLIFF 2.1 is what carries segment-level content and inline markup, with the term base travelling alongside. Bluente supports term base enforcement across 120+ languages in a single job, which is what keeps a five-jurisdiction matter on one vocabulary rather than five.
Archiving With the Matter File at Close
Disputes about what a translated clause meant surface years after closing, usually when nobody involved is still at the firm.
At close, freeze and export three things into the matter file: the term base version used, the enforcement reports showing which terms were applied and where they were overridden, and the decision log with its attributions. That package is the difference between demonstrating how a rendering was arrived at and offering a recollection. It is also what makes foreign-language contract review tractable when the same client returns with a related transaction.
Retention should follow the matter's retention schedule. Then curate: promote the genuinely reusable entries — jurisdiction-standard renderings, the client's entity names, terminology validated by local counsel — up to the client or firm layer, and leave the matter-specific definitions behind, retired rather than deleted. That promotion step is the only mechanism by which a firm-level base gets better instead of merely larger. Practitioners describe the alternative — one large document, one person, no shared terminology — in this r/software thread on translating a long Word document.
Sources and Further Reading
Word field codes — REF and cross-reference fields used for defined terms
ISO 30042 (TBX) — concept-oriented term entries across multiple languages
XLIFF 2.1 — bitext interchange between firm and vendor systems
r/software on translating a 100-page Word document — practitioners weighing tooling for long single-matter documents
Related Reading
Last reviewed 24 August 2026 by the Bluente document engineering team, who build and test the pipeline described here. We update these guides when the underlying standards, regulations or file formats change.
Build the glossary from clause 1.1, and let it close with the matter. Try BluTranslate free.