Crafting an Investigator's Brochure that stands up to FDA review

The Investigator's Brochure is one of the most consequential documents in a clinical program. It is the document a clinical investigator opens to make a benefit-risk judgment before enrolling the first subject. It is the document IRBs and ethics committees rely on when reviewing study approval. And it is the reference document FDA uses to understand the program's benefit-risk profile across all completed and ongoing studies. The IB is read carefully — cover-to-cover, by multiple audiences — and it carries strategic weight in how the program is perceived.

This article walks the seven IB sections per ICH E6(R3) and 21 CFR 312.55, identifies what each section needs to do, and shows phrasing patterns that distinguish a strong section from a weak one. Examples below are pulled from the Vertex IB template — the same example text that ships with every Vertex license.

Why the IB matters more in early development

For first-IND and early-development programs, the IB does double duty. Beyond its safety-reference function, it is a positioning document. Sponsors choose what data to include, what to lead with, and how to frame benefit-risk in a way that shapes how the agency, IRBs, and investigators understand the program. What goes into the IB — and what does not — defines the program's regulatory narrative early on, when that narrative is most malleable.

For larger pharma running late-phase programs, the IB shifts from positioning toward reference. Multiple studies, multiple indications, and a deeper safety database mean the IB carries more historical content than strategic framing. But structural rigor still matters: a poorly organized late-phase IB makes the agency work harder to find what it needs across studies, and that friction shows up in review timelines.

The IB structure is the same whether the sponsor is a first-IND biotech or a global pharma. What changes is how the document is used strategically. The Vertex IB template is designed to work the same way regardless of program stage — the structure does the structural work, and the writer focuses on the program-specific judgments.

Section 1 — Summary

The Summary is approximately one to two pages and is the first thing both investigators and reviewers read. It frames everything that follows. The most common failure mode is hedging in the wrong direction — over-stating efficacy on weak data or under-stating safety on real signals.

Example: benefit-risk framing

The weak version uses promotional language ("impressive," "strong," "transformative") that signals the writer is selling the program rather than describing it. The strong version cites the study, gives the denominator, reports the response rate with a confidence interval, and characterizes the safety findings at a level of specificity a reviewer can map to the proposed trial. Reviewers prefer the second version regardless of how favorable the data are.

Section 2 — Introduction

The Introduction situates the product in its therapeutic context: disease background, current treatment landscape, unmet need, and the rationale for the development program. This section is short — typically one to three pages — and works best when written for a clinical investigator who knows the disease but does not know the asset.

Common failure: writing the Introduction as a marketing-style market-opportunity argument. The IB is not a fundraising deck. The Introduction should describe why this molecule is being developed in this indication, with concrete reference to the standard of care and the specific patient population the program is targeting.

Section 3 — Physical, chemical, and pharmaceutical properties and formulation

Section 3 is concise and factual: chemistry, formulation, dose strengths available, storage conditions, reconstitution if applicable. The investigator-facing piece is "what do I actually administer and how do I handle it." The reviewer-facing piece is "is the formulation appropriate for the proposed trial."

The Vertex template ships Section 3 with placeholder text for both small molecules and biologics, and with formulation tables structured to match what CMC will provide. Most writers do not draft Section 3 from scratch — they consume content from the CMC team — so the template's job is making integration mechanical.

Section 4 — Nonclinical studies

Section 4 covers pharmacology (in vitro and in vivo), pharmacokinetics and metabolism, and toxicology. This is where reviewers look for safety findings that should inform the proposed clinical trial — target organ toxicity, NOAEL-derived starting dose justification, species selection rationale, and any genotoxicity or reproductive-toxicity findings that flow into the eligibility criteria.

Example: nonclinical safety summary

The strong version names the study, identifies the NOAEL, links the human starting dose to the safety margin, and characterizes target-organ findings with reversibility — all things a reviewer needs to assess the proposed clinical dose.

Section 5 — Effects in humans

Section 5 integrates clinical pharmacology, safety, and efficacy across all completed and ongoing human studies. For first-in-human programs this section is short. For programs with multiple completed trials it can run 30 to 60 pages. The structural challenge is summarizing across studies without losing study-level traceability — a reviewer reading Section 5 should be able to identify which finding came from which study without going to Section 6 or the appendices.

Vertex templates handle this by giving each completed study its own subsection within Section 5, with an integrated summary at the start. The integrated summary uses pooled data where appropriate (PK parameters, common AEs) and study-specific data where pooling would mislead (efficacy by indication, dose-finding observations).

Section 6 — Summary of data and guidance for the investigator

This is the section investigators actually use during a trial — the page they reference when a subject has an event and they need to assess relatedness, or when they are deciding whether to continue dosing through a finding. Practical guidance, not narrative summary.

The Vertex template structures Section 6 around four investigator-facing questions: What should I monitor? What dose adjustments are appropriate for which findings? When should I withhold dose? When should I report to the sponsor on an expedited timeline? Each question has draftable example text in current FDA-acceptable phrasing.

Section 7 — Reference Safety Information

The RSI is the section that drives SUSAR (Suspected Unexpected Serious Adverse Reaction) assessments throughout the trial. Whether an event is "expected" or "unexpected" — and therefore whether it triggers an expedited report — is determined by what is and is not listed in the RSI. RSI structure is therefore both a safety-reporting issue and a regulatory-burden issue.

The RSI requires unusual care because two opposing failure modes both cause problems. Listing too few events makes more events "unexpected" and increases SUSAR reporting volume; this looks like the trial is generating safety signals when really the RSI is just under-specified. Listing too many events — particularly low-frequency events at low confidence — risks claiming a known safety profile that is not actually established.

Example: RSI structure

The weak version uses ambiguous catch-all phrasing ("various," "other," "may occur") that does not establish a clear expectedness baseline. Pharmacovigilance staff cannot make consistent expectedness assessments from it. The strong version names each expected event with frequency thresholds and explicitly defines what is unexpected.

What strong IBs do well

Across well-received IBs — for first-IND programs and late-phase programs alike — the same patterns show up:

1. The Summary calibrates language to the data. Neither over-claims on early efficacy nor under-states real safety findings. Promotional adjectives are absent because they signal to readers that the document is selling rather than describing.
2. Dose units are consistent across sections. One unit (mg/kg, mg/m², or flat-dose mg) is chosen and used throughout, with a single dose-conversion table where it's needed. Cross-section reconciliation isn't asked of the reader.
3. RSI is structurally tied to Section 5. When new AE data is added to Section 5 from an ongoing study, Section 7 RSI is updated in the same revision. The IB carries one consistent expectedness baseline across the whole document.
4. Section 6 is written as actionable investigator guidance. Investigators open Section 6 during a clinical event and need a clear decision path: monitor, dose-modify, withhold, or report. Strong Section 6s answer those questions directly rather than re-summarizing data the investigator just read.
5. The strategic framing matches the program stage. Early-development IBs lean into positioning — what's being investigated, what's known, what's deliberately not yet claimed. Late-phase IBs lean into reference structure — finding the right safety data across multiple studies should not require effort.

How the Vertex IB template adapts to your program

The Vertex IB template ships with example text variants for first-in-human, dose-expansion, and pivotal stages — same structure across all three, different strategic framing per stage. The dose-units table is defined once and propagates into every section. The RSI is structurally tied to Section 5 so updates to one prompt updates to the other. Section 6 is written as four investigator-facing questions with concrete answer language.

The structure is the same whether you're filing your first IND or your fifteenth. The Vertex IB template works regardless of where you are in development.

The template also includes the Vertex Word ribbon and VBA macros for the formatting cleanup that eats hours during IB updates: bulk caption renumbering when sections move, comment hygiene passes that remove resolved-comment artifacts, and tracked-change displays that hold up across IB version transitions.