How to assemble the Module 4 nonclinical report package

What belongs in a CTD Module 4 nonclinical report package?

Module 4 contains the underlying nonclinical study reports and literature supporting the submission. Assemble the applicable pharmacology, pharmacokinetic and toxicology evidence with its controlled versions and companion files. Reconcile it with Module 2 summaries; a populated document tree alone does not establish that the scientific package is adequate.

Before you begin

FDA human-pharmaceutical dossier preparation. Scientific scope depends on product, pathway and development stage; this is not a study-requirements calculator.

What you will prepare: A report inventory and evidence handoff that a nonclinical reviewer and submission publisher can reconcile.

Define the evidence package before filling the tree

Module 4 organizes the underlying nonclinical evidence. A catalog entry is a place to put evidence, not an instruction to commission a study. Start with the application pathway, submission purpose, product modality, intended population and the approved nonclinical strategy. Ask the scientific lead to identify which evidence supports this particular submission and which questions remain open.

Keep four dispositions in the working inventory: included, referenced elsewhere, not applicable with a documented rationale, and unresolved. A missing report is not automatically “not applicable.” If an agency discussion changes the planned package, retain the actual correspondence and have its scope interpreted by the regulatory owner. FDA's current streamlined-studies resource is a useful entry point to product-specific recommendations; it is not a blanket permission to omit animal evidence.

Make a report-level contents record

Create one working row for each study: stable study identifier, descriptive title, objective, species or test system, route when relevant, report version/date, responsible owner, proposed CTD location and companion documents. Use another row when there is another study, even if the studies share a CTD heading. Do not create a fresh guide or a fresh scientific report for each animal, assay run or report appendix.

ICH M4S describes a Module 4 contents list at 4.1. The inspected FDA v4.0 hierarchy starts numbered Module 4 content at 4.2. Preserve the useful contents task while letting the publisher implement the supported electronic structure; do not invent a 4.1 electronic leaf merely to reproduce the older narrative outline.

Reconcile the inventory with the report repository and the Module 2.4/2.6 citation lists. This is a two-way check: every cited report must be retrievable, and every included report needs the appropriate summary disposition.

Separate the report from its companion artifacts

For each study, identify the controlled report body, appendices and individual-animal data, protocol/amendments, analytical or pathology contributions, and genuine signatures or quality statements where relevant. Record whether each item is embedded, separate, referenced or unavailable. The FDA hierarchy lists allowed document types, including datasets and reviewer guides; availability in that list does not make every type mandatory for every study.

Assign dataset applicability and supported versions to the study-data specialist using the current FDA standards catalog and applicable submission guidance. A narrative report, SEND dataset, data definition and nonclinical study data reviewer's guide serve different tasks. One cannot silently substitute for another. This preparation guide does not establish SEND applicability or technical validation criteria.

Before final packaging, compare identifiers and version relationships across all included artifacts. A report amendment that changes a conclusion may also require a dataset explanation or summary correction; identify affected records explicitly.

For a Part 58 study, check the final-report rule directly

First have the responsible regulatory and quality owners establish whether Part 58 applies to the study. Placement in Module 4 alone does not answer that question. If it applies, the final-report requirements in 21 CFR 58.185 are binding; the following working map groups the rule's content for preparation rather than creating another agency form.

• Identity and conduct: identify the performing facility and address, study start/completion dates, protocol objectives and procedures with changes, statistical methods and methods actually used.
• Materials and test system: identify test/control articles and their relevant strength, purity, composition or other characteristics; document their stability under administration conditions. Describe the test system and applicable animal numbers, sex, weight range, supply source, species/strain/substrain, age and identification. Include dose, regimen, administration route and duration.
• Data and people: describe circumstances affecting data quality or integrity; identify the study director, other scientists/professionals and supervisory personnel. Explain data transformations/calculations, summarize and analyze the data, and state the resulting conclusions.
• Accountable records: include the individual scientists' or professionals' signed, dated reports, identify storage locations for specimens, raw data and the final report, and include the quality assurance unit's signed statement. Under 58.35(b)(7), that statement specifies inspection dates and when findings were reported to management and the study director.

The final report must be signed and dated by the study director. Under 58.185(c), corrections or additions are made through a study-director amendment identifying the affected report content and reasons, signed and dated by the responsible person. Obtain genuine execution from the responsible people; do not reconstruct a signature or silently overwrite an issued report. Missing information should return to its owner for a controlled resolution before the package is represented as complete.

Work a missing-evidence discrepancy through to closure

Fictional review exercise: the inventory lists study NC-17 as final version 2, the uploaded PDF is version 1, and Module 2.6 quotes a finding introduced in version 2. The publishing check sees a readable PDF and a valid heading, but the evidence package is inconsistent.

Hold the affected package, obtain the controlled version from its owner, and compare its change history with the cited conclusion. Replace or relate documents using the actual submission lifecycle rules, then rerun the report-to-summary check. Do not rename version 1 to disguise the discrepancy.

Finish with separate sign-offs for document presence, electronic correctness, scientific interpretation and any applicable quality-system review. Checking all four boxes in a local authoring checklist records work; it does not establish that the agency has accepted the evidence.

Build a release map for each report and its dependencies

Use this editorial map during the handoff between the study owner, medical writer and publisher. It complements the inventory above by showing what changes when one source changes.

Add an owner, resolution record and status to each discrepancy. “PDF received” should not close a discrepancy about a missing scientific interpretation. Conversely, an accepted scientific explanation does not prove that the corrected file reached the publishing package.

Handoff exercise: a toxicokinetic amendment changes the exposure estimate, while the main toxicity report's administered dose remains correct. The amendment does not automatically change every conclusion. Ask the responsible scientists which exposure comparisons and interpretations are affected, obtain the controlled resolution, then trace those changes through the toxicology summaries and nonclinical overview. Record a reason when a dependent conclusion remains unchanged.

Finish by sampling the actual assembled package: follow a summary citation to the report, open its cited contributing record, and confirm the version relationships. This catches a delivery error that a repository-only review misses. Retain separate conclusions for scientific readiness, document execution and electronic readiness.

Frequently asked questions

Sources and revisions

Requirements, source recommendations and editorial preparation advice have different roles. Review the scope and revision of the source you use.

Related guides