verifiedApproved
Term: Sign in
- Approved: Sign in (sentence case)
- Forbidden: Log‑in, Login (verb)
- Locale variants: en‑GB Sign in; de‑DE Anmelden; ar تسجيل الدخول
- Context: UI button; max width 96px; screenshot anchored
Terminology Governance that scales with your releases
Approved terms, forbidden lists, locale variants and redlines—kept in sync with your sprints, whether you translate, localise/localize, transcreate, adapt, or run MTPE.
translateTranslate
publicLocalise
auto_fix_highTranscreate
tuneAdapt
smart_toyMT/MTPE
schemai18n/g11n
Hex‑Grid Term Map
Your single source of truth—centralized, versioned, locale‑aware—so every translation, localization and transcreation uses the same approved lexicon.
blockForbidden
Term: Homepage
- Approved: Home
- Forbidden: Homepage (in navigation)
- Variants: de‑DE Startseite; fr‑FR Accueil
- Usage: Navigation; breadcrumb; title case rules
sync_saved_locallyVariant
Term: Organization / Organisation
- en‑US: Organization; en‑GB: Organisation
- Rule: Respect market orthography; keep glossary pair
- Notes: Applies to localize/localise, globalize/globalise
smart_toyMT hint
Term: Retry
- MTPE: prefer human‑curated context in error states
- Gloss: keep concise verbs; avoid gerunds when truncating
- Keys: ui.errors.retry; ui.cta.retry
Variant Radar (Locale collisions)
See where variants collide by locale—en‑GB localisation/organise, en‑US localization/organize; product vs marketing translate/transcreate; medical vs legal terminology.
- Orthography rules (‑ize/‑ise)
- Plural/abbrev rules and morphology
- Domain preference: pharma translations, legal translations, technical translations
Concordance Lab — Before/After
Product UI (translated → transcreated)
Drag to compare: strictly translated vs lightly transcreated CTA text to fit truncation.
Legal clause (adapted)
Show how a translated clause is adapted with jurisdictional terminology while keeping meaning intact.
Help Center (localized)
Metadata, breadcrumbs and links are localized (hreflang, canonical, altLang) alongside the translation.
Change‑Control Ledger
Every change is redlined, approved, and time‑stamped—across translation, localisation/localization, MT post‑editing and review.
- Request → Review → Approval → Release
- Reviewer notes + impacted files/locales + i18n keys
Domain Packs
Legal translation
Medical localisation
Technical translations
Marketing transcreation
Public sector adaptation
Governance Workflows
Roles
- PM
- Lead Linguist
- Reviewer (Client)
- SME
- Compliance
Stepper
- Propose
- Validate
- Trial‑use
- Approve
- Publish
- Sunset
Quality gates
- MTPE gates
- Bilingual review
- LQA
- In‑context translating
Integrations & Exchange
CI checks block mis‑translated or non‑localized terms; webhooks notify reviewers during translating/localizing.
Evidence & Audits
0
Reduction in reviewer cycles
0
Fewer regulator queries
0
Audit‑ready exports
Reviewer‑independence
ISO 17100
Change‑log by locale
Redlines
Acceptance criteria
Engagement Models
Standard — termbase cleanup + forbidden list + style guide refresh
For day‑to‑day translations and localisation requests.
Enhanced — TBX exchange + concordance checks + reviewer onboarding
Ideal for marketing transcreation and website localization.
Enterprise — SSO + permissioning + CI term‑lint + quarterly audits
For regulated translations in pharma/medical/legal.
Case Reels
SaaS — 12 markets, 1.8k terms
−62% reviewer cycles; zero critical terminology defects in last 6 releases; smoother software localization.
Pharma — IFU/labeling pack
Regulator queries reduced by 48%; first‑round approval; medical translations aligned with localised dosing language.
FAQ
Repo & TBX support?
Yes—import/export TBX; synchronize lexicon with Git/CMS/TMS during translating and localizing.
Yes—import/export TBX; synchronize lexicon with Git/CMS/TMS during translating and localizing.
Reviewer training included?
Yes—playbooks for translation, transcreation and adaptation scenarios.
Yes—playbooks for translation, transcreation and adaptation scenarios.
EN variants (US/UK)?
We govern organize/organise, localize/localise and related translated forms per locale.
We govern organize/organise, localize/localise and related translated forms per locale.
Forbidden vs deprecated?
Deprecated allowed historically; forbidden blocked prospectively with term‑lint during translation and MTPE.
Deprecated allowed historically; forbidden blocked prospectively with term‑lint during translation and MTPE.
Import existing glossaries?
Yes—we normalize, de‑dupe and map to domains for technical/legal/medical/marketing translations.
Yes—we normalize, de‑dupe and map to domains for technical/legal/medical/marketing translations.
Security & compliance?
ISO 17100 & 27001; least‑privilege; secure delivery; audit‑ready translation evidence.
ISO 17100 & 27001; least‑privilege; secure delivery; audit‑ready translation evidence.
Ready to standardize language across products and regions?
Governance that supports translation/localization/transcreation, i18n/g11n and MTPE — with reviewer‑independence and audit trails.
