FDA Deficiency Letters: How to Respond Strategically and Keep Your Review Moving Forward

May 17, 2026

Key Takeaways

• An FDA deficiency letter during a 510(k) or PMA review is not a rejection, but a disorganized or non-targeted response can generate a second round of requests, adding months to your timeline.

• A well-constructed response closes each deficiency completely, is organized so FDA can process it without redigging through your submission, and does not introduce new problems by volunteering unanswered questions.

Getting a deficiency letter from FDA, whether an Additional Information (AI) request during a 510(k) review or a major deficiency letter during a Pre-Market Approval (PMA) substantive review, is one of the highest-stakes moments in a premarket submission. The instinct is to respond quickly, address every point, and get the review moving again.

That instinct, without discipline and strategy, is how companies end up in additional rounds of requests.

Speed is not the priority. Completeness and clarity are.

What Type of Deficiency You're Dealing With Changes Your Response Strategy

Not all FDA requests work the same way, and understanding the mechanics matters.

For 510(k) submissions, FDA may issue an Additional Information request at any point during the substantive review period. Per FDA's guidance The 510(k) Program: Evaluating Substantial Equivalence in Premarket Notifications [510(k)], the 90-day review clock pauses when an AI request is issued and restarts when FDA receives your response. In practice, FDA typically requires a response in 180 days. The practical implication here is significant: the total review timeline only moves forward when your response is substantive enough to satisfy FDA's concern.

For PMA submissions, FDA issues major and minor deficiency letters during the 180-day review period that begins after filing. Major deficiency letters address substantive scientific or regulatory gaps. Minor deficiency letters address documentation or completeness issues. Unresolved major deficiencies significantly increase the likelihood of a "not approvable" outcome at the end of the 180-day period.

An important caveat: the distinction between a "minor" and "major" deficiency is not always as clear as it sounds. What reads as a formatting request often reflects an underlying concern about the completeness or reliability of your underlying data.

Read the Letter Before You Start Drafting

The most valuable thing you can do immediately after receiving a deficiency letter is read it carefully, not to begin writing answers, but to understand what FDA is actually asking and the relatedness of the deficiencies to each other.

Deficiencies typically fall into one of three categories:

• Presentation deficiencies: The information exists in your submission, but it was not organized or labeled in a way FDA could easily locate and evaluate. These are relatively fast to resolve — the data is there, it just needs to be surfaced and cross-referenced clearly.

• Data gaps: FDA needs information that was not included in the submission. These require going back to your technical files, your testing team, or in some cases running additional analyses.

• Regulatory interpretation disagreements: FDA disagrees with your analysis, your predicate selection, your substantial equivalence argument, or your clinical evidence rationale. These require the most strategic care.

Categorize every deficiency before you write anything. The third category is where founders most often go wrong — they answer what FDA literally asked without addressing the underlying regulatory disagreement, the response checks a box without resolving the issue, and FDA asks again in sharper terms next round.

When to Call FDA Before You Respond

For deficiencies that reflect a genuine interpretation disagreement, or for any deficiency where the scope of what FDA is asking is unclear, requesting a clarification call before submitting your formal written response is often the right decision.

A well-structured clarification call lets you confirm FDA's underlying concern before you commit your answer in writing. It can also surface related concerns that have not yet been formally captured in a deficiency letter — information that can prevent you from triggering a new round of requests on adjacent issues. Document the call thoroughly. The agreements reached verbally need to be reflected accurately in your written response, and that documentation becomes part of your regulatory history.

5 Best Practices for Writing a Response That Actually Closes the Deficiency

A response that leaves room for interpretation is a response that invites more questions. What we consistently observe with first-time submitters is a response document that is technically complete but difficult for a reviewer to process — answers buried in dense paragraphs, supporting data not tied explicitly to the deficiency it addresses, and positions stated ambiguously. FDA reviewers are managing multiple submissions simultaneously. The easier your response is to follow, the faster it gets resolved.

1. Address each deficiency clearly and completely, in the order FDA raised it.

Quote the original deficiency text — including the number — before providing your response. This eliminates any ambiguity about which question each section answers. Do not group deficiencies together unless FDA explicitly asked a linked question, and do not partially address one deficiency while folding it into the answer to another. FDA needs to be able to confirm each issue is closed independently.

2. After you draft each response, re-read the original deficiency against what you wrote.

This sounds obvious, but it is one of the most commonly skipped steps. Multi-part deficiency questions — especially for complex technical or clinical topics — often contain two, three, or four distinct requests embedded in one paragraph. Responding fully to one embedded question while missing another is one of the most common ways to generate a follow-up request. Read the original question again after you write your response, not before.

3. Support strong statements with specific references to your testing data or the scientific literature.

"Our data demonstrates biocompatibility" is not a response. "Biocompatibility has been assessed in accordance with ISO 10993-1:2018 and ISO 10993-5 (cytotoxicity), demonstrating an acceptable cytotoxicity profile as reported in Attachment B, Test Report TR-2024-012" is a response. FDA reviewers need a path from your assertion to the evidence supporting it. Cite the specific test report, study section, or published reference by name, document number, or attachment label. General references to "data on file" or "as shown in our submission" are not sufficient.

4. Use tables to organize point-by-point responses to lengthy or multi-part questions.

When FDA asks a question with multiple sub-points, particularly in the context of performance testing, design controls, or clinical evidence, a table is frequently the most efficient format. Structure it so each row maps one sub-question or data request to your direct response and the specific attachment or section where supporting evidence can be found. This format eliminates the reviewer's need to trace arguments across paragraphs and directly reduces the likelihood that a component of your answer gets missed.

5. Make your response document self-navigating.

Include a response matrix at the front of the document, a simple table listing every deficiency number, a one-line summary of the deficiency, the section of your response document where it is addressed, and the associated attachment labels. A reviewer who needs to confirm that deficiency #4 is resolved should not have to search the document. They should be able to go directly there.

When to Push Back — And How to Do It Effectively

Pushing back on an FDA deficiency is appropriate and sometimes necessary. FDA reviewers are not infallible, and regulatory disagreements are a normal part of the premarket review process.

Effective pushback is evidence-based and precise. Reference the relevant FDA guidance document by full title, explain why your approach satisfies the regulatory standard, and do not frame the disagreement as adversarial. The tone is: "We believe our approach satisfies the requirements of [specific guidance] for the following reasons, supported by [data reference]" — not a general assertion that your position is correct. If you disagree with FDA's interpretation of a guidance document, cite the specific section and explain why your reading is supported by the document's language or intent.

Pushback that escalates the tone without adding regulatory substance rarely succeeds. It also damages the working relationship with the review team, a relationship that matters for the remainder of your review and any future submissions.

Questions to Ask About Your Program

• Have you categorized each deficiency as a presentation issue, a data gap, or a regulatory interpretation disagreement, and adjusted your response strategy accordingly?

• After drafting each response, did you re-read the original deficiency text to confirm every sub-question or embedded request has been addressed?

• Are your evidentiary references specific enough that a reviewer can locate the supporting data without searching the original submission?

• Does your response document include a matrix at the front that maps each deficiency number to your response section and attachments?

• For any deficiency reflecting a genuine regulatory disagreement, have you considered requesting a clarification call with the review team before submitting your written response?

If you are working through a deficiency letter and want a second perspective on how to approach a particular response, Folio Consulting Group is happy to help.