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.
- A dossier is not a document
- Where the language work bites
- How to run it so it holds together
A dossier is not a document
The Common Technical Document (CTD, filed electronically as the eCTD) is a structured dossier: quality, nonclinical and clinical data organized into defined modules, much of it cross-referencing the rest. Treating a submission as "a stack of documents to translate" misses what a reviewer is actually doing — checking that the labeling matches the clinical data, that a term in Module 3 means the same thing in Module 5, that a number in a summary traces to the study it came from.
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.
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, device 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 — these must carry through untouched and consistent. 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.
How to run it so it holds together
Build and lock the terminology before volume translation starts, seeded from the sponsor’s approved terms and the source dossier, and treat any mid-project term decision as a change that propagates to every module — not a local edit.
Keep the submission’s reused segments in a shared memory so identical source resolves identically everywhere, and reconcile the cross-references as a distinct QA step rather than assuming per-document review will catch dossier-level drift.
And sequence with the regulatory timeline in view: the modules are not independent, so the terminology decisions made on the earliest translated content set the standard the rest inherits. Getting the quality and clinical terminology right first pays off across everything filed afterward. As always with regulated submissions, treat this as workflow guidance — the binding requirements are the target authority’s, and your regulatory team owns them.