eSTAR Additional Information Response Playbook: How to Answer FDA Deficiency Letters Inside the eSTAR Workflow

What This Article Covers

This article is a focused playbook for responding to FDA Additional Information (AI) requests when your 510(k) or De Novo submission was filed using eSTAR. It covers the AI response timeline, how to structure your response package, the mandatory response table format, file naming conventions, section mapping between deficiencies and eSTAR sections, and the most common failure modes that cause responses to be rejected or deemed insufficient.

This article covers:

• The 510(k) and De Novo review timeline and where AI requests fit
• The difference between RTA holds, technical screening deficiencies, and substantive AI requests
• How to decode FDA deficiencies into their four required components
• The exact structure and format of an AI response package for eSTAR submissions
• Response table templates with worked examples
• File naming, version control, and attachment management
• Section-by-section mapping of deficiency topics to eSTAR sections
• Pre-response planning checklists and RACI assignments
• Sample response language for common scenarios

This article does NOT cover:

• How to prepare an eSTAR submission from scratch (see the eSTAR submission guide)
• General 510(k) or De Novo submission strategy (see the 510(k) submission guide)
• How to select a predicate device or establish substantial equivalence
• Post-market requirements, registration and listing, or UDI compliance
• PMA supplement responses (different process)

AI Request Context in the 510(k)/De Novo Review Timeline

Understanding where the AI request falls in the review timeline is essential. The FDA follows a structured review process with defined milestones. The AI request is not a random event — it is a predictable outcome of substantive review, and the clock starts ticking the moment you receive it.

510(k) Review Timeline

De Novo Review Timeline

The De Novo process follows the same 180-day AI response window. However, there is a critical difference: if you do not respond within 180 calendar days, the De Novo request is considered automatically withdrawn. There is no grace period, no automatic extension, and no appeal of a withdrawal due to missed deadline. You would need to start a new De Novo submission from the beginning.

Since October 1, 2025, all De Novo requests must be submitted via eSTAR, so the AI response process described in this playbook applies equally to De Novo submissions.

Key Numbers to Remember

• 180 calendar days: The hard deadline for responding to an AI request. This is not business days. Weekends and federal holidays count. Mark the exact date on your calendar the day you receive the AI letter.
• 10 calendar days: The window during which the FDA offers a teleconference to discuss the AI letter. Take advantage of this — it is the fastest way to clarify ambiguities before investing weeks of work in your response.
• ~146 calendar days: The real-world average total review time for 510(k) submissions in 2025 (per FDA MDUFA performance data), which means many submissions go through at least one AI cycle before clearance.

RTA Hold vs AI Request vs Technical Screening Deficiency — Key Differences

These three types of FDA communications are frequently confused, but they have different causes, different response requirements, and different implications for your timeline.

Important Note on eSTAR Technical Screening

eSTAR submissions do not undergo the traditional Refuse to Accept (RTA) review. Instead, they go through technical screening, which is an automated process. The FDA checks that the eSTAR file is not corrupted, passes virus scanning, and has all required fields completed (the completeness banner in eSTAR must show green). If the eSTAR fails technical screening, the FDA places the submission on hold and notifies the submitter of the specific deficiencies.

Traditional RTA review, which uses the RTA checklist (a 52-item checklist for completeness), applies to non-eSTAR submissions. Since all 510(k) and De Novo submissions must now use eSTAR, the RTA checklist is no longer the gatekeeping mechanism — technical screening is.

FDA Deficiency Content Requirements

Per the FDA guidance document "Developing and Responding to Deficiencies in Accordance with the Least Burdensome Provisions" (issued September 2023, updated 2024), each deficiency in an AI letter must contain four specific components. Understanding this structure helps you decode what the FDA is actually asking for.

The Four Required Components of a Deficiency

1. What was submitted: A statement identifying the specific information or data in the submission that the FDA reviewed
2. Identification of the issue: A clear description of the specific concern, gap, or inadequacy the reviewer identified
3. Statement of basis: The regulatory, scientific, or standards-based reason why the submitted information is insufficient
4. Explicit request: A specific, actionable statement of what additional information is needed to resolve the deficiency

Example: Decoding a Deficiency

Consider this hypothetical deficiency from an AI letter:

"The submission includes a device description in Section 4 of the eSTAR that describes the device as a ' handheld, battery-powered surgical instrument for soft tissue cutting.' However, the description does not include the device dimensions, material composition of the blade, or the operating principle (e.g., ultrasonic, mechanical oscillation). Under 21 CFR 807.92(a)(3), the device description must be sufficient to understand the device's design and operation. Please provide a complete device description including device dimensions, material composition of patient-contacting components, and a description of the operating principle with accompanying diagrams."

Breaking this into four components:

When you read each deficiency through this lens, you can identify exactly what data the FDA needs. If any of the four components are unclear in a deficiency, that is a strong reason to request a teleconference within the 10-day window.

AI Response Package Structure for eSTAR Submissions

The AI response for an eSTAR submission is not a set of separate documents emailed to the FDA. The response must be incorporated inside the eSTAR file itself. This is a fundamental difference from the pre-eSTAR era, where you could submit standalone PDFs as your response.

Required Components of the Response Package

1. Updated eSTAR file — The complete eSTAR with all AI responses incorporated directly into the relevant sections. To convert your original submission into an AI response, open the original eSTAR file and on page 2, change the "Application/Submission Type" from "New Application/Submission" to "Additional Information" and enter the assigned submission number (e.g., K###### or DEN#####). This activates the "Additional Information Response" section near the end of the eSTAR, which provides structured text fields for entering each deficiency and your response.
2. Cover letter — A standalone document (attached to the eSTAR) that serves as the response roadmap. It should identify the submission (K-number or DEN-number), list each deficiency being addressed, reference the response table, and provide a high-level summary of changes.
3. Response table — A structured table (embedded in the cover letter or as a separate attachment) that maps each FDA deficiency to the specific location in the eSTAR where the response can be found.
4. Updated attachments — Any supporting documents that were revised in response to deficiencies (test reports, labeling, risk analysis files, etc.), re-attached to the relevant eSTAR questions with proper version control.

What the Response Package Is NOT

• Not a set of standalone PDF responses separate from the eSTAR
• Not an email with attachments (the FDA will not accept it)
• Not an eCopy submission (eSTAR submissions must be responded to via eSTAR)
• Not a new 510(k) or De Novo submission (you are updating the existing one)

Response Table Format (Mandatory)

The response table is the most critical element of your AI response package. It provides traceability between each FDA deficiency and your response, and it allows the reviewer to quickly locate the information without hunting through the entire eSTAR.

Response Table Template

Illustrative Example

Response Table Best Practices

• Restate the full deficiency text verbatim. Do not paraphrase. The reviewer needs to see the exact deficiency they wrote.
• Number deficiencies exactly as FDA numbered them. If the AI letter numbers deficiencies 1 through 7, your table should have rows 1 through 7 in the same order.
• Be specific about location. "Updated in eSTAR" is not sufficient. Tell the reviewer exactly which section, which question, and which attachment to look at.
• Address every deficiency. If the FDA issued 12 deficiencies, your table must have 12 rows. A partial response is treated as an incomplete response.
• If a deficiency has sub-parts (a, b, c), address each sub-part. Use sub-rows or nested formatting.

File Naming and Version Control

FDA reviewers deal with hundreds of submissions. Clear, consistent file naming makes their job easier and reduces the chance that your response is misinterpreted or that the wrong document is reviewed.

Naming Conventions

Follow these conventions for all attachments in your AI response:

Format: [DocumentType]_v[Version]_[Knumber].pdf

Examples:

• Device_Description_v2_K250001.pdf
• Risk_Analysis_Report_v2_K250001.pdf
• SW_Documentation_Package_v2_K250001.pdf
• Labeling_IFU_v2_K250001.pdf
• Biocompatibility_Assessment_v2_K250001.pdf

Version Control Rules

• Always increment the version number. If the original attachment was Test_Report_v1.pdf, the updated version is Test_Report_v2.pdf. Never overwrite the original.
• Do not delete original attachments from the eSTAR. FDA reviewers may need to compare the original and updated versions. Keep both in the attachment pane.
• Combine related documents. If the FDA requested multiple software documents, combine them into a single PDF with bookmarks and a table of contents rather than attaching 15 separate files. Reviewers navigate by bookmarks, not by scrolling through a disorganized attachment list.
• Remove all security and password protection from PDFs. The FDA's document management system cannot process encrypted files. This includes print restrictions, edit passwords, and certificate-based security.
• Keep attachment file sizes reasonable. Individual attachments should generally be under 100 MB. If a file is larger, consider splitting it into logical volumes and noting the split in the response table.
• Ensure bookmarks and hyperlinks work. If your PDF has internal bookmarks or cross-references, verify they function correctly after you merge, split, or update the document.

Section Mapping: AI Deficiency to eSTAR Section

One of the most common errors in AI responses is placing information in the wrong eSTAR section. The following table maps common deficiency topic areas to their corresponding eSTAR sections so you can update the correct location.

How to Update the Correct Section

When a deficiency identifies an issue with your risk analysis, do not respond by adding risk analysis content to Section 4 (Device Description). Instead:

1. Navigate to the specific eSTAR question in the correct section
2. Update the response field with the new or revised information
3. Replace the relevant attachment in that section's attachment pane
4. Reference the exact question number and attachment name in your response table

FDA reviewers use the eSTAR's structured navigation to jump directly to sections. If your response is in the wrong section, the reviewer may not find it, and the deficiency may be marked as unresolved.

Updated Attachments Strategy

Handling updated attachments requires care. The goal is to make it easy for the reviewer to understand what changed and where to find the new information.

Replace, Do Not Append

When updating an attachment:

1. Upload the new version to the relevant eSTAR question's attachment pane
2. Keep the original version in the attachment pane (do not delete it)
3. Clearly label both versions (e.g., Risk_Analysis_Report_v1_K250001.pdf and Risk_Analysis_Report_v2_K250001.pdf)

Tracked Changes and Clean Versions

For substantive text documents (risk analysis reports, test reports, clinical evaluations):

• Provide a tracked-changes version that highlights exactly what was added, modified, or removed in response to the deficiency. This is the document the reviewer will focus on.
• Provide a clean version that incorporates all changes and is ready for reference. This is the version the reviewer will cite if the submission is cleared.
• Name them clearly: Risk_Analysis_Report_v2_TrackedChanges_K250001.pdf and Risk_Analysis_Report_v2_Clean_K250001.pdf

Summarize Changes in the Response Table

For each updated attachment, include a brief summary of what changed in the Response Summary column of the response table. For example:

"Updated Risk Analysis Report (v2): Added three new risk entries for battery failure modes (Sections 5.3.1-5.3.3). Added mitigation measures including battery management system firmware v2.1 and low-voltage alert algorithm. Updated risk acceptability matrix to reflect new mitigations. No changes to existing risk entries 1-47."

This level of specificity tells the reviewer exactly where to look and what was changed, without requiring them to compare the entire document line by line.

When to Provide New vs. Updated Attachments

Pre-Response Planning Checklist

Before drafting a single word of your response, complete this checklist. Rushing into drafting without planning leads to incomplete responses, missed deadlines, and sometimes the need for a second AI cycle.

Immediate Actions (Days 1-5 After Receiving AI Letter)

• Read the entire AI letter end to end, twice. The first pass is to absorb the overall picture. The second pass is to annotate each deficiency individually.
• Classify each deficiency as major (requires new testing, new data, or significant additional analysis) or minor (requires clarification, reformatting, or minor additions).
• Identify which deficiencies require new testing or data collection versus which can be addressed with existing information, reanalysis, or clarification.
• List every FDA guidance document, recognized consensus standard, or regulation cited in the deficiencies. Download or locate each one. Confirm you are referencing the current version.
• Schedule the FDA teleconference (offered within 10 calendar days of the AI letter). Prepare a list of specific questions for each deficiency where the request is ambiguous or where you want to propose an alternative approach.
• Consider whether any deficiencies involve issues complex enough to warrant a Submission Issue Request (SIR) via the Q-Submission process. A SIR allows you to discuss a specific deficiency with the FDA review team and get feedback before submitting your formal response. This can be especially valuable when the deficiency requires a new test protocol or involves a novel technology where the "right" answer is not clear from existing guidance.

Planning Actions (Days 5-30)

• Assign ownership for each deficiency response (see RACI table below).
• Develop a project timeline working backward from the 180-day deadline. Build in at least 30 days of buffer for internal review, legal review, and quality review of the final response package.
• For deficiencies requiring new testing: confirm test lab availability, sample availability, and estimated turnaround time. Determine whether testing can realistically be completed within the 180-day window.
• For deficiencies where you plan to provide alternate information (not exactly what the FDA requested, but information you believe addresses the underlying concern): document the rationale and prepare a clear explanation of why the alternate approach is appropriate.

Quality Check (Days 150-180)

• Verify every deficiency in the AI letter has a corresponding row in the response table.
• Verify every response table row references the correct eSTAR section and attachment.
• Verify all updated attachments are properly named, versioned, and uploaded to the correct eSTAR section.
• Verify the eSTAR completeness banner shows green (all required fields completed).
• Have the response reviewed by someone who was not involved in drafting it — fresh eyes catch gaps that the author misses.
• Confirm no PDF attachments are password-protected or encrypted.
• Verify file sizes are within acceptable limits.
• Submit via the correct channel (CDRH Portal for eSTAR, not email).

Common Failure Modes and Remediation

Sample Response Language (Illustrative)

The following are examples of response language for common scenarios. Adapt these to your specific situation — do not copy them verbatim without tailoring the content.

Cover Letter Opening

Dear Reviewer,

[Company Name] is submitting this Additional Information response for [K-number or DEN-number],
[Device Trade Name], received by FDA on [original submission date]. This response addresses
all deficiencies identified in the FDA's Additional Information letter dated [AI letter date].

A response table is provided below mapping each deficiency to the updated eSTAR section and
supporting attachments. All responses have been incorporated directly into the updated eSTAR
file as required. Updated attachments are version-controlled and clearly labeled.

Individual Deficiency Response Structure

Deficiency [X]: [Full text of deficiency, restated verbatim]

Response:
[Provide a direct, specific answer to the deficiency. Start with what was done, then provide
the data or information.]

The [device description / risk analysis / test report / labeling] has been updated to address
this deficiency. Specifically:

1. [Specific change or addition #1]
2. [Specific change or addition #2]
3. [Specific change or addition #3]

The updated information is located in [eSTAR Section X, Question Y]. Supporting documentation
is provided in [Attachment Name, Version]. Please refer to [page numbers or section references]
within the attachment for the relevant data.

Summary of changes from the original submission:
- [Change 1]
- [Change 2]

When You Disagree with a Deficiency

Deficiency [X]: [Full text of deficiency]

Response:
[Company Name] respectfully provides the following information to address this deficiency.

While we understand the reviewer's concern regarding [topic], we believe the originally
submitted data is sufficient to demonstrate [safety / effectiveness / substantial equivalence]
based on the following rationale:

1. [Scientific or regulatory basis for your position]
2. [Reference to relevant FDA guidance or recognized standard that supports your approach]
3. [Supporting data from your original submission, with specific citations]

However, to further support our position and in the interest of resolving this deficiency
efficiently, we have also provided [additional information / clarifying analysis / supplementary
data] in [eSTAR Section, Attachment]. This supplemental information demonstrates [specific
conclusion].

We welcome the opportunity to discuss this further if additional clarification would be helpful.

When Providing Alternate Information

Deficiency [X]: [Full text of deficiency, which requested a specific test or analysis]

Response:
[Company Name] has evaluated this request. While the deficiency requests [specific test or
analysis requested by FDA], we propose an alternative approach that we believe addresses the
underlying regulatory concern in a manner consistent with the least burdensome provisions
(21 CFR 7(d) and 21 CFR 807.87(g)).

Specifically, instead of [requested approach], we have conducted [alternative approach], which
provides equivalent or greater assurance of [safety / effectiveness] for the following reasons:

1. [Scientific rationale for alternative approach]
2. [How the alternative addresses the same risk or concern]
3. [Reference to precedents, if any — e.g., other cleared devices using this approach]

The results of this alternative analysis are provided in [eSTAR Section, Attachment Name].

When New Testing Was Required

Deficiency [X]: [Full text of deficiency requesting additional testing]

Response:
[Company Name] conducted [specific test] to address this deficiency, in accordance with
[applicable standard, e.g., IEC 60601-1-2:2014+A1:2017, Edition 4.1] and the FDA guidance
"[applicable guidance document title]" issued [date].

Testing was performed at [test laboratory name], which holds [accreditation status, e.g.,
ISO 17025 accreditation, FDA ASCA recognition]. The full test report is provided in
[Attachment Name].

Key results summary:
- [Test parameter 1]: [Result] — [Pass/Fail per acceptance criteria]
- [Test parameter 2]: [Result] — [Pass/Fail per acceptance criteria]
- [Test parameter 3]: [Result] — [Pass/Fail per acceptance criteria]

All acceptance criteria were met. The complete test report, including test setup photographs,
raw data, and instrument calibration certificates, is provided in the attachment referenced
in the response table.

RACI Table for AI Response Process

Clear ownership is essential for a timely, complete response. The following RACI (Responsible, Accountable, Consulted, Informed) table assigns roles for the AI response process.

Final Considerations

The 180-Day Clock Is Inflexible

This bears repeating because it is the single most consequential fact about the AI response process. The FDA does not grant extensions for 510(k) or De Novo AI responses. If you are on day 179 and your testing is not complete, you face a binary choice: submit what you have (risking an incomplete response) or lose the submission. Plan accordingly and start working on testing-dependent deficiencies as early as possible.

Teleconference Is Undervalued

Many submitters skip the offered teleconference, assuming the AI letter is self-explanatory. In practice, the teleconference can resolve ambiguities, confirm whether the FDA will accept an alternative approach, and save weeks of work on a response that might otherwise miss the mark. The teleconference must be requested within 10 calendar days of the AI letter. There is no downside to requesting it.

Submission Issue Requests for Complex Deficiencies

For deficiencies that involve novel scientific questions, complex statistical analyses, or disagreements about the appropriate test method, consider using a Submission Issue Request (SIR) via the Q-Submission process (also submitted via PreSTAR since Version 2.0). A SIR allows you to propose a specific approach and get FDA feedback before committing to it in your formal response. The SIR process typically takes 60-90 days, so factor this into your 180-day timeline.

eSTAR Version Compatibility

Ensure your updated eSTAR file is in a version compatible with the FDA's current processing system. The current template is eSTAR v6.1 (February 2026). If your original submission was prepared in an earlier version, check whether the FDA has issued guidance about updating the template version for AI responses. In general, responses should be submitted in the same eSTAR version as the original submission unless the FDA directs otherwise.

Record Everything

Document every decision, every teleconference, every email exchange with the FDA, and every version of every attachment. If your submission is ultimately cleared, this documentation becomes part of your design history file. If it is not cleared, this documentation is essential for understanding what went wrong and how to fix it in a resubmission.

For more information on preparing your initial eSTAR submission, see the complete eSTAR submission guide. For details on FDA-recognized consensus standards that may be referenced in AI deficiencies, see the FDA recognized consensus standards guide.