Content Localization Brief template
This localization brief gives a language team context before translation begins. It records the source version, target locale, audience, terminology, formatting constraints and local reviewer. Use a separate response when a locale has different requirements, so one market's preferences are not silently applied to every version.
12 questions · Free plan: 500 responses/month · fully customizable
- Editable cover artwork
What’s inside
The questions this template ships with — rename, reorder, or delete any of them in the builder.
When to use this template
- Adapting approved web or campaign content for a new locale
- Giving a translator terminology and interface constraints
- Coordinating local review before publication
Tips to get more from it
- Specify the locale and audience, not only a language name.
- Include approved terminology and explain product terms that should remain unchanged.
- Freeze or identify the source version so revisions can be tracked rather than translated twice.
Supply context that changes the translation decision
Identify where the content appears and what the reader should do. A short interface label, a support article and a campaign headline have different space and tone requirements even when they mention the same product. Include placeholder tokens, character constraints and a reference to the surrounding layout when they affect meaning.
A glossary should explain a term's intended meaning as well as its preferred wording. Identify product names that remain unchanged and point out locale-specific tone or formatting expectations. If no terminology decisions exist yet, say so and name who can resolve questions.
Plan local review and the final layout check
Translation review should include the person who understands the intended audience. Ask that reviewer to check examples, offers, currency references and imagery for the stated market. Record questions about local suitability for a decision instead of assuming that changing words makes the entire asset ready.
Review the localized text in its actual layout before publication. Expanded text, line breaks and placeholders can create problems that are invisible in a document. This form collects the brief; it does not translate text, enforce a glossary, run layout tests or publish language variants.
Example response and next steps
Illustrative example, not a real customer submission.
A software company is adapting an English product onboarding page for French-speaking users in Canada.
- Source language and target locale
- English to French for Canada (fr-CA).
- Terms to preserve, approved terminology and tone requirements
- Keep the product name unchanged. Use the approved glossary for account and workspace terms.
- Length limits, placeholders, date formats and layout constraints
- Preserve the {workspace_name} token and review button text in the mobile layout.
How to use the response
Confirm who owns terminology decisions and provide the reviewer with the actual page context. Check the placeholder and rendered button after translation. A language approval should identify the localized version and does not automatically approve a different market's variant.
Before publishing your version
Customize the locale example and test every reference link. Confirm the source version and local reviewer before sending the brief to production; do not paste private customer content into sample responses.
Questions people ask
Does this form translate the content?
No. It gathers instructions for a translator or localization team. Translation and publication happen in the tools chosen for the project.
Should I combine all languages into one response?
Use separate responses when locales have different terminology, reviewers or constraints. A common source link can be reused while preserving each locale's requirements.
Is a glossary link enough?
Only if the team can access it and understand the entries. Include context, terms that remain unchanged and the person who resolves terminology questions.
Go deeper
Related templates
Collect one page's copy, image links, approval state and content owner for a website build.
Brief a writer on the reader, desired action, voice, evidence and review process for a specific deliverable.
Record a review decision against a specific creative version, with required correction notes when changes are requested.
Better forms.
Better data.
Start with a conversation, a document or a single page. Unlimited forms and 500 responses per month on Free. No card required.