# Localization Content Brief

Give localization teams the audience, purpose, terminology, interface context, source evidence, adaptation boundaries, variables, and review path they need.

## Usage note

Create one brief for a defined asset, locale, and release context. Translation quality depends on complete source meaning and real product context; word substitution alone is not localization.

## How to use this template

1. Define the source asset, target locale, reader situation, task, channel, and release.
2. Package the locked source, screenshots, evidence, terminology, variables, and known ambiguities.
3. Mark invariant meaning and clearly authorize only the adaptations appropriate to the locale.
4. Assign translation, linguistic review, subject review, functional QA, and final approval.
5. Track source changes, resolve defects by locale, and publish only reviewed equivalents.

## Blank template

### Project and audience

- **Project and asset ID:** [Enter]
- **Source URL/file and version:** [Enter]
- **Source locale:** [Enter language and locale]
- **Target locale:** [Enter language, region, and script where relevant]
- **Reader situation and prior step:** [Describe]
- **Required reader outcome:** [Describe]
- **Channel and content type:** [Web / Email / Product UI / Help / Other]
- **Release date and dependency:** [Enter]
- **Localization owner:** [Name/team]

### Context packet

- **Safe preview or screenshots:** [Enter reference]
- **Character or layout constraints:** [List]
- **Connected controls and destinations:** [Describe]
- **Source evidence for material claims:** [List]
- **Related assets:** [Terms, privacy, help, campaign, other]
- **Known source ambiguities:** [List with resolution owner]
- **Tone, relationship, and formality:** [Describe]
- **Accessibility context:** [Reading order, alt text, captions, labels]

### Terminology and protected elements

- **Product and feature names:** [Approved handling]
- **Termbase entries:** [Source term / Definition / Approved target / Avoid / Example]
- **Variables and placeholders:** [Syntax, meaning, sample rendered value]
- **Commands, code, and filenames:** [Translate / Preserve / Explain]
- **Names and addresses:** [Handling]
- **Dates, times, numbers, currencies, and units:** [Locale rules]
- **Quoted or regulated text:** [Owner and required handling]
- **URLs:** [Localized destination / Source destination / Do not link]

### Adaptation boundaries

- **Meaning that must not change:** [List claims, conditions, limitations]
- **Examples that may localize:** [Scope and approval]
- **Idioms or cultural references:** [Replace / Explain / Preserve]
- **Call-to-action flexibility:** [Describe]
- **Search language research:** [Approved query language, if relevant]
- **Prohibited additions or omissions:** [List]
- **Questions for the source owner:** [List]

### Review and release

- [ ] Source version was locked and ambiguities were resolved.
- [ ] Translation is complete with no unapproved fallback text.
- [ ] A qualified linguistic reviewer checked fluency and terminology.
- [ ] A subject or product owner verified claims and instructions.
- [ ] Variables, links, layout, reading order, and interaction were tested.
- [ ] Dates, numbers, units, names, and locale conventions were checked.
- **Translation and review owners:** [Names/dates]
- **Defects and resolution:** [List or None]
- **Final approver and version:** [Name/version/date]
- **Source-change monitoring owner:** [Name/team]