Building a Bilingual Legal Term Glossary

On a matter that runs across Marathi pleadings, a Hindi FIR and English correspondence, the same word can leave three different fingerprints. One associate renders dakhal as "possession", another as "entry", a third as "admission" depending on where it sat. By the time a partner reads the file, the inconsistency looks like a factual disagreement rather than a translation choice. A bilingual glossary is how a team stops re-deciding the same word and starts deciding it once, on the record.

Decide what earns a place in the glossary

Not every word needs an entry. Reserve the glossary for terms where a wrong choice changes meaning or outcome:

• Terms of art with no clean English equivalent, such as khata, patta, vakalatnama or stridhan.
• Words whose meaning shifts by context, where a revenue record and a criminal complaint use the same script differently.
• Court and procedural vocabulary that a fluent-sounding machine translation tends to smooth over.
• Names of statutes, offices and local designations that should read identically every time.

Record the source context, not just the word

An entry with only "original term equals English term" invites the same mistakes it was meant to prevent. For each term, capture the original script exactly, one sentence of surrounding text, the proposed working translation, and any alternative reading you rejected and why. The context line is the part that does the real work: it tells the next reader that dakhal meaning "possession" was drawn from a land record, so its use in a bail application should be checked afresh rather than copied.

Name an approver for context-dependent terms

A glossary carries authority only when a competent bilingual reader has signed off on the harder entries. Mark which terms were approved, by whom, and on what date. Leave genuinely ambiguous terms flagged as provisional rather than promoting them to settled usage. When a term touches rights, identity or amounts, treat the entry as a draft until someone qualified confirms it against how the document actually uses the word.

Keep transliteration of names consistent

Names deserve their own discipline. A single client may appear as Krishnan, Krishnan, or Krishna across scripts, and each variant can attach to a different record. Fix one spelling per person or place, note the variants you have seen, and reconcile the choice against existing client records rather than inventing a fresh transliteration each time. Consistency here prevents a later drafter from treating two spellings as two people.

Apply it without overwriting meaning

Use the glossary to standardise, not to auto-replace. Running a blanket find-and-replace across a file will quietly change a word in the one paragraph where it meant something else. Apply agreed renderings while re-reading the surrounding clause, and preserve the original wording wherever the legal effect turns on it. A working translation built for internal understanding should still let a reader reach the source.

Some teams keep the glossary alongside the documents themselves. Juniorlawyer's legal translation keeps source and translation aligned on screen, which makes it easier to see the term in context while you record the chosen rendering rather than deciding it from memory.

Treated this way, the glossary becomes a shared memory for the matter: the source is visible, the decision has an owner, and the next person can check how a term was settled instead of guessing. That is the difference between a file that reads smoothly and one that holds up when a translation choice is questioned.