Build entries around concepts
Record the source, target, definition or example and product or discipline label. Link names, abbreviations and full forms. Separate genuinely different senses rather than forcing a single equivalent for every context.
Record approval and preference
Include approval status, source, owner and prohibited alternatives. Pending terms should not be treated as approved. Keep the basis for decisions from brand, engineering or legal teams so future users can understand and maintain them.
Use it throughout the workflow
Resolve frequent and high-risk terms before translation, check usage during review and collect additions at delivery. When a term changes, identify the affected documents instead of replacing it blindly throughout all historical translations.
A checklist for your brief
- Source, target and discipline
- Definition, example and source
- Approval status and owner
A common question
Can an existing word list become the standard?
First check duplicates, conflicts and applicability. Entries without context or approval records need verification before becoming authoritative.
This guide supports project preparation and communication; it does not replace legal, financial or specialist technical advice. Service scope, recipient requirements and delivery arrangements must be agreed for the specific project.
