How should US regulated teams control changes to translations?
Translation change control is a documented process that evaluates, approves, implements and records every change to source content or translated content before it is released. In US regulated settings, each change needs a named owner, an impact category, an approval, updated translation assets and a retrievable record. Access control, an audit trail and QA verification apply at every stage.
Table of Contents
What does translation change control mean?
Translation change control applies change-control principles to multilingual content. A change can start in the source text, in the terminology, in the translation memory or in a target-language file. The process decides whether the change is made, who approves it, and how the result is verified and recorded.
The AATB 2024 Change Control Best Practices Tool defines change control as the part of change management concerned with evaluating, planning, approving, implementing, monitoring, documenting and communicating changes that may affect organizational systems. That definition fits translation workflows without modification.
How does it differ from general change management?
The CDC Unified Process separates two disciplines. Change management implements requested changes through a predefined process. Configuration management maintains the consistency and control of established project products and documentation.
In translation, change management handles the request: a revised dosage statement, a new clause, an updated user interface string. Configuration management keeps the approved translation, translation memory and term base consistent with the approved source. A mature program runs both.
What is in scope?
The scope covers four object types:
Source documents, such as instructions for use, contracts, policies, standard operating procedures and disclosures.
Translated deliverables in every target language.
Linguistic assets: translation memories, term bases and style guides.
Process records: specifications, briefs, reviewer qualifications, QA reports and approvals.
The scope excludes ad hoc edits made outside the controlled workflow. Those edits are the main source of version drift.
Which steps move a change from request to approved translation?
The steps below follow the CDC description of change management, which covers submission, documentation, review, evaluation, categorization, approval and release against project baselines. Each step lists an owner and a control.
Step 1: Record the specification and baseline
Owner: localization manager.
Control: written translation specification.
ASTM F2575-25 states that specifications should document the purpose of the translation and the needs and expectations of the requester and end user. The standard also recognizes that more than one translation can be correct when specifications differ. A change cannot be judged without a baseline specification to compare against.
The same standard says requesters should conduct a needs analysis. It also says projects shall develop specifications in pre-production, follow them during production and evaluate the project against them afterward.
Step 2: Log the change request
Owner: requester, such as the content owner or regulatory affairs lead.
Control: change log entry with unique ID, date, requester and reason.
The CDC Unified Process says every project should maintain a change log and manage requested changes throughout the project lifecycle. It also calls for preserving historical documentation as requests are submitted and resolved. Closed requests stay in the log.
Step 3: Assess impact and categorize
Owner: change-control group lead.
Control: documented impact assessment with approved category.
The AATB tool categorizes potential impact as major, minor or inconsequential. It requires approval of the categorization and a determination of whether further change management is needed. Its impact checklist covers regulatory compliance and communication, vendors, IT hardware and software, operations, validation, products, controlled documents and training requirements.
For translation, add these questions:
Does the change alter meaning, dosage, warnings, legal obligations or numeric values?
How many languages and document types does it touch?
Does it alter a term that exists in the term base?
Does it change layout, character length or file format?
Does it affect a submission, a label or a filed document?
Step 4: Approve through the right authority
Owner: change-control group or delegated project manager.
Control: approval thresholds with recorded sign-off.
The CDC recommends approval thresholds. Larger-scope changes go to a Change Control Board. Lower-impact changes may be approved by a project manager under delegated authority. The AATB tool recommends a change-control group of relevant leadership, stakeholders and subject-matter experts, with a designated lead accountable for timely execution of the action plan.
Step 5: Implement the change in source, assets and target
Owner: language service provider project manager.
Control: versioned files, access control, controlled asset updates.
Implement in this order: update the approved source, update the term base, translate or revise, then update the translation memory. Skipping the term base step causes the same discrepancy to return in later projects. Only authorized users should be able to edit controlled assets.
Step 6: Verify the translation
Owner: reviser and project manager.
Control: bilingual review and recorded verification.
The ASTM F2575-23 definition of bilingual editing is a comparison of the initial translation with the source to verify correspondence and adherence to project specifications and professional practices. ISO 17100:2015 defines verification as confirmation by the project manager that specifications have been fulfilled.
Step 7: Release, file and close
Owner: change-control group lead.
Control: complete change-control file.
The AATB tool says the change-control file should contain the relevant change documentation and evidence that associated activities were completed. This supports transparency, accountability and traceability. Close the log entry only after the file is complete.
Who should review and approve translation changes?
Roles should be fixed before the first change arrives.
Role | Responsibility | Control |
Requester | Describes the change and the reason | Change log entry |
Change-control group lead | Owns categorization and action plan | Approved impact assessment |
Subject-matter expert | Judges technical, medical or legal accuracy | Recorded review |
Linguist and reviser | Translate and revise against specification | QA report |
Project manager | Confirms specifications are fulfilled | Verification record |
Terminology owner | Approves term base changes | Version history |
Compliance or regulatory lead | Confirms regulatory impact | Sign-off |
ISO 17100 requires documented competence records for translators, revisers, reviewers and other professionals. It also states that the translation service provider keeps responsibility when third parties perform translation work. A subcontracted linguist does not move accountability away from the provider.
How should versions, translation memories and terminology be controlled?
Translation memory and term bases are controlled configuration items. An approved correction should update the reusable asset. An obsolete term or a superseded version should stay traceable and should not be silently overwritten.
The Enosema multilingual terminology guidance calls for these practices:
Regular review cycles.
Change-request handling.
Synchronization across languages.
Version history.
Obsolescence management.
Incorporation of feedback.
For vendor handoffs, send the vendor the approved specification, the current term base, the current translation memory and the change log entry. Require the vendor to return the updated assets with the translation. Reconcile the returned assets against the version history before accepting them.
How should teams assess impact and priority?
Use a simple matrix. Rate each change on linguistic, technical, cost, schedule and compliance risk. Assign the highest rating to the category.
Category | Example | Typical route |
Major | Changed warning, dosage, contractual obligation or numeric limit | Change-control group, subject-matter expert review, full verification |
Minor | Reworded sentence with no change in meaning or obligation | Delegated project manager approval, bilingual review |
Inconsequential | Typographical correction in a non-controlled document | Logged correction, spot check |
The three category names come from the AATB tool. The examples and routes are suggested applications, and each organization sets its own thresholds in writing. Compliance impact outranks cost and schedule when ratings conflict.
What validation and audit-trail practices apply in regulated US industries?
Where translated content is held as electronic records in FDA-regulated settings, 21 CFR Part 11 may apply. 21 CFR 11.10 covers persons using closed systems to create, modify, maintain or transmit electronic records. It requires controls for authenticity, integrity and, when appropriate, confidentiality.
For applicable closed systems, the section lists these controls:
System validation.
Accurate and complete copies of records.
Record retrievability.
Authorized access.
Secure, computer-generated, time-stamped audit trails.
Authority checks.
Trained personnel.
Controlled system documentation with revision and change-control procedures.
Whether Part 11 applies to a given system is a determination for the organization’s regulatory affairs or quality function. Confirm applicability with that function before setting the control set.
ISO 17100 separates corrections from corrective actions. A correction fixes one error. A corrective action investigates and eliminates the cause of recurring translation or process errors. Record both, and open a corrective action when the same error appears twice.
Which criteria should guide the choice of a translation vendor for controlled changes?
Score each vendor against criteria that map to the controls above.
Documented competence records for every linguist, reviser and reviewer, as ISO 17100 requires.
Defined responsibility for subcontracted work.
Support for client translation memories and term bases, with version history.
Role-based access control and a time-stamped audit trail on files and assets.
Subject-matter expert review for the content domain.
Information security certification and defined data hosting location.
A written process for corrections and corrective actions.
Willingness to work inside the client’s change log and approval thresholds.
Where machine output is part of the workflow, add controls for the system itself. A 1982 Air Force machine-translation quality-control paper reports that comparing outputs between system versions exposed both improvements and degradation. The authors responded with baseline maintenance, controlled modification, comparator testing and validation against representative random text. The same discipline applies to any model update today.
What do worked examples look like?
Example 1: Medical device instructions for use
A manufacturer corrects a maximum operating temperature in the English instructions. The requester logs the change. The group lead rates it major because the value affects safe use. Regulatory affairs confirms the labeling impact. Each target language is revised by a subject-matter expert, verified by the project manager and filed. The term base is checked for the unit expression. The change-control file is closed after all languages are released.
Example 2: Contract template clause
A legal team revises a limitation of liability clause. The change is major. A legal reviewer in each target language checks that the obligation is preserved. The translation memory is updated only after sign-off, so that the unapproved wording does not reach other contracts.
Example 3: Software interface string
A product team shortens a button label. The change is minor. The project manager approves it under delegated authority. Bilingual review checks length and meaning. The term base entry is updated with the new version and the old label is marked obsolete.
What are the common failure modes and their mitigations?
Failure mode | Cause | Mitigation |
Source and target out of sync | Source edited without a request | Lock source files, require a log entry |
Old terms return | Term base not updated after approval | Update the term base before the translation memory |
Silent overwrite of memory | Uncontrolled edit rights | Access control, version history |
Missing evidence | Approvals by email only | Single change-control file |
Wrong approver | No thresholds | Written approval thresholds, as the CDC recommends |
Repeated error | Only corrections made | Open a corrective action, as ISO 17100 distinguishes |
Vendor handoff gaps | Assets not returned | Contract clause for returned assets |
Unreviewed model update | No comparator test | Baseline and comparator testing before release |
How can teams measure and improve the process?
Track cycle time per category, rework rate, number of corrective actions, and the share of changes with a complete file. Review these figures on a fixed schedule.
The Enosema guidance (EFS 2504:2025) recommends gathering user feedback on localized terminology through surveys, community reviews, usage monitoring and local experts. It also recommends periodic review and update cycles. Feed those findings back into the term base through the same change-control process.
A 1992 paper on translation quality management lists consultation, a clear requirements statement, translator briefing, regular status reports, change-control procedures and validation or quality-control procedures as management processes. Change control sits alongside the others and does not replace them.
Where AD VERBUM fits
AD VERBUM is a language service provider with more than 25 years of experience. It combines AI+HUMAN hybrid translation with subject-matter expert review and integrates client translation memories and term bases. Its LangOps System runs on EU-hosted infrastructure. It holds ISO 17100, ISO 18587, ISO 27001 and ISO 42001 certifications, audited by Bureau Veritas. It offers translation, localization and related services for regulated sectors.
Perspective
Change control fails at the handoff, not at the translation. A correct sentence still creates risk when the term base, the memory and the approval record do not agree with it. We build our work around that point. Every project is AI+HUMAN hybrid, with subject-matter experts reviewing regulated content. Client translation memories and term bases are integrated, so an approved change updates the assets that future work draws on. Our ISO 17100 and ISO 18587 certifications describe how translation and post-editing are verified. Our ISO 27001 and ISO 42001 certifications cover information security and AI use. We state our turnaround as 3x to 5x faster than traditional workflows. Regulated teams should treat speed as acceptable only when each change keeps its owner, its control and its record. Eric Brown
Key points
Translation change control evaluates, approves, implements and records every change to source and target content.
Change management handles the request. Configuration management keeps approved assets consistent.
Write the specification first. ASTM F2575-25 ties evaluation to the specification.
Categorize each change as major, minor or inconsequential and set written approval thresholds.
Treat translation memory and term bases as controlled items with version history.
Keep one change-control file per change, with access control and a time-stamped audit trail where 21 CFR 11.10 applies.
Separate corrections from corrective actions, as ISO 17100 does.
Measure cycle time, rework and terminology feedback, and review them on a schedule.
FAQ
What is the difference between translation change control and translation change management?
Change management is the wider discipline of implementing requested changes through a predefined process. Change control is the part that evaluates, approves, documents and communicates each change. In practice the two terms often describe the same workflow, with change control naming the approval and record-keeping steps.
Does 21 CFR Part 11 apply to translated documents?
It can apply when translated content is held as electronic records in an FDA-regulated closed system. The section requires controls such as validation, authorized access and time-stamped audit trails. Regulatory affairs or quality should confirm applicability for each system.
Who approves a minor translation change?
The CDC recommends that lower-impact changes may be approved by a project manager under delegated authority. Larger-scope changes go to a Change Control Board. Define both thresholds in writing before changes arrive.
What should a change-control file contain?
The AATB tool says the file should contain the relevant change documentation and evidence that associated activities were completed. For translation, include the request, impact assessment, approval, revised source, verified target files, updated assets and verification record.
Sources
