All posts
·11 min read

How to Write CTD Module 2.4 Nonclinical Overview

Practical guide to writing the CTD Module 2.4 Nonclinical Overview for IND submissions. Structure, content, dose justification, what FDA reviewers look for, and common mistakes.

Dr. James Chen
Dr. James Chen
Preclinical Biology, PhD
How to Write CTD Module 2.4 Nonclinical Overview

Module 2.4 is the document that decides whether an FDA reviewer reads the rest of your nonclinical package with confidence or with suspicion. It's the Nonclinical Overview — a narrative that integrates your pharmacology, pharmacokinetics, and toxicology data into a coherent story about why your drug is safe enough to test in humans.

I've read more Module 2.4 documents than I'd care to count. The good ones take me 20 minutes to read and leave me with a clear understanding of the drug's safety profile. The bad ones take an hour, leave me confused about which species was used for what, and bury the dose justification somewhere between the PK tables and the reproductive toxicity section.

FDA reviewers have the same experience, except they're reading dozens of these. Make yours clear, and you make their job easier. Make their job easier, and your IND moves through the review process without unnecessary questions.

What Module 2.4 is and isn't

Module 2.4 is NOT a repeat of Module 4. Module 4 contains your individual study reports — the full, detailed, 200-page nonclinical study reports for each study. Module 2.4 is a 15-30 page narrative that integrates the findings across all of those studies.

Think of it this way: Module 4 is the evidence. Module 2.4 is the argument. The argument explains what the evidence means, how the studies relate to each other, and why the aggregate nonclinical data supports proceeding to clinical trials.

Module 2.4 is also distinct from Module 2.6 — the Nonclinical Written and Tabulated Summaries. Module 2.6 is a detailed, discipline-by-discipline summary of each study. Module 2.4 is higher-level — it's the integrated narrative that crosses disciplinary boundaries and connects pharmacology to PK to toxicology.

The hierarchy: Module 2.4 (integrated overview, ~15-30 pages) → Module 2.6 (detailed summaries by discipline, ~50-100 pages) → Module 4 (full study reports, hundreds of pages each).

Structure

ICH M4S(R2) provides the structural template. I'd organize it like this, with notes on what each section actually needs to accomplish:

1. Overview of nonclinical testing strategy (1-2 pages)

Your opening argument. Drug class, mechanism of action, clinical indication, patient population. Which studies you ran, in which species, why. Species selection rationale — especially important for biologics (cite ICH S6(R1)). GLP status of pivotal studies.

Don't pad this with corporate overview or disease epidemiology. The clinical sections handle that. Get to the point: drug, plan, species, rationale.

2. Pharmacology and pharmacokinetics

I'm combining these because in practice they should read as a continuous narrative, even though ICH M4S(R2) separates them structurally. The pharmacology tells the reviewer what the drug does. The PK tells them where it goes and how long it stays. Together, they establish whether the animal models you chose actually saw the drug and responded to it. That's the question the reviewer is asking.

Pharmacology (2-4 pages): Summarize primary, secondary, and safety pharmacology findings. For primary PD, include potency values — IC50, EC50, Ki. Don't make the reviewer guess how potent your drug is. For secondary PD, anything with off-target activity within 10-30x of the primary target IC50 is worth flagging. Relate it to potential clinical signals. For safety pharmacology, present hERG IC50 and safety margin, in vivo cardiovascular results, respiratory, CNS — all as exposure multiples relative to anticipated clinical exposure. That's the format reviewers expect. (More on the core battery in the ICH S7A guide.)

PK (2-4 pages): ADME characterization across species. The single most useful thing you can put in this section is a cross-species PK comparison table: Cmax, AUC, t1/2, CL, Vd, F% for rat, dog (or NHP), and projected human. One table. Reviewers will refer back to it throughout their assessment.

Cover absorption (bioavailability, Tmax, food effect), distribution (Vd, plasma protein binding across species including human), metabolism (CYP enzymes, active metabolites, cross-species comparison — this is critical for species relevance justification), and excretion (routes, renal vs. hepatic).

Toxicokinetics: Fold TK data from your repeat-dose studies into this section. Did animals achieve adequate systemic exposure? Sex differences? Accumulation on repeat dosing? This is where you connect the PK story to the tox story. If rats had 5x lower exposure than dogs at the same dose, that explains why dogs showed toxicity and rats didn't — and the reviewer needs to see that connection made explicitly.

4. Toxicology

Length: 4-8 pages

This is the longest section and the one FDA reviewers spend the most time on. Organize it by study type:

Single-dose toxicity: Brief — 1 paragraph is often sufficient. Acute LD50 or approximate lethal dose. Maximum tolerated single dose. Target organs at high doses. If single-dose toxicity was evaluated within the repeat-dose study, state that.

Repeat-dose toxicity: This is the section. For each species:

  • Study design: duration, doses, route, number of animals
  • Key findings by dose level
  • NOAEL (No Observed Adverse Effect Level) — this is the number that feeds your dose justification
  • Target organs identified
  • Reversibility of findings (if recovery groups were included)
  • GLP status

Present findings as a narrative, not a table dump. A table of findings by dose and organ system is useful in Module 2.6. In Module 2.4, the narrative should integrate across species: "Hepatotoxicity was observed in both rats (ALT elevation at 300 mg/kg, NOAEL 100 mg/kg) and dogs (ALT elevation at 30 mg/kg/day, NOAEL 10 mg/kg/day). The dog was the more sensitive species."

Genotoxicity: Summarize the standard battery per ICH S2(R1). State each assay, the result (positive/negative), and the highest concentration/dose tested. If all three assays are negative, one paragraph is sufficient. If any assay is positive, discuss the follow-up strategy and relevance to human risk.

Reproductive and developmental toxicity: Summarize per ICH S5(R3). If studies are deferred (e.g., Phase 1 enrolls only males), state the rationale per ICH M3(R2). If fertility studies or embryo-fetal development studies are completed, summarize key findings and NOAELs.

Other toxicity studies: Immunotoxicity per ICH S8, local tolerance for parenteral formulations, phototoxicity if relevant. Brief summaries — 1-2 paragraphs each unless there are findings that require discussion.

5. Integrated overview and conclusions

Length: 2-3 pages

This is where you tie everything together. State:

  1. The overall nonclinical safety profile. What are the main risks identified? What are the target organs? Are the effects monitorable in clinical trials? Are they reversible?

  2. The dose justification. This is critical. Walk through the calculation:

    • NOAEL from the most sensitive species (state the species, study, and NOAEL value)
    • Human equivalent dose (HED) using FDA's body surface area conversion factor
    • Safety factor applied (and justification for the factor chosen)
    • Proposed clinical starting dose
    • Safety margin: ratio of NOAEL (in exposure terms, ideally AUC or Cmax) to projected human exposure at the starting dose

    Show the math. Don't make the reviewer calculate it themselves.

  3. The risk-benefit assessment. For a Phase 1 IND, this is straightforward: based on the nonclinical data, the proposed starting dose provides an adequate safety margin, the identified risks are monitorable, and proceeding to first-in-human dosing is justified.

  4. Nonclinical studies planned but not yet completed. If you have ongoing studies (e.g., carcinogenicity, chronic toxicity for later phases), list them here with expected completion dates.

What makes a good Module 2.4

It's readable. An FDA reviewer who is not an expert in your specific therapeutic area should be able to read Module 2.4 and understand your drug's nonclinical safety profile. Use plain language where possible. Define abbreviations. Don't assume the reader remembers what NOAEL your 28-day rat study produced — state it where it's needed.

Cross-references are precise. When you reference a study, cite the Module 4 report location. "See Study Report 4.2.3.2-1" is better than "See the repeat-dose toxicology section." Reviewers navigate the eCTD by module location, not by section headers.

Exposure context is consistent. Every safety finding should be presented with an exposure comparison to the anticipated clinical dose. "Hepatocellular hypertrophy was observed at 300 mg/kg in rats, corresponding to AUC exposures approximately 25x the projected human AUC at the proposed starting dose." This sentence tells the reviewer everything they need to assess relevance.

The dose justification is in Section 5, not in an appendix. I've seen Module 2.4 documents that reference a separate "dose justification document" in Module 5 or Module 1. Don't do this. The dose justification is a core element of the nonclinical argument for proceeding to human trials. It belongs in Module 2.4.

Gaps are acknowledged. If a study isn't complete, say so. State when it will be completed. If a study had a GLP deviation, acknowledge it and discuss the impact. If the species relevance for a biologic is less than ideal, explain the limitations. FDA reviewers appreciate transparency. They do not appreciate discovering gaps that you tried to obscure.

Where Module 2.4 goes wrong

Length problems. More than 30 pages means you're duplicating Module 2.6. Less than 10 means you're not integrating. The sweet spot is 15-25 pages for a standard small molecule IND. The dose justification section alone should be 2-3 pages — if yours fits in a paragraph, you're not showing enough work.

Findings without interpretation. This is the big one, and it's where I spend most of my review time. "ALT was elevated 3x at the high dose" is a finding. It tells me nothing about risk. "ALT elevation at the high dose (exposure margin 50x over projected clinical exposure) suggests hepatotoxic potential at supratherapeutic exposures; this finding will be monitored clinically via liver function tests at each study visit" — that's an interpretation. FDA wants the second version. They want to know you've thought about what the finding means for patients, not just that you noticed it.

There's a related failure mode that I find almost more troubling: cross-species inconsistencies that nobody addresses. Rats show hepatotoxicity at 300 mg/kg, dogs show nothing at any dose. Why? Metabolic differences? Species-specific sensitivity? Exposure differences? Maybe the rats had 3x higher AUC at the same mg/kg dose and it's purely an exposure-driven effect. That's a defensible explanation — but you have to make it. Leaving the discrepancy unaddressed is an invitation for the reviewer to generate their own hypothesis, which is never what you want.

No reference to the pre-IND meeting. If you had a pre-IND meeting with FDA, Module 2.4 should close the loop — reference FDA's feedback and describe how each recommendation was addressed. The same reviewer who wrote the pre-IND response may be reviewing your IND. They'll notice if their advice was ignored. Actually, tangent: I've heard from two regulatory affairs people that some reviewers ctrl+F their own pre-IND recommendations in the Module 2.4 text. Whether that's true or apocryphal, writing as if it's true seems like good practice.

A practical workflow

  1. Draft Module 2.4 in parallel with Module 4. Don't wait until all study reports are final. Start the framework — testing strategy, species rationale, pharmacology summary — while studies are still in progress.

  2. Write the dose justification first. This forces you to identify the NOAEL, calculate the HED, and determine whether your safety margin is adequate. If the margin is thin, you want to know that before you finalize your clinical starting dose, not after.

  3. Have a regulatory affairs person review it. The nonclinical scientist writes the content. The regulatory affairs person checks that the structure, cross-references, and regulatory framing are correct. Module 2.4 is a regulatory document with scientific content, not a scientific document in a regulatory wrapper.

  4. Read it from the reviewer's perspective. After a draft is complete, read it as if you've never seen the data before. Can you follow the narrative? Do you understand the safety profile? Could you explain the dose justification to a colleague? If not, revise.

Write Module 2.4 well and the rest of your nonclinical section reads easier. Write it poorly and every study report in Module 4 gets extra scrutiny.


Related reading:

According to ICH M4S(R2), Module 2.4 is one of only two documents (along with Module 2.5, the Clinical Overview) that FDA reviewers are expected to read in full before diving into the detailed study reports. Write it well and everything else reads easier. Write it poorly and every report in Module 4 gets extra scrutiny.

Check your studies against 1,054 rules

Upload your preclinical reports. Get a compliance score in 3 minutes.

Try Regfo free