Terminology Glossary Builder
Create a consistent glossary for a project.
Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).
Build a bilingual glossary. Domain: [DOMAIN]. Languages: [LANGUAGE_PAIR]. Sample source documents: [DOCUMENTS_OR_TERMS]. Extract candidate terms and group them into must-translate-consistently, do-not-translate (brand names, codes), and context-dependent. For each term provide the preferred translation, alternatives to avoid, part of speech, a definition, an example sentence, and the source of truth to verify (a standard, regulator, or dictionary). Where you are unsure of the best translation, write [VERIFY] and propose how to confirm it. Provide a format that can be imported into a spreadsheet or translation tool, and a governance process: who approves terms, how changes are logged, and how teams are notified. Add a short guide to handling terms with multiple valid translations and to marking terms by confidence level. Provide a monthly review routine for the glossary and a policy for retiring terms. Include three invented example entries to show the level of detail, labelled as examples, and a rule that the glossary is the first thing to update when a style decision changes.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.