write-a-localization-brief

# write-a-localization-brief Provide context and decision rules, not only source strings. ## When to use - Use for product, website, support, policy, campaign, media, legal, or technical localization. - Do not expose unnecessary personal, customer, security, or pre-release information. ## Procedure 1. Identify project, source version, content owner, target locales, markets, audience, purpose, and release date. 2. Describe channel, user journey, screenshots, character limits, variables, plural, gender, tone, and accessibility. 3. Provide approved terminology, do-not-translate list, product names, references, examples, pronunciation, and prior translations. 4. Explain legal, regulatory, cultural, safety, privacy, date, number, currency, address, and measurement constraints. 5. Define file format, encoding, tags, placeholders, layout, right-to-left, font, subtitle, or voice requirements. 6. Set translator, reviewer, in-market, legal, technical, and final approval roles. 7. Specify query, version, change, quality, testing, delivery, and correction workflows. 8. Package source, references, access, deadlines, and acceptance criteria; verify recipients can open them safely. ## Done - A localization brief documents source, locales, audiences, context, terminology, constraints, files, roles, testing, and acceptance - Version, placeholder, terminology, market, accessibility, format, security, reviewer, query, and package-access checks verify readiness