# Multilingual Review Checklist

Review a localized asset for preserved meaning, natural language, approved terminology, locale conventions, layout, links, accessibility, and release readiness.

## Usage note

Use this checklist on a defined source version and one target locale at a time. Review the target content in its rendered context whenever possible. Fluency alone does not establish accuracy, and a clean bilingual comparison does not prove that links, variables, layout, interaction, accessibility, or local conventions work after release.

## How to use this template

1. Record the exact source version, target locale, asset scope, audience, owners, and release criteria.
2. Compare meaning first, then review fluency, terminology, tone, grammar, and locale conventions.
3. Test the complete rendered experience, including variables, layout, media, links, accessibility, and metadata.
4. Log every defect with impact, evidence, correction owner, deadline, and required review level.
5. Retest corrections, record approval or a safe hold, and verify the live localized asset after release.

## Blank template

### Review setup

- **Asset and version:** [Title, URL or file, commit, or release]
- **Source locale and version:** [Enter]
- **Target locale and language variety:** [Enter]
- **Audience and task:** [Who uses it and what they must do]
- **Content type and risk:** [Marketing, help, product, policy, or another]
- **Source owner:** [Name or team]
- **Translator:** [Name or provider]
- **Linguistic reviewer:** [Name and qualifications]
- **Subject or product reviewer:** [Name]
- **Release owner and date:** [Name and target]

### Meaning and language review

- [ ] No required sentence, label, list item, caption, or note is omitted.
- [ ] The target adds no unsupported fact, promise, instruction, or implication.
- [ ] Negation, conditions, sequence, scope, certainty, and causation match the source.
- [ ] Claims, names, numbers, quotations, and limitations remain accurate.
- [ ] Approved terminology is used consistently and in the correct grammatical form.
- [ ] Register, formality, tone, spelling, punctuation, and word order fit the locale.
- [ ] Idioms and examples are understandable without introducing a stereotype.
- [ ] Unresolved source ambiguity is returned to the source owner instead of guessed.

### Functional and locale review

- [ ] Placeholders, variables, plurals, gender, code, and protected tokens render correctly.
- [ ] Text fits controls and layouts at required screen sizes and zoom levels.
- [ ] Reading order, headings, focus context, alternatives, captions, and transcripts work.
- [ ] Dates, time zones, numbers, currencies, units, names, addresses, and ranges follow policy.
- [ ] Links open the intended reviewed locale and retain necessary context.
- [ ] Images, screenshots, audio, video, and downloadable files match the target language.
- [ ] Metadata, structured data, language declarations, and locale navigation are accurate.
- [ ] The complete task succeeds using realistic sample data.

### Defect and decision record

- **Defect ID and location:** [Enter]
- **Source and target excerpt:** [Enter]
- **Category:** [Meaning, terminology, fluency, locale, functional, visual, accessibility]
- **Severity:** [Blocker, high, medium, low with user impact]
- **Correction and owner:** [Enter]
- **Retest evidence:** [Build, screenshot, URL, or notes]
- **Status:** [Open, fixed, accepted risk, deferred]
- **Final decision:** [Approve, approve with recorded follow-up, or hold]
- **Approver and date:** [Name and YYYY-MM-DD]
- **Live verification:** [URL, date, and result]