Translate passport content and review machine drafts

Interface and content are different things

The consumer surface has interface chrome in the EU language set plus negotiation from the browser's preference. The content itself - the product name, descriptions, statements - is authored and reviewed per language.

Only reviewed or approved content is served publicly. A language with no approved content falls back to your authored source rather than to another market's translation.

Authoring a translation

1. Open the passport and the translations panel.
2. Pick a language and enter the translated values for the fields the platform offers.
3. Save as draft, review it, then approve it.
4. Check the public preview in that language before publishing.

Machine drafting

Machine drafting produces drafts only. It protects the terms that must not be translated - standards, regimes, hazard codes, units, numbers, identifiers, links - by masking them before the text leaves the platform and verifying that each one came back; a protected term that does not survive is reported as a finding, because a translated standard reference is a compliance defect rather than a style choice.

Each language gets a triage verdict based on observable signals: placeholders kept and unique, not an echo of the source, a plausible length ratio, and for Greek and Cyrillic that the target script actually appears. A draft whose source changed underneath it is flagged as stale. A dry run shows you the masked payload without calling the provider or writing anything.

The review gate

Drafts land in the review queue with their signals and their freshness. Replacing an existing draft requires a deliberate overwrite, and a reviewed or approved translation is never replaced silently.

The platform states plainly that it cannot judge correctness. A qualified reviewer decides whether a draft is usable, and approval is the only path from a draft to a public passport.

Coverage

Coverage reports how much of the localizable content exists per language across published passports, and the market view tells you which languages a market expects. That view is advisory: it helps you plan, and it never changes a compliance score.

Screen-by-screen reference

These pages were checked in the organization console on 8 October 2026 using an isolated sample organization. Controls can differ by role, plan, record state and configured providers. Each page below explains its purpose, a practical workflow, the visible controls and what to verify afterward.

Localization (/localization)

Localization tracks approved language coverage, drafts awaiting review, protected glossary terms and translation import/export.

Use coverage to choose which passport languages need work, then export only the required content to translators. Import results are drafts until reviewed; quality flags and glossary terms help identify inconsistent terminology. Open the passport's own language panel to approve the actual public translation and check it against the source version.

Machine-generated text stays a draft until a human reviewer approves it.

Controls and options

• Read Coverage for missing languages and Awaiting review for machine or human drafts.
• Export for translators with language, format and only-missing options.
• Import translated file and review quality flags before approval.
• Manage glossary terms so protected words survive translation; open a passport's language panel to approve its actual content.