How to Write an FDA Pre-Submission That Gets Real Answers

May 17, 2026

Key Takeaways

• The PreSTAR template ensures your Pre-Submission meets the minimum structural FDA requirements for a Q-Sub, but minimum structure is not enough to get substantive FDA feedback.

• FDA will respond at the level of detail you provide — submit a high-level testing plan instead of a complete protocol, and you will receive responses that don't help shape your regulatory strategy.

• Every Pre-Submission question should include your position: what you believe, your reasoning, and the specific confirmation, challenge, or refinement you are asking FDA to provide.

If your Pre-Submission came back from FDA with responses that felt generic, inconclusive, or that left you with more uncertainty than you started with, the problem was almost certainly not FDA.

We see this more often than we should: a company uses the PreSTAR template, checks every box, submits something that looks complete on the surface, and then receives feedback that reads like an FDA Guidance Document, rather than specific feedback. The structure was right. The sections were present. But the technical substance was missing, and FDA responded similarly.

The PreSTAR template is a structural tool. Its purpose is to ensure your submission includes the required elements outlined in FDA's guidance document, Requests for Feedback and Meetings for Medical Device Submissions: The Q-Submission Program. It tells you what sections to include, like a checklist, but does not tell you what amount of detail to include.

That distinction is where programs waste this opportunity to align with the Agency.

The Q-Sub Program Is Only as Useful as The Information You Include

The Q-Submission program is one of the most valuable regulatory tools available to device developers. Under the program, FDA commits to providing written feedback on your specific questions, typically within 70 days, and also agrees to meet to discuss the feedback interactively. That feedback is informal and non-binding, but in practice, it helps programs align with regulators and mitigate development risks. A well-crafted Pre-Sub can establish FDA's position on your testing approach, validate your predicate selection, confirm your regulatory pathway, or surface a concern early enough to address it before it becomes a lengthy delay.

The operative phrase is "your specific questions." FDA's obligation under the program is to respond to what you ask. If what you ask is vague, FDA's response will reflect that.

The practical implication here is significant: the quality of your Pre-Submission output is a direct function of the quality of your Pre-Submission input. The program is not designed for FDA to do your analytical work. It is designed for FDA to weigh in on work you have already done.

Where the Substance Gaps Live

What we typically see in underprepared Pre-Submissions:

Thin background sections. The background should frame your device in terms FDA reviewers will recognize: the indication for use, the patient population, the clinical context, and the relevant cleared device landscape. A summary of the device without regulatory framing forces the reviewer to make assumptions. Those assumptions may not favor your program.

Testing plans described in paragraphs instead of protocols. If you are asking FDA to weigh in on your bench testing approach or animal study design, FDA needs the same information your study team needs to execute: the study rationale, endpoints, acceptance criteria, statistical approach, and GLP compliance status. A high-level description doesn't give FDA enough to engage with substantively. It gives them just enough to confirm they received your question.

Questions written without a sponsor position. Asking FDA "Is our proposed animal model appropriate?" is not a question FDA can meaningfully answer without knowing what model you have proposed, why you selected it, what data or precedent supports that selection, and what alternative you considered and rejected.

A client came to us after receiving exactly this kind of feedback from their Pre-Sub. The PreSTAR structure was intact — every required section was present. But the background was thin, the proposed non-clinical testing details were absent, and the questions were vague. This was a missed opportunity and 70 days wasted, when the feedback did not confirm anything additional to what they could read in FDA Guidance Documents.

Build Your Pre-Sub Around the Decisions That Cannot Go Wrong

The most useful way to approach a Pre-Submission is not to start with the template. Start with the decisions your program cannot afford to make incorrectly.

If your project timeline has identified biocompatibility evaluation and your animal study as your longest lead-time items — items that, if they fail, reset your entire development schedule — then those are your Pre-Sub priorities. Submit your complete biocompatibility evaluation plan, including the specific ISO 10993 series assessments you have selected and your rationale for each endpoint under ISO 10993-1. Submit your full animal study protocol: the species selection rationale, the endpoints mapped to your clinical claims, your study timepoints, GLP compliance status, and the specific questions you need answered before you initiate the study.

These are the documents you are asking FDA to review. Submit them. Do not describe them.

The same logic applies to your questions. Every question should include three things:

• Your position — what you believe to be true about your device, your approach, or the applicable regulatory framework

• Your reasoning — the data, precedent, or regulatory basis that supports your position

• Your specific ask — whether you are seeking confirmation, identifying a potential point of disagreement, or asking FDA to weigh in on an alternative approach

Here is the difference in practice.

A weak question: "Does FDA agree with our proposed bench testing approach?"

A stronger version: "Sponsor proposes [specific test] per [specific standard] using [specific parameters], based on [specific rationale tied to clinical use conditions and predicate precedent]. Does FDA agree this approach adequately characterizes [specific performance characteristic], or are there additional parameters FDA would recommend given [specific clinical scenario]?"

The second question gives FDA something to respond to. The first gives FDA an opportunity to say "it depends" — and leave it there.

What a Well-Used Pre-Sub Actually Accomplishes

Used well, the Q-Sub program does more than answer questions. It creates a documented record of FDA's position at a specific point in your development. That record has practical value at every subsequent stage: when you are finalizing your testing plan, when you are managing a design change, when you are preparing your 510(k) or PMA, and when you are responding to a deficiency letter.

An important caveat: Q-Sub feedback is informal and non-binding, and FDA can revisit a position. But a well-documented Pre-Sub response that you have built your program around places you in a significantly stronger position than a program built entirely on internal assumptions.

Used poorly, the Pre-Sub program is an expensive and time-consuming way to confirm you were not ready.

Questions to Ask About Your Pre-Submission

• Have you identified the decisions in your current development plan that would be most costly to get wrong, and is your Pre-Submission organized around getting FDA alignment on those specific high impact decisions?

• If you are asking FDA to weigh in on a testing approach, have you submitted the actual protocol rather than a description of what the protocol will contain?

• Does each question include your sponsor position, the reasoning that supports it, and a specific ask — or are you asking FDA to generate the reasoning for you?

• If your Pre-Sub spans multiple topic areas, have you prioritized them by timeline impact, so that your most consequential questions are front and center?

• Do you know what you will do with each possible FDA response — and have you built that decision logic into your development plan?

If any of these are hard to answer confidently, it may be worth stepping back before you submit.

If you are preparing a Pre-Sub and want a strategic perspective on whether your questions and supporting documentation are positioned to get you the FDA feedback you need, we are happy to think through it with you.