Multilingual AI Workflow Brief
Use this before automating translation, localization, support, or knowledge search across languages.
Workflow Scope
- Workflow name:
- Owner:
- Source language(s):
- Target language(s):
- User group:
- Customer-visible? Yes / No
- Data classes allowed:
- Approved AI tools:
Language And Source Handling
- The workflow detects source language from content.
- The original text remains stored or linked.
- The output language is explicit.
- Users/operators can override detected language.
- Source document/version is recorded.
- Translated summaries are not treated as the source of truth.
Glossary
| Term | Approved translation | Do not use | Notes |
|---|---|---|---|
Review Rules
| Output type | Review pattern | Owner |
|---|---|---|
| Internal summary | Consequence- and language-specific review | |
| Draft support reply | Human approval before send | |
| Public marketing copy | Editorial review before publish | |
| Legal, billing, HR, medical, or financial content | Human owns final decision |
Quality Checks
- Meaning preserved from source.
- Approved terminology used.
- Tone fits customer relationship.
- No invented pricing, policy, availability, or compliance claim.
- Links are from approved domains.
- Internal notes are not exposed to customers.
- Privacy requirements are unchanged after translation.
Meaning Check And Revision Trace
- Exact source passage and version:
- Action, condition, deadline, negation and uncertainty preserved:
- Target-language reviewer and unresolved ambiguity:
- Source revision that makes targets stale:
- Affected target versions and publication decision:
Invented example: Estonian “Saadame tellimuse välja reedel, kui makse laekub hiljemalt neljapäeval” means dispatch on Friday conditional on payment received by Thursday. It does not promise customer receipt on Friday. Check against the source; same-model back-translation is not independent verification.