A regulatory submission can contain strong science, complete documentation, and all the expected components of the Common Technical Document (CTD) yet still leave a reviewer with questions.

Often, the problem is not what is missing. It is what does not quite connect.

A study may be described in one way in a detailed report and slightly differently in a summary. A conclusion may appear stronger when condensed into Module 2 than the underlying evidence in Module 4 or 5 supports. A specification or proposed shelf life may be presented without making its scientific basis sufficiently clear. Information updated in one part of the dossier may remain unchanged somewhere else.

None of these issues necessarily reflect poor science. But together, they can weaken confidence in the submission.

Drawing on extensive firsthand experience working with nonclinical and clinical evidence in Modules 4 and 5, Dr. Maryam Kamarehei views CTD quality as more than completeness or compliance with a prescribed structure. A strong CTD should tell a coherent scientific and regulatory story. The evidence, interpretation, rationale, and conclusions need to remain aligned wherever they appear.

The structure is standardized. The story still has to be built.

The CTD brought an essential degree of harmonization to pharmaceutical submissions. Module 1 contains region-specific administrative and prescribing information, while Modules 2 through 5 provide the summaries and the underlying quality, nonclinical, and clinical information that support the application^1,2.

That structure solves an important organizational problem. It does not, however, guarantee that the information within it will be internally consistent.

In practice, a dossier is rarely developed by one person, in one system, at one time. Research and development, clinical, nonclinical, quality, manufacturing, regulatory affairs, medical writing, and other functions may all contribute information. Documents evolve at different points in development. Data may be drawn from different repositories. Analyses change. Versions change. Scientific understanding changes.

By the time all of that material comes together in the CTD, the challenge is no longer simply assembling documents. It is preserving the connections among them.

That challenge is especially visible in Modules 4 and 5, where Dr. Kamarehei has extensive practical experience. These modules contain the nonclinical and clinical study reports that form an important part of the evidentiary foundation of a submission. Their findings are then represented at higher levels of the dossier, particularly through the nonclinical and clinical summaries and overviews in Module 2.

That movement from detailed evidence to increasingly concise interpretation is necessary. It is also one of the points at which coherence can be lost.

Consistency means more than matching numbers.

Cross-document consistency is sometimes approached as a reconciliation exercise: Does the same value appear everywhere it should? Are the study identifiers correct? Are tables and narratives aligned?

Those checks matter, but scientific consistency goes further.

The same evidence may appear in several forms across a submission. A study report contains the detailed methods, results, limitations, and analyses. A summary necessarily condenses them. An overview goes further still by interpreting the evidence and placing it within the broader argument supporting the product.

At each step, information becomes more selective.

The regulatory question is therefore not only whether the numbers match. It is whether the meaning still matches.

From a Modules 4 and 5 perspective, this distinction is particularly important. A clinical finding can be factually reproduced while important context surrounding that finding becomes less visible. A nonclinical observation can be accurately summarized but given more or less weight than the underlying evidence warrants. Differences in terminology, analysis of populations, endpoints, time points, or interpretation can also create subtle inconsistencies between detailed reports and higher-level summaries.

These may not look like major errors when sections are reviewed independently. They become much more noticeable when the dossier is read as a whole.

The same principle applies beyond Modules 4 and 5. Manufacturing processes, formulation information, analytical methods, specifications, stability data, and proposed storage conditions may appear in several parts of the submission. When information changes in one location, every place that depends on that information needs to be considered.

The CTD may be modular in structure, but regulatory review is not confined by those boundaries.

A reviewer should not have to reconstruct the rationale.

Consistency alone is not enough. A submission must also make the reasoning behind important decisions visible.

This is where technically complete dossiers can still fall short.

A specification may be presented with appropriate acceptance criteria, for example, but the connection between those criteria and the development, manufacturing, analytical, or stability data supporting them may not be sufficiently clear. Similarly, a proposed shelf life may be stated consistently throughout the dossier while the rationale connecting the proposed period to the available stability data, storage conditions, and testing time points remains difficult to follow.

The underlying evidence may exist. The problem is that the reviewer has to work too hard to reconstruct the argument.

The same issue arises in the nonclinical and clinical portions of the CTD. Study reports provide detailed evidence, but a regulatory submission must do more than reproduce study findings. The summaries and overviews need to demonstrate how the evidence fits together and how the conclusions presented to the regulator arise from it.

Extensive work with Modules 4 and 5 makes this especially clear: good regulatory writing requires judgment about what needs to be carried forward, what context must be retained, and where an inference or conclusion requires explanation.

A reviewer should be able to move from a conclusion back to its supporting evidence without encountering unexplained gaps along the way.

Traceability protects the scientific story.

That makes traceability more than a document-management concern.

CTD content may draw on laboratory studies, clinical studies, analytical data, manufacturing records, databases, statistical outputs, and, where relevant, other sources of evidence. Every transformation of that information creates another opportunity for context to change or for an outdated version to survive.

Clear source documentation, disciplined version control, and reconciliation across documents help preserve the relationship between the evidence and the claims ultimately presented in the submission.

This is particularly important when documents are revised at different times. A change to an analysis, study interpretation, manufacturing process, specification, or stability assessment should prompt a broader question: Where else in the dossier is this information reflected, summarized, interpreted, or relied upon?

That question is more useful than simply asking whether the document containing the change has been updated.

Quality control should test coherence, not just correctness.

Quality control (QC) is often discussed near the end of CTD preparation, when documents are checked for formatting, references, controlled terminology, approval status, publishing requirements, and other technical details.

Those activities remain essential. But limiting QC to end-stage document checks miss an important part of its value.

Effective QC should also test whether the submission works as an integrated whole.

Does the Module 2 summary faithfully represent the evidence that follows? Are important conclusions supported at the appropriate level of detail? If information appears in several places, is it consistent not only in wording and values but also in interpretation? Can key decisions be traced to an identifiable scientific rationale? Have late changes been propagated to every affected part of the dossier?

These questions are easier to address when quality is built into CTD development rather than deferred until finalization.

Cross-functional review is particularly important here. The people who generate evidence know its technical details. Those responsible for regulatory strategy understand how the evidence must support the application. Writers and reviewers working across the dossier can identify places where information has been condensed, interpreted, or carried forward inconsistently.

The objective is not simply to have more reviewers. It is to have the right perspectives brought together before inconsistencies become embedded in the final submission.

Read the dossier the way a regulator will.

Perhaps the most useful shift in CTD preparation is to stop thinking exclusively in terms of individual documents and start thinking in terms of the reviewer’s journey through the evidence.

A reviewer does not encounter a clinical summary, nonclinical overview, manufacturing description, or stability discussion in isolation. Each contributes to an assessment of the same product. Statements made in one place establish expectations for what will appear elsewhere.

Years of hands-on work with detailed nonclinical and clinical evidence reinforce a simple point: some of the most consequential CTD quality issues can be surprisingly small. A changed value. An outdated description. A difference in terminology. A conclusion that has become more definitive as it moved farther from the source evidence.

Individually, each may seem minor. Collectively, they can create uncertainty about which version of the story the reviewer should trust.

The CTD was designed to provide a common structure for presenting quality, safety, and efficacy information. The structure is essential, but it is only the framework. The quality of the submission ultimately depends on what happens inside that framework.

The best CTDs do more than contain the required information. They allow the reviewer to follow the evidence, understand the rationale, and see how the pieces fit together.

When every part of the dossier supports the same scientific story, the CTD becomes more than a collection of documents. It becomes what it is meant to be: a coherent regulatory case for the product.

References

1. International Council for Harmonisation. M4: The Common Technical Document. ICH CTD webpage

2. U.S. Food and Drug Administration. M4 Organization of the Common Technical Document for the Registration of Pharmaceuticals for Human Use: Guidance for Industry. October 2017. FDA guidance