Multilingual Release Sign-Off (QA)

Multilingual Release Sign-Off (QA)

1. 01

   Freeze the source string set and record its commit or content hash before review begins

   Any string edited after the freeze gets a new hash and re-enters the queue, so reviewers never approve copy that has already drifted.

2. 02

   Run automated QA on every target locale: placeholder parity, plural-form coverage, and string-length overflow

   German and Finnish routinely expand 30 percent over English source, and a broken {variable} in a checkout flow costs more than a mistranslation.

3. 03

   Score machine output against a client glossary before a human sees it

   Platforms such as Phrase expose quality scoring that flags low-confidence segments; route only those segments to native review and let the rest pass.

4. 04

   Assign in-context review to a native speaker who can see the rendered screen, not a spreadsheet

   Lokalise and Localize both support in-context editing; reviewing a button label outside its UI hides truncation and tone failures.

5. 05

   Verify locale-specific formatting for dates, currency, addresses, and legal disclaimers

   A US date format in a Japanese invoice or a missing GDPR notice in an EU locale is a compliance defect, not a style preference.

6. 06

   Confirm hreflang tags and language-specific URLs resolve correctly on staging

   Weglot and Linguise generate these automatically, but a misconfigured canonical can still point every locale back to the English page.

7. 07

   Log every rejected segment with a reason code and feed it back into the glossary

   Terminology drift compounds across releases; a rejection without a glossary update guarantees the same error next sprint.

8. 08

   Get written client sign-off per locale and archive the approved build

   Retainer clients need an audit trail showing which locale shipped on which date, especially when a regional team disputes a translation.