A regulatory submission is not one document to translate — it is a structured dossier where consistency across modules, and against the source data, is the thing reviewers check. What that means for how the translation is run.
View the file review example ↓View references (1) ↓A dossier is not a document
The Common Technical Document organizes medicine-registration content into modules. Module 1 is region-specific; Modules 2–5 follow the harmonized structure. eCTD adds electronic structure and lifecycle requirements. It is not the submission format for every medical product, and a 510(k) should not be treated as a CTD dossier.
That makes internal consistency across the whole dossier the real deliverable, not the quality of any single translated document in isolation. A submission where each document is individually fine but the terminology drifts between modules is a submission that invites reviewer questions — and questions cost review cycles.
Translation scope is set by the target authority and submission route. eCTD publishing, technical validation and applicant approval are separate from translating the documents and must be scoped explicitly.
From reading to a project
Keep each translated file tied to its source and references
Dossier file map · self-created example
- Request / source set
- DEMO-DOSSIER-01 · file list confirmed by owner
- Source file / revision
- DEMO-FILE-02 · revision [as supplied]
- Related source reference
- DEMO-FILE-02 ↔ [supplied section or attachment ID]
- Chinese handover note
- 待确认源文件版本及交叉引用
Review status: questions to confirm
Match the actual source set
Record the file title, actual source language and revision provided by the owner. Mark context-only or pending files separately from the translation set.
Trace references before review
Keep supplied section, table and attachment references linked to their source locations. Flag missing or changed references for the source owner instead of reconstructing them.
Carry approved terms across files
Use the supplied terminology reference and record where a repeated phrase appears. Route conflicting source wording or terminology decisions to the named owner.
Share the actual source file list, revisions, linked references and review handover requested for the Chinese language work.
Where the language work bites
Terminology has to hold across modules and across time. A dossier is assembled over months by different authors and often different translators. Without a shared, enforced termbase, the same substance, product or endpoint drifts into several renderings, and the drift is exactly what a careful reviewer notices. This is the single highest-leverage control in submission translation.
Numbers, units and names are not prose. Doses, values, study identifiers, product names — preserve their meaning and traceability, using approved localized names or formats where required rather than silently changing them. They are the spine a reviewer traces; a transcription slip here is worse than an awkward sentence.
Reused text should be reused, not re-translated. Summaries quote the underlying reports; labeling echoes agreed wording. When the same source text appears in several places, it should resolve to the same target text every time. Independently re-translating each instance manufactures inconsistency the reviewer will flag.
| Control | What goes wrong without it | Why a reviewer notices |
|---|---|---|
| A shared, enforced termbase | A dossier is assembled over months by different authors and often different translators; the same substance, product or endpoint drifts into several renderings. | They are checking that a term in Module 3 means the same thing in Module 5. Drift is exactly what a careful reviewer sees. |
| Numbers, units and identifiers checked against the source | Doses, values, study identifiers and product names get treated as prose and reworded. | These are the spine a reviewer traces back to the study. A transcription slip here is worse than an awkward sentence. |
| Reused text reused, not re-translated | Summaries quote the underlying reports and labelling echoes agreed wording — translated independently each time. | The same source text resolving to different target text across the dossier is manufactured inconsistency. |
Dossier-level drift is invisible to per-document review: each file reads correctly on its own, and the mismatch only appears when they sit together. By then it is distributed across the whole submission and cannot be fixed in one place.
How a dossier actually comes apart
A dossier is more than a set of files; the modules reference each other. Terminology settled on the earliest translated content is inherited by everything that follows — including the parts not yet written when those decisions were made.
That is why dossier-level drift is invisible to per-document review. Each file reads correctly on its own; the mismatch only appears when they sit together — the same source term resolved differently across modules, cross-references pointing at paragraph numbers that no longer line up. By the time a reviewer asks about it, the problem is distributed across the whole submission and cannot be fixed in one place.
As always with regulated submissions, the binding requirements are the target authority’s, and your regulatory team owns them.