How to Draft an Effective Pre-Meeting Briefing Document

Published on 21/12/2025

Creating a Strategic Briefing Document for FDA Pre-Submission Meetings

Table of Contents

Importance of the Briefing Document in FDA Interactions

The briefing document is a foundational element in preparing for formal meetings with the U.S. Food and Drug Administration (FDA), including Type A, B, or C interactions. It is the first opportunity to present your development program’s context, raise critical questions, and align expectations with regulators. A well-crafted document can significantly influence the quality of feedback you receive—and ultimately the success of your regulatory submission.

Whether you’re requesting a pre-IND, end-of-Phase 2, or pre-NDA meeting, the briefing package demonstrates your team’s scientific and regulatory readiness. It must strike the right balance between being informative and concise while addressing all necessary data and questions to support efficient FDA discussion.

Timeline and Submission Logistics

According to FDA guidance, the briefing document should be submitted:

At least 30 days prior to the scheduled meeting date for Type B meetings
Alongside

the meeting request for Type A and some Type C meetings

The document must be submitted in eCTD format through the Electronic Submission Gateway (ESG). Failure to follow format guidelines could result in rejection or delay of your meeting request. Sponsors should check current eCTD validation rules before submitting.

Essential Sections of a Pre-Meeting Briefing Document

A typical briefing document includes the following core components:

Cover Letter: Includes the meeting type, product name, IND/NDA number (if available), and purpose of the meeting.
Table of Contents: Hyperlinked TOC is encouraged in the PDF version.
Product Background: Non-proprietary name, dosage form, route of administration, intended indication, and summary of mechanism of action.
Development History: Summary of nonclinical studies, completed clinical trials, and regulatory interactions to date.
Proposed Clinical Plan: Key trial designs, endpoints, statistical plans, and comparator arms (if applicable).
CMC Overview: Manufacturing strategy, control strategies, formulation, and stability plans.
Questions for FDA: Clear, structured queries grouped by functional area (clinical, CMC, regulatory, nonclinical).
Appendices: Protocol synopsis, draft labeling (for pre-NDA), or critical datasets.

Continue with Formatting Tips, Case Study, and Real-World Challenges

Formatting and Presentation Best Practices

The FDA recommends concise, focused documents not exceeding 100 pages. Key formatting best practices include:

Font and Spacing: Use 11- or 12-point font with at least 1.0 spacing.
Hyperlinking: Include bookmarks for navigation and hyperlinks in the TOC.
Tables and Figures: Use summary tables and visual aids (PK curves, timelines) for clarity.
File Naming: Follow eCTD naming conventions, e.g., briefing-document-clinical.pdf.

FDA reviewers are often working across multiple meetings each week. Making your content accessible and easy to interpret increases the likelihood of comprehensive feedback.

Case Study: Pre-IND Briefing for an Oral Antidiabetic Drug

A small biotech firm developing a novel GLP-1 receptor agonist requested a Type B pre-IND meeting. Their briefing document highlighted:

Animal toxicology data from both rodent and non-rodent species
Preliminary formulation challenges with oral capsule design
Draft clinical protocol for a first-in-human (FIH) single ascending dose study
Three core questions related to safety margins, starting dose selection, and food effect assessments

The clear structuring of clinical and CMC questions allowed the FDA to provide focused, actionable feedback. Within six months, the IND was successfully submitted and cleared.

Common Mistakes to Avoid

Overloading with Irrelevant Data: Limit raw study reports unless directly relevant to the meeting questions.
Poor Question Framing: Avoid binary or yes/no questions. Instead, ask FDA for “recommendation” or “agreement” on plans.
Lack of Context: Always provide a summary of your rationale before posing questions.
Last-Minute Submissions: Submit at least five business days before the 30-day deadline to avoid technical issues with ESG.

Collaborating Internally for Document Development

Creating the briefing package is a cross-functional effort involving Regulatory Affairs, Clinical Operations, Biostatistics, CMC, and Nonclinical teams. Use shared templates and collaborative review cycles to finalize the document.

Regulatory leads should maintain a central repository of historical FDA questions and feedback to inform drafting.

FDA Feedback Mechanisms Based on the Briefing Document

Depending on the meeting format, the FDA may:

Provide written responses only (WRO)
Hold a teleconference or in-person meeting
Issue minutes summarizing answers to each submitted question

If the FDA declines to address a question due to insufficient data or clarity, that feedback helps guide your next steps in data collection or regulatory engagement.

External Tools and Resources

To view examples of successful INDs and pre-submission strategies, visit the EU Clinical Trials Register for public study filings and regulatory summaries. These references can inform the structure and content of your own briefing documents.

Conclusion: Set the Stage for Regulatory Success

A well-drafted FDA pre-meeting briefing document is more than a formality—it is a strategic tool. When written clearly, submitted timely, and supported with strong rationale, it enhances regulatory interactions and strengthens the success of your IND, NDA, or BLA submissions.