FDA Information Request: How to Respond Effectively
An FDA information request (IR) is a formal communication during NDA or BLA review asking the sponsor to provide additional data or clarification. The sponsor's response is classified as either a minor amendment (does not affect the PDUFA date) or a major amendment (extends the PDUFA goal date by 3 months). Responding promptly, accurately, and in the correct eCTD format is essential to keeping the review on track.
Key Takeaways
Key Takeaways
- A response classified as a major amendment extends the PDUFA goal date by 3 months; minor amendments do not affect the timeline.
- IRs are routine during most NDA/BLA reviews and indicate active review team engagement, not necessarily a negative signal.
- Failure to respond to an IR will likely result in a Complete Response Letter citing the unresolved issue as a deficiency.
- The classification of your response as minor or major depends on the content submitted, not the speed of submission.
- During the review of a New Drug Application (NDA) or Biologics License Application (BLA), FDA review divisions routinely issue information requests to sponsors when the submitted data are insufficient, unclear, or require supplementation. An IR is not a rejection or a negative signal per se, but the sponsor's response directly affects the review timeline and can determine whether the PDUFA goal date holds.
- Understanding the mechanics of information requests, how they differ from discipline review letters, and how responses are classified as amendments is essential knowledge for any regulatory affairs professional managing an application through FDA review.
- In this guide, you will learn:
- What an FDA information request is and how it differs from a discipline review letter
- How IR responses are classified as minor or major amendments
- The impact of amendments on the PDUFA goal date and review clock
- Best practices for responding to information requests
- How to request and prepare for an IR-related meeting with FDA
- ---
What Is an FDA Information Request?
An information request (IR) is a formal written communication from an FDA review division to a sponsor during the review of a pending marketing application (NDA, BLA, or supplement), asking for additional data, analyses, or clarification needed to complete the review.
Information requests are a standard part of FDA's review process. They arise when the review team identifies gaps in the submission that prevent a complete assessment. IRs can come from any review discipline: clinical, nonclinical, CMC, biopharmaceutics, statistics, or clinical pharmacology.
Key characteristics of information requests:
- Issued during the active review cycle (between filing and PDUFA date)
- Directed to the sponsor by the review division via a formal letter
- Request specific data, analyses, or clarifications
- The sponsor's response is submitted as an amendment to the application
- The amendment classification (minor or major) determines impact on the PDUFA date
IR vs Discipline Review Letter: Key Differences
| Attribute | Information Request (IR) | Discipline Review Letter (DRL) |
|---|---|---|
| Source | Review division (through project manager) | Individual review discipline (see DRL guide) |
| Purpose | Request additional data or clarification | Communicate review status, preliminary findings, or concerns |
| Response expected | Yes, formal amendment required | Varies; may or may not require a formal response |
| PDUFA impact | Response may trigger major amendment (3-month extension) | Generally does not directly affect PDUFA date |
| Formality | Formal letter with specific data requests | Formal communication but scope varies |
| Typical timing | Any point during review cycle | Often mid-cycle or during discipline-specific review milestones |
Not every communication from FDA during review is an information request. Discipline review letters, informal questions via teleconference, and mid-cycle meeting discussions may raise issues without constituting a formal IR. The distinction matters because only responses to formal IRs trigger amendment classification.
Response Timelines and the Review Clock
How the Review Clock Works
The PDUFA review clock starts on the filing date (Day 0 of the review cycle) and runs continuously toward the PDUFA goal date. Under PDUFA VII commitments, the standard review timeline is 10 months from the date of submission (which translates to approximately 8 months from the filing date, since filing review takes approximately 60 days). Priority review applications have a 6-month timeline from submission.
The review clock is not literally a clock that FDA pauses and restarts. Instead, the PDUFA date may be extended when the sponsor submits a major amendment. There is no mechanism for FDA to unilaterally "stop" the clock absent a major amendment from the sponsor.
Amendment Classification
When a sponsor responds to an information request, the response constitutes an amendment to the application. FDA classifies this amendment as either minor or major.
| Classification | Criteria | PDUFA Impact |
|---|---|---|
| Minor amendment | Response contains limited information that does not require significant additional review time | No change to PDUFA goal date |
| Major amendment | Response contains substantial new data, analyses, or information that requires significant additional review time | PDUFA goal date extended by 3 months from the date of the major amendment |
What Constitutes a Major Amendment?
Per FDA's PDUFA commitments and the guidance "PDUFA Reauthorization Performance Goals and Procedures" (PDUFA VII), a major amendment is a response that:
- Includes substantial new clinical data (e.g., results from new or ongoing studies)
- Introduces significant new safety information
- Includes major CMC changes (new manufacturing site, process changes, new formulation)
- Requires re-review by multiple disciplines
- Is submitted by the sponsor within the last 3 months of the review cycle and contains more than minor clarifications
The timing of your response matters significantly. A response that might be classified as a minor amendment early in the review cycle could be classified as major if submitted in the final 3 months, because FDA needs adequate time to evaluate the new information before the PDUFA date. If you anticipate a late-cycle response, discuss classification prospectively with the review division.
PDUFA Date Extension Mechanics
When a major amendment extends the PDUFA date:
| Scenario | Original PDUFA Date | Major Amendment Date | New PDUFA Date |
|---|---|---|---|
| Standard review | Month 10 from submission | Month 7 | Month 10 (3 months from amendment) |
| Standard review | Month 10 from submission | Month 9 | Month 12 (3 months from amendment) |
| Priority review | Month 6 from submission | Month 4 | Month 7 (3 months from amendment) |
The 3-month extension runs from the date FDA receives the major amendment, not from the original PDUFA date.
Content Expectations for IR Responses
What FDA Expects
An effective IR response provides:
- Direct answers to each question posed in the IR, organized in the same order as the IR
- Supporting data in the format requested (tables, listings, datasets, analyses)
- Cross-references to specific eCTD locations where supporting documents are placed
- Context explaining how the response addresses FDA's underlying concern, not just the surface question
eCTD Submission Format
IR responses are submitted as amendments to the original application in eCTD format:
| Element | Requirement |
|---|---|
| Sequence | New sequence number continuing from the last submission |
| Cover letter | Reference the IR date and number; list each question with the corresponding response location |
| Module placement | Place responses in the same eCTD module as the original content being supplemented |
| Datasets | If requested, submit in CDISC format (SDTM/ADaM) per FDA's Data Standards Catalog |
| Operation attributes | Use "new" for supplemental documents, "replace" for updated documents |
Response Organization
| IR Discipline | Typical Data Requested | Response Module |
|---|---|---|
| Clinical | Subgroup analyses, additional efficacy endpoints, safety analyses, patient narratives | Module 5 (Clinical Study Reports), Module 2.7 (Clinical Summary) |
| CMC | Process validation data, stability results, specifications justification, comparability data | Module 3 (Quality) |
| Nonclinical | Additional toxicology data, carcinogenicity study results, pharmacology studies | Module 4 (Nonclinical Study Reports), Module 2.6 (Nonclinical Written Summary) |
| Statistics | Re-analyses with different methods, sensitivity analyses, missing data handling | Module 5 (integrated into clinical study reports) |
| Clinical Pharmacology | PK/PD analyses, drug interaction studies, special population PK, exposure-response | Module 5, Module 2.7.2 |
| Biopharmaceutics | Dissolution data, bioequivalence study results, in vitro-in vivo correlation | Module 5, Module 3 |
How IRs Affect the PDUFA Date: Practical Scenarios
Scenario 1: Minor Amendment, No PDUFA Impact
FDA issues an IR in Month 4 requesting clarification on a statistical analysis method. The sponsor responds in Month 5 with a 10-page clarification document and supporting tables. FDA classifies this as a minor amendment. The PDUFA date does not change.
Scenario 2: Major Amendment, PDUFA Extension
FDA issues an IR in Month 6 requesting additional clinical subgroup analyses and a new safety evaluation. The sponsor responds in Month 8 with 200+ pages of new analyses and two supplemental datasets. FDA classifies this as a major amendment. The PDUFA date extends by 3 months from the date of the amendment.
Scenario 3: Late-Cycle IR Creates Scheduling Risk
FDA issues an IR in Month 8 of a 10-month review. Even if the sponsor responds promptly, the response arrives late enough that FDA may classify it as a major amendment regardless of content volume, because the review team needs adequate time to evaluate the response before the PDUFA date.
If you receive an IR late in the review cycle, contact the review division immediately to discuss the expected scope and classification of your response. In some cases, FDA may agree to handle a focused response as a minor amendment if the scope is narrow enough.
Requesting an IR Meeting with FDA
When an IR is ambiguous, requests data the sponsor believes it has already provided, or raises concerns the sponsor disagrees with, requesting a meeting can prevent wasted effort.
Meeting Types for IR Discussions
| Meeting Type | When Appropriate | Scheduling Timeline |
|---|---|---|
| Teleconference (informal) | Quick clarification on specific IR questions | Days (arranged through project manager) |
| Type B meeting | Substantive disagreement about what data are needed, or if the IR raises issues that affect the development program | 60 days from request |
| Type A meeting | Only if the IR effectively stalls the entire program (rare during active review) | 30 days from request |
Best Practices for IR Meetings
- Prepare specific questions that map to each IR item requiring clarification
- Propose your interpretation of what FDA is asking, so the review team can confirm or correct
- Bring data to the meeting that demonstrates you have already addressed the concern, if applicable
- Document agreements in meeting minutes and reference them in your IR response
Best Practices for IR Response
Do
| Practice | Rationale |
|---|---|
| Respond within the timeline discussed with the review division | Avoids PDUFA date impact; demonstrates responsiveness |
| Address every item in the IR, even if the answer is "data not available" | Unanswered items may generate follow-up IRs or CRL deficiencies |
| Provide a cross-reference table mapping each IR item to the response location | Facilitates efficient FDA review |
| Run eCTD validation on the amendment before submission | Technical failures delay the response reaching the review team |
| Coordinate with the review division on response timing | Allows planning to minimize PDUFA impact |
Do Not
| Practice | Risk |
|---|---|
| Submit unsolicited major new data alongside the IR response | May trigger major amendment classification even if the IR response itself is minor |
| Ignore the IR's implied concerns and respond only to the literal text | FDA may issue a follow-up IR or cite the issue in a CRL |
| Wait until the last possible moment to respond | Late responses are more likely to be classified as major amendments |
| Submit IR responses piecemeal across multiple amendments | Creates confusion and may trigger multiple amendment classifications |
| Assume informal FDA communications substitute for a formal IR response | Only formal amendments satisfy the IR requirement |
Multiple Information Requests During Review
It is not uncommon for FDA to issue multiple IRs during a single review cycle, sometimes from different review disciplines. Each IR requires a separate response, and each response is independently classified as a minor or major amendment.
Managing Multiple IRs
| Strategy | Implementation |
|---|---|
| Consolidated response | If multiple IRs are received within a short window, discuss with the review division whether a single consolidated response is acceptable |
| Staggered responses | If IRs come from different disciplines with different timelines, respond to each as it is ready rather than holding all for a single submission |
| Response tracker | Maintain an internal tracker mapping each IR question to its response status, responsible team, and submission timeline |
| Classification awareness | Each response is independently assessed for amendment classification; consolidating responses does not automatically make them a single amendment |
Key Regulatory References
| Document | Relevance |
|---|---|
| PDUFA VII Commitment Letter (2022) | Review timeline commitments, major amendment definitions |
| FDA Guidance: "Formal Meetings Between the FDA and Sponsors or Applicants of PDUFA Products" (Rev. 2017) | Meeting request procedures for IR-related discussions |
| 21 CFR 314.50 | NDA content and format requirements (including amendments) |
| 21 CFR 601.2 | BLA content and format requirements (including amendments) |
| FDA Guidance: "Providing Regulatory Submissions in Electronic Format — Certain Human Pharmaceutical Product Applications and Related Submissions Using the eCTD Specifications" (Rev. 2023) | eCTD format requirements for amendments |
| FDA Technical Specifications for eCTD | Validation criteria for amendment submissions |
Can FDA issue an information request after the PDUFA date?
No. If FDA has not completed its review by the PDUFA date, it issues an action (approval, CRL, or in rare cases, requests a 3-month extension if a major amendment was recently received). Information requests are tools used during the active review cycle.
Is an information request a bad sign?
Not necessarily. IRs are routine during most NDA and BLA reviews. They indicate that the review team is actively evaluating the application and needs clarification. A review without any IRs is uncommon for complex applications.
Can I refuse to respond to an information request?
You can, but the consequences are significant. If FDA needs the requested information to complete its review, failure to provide it will likely result in a CRL citing the unresolved issue as a deficiency.
How many information requests are typical during a review?
This varies by application complexity. Simple applications may receive one or two IRs. Complex applications with novel endpoints, multiple indications, or challenging CMC profiles may receive five or more IRs across different disciplines.
Does responding to an IR guarantee the PDUFA date will not change?
No. Even a prompt response can be classified as a major amendment if it contains substantial new information. The classification depends on the content of the response, not the speed of submission.