Plan a multilingual release

Connect each audience's content to its source revision, delivery checks, quality evidence, and publication decision.

A multilingual release gives different audiences usable versions of the same intended work. Translation completion supplies text; release readiness also requires the right resources, working routes, relevant review, and authority to publish.

Plan around what each audience will receive. That makes a missing locale or unresolved claim visible even when most translation jobs have finished.

Define the release set #

List required locales and reader-facing content: application messages, documents, emails, metadata, and other included surfaces. Record source revisions and intended timing. Separate required coverage from optional additions so incomplete work does not disappear inside a general multilingual status.

Use stable identities rather than file counts alone. Ten files can include a duplicate and omit an important message. Connect catalogs to screens or flows, and documents to routes, slugs, and alternate-language relationships.

For each item, record three facts: its translation evidence, its delivery evidence, and the remaining decision. A reviewed email still needs rendered subjects, body, and links. A retrieved help-page translation still needs a working route and content-owner acceptance. Keep these records in the system the team already uses for release work.

Preserve the pairing reviewers examine #

Record the source and target revisions supplied for review. If the source changes, identify the evidence affected rather than treating every target as equally stale. A spelling correction and a changed refund condition have different consequences.

Keep prior source, accepted targets, and workflow state for incremental preservation. Resolve local conflicts before retrieving replacement output rather than forcing every locale to regenerate.

Choose the trigger and authority for submission, execution approval, translation acceptance, and publication. One person can hold several roles, but the permissions remain different.

Test delivery in the form readers will use #

For application catalogs, load the target through the real runtime, exercise variables and plurals, and inspect important screens. For documents, open the actual route, follow links, and validate components and fragments. For emails, render subject, preheader, HTML, and plain text with safe fixture values.

Check explicit language choice, negotiation, and fallback. Fallback can keep an interface usable while hiding missing required translation. Record where it is permitted and test the required target directly.

Use format-appropriate checks. JSON parsing, Android builds, Rails lookups, and Markdoc validation establish different properties. Keep their evidence with the release item each check covers.

Establish acceptance before summarizing quality #

Name the requirements that can block publication: meaning, protected terminology, variables, accessibility, route availability, or voice. Choose qualified review or an applicable measurement for each. A score supplies evidence about a criterion; it does not grant release permission.

Record unresolved evidence. Measurement design explains answer states and denominators so an overall result does not hide languages with little coverage or no completed answer.

Decide what partial readiness permits #

Choose whether an incomplete locale blocks the whole release, is withheld, or uses an explicitly accepted fallback. Consider dependencies: a help article can often publish separately, while an unresolved price condition can block a locale's transaction flow.

Assign the publication owner and rollback method in the system that actually deploys or publishes. Retain the last accepted artifact and know how to restore it without translating again. No universal translation-tool publish action is assumed.

At the final decision, compare the release set with actual artifacts: what goes live, which revisions it contains, what remains withheld, and who approved it. Readiness means those facts agree, not that the translation queue happens to be empty.