Multilingual Document Control

Multilingual document control keeps each language version connected to its approved source, verified meaning and authorized use. Translating the newest file is insufficient: the source may be a draft, the translation may reflect an older revision, or a correct translation may not yet be released for its intended site.

This procedure covers internal pharmaceutical instructions such as SOPs and work instructions. It produces a translation register, review record and release decision. It does not determine national language obligations or replace the separate review process for product labeling, patient information or clinical consent materials.

For example, EMA maintains a specific linguistic-review process for human product information in the centralised procedure. That process should not be copied indiscriminately into an internal SOP workflow. EMA linguistic review—Human.

The examples below are fictional documentary exercises, not qualified translations or a tested EDMS workflow. Primary sources were checked October 6, 2026.

1. Decide which language versions are controlled

Begin with the process owner, local operational representatives, document controller and authorized reviewers. Identify the activities, sites and users that need each language. Record the applicable requirements and why each version is needed. Do not assume that every document must exist in every company language, or that an English master alone is suitable for every user.

Define each document's status: an authoritative source instruction, a controlled translation for operational use, an approved local adaptation or an informational reference. These categories have different consequences. A reference translation should not quietly become the instruction used to perform work.

For human-medicines GMP documentation within its scope, EU Chapter 4 section 4.4 addresses language and style fitting the intended use. Sections 4.1–4.3 address document controls, reproduction and identifiable approved instructions. The Commission's current index lists the January 2011 revision. Chapter 4, revision 1, current EudraLex index.

Decide how a discrepancy is escalated. Naming one source language as authoritative does not make a contradictory translation safe to use. If the version needed by operators contains uncertain instructions, hold the affected use and obtain an authorized resolution.

2. Link language versions without forcing identical numbering

Use a common document-family identity, an exact source revision and a distinct target-language revision. A translation can need a correction even when the source content is unchanged, so source and target revision numbers need not move together.

Maintain the following information in the authoritative document-control system. If a worksheet is used during preparation, reconcile it into that system rather than leaving an uncontrolled competing register.

Do not infer a missing language or locale from a filename. Resolve ambiguity before issuing work. Where one language variant is acceptable for several sites, document that decision; where local terminology changes the meaning, route it for technical assessment.

Distinguish translation from process change. Replacing a source term with an approved equivalent is translation. Changing the equipment, acceptance limit or sequence to match local practice is a substantive adaptation that needs the applicable change and approval process.

3. Issue a translation package with a fixed baseline

Give the translator the exact source, relevant figures/tables, controlled terminology, existing approved translation where useful, and the change description. Include instructions for questions, placeholders and uncertain terms. A translator should not silently repair a technically ambiguous source.

Record what was delivered. If the source changes during translation, identify the changed sections and decide whether to reissue the package or apply a controlled delta. Do not send a replacement attachment without recording which translator or reviewer received it.

When translation begins from a draft to support planning, label the work provisional and preserve that relationship. Release still requires reconciliation to the final approved source and the target's own required review/approval. Early translation work does not make the provisional source operationally authoritative.

A translation-memory match or reused paragraph can reduce repetitive work, but check its source revision and context. Identical words around a changed limit may still require review. Record reused content under the same acceptance criteria as newly translated content.

4. Review meaning before approving the rendition

Assign review that can assess both language and the technical activity. Define who resolves terminology, process intent and local-use questions. The required independence or approval route comes from the applicable process and quality system; this article does not impose one universal translator credential or two-reviewer rule.

Use these checks for each consequential instruction:

A language reviewer should not approve a technically changed limit merely because the sentence is fluent. Conversely, a technical reviewer who cannot assess the target language needs appropriate linguistic support. Document how the combined evidence establishes suitability for the intended users.

Check numerical conventions explicitly. A comma or full stop may act as a decimal separator or thousands separator depending on the intended locale. If “1,000” cannot be interpreted unambiguously in the supplied source, ask the source owner; do not infer a value from the translation tool's default locale.

Machine translation or AI-generated wording may be used only within the permitted workflow. Treat its output as material for review, not evidence that meaning is preserved. A back-translation can help reveal a discrepancy but does not itself establish that the target is correct, complete or usable. Retain the review evidence required by the procedure for the actual released target.

5. Choose a coordinated or staged release

Before approval, decide whether the affected language versions must become effective together or may be released by site/activity. A coordinated release waits for all required versions and readiness conditions. A staged release needs an authorized scope and transition plan showing why the differences are acceptable.

Avoid equating “translation completed” with “ready for use.” Record required user communication, training or qualification, controlled-copy changes and connected-system updates. Verify the displayed or printed rendition, not only the editable file accepted by the translator.

For applicable US drug production/process-control procedures, 21 CFR 211.100 requires controlled review/approval of procedures and changes and addresses following procedures and documenting deviations. Translating a substantive change does not bypass that process. 21 CFR 211.100.

Use this release decision worksheet, with a result, evidence reference, owner and date for every row:

A required adverse or unknown result holds the affected release. “Not applicable” needs a documented scope reason; it cannot be used to dismiss a missing translation required by the approved plan.

6. Work through a late-translation case

Assume fictional SOP-24 has English source revision E3 approved for a coordinated October 1 transition at two sites. North requires the English version; South requires a reviewed French version. The change replaces an illustrative maximum hold time of 15 minutes with 10 minutes. These values are synthetic and are not operating advice.

French revision F5 corresponds to older source E2. F6 is the proposed translation of E3. The coordinated plan requires both sites' versions and readiness to be accepted before release.

For the comparator example, a 12-minute duration satisfies “at least 10” but violates “no longer than 10.” At exactly 10 minutes both statements allow the value, so a boundary-only check would miss the reversal. Test a value on each side when reviewing consequential limits.

Do not automatically let South continue using F5 after the planned transition, and do not silently release E3 at North under a plan that requires both sites. The authorized owners must revise the transition plan if a staggered approach is appropriate. That decision should assess the process consequences, site readiness and any applicable requirements; translation delay alone is not approval.

If the original plan instead authorizes independent site release and the process assessment supports it, North may become eligible when its own conditions are satisfied while South remains held. Record that different starting assumption. The same missing French version leads to a different scope decision, not a different assessment of the French evidence.

7. Maintain the language relationship through change

When the source changes, identify every dependent target and record its impact assessment. A source amendment may require revised translation, a reviewed no-change conclusion or retirement of an unnecessary version. Do not mark all translations current by merely changing their source-version field.

When only a target-language error is corrected, preserve the unchanged source mapping and revise the target under the approved control process. Assess whether the earlier wording affected work already performed. Retain the prior rendition and correction history as required; replacing the file should not erase the evidence of what users received.

For a separate paper exercise, take E3 as unchanged and correct the comparator error in F6 by creating F7. The proposed register row is: family SOP-24; source E3; target French F7; site South; change “correct minimum to maximum”; review reference TR-07; release decision Pending. TR-07 confirms the corrected meaning, but no target approval or South readiness evidence is supplied. Meaning review passes that check; operational release remains held. F7's higher number does not prove approval, and creating an English E4 solely to match the French revision would misstate the source history. The document controller obtains the remaining decisions and records when F7 replaces the affected F6 copies. The process owner separately assesses any earlier work using F6; a corrected translation does not establish that the earlier work was acceptable.

Test retrieval by the intended users after release. A language selector, search result or printed copy should make the correct site/language/revision available without presenting a superseded translation as current. Inspect mixed-language tables, clipped text, special characters and linked forms in the final rendition. These are concrete places where correct editable text can be delivered incorrectly.

For completion, retain the source package, target version, resolved questions, review/approval, readiness and distribution evidence. The QMS document-control guide covers the wider lifecycle. For an Assyro regulatory-document evaluation, bring a source/target pair and its release decision to establish the required workflow and evidence before accepting capability claims.