Global-Ready Launch Checklist (Delivery)

Global-Ready Launch Checklist (Delivery)

1. 01

   Map the client's content inventory against target locales

   Catalog every asset type, from marketing pages to in-app strings, and tag each with the languages it must reach. This inventory becomes the source of truth for scoping effort and pricing the retainer.

2. 02

   Define the linguistic quality bar per market

   Decide which locales need human review versus machine translation with post-editing. A brand like a luxury retailer may require native linguists for tone, while a SaaS dashboard might pass with AI plus glossary enforcement.

3. 03

   Set up a shared translation memory and glossary

   Configure the platform so repeated phrases and brand terms stay consistent across updates. This cuts costs on recurring content and prevents drift in terminology between versions.

4. 04

   Integrate the localization platform with the client's CI/CD or CMS

   Connect to the development workflow so new strings are pushed automatically and translations return without manual exports. Tools like Crowdin and Lokalise offer plugins for GitHub, Figma, and WordPress that remove copy-paste friction.

5. 05

   Establish a review workflow with client-side approvers

   Assign a named reviewer per locale and set SLAs for sign-off. Without this, translations can sit in limbo and delay the launch window you promised.

6. 06

   Run a functional QA pass in each language before go-live

   Check for layout breaks, truncated strings, and untranslated hard-coded text. Automated checks catch most issues, but a human spot-check on key user flows is non-negotiable for client trust.

7. 07

   Document the workflow and hand off ownership

   Create a runbook that shows the client how to request new translations, update strings, and manage their glossary. This turns a one-off project into a repeatable service that justifies a monthly retainer.