Localization Review Pack

# Localization Review Pack

Adapt approved content for a named locale while preserving meaning and required terms.

1Overview

A localized draft, terminology table and reviewer questions.

2Requirements

Provide source content, target locale and approved terminology; use a qualified reviewer for consequential copy.

3Steps

1. 1. Extract names, numbers, dates, legal wording and required calls to action before translating.

2. 2. Create a small terminology table for product names and domain-specific words.

3. 3. Adapt register and formatting to the specified locale while preserving claims and conditions.

4. 4. Compare the localized draft against the fact list and flag ambiguity for the locale reviewer.

5. 5. Save the source, localized copy and reviewer changes together before distribution.

4Worked example

6. Input

```text Source: "The beta opens October 20, 2026. Apply by October 18. Limited to 50 teams." Locale: es-ES. ```

7. Expected result

```text La versión beta se abre el 20 de octubre de 2026. Envía tu solicitud antes del 18 de octubre. El acceso está limitado a 50 equipos. Review: confirm the intended application deadline boundary and approved translation of beta. ```

5Acceptance checks

Both dates and the 50-team limit survive; ambiguous deadline meaning is flagged rather than silently changed.

6Limits

A fluent draft is not proof of legal, cultural or domain accuracy. Voice/video localization requires separate tools and review.

7Suggested tools

• Your AI assistant: Draft and compare localized wording
• LibreOffice or your document editor: Maintain terminology and reviewer changes