Meeting strategy and scope
Identify the decision that needs FDA feedback, the timing that gives the team room to use it, and the questions that are specific enough to lead somewhere useful.
FDA PRE-SUBMISSION CONSULTING
FDA Pre-Submission Consulting
Turn an important question into a focused FDA conversation, before the pathway, evidence plan, or product decisions become difficult to change.
Discuss your Pre-Submission →THE DECISION BEFORE THE MEETING
A useful Pre-Submission does more than ask FDA for feedback.
Medical-device teams often reach a point where a decision affects everything that comes next: the intended use they can support, the evidence they need to generate, the test plan they can defend, or the regulatory route that makes sense for the product. Moving forward without a clear answer can create avoidable work, narrow the available options, or leave the team explaining assumptions after they have become embedded in the program.
Qualira helps teams prepare FDA Pre-Submissions that make the decision in front of the program clear. The work starts with the device, its intended use, the evidence already available, and the milestone the team needs to reach. From there, Qualira helps shape a focused proposed approach and the questions most likely to give the team practical direction.
WHERE QUALIRA HELPS
Senior support for the questions that can change the direction of a device program.
Pathway and evidence planning
Connect the proposed regulatory route, intended use, device differences, non-clinical testing, clinical evidence, and quality readiness to the question being asked.
Package development
Build a coherent package that gives reviewers the context, rationale, and supporting information needed to understand the device and the proposed approach.
Feedback into action
Translate FDA feedback into clear next steps across regulatory, engineering, clinical, quality, labeling, and submission work so the meeting has a practical result.
FROM UNCERTAINTY TO A USEFUL QUESTION
Ask for feedback while it can still improve the work.
A Pre-Submission is strongest when it is tied to a real program decision. A team may need to understand whether its proposed evidence is appropriate for the claims it intends to make. It may be weighing a 510(k) against another pathway, deciding how to support a novel technology, planning a clinical investigation, or trying to resolve a question that could otherwise surface much later in review. The goal is not to ask every possible question. It is to ask the questions that can change the plan in a meaningful way.
That requires a clear view of the product and its context. FDA needs to understand what the device does, who will use it, what makes it similar to or different from other products, and why the proposed approach is appropriate. Qualira helps teams bring those points together before the writing begins, so the package reflects the actual product strategy rather than a collection of disconnected technical inputs.
The proposed approach matters as much as the question. A vague request for direction is less useful than a well-supported plan that identifies the decision, explains the reasoning, and asks FDA to comment on a defined path. For example, a team may need feedback on a non-clinical test program, a clinical-evidence strategy, a predicate rationale, or the information needed to support a particular intended use. Qualira helps make the rationale clear enough for a productive discussion while keeping the work proportionate to the decision at hand.
Preparing for the meeting also means preparing the team. Regulatory, engineering, clinical, quality, and leadership stakeholders may each see the issue differently. When those views are not aligned before the meeting, the discussion can produce ambiguity instead of clarity. Qualira helps teams identify the assumptions behind the proposed approach, anticipate the follow-up questions that may matter, and decide who needs to be ready to explain each part of the program.
The work does not end when feedback arrives. A response may affect testing, protocol development, risk management, labeling, submission content, timelines, and the order in which the team moves through the next milestone. Qualira can help translate that feedback into a coordinated plan that preserves the logic of the original discussion and gives each contributor a clear role in carrying it forward.
WHAT A STRONG ENGAGEMENT CLARIFIES
Make the meeting useful to the people building the device.
The best Pre-Submission work creates a clearer decision path for the whole program. It helps the team understand what needs to be settled before the meeting, what information belongs in the package, and what will need to change after feedback is received.
Which questions deserve FDA feedback now
Not every uncertainty needs a meeting. Qualira helps distinguish between questions the team can resolve internally and questions where early FDA feedback can protect a material regulatory, clinical, technical, or commercial decision.
What the proposed approach needs to show
A useful package gives the reviewer a complete picture without burying the decision. Qualira can help connect the device description, intended use, supporting evidence, risk considerations, and proposed plan into a clear narrative.
How to prepare for the discussion
The meeting should move the program forward, not introduce new uncertainty. Qualira helps teams align on the critical messages, prepare for likely discussion points, and make sure the people who own the key decisions are ready to participate.
How feedback changes the next milestone
FDA feedback is valuable when it changes the work in a deliberate way. Qualira can help translate the outcome into updates to the evidence plan, development priorities, documentation, and timeline so the team can act while the decision is still fresh.
PRACTICAL PROGRAM SUPPORT
Bring the evidence, regulatory, and product decisions into the same room.
A Pre-Submission can be especially valuable when a program is carrying more than one uncertainty at once. A novel device may need a clearer route to market. A team may be deciding how much evidence is enough to support its claims. A clinical plan may depend on a regulatory assumption that has not been tested. In those situations, a well-prepared FDA conversation can give the program a more reliable foundation for the work that follows.
Qualira has supported a novel-device team through a 513(g) and Pre-Submission process that helped clarify the route to market, with FDA recommending a De Novo path and agreeing the program could move forward with animal-study data rather than an IDE clinical trial. That kind of outcome depends on connecting the product, evidence, and regulatory rationale before the meeting, then using the feedback to guide the next decision.
View client outcomes →A USEFUL FIRST CONVERSATION
Bring the question that could change what your team does next.
What decision could a focused FDA conversation help us make before we commit to the next phase of work?
Which questions about pathway, evidence, testing, clinical work, or intended use are material enough to bring forward now?
What information does FDA need to understand our device and proposed approach without losing the point of the discussion?
How will we turn the meeting outcome into specific actions across the program?
FREQUENTLY ASKED QUESTIONS
Frequently asked questions
When should a medical device team request an FDA Pre-Submission?
A Pre-Submission is most useful before a decision becomes expensive to reverse. That may be before finalizing a 510(k), De Novo, PMA, IDE, clinical study, non-clinical test plan, or substantial design change. The meeting should address a question that matters to the program and where FDA feedback can still influence the work that follows.
What can a Pre-Submission help a medical device company decide?
It can help clarify the questions FDA will consider important for a proposed approach, including device classification, intended use, evidence expectations, clinical-study design, test strategy, predicate reasoning, or another focused regulatory issue. It does not replace the submission itself, but it can give the team direction before it commits significant time and budget.
How detailed should an FDA Pre-Submission package be?
It needs enough device-specific context for FDA to understand the decision in front of the team and provide useful feedback. The right level of detail depends on the question, but the package should make the proposed approach, supporting rationale, and specific questions easy to follow without asking reviewers to infer the program strategy.
Can Qualira help after an FDA Pre-Submission meeting?
Yes. The value of a meeting is in how the team uses the feedback. Qualira can help interpret the response, adjust the regulatory and evidence plan, coordinate affected workstreams, and keep the final record aligned as the program moves toward the next milestone.
Can a Pre-Submission support a device that may not fit a 510(k) pathway?
Yes. When the pathway is uncertain, early feedback can be especially useful. Qualira can help frame the decision around the device, intended use, available evidence, and realistic alternatives so the team can evaluate the most defensible next step rather than invest in an assumption that may not hold.
TALK WITH QUALIRA