By Tangenix · Published 2026-10-24 · Free template

Product Translation Terminology Log

Give translators the meaning of product terms, fixed names and claim conditions so localized marketing stays consistent with the actual workflow.

Read this resource as Markdown

When to use this template

Use this when a software product’s terms appear across landing pages, tutorials and interface references. Record meaning and context before asking someone to translate the words.

Choose another approach when: You need a general localization project handoff, want literal word substitution without context, or intend to turn a limited product claim into a stronger promise in another language.

Gather these inputs

• The actual product concepts, UI labels and approved claims in the source language.
• Screens or examples showing how each ambiguous term is used.
• A qualified language reviewer and a clear decision owner for unresolved terminology.

Copy and adapt the template

Edit the text below and copy it into your own document. Edits stay in this browser field and are not submitted or saved by this page.

Worked example

Illustrative example, not a Crany customer result. Replace every example detail with facts you can verify.

Fictional example: a document app uses “workspace” for the shared account area and “project” for a group of files inside it. A translator who receives only a word list could treat those as synonyms and make the localized instructions confusing.
The terminology log supplies actual definitions, UI context and separate concept identifiers. The language reviewer chooses appropriate terms; the founder does not invent translations without expertise.
A statement about an approved-only workflow keeps that qualification in every localized version. The log also records unresolved terms as unresolved instead of counting an unreviewed machine translation as completed research. No Crany localization or product availability is implied.

How to use it

1. Identify ambiguous terms and define their actual product concepts with context.
2. Have the appropriate language reviewer decide target terms and necessary invariants.
3. Propagate approved decisions to affected assets and preserve material claim conditions.

Check before using it

• Different product concepts have not been collapsed into one convenient synonym.
• Target-language wording has actual review rather than a fabricated approval.
• Availability and approval conditions survive translation.

What to measure

Track terminology conflicts, meaning changes and unresolved review decisions. Review whether readers can match the instructions to the product they actually see. A completed log is not a full translation-quality certification or proof of international demand.

Research and sources

Microsoft recommends clear global writing, avoiding culture-specific idioms and using one consistent word per concept. This original terminology decision log adds product context and human review without inventing translations or claiming professional linguistic validation.

• Microsoft Style Guide: Writing tips for global communications — checked 2026-10-24. Clear source text, avoiding idioms and maintaining a consistent term for each concept. Target translations still require actual language review.

This original template and worked example were prepared with AI assistance. Source documentation supports the principles stated above; it does not endorse Crany or guarantee this template’s performance.

About Crany

Crany is an AI marketing co-founder in development for software founders and vibe coders, designed to strategize, execute approved marketing and improve based on results. This free resource is usable independently of the product. Join the public waitlist.