how-to
FDA Pre-Sub Meeting Strategy: Best Practices
Table of Contents
- What Is an FDA Pre-Sub Meeting and Why It Matters
- Crafting Effective FDA Pre-Sub Meeting Questions
- Building Your FDA Pre-Submission Briefing Document
- Understanding the FDA Pre-Submission Timeline
- Real FDA Pre-Sub Meeting Examples and What They Reveal
- How to Use FDA Feedback After Your Pre-Sub Meeting
- Frequently Asked Questions
Last Updated: October 8, 2026
What Is an FDA Pre-Sub Meeting and Why It Matters
An FDA pre-submission meeting is a formal conversation between your company and the FDA before you submit a regulatory application. You ask questions. The FDA gives feedback. This happens before you invest months and money into a full submission.
The goal is simple: get clarity on the pathway forward. Will the FDA accept your evidence package? Do they want additional studies? What classification are they thinking? These answers save you from building the wrong submission.
Pre-sub meetings matter because they reduce risk. Without one, you might spend six months preparing a 510(k) submission only to learn the FDA thinks your device needs a De Novo or PMA instead. That's expensive. That's a delay. A pre-sub meeting prevents it.
E & E Medicals and Consulting offers professional and authoritative guidance, specializing in FDA regulatory expertise and quality management for the medical device industry. The difference between a productive pre-sub and a wasted one comes down to preparation. You need clear questions. You need a solid briefing document. You need to know what you're actually asking for.
This guide walks you through the entire FDA pre-sub meeting strategy, from crafting questions to using the feedback you receive.
Crafting Effective FDA Pre-Sub Meeting Questions
The FDA won't answer vague questions. They won't guess at your intent. If you ask "Is our device safe?" they'll decline to answer. If you ask "What nonclinical testing do you expect for a percutaneous glucose monitor with wireless connectivity?" they'll give you a straight answer.
Your questions must be:
- Specific, name your device, your intended use, your patient population
- Actionable, ask for a yes/no, a recommendation, or a list of expectations
- Realistic, don't ask the FDA to make a regulatory decision; ask them what they need to see
- Focused, limit yourself to 5-7 core questions per meeting
Common question areas include classification pathway, predicate device selection, clinical evidence requirements, manufacturing and quality standards, and labeling expectations.
One mistake teams make is asking the same question multiple ways. This wastes time. Another is asking questions you could answer yourself by reading FDA guidance documents. Read the guidance first. Then ask what's unclear or specific to your situation.
The best FDA pre-submission meeting questions are ones that move your project forward. They address genuine uncertainty, not things you can figure out independently.
Building Your FDA Pre-Submission Briefing Document
Your briefing document is the foundation of the entire meeting. This is a written summary of your device, your intended use, and your questions. The FDA reads it before the meeting. Your team uses it to stay on track during the conversation.
A weak briefing document creates a weak meeting. The FDA might misunderstand your device. You might waste 30 minutes clarifying something that should have been clear in writing.
Core Components of a Strong Briefing Document
Your briefing document should include:
- Device description, what it is, how it works, what it's made of, how it's used
- Intended use statement, patient population, indication, contraindications, operating environment
- Predicate device(s), if you're claiming substantial equivalence, name the predicate and explain why it's appropriate
- Regulatory pathway, are you planning 510(k), De Novo, or PMA? State your assumption
- Manufacturing and quality, ISO 13485 status, design controls approach, risk management framework
- Clinical and nonclinical data, what testing have you done or planned? What do you think the FDA will expect?
- Your specific questions, numbered, clear, and focused
- Timeline, when do you plan to submit? When do you need feedback?
Keep it concise. Most briefing documents are 10-15 pages. Longer isn't better. Clarity is.
Avoiding Common Briefing Document Mistakes
Teams often make these errors:
- Burying the device description, put it early and make it clear
- Assuming the FDA knows your market, explain context the FDA might not have
- Asking for a regulatory decision, the FDA won't tell you "use the 510(k) pathway." They'll tell you what evidence they expect to see
- Including irrelevant marketing content, focus on regulatory facts, not competitive claims
- Submitting a rough draft, treat this like a formal submission; it sets the tone for the entire interaction
The briefing document is your chance to control the narrative. Use it.
Understanding the FDA Pre-Submission Timeline
The FDA pre-submission timeline varies based on the complexity of your device and the FDA's workload. Expect the process to take 4-8 weeks from submission to meeting.
Here's how it typically works:
- Week 1, You submit your briefing document and pre-sub request through FDA's Q-Submission system
- Week 2-3, FDA reviews your submission and determines if it's complete
- Week 3-6, FDA prepares their response and schedules a meeting date
- Week 6-8, You attend the meeting (in-person or virtual)
- Post-meeting, FDA sends a written summary of the discussion within 30 days
If your submission is incomplete, the FDA will ask for clarification. This can add 2-4 weeks to the timeline. So make sure your briefing document is thorough and clear from the start.
The timing matters. If you're planning a submission in Q2 2027, you should request a pre-sub meeting by Q4 2026. Don't wait until the last minute.
Real FDA Pre-Sub Meeting Examples and What They Reveal
Example 1: A company developing a wearable continuous glucose monitor submitted a pre-sub asking about clinical evidence requirements. They assumed they'd need a large pivotal trial. The FDA's feedback: for certain patient populations, a smaller study with specific accuracy metrics would suffice. This saved the company 18 months and millions in development costs.
Example 2: A software-as-a-medical-device (SaMD) company asked about validation requirements for their AI-powered diagnostic tool. The FDA clarified which parts of the software needed formal validation and which didn't. The company adjusted their approach and reduced validation scope by 40%.
Example 3: A combination product company (device + drug) asked about regulatory jurisdiction. They weren't sure if the FDA would regulate it as a device or a drug. The FDA's response clarified the pathway, which then determined their entire submission strategy.
These examples show why FDA pre-sub meeting examples matter. They reveal what the FDA actually cares about, not what you assume they care about.
How to Use FDA Feedback After Your Pre-Sub Meeting
The FDA sends a written summary of the meeting within 30 days. This document is your roadmap. It's not legally binding, but it's the FDA's word on what they expect.
Here's what to do with it:
- Align your team, make sure everyone understands the FDA's expectations
- Adjust your plan, if the FDA said they want additional testing, build it into your timeline
- Document decisions, record why you're making changes based on FDA feedback
- Flag disagreements, if you disagree with the FDA's guidance, you can ask for a follow-up meeting
- Reference it in your submission, when you eventually submit, reference the pre-sub meeting feedback
The feedback is only useful if you act on it. Teams sometimes request pre-subs, get feedback, and then ignore it. That defeats the purpose.
If the FDA's feedback contradicts your internal assumptions, don't fight it. Adjust your strategy. The FDA has already told you what they're thinking. That's invaluable information.
Preparing for an FDA pre-sub meeting requires strategy. Your briefing document must be clear. Your questions must be specific. Your timeline must be realistic. E & E Medicals and Consulting helps medical device companies navigate this process with expertise in FDA regulatory strategy, quality management, and submission preparation. We ensure your pre-sub meeting delivers the clarity you need to move forward with confidence. Contact E & E Medicals and Consulting to discuss your FDA pre-sub strategy and get expert guidance on your regulatory pathway.
Frequently Asked Questions
What is the difference between an FDA pre-sub meeting and a Q-Submission?
An FDA pre-sub meeting is a formal meeting between your team and the FDA to discuss your regulatory strategy before submission. A Q-Submission is the formal request mechanism through which you ask the FDA written questions about your submission pathway. Pre-sub meetings often follow Q-Submissions and allow real-time discussion. Both pathways provide FDA feedback, but pre-sub meetings enable dialogue, while Q-Submissions are asynchronous written exchanges.
How long does it take the FDA to respond to an FDA pre-submission request?
The FDA typically responds to Q-Submission requests within 30 days. However, the timeline can vary based on complexity and FDA workload. Once you receive the written response, scheduling the actual pre-sub meeting may take additional weeks. Plan for 60-90 days from submission to meeting completion, accounting for preparation time on both sides.
Can you rely on FDA pre-submission feedback for your 510(k) submission?
FDA pre-submission feedback is advisory and not binding. However, it carries significant weight. The FDA provides guidance on your proposed pathway, design, testing, and labeling expectations. Following pre-sub feedback strengthens your submission and reduces the likelihood of deficiency letters. Document the feedback and your responses in your submission to show alignment with FDA's recommendations.
What should you do immediately after your FDA pre-sub meeting?
Document all feedback from the meeting in writing and send a follow-up letter to the FDA summarizing your understanding of their recommendations. Address any clarifications or disagreements promptly. Incorporate the feedback into your development plan and submission strategy. Create an internal action plan assigning responsibility for each recommendation. Track compliance with FDA guidance throughout your product development and submission preparation.
