FDA Pre-Submission Guide: Questions, Package and Realistic Timeline

The Pre-Submission is the most commonly used interaction within FDA’s Q-Submission Program. It is voluntary and intended to obtain feedback before an intended premarket submission or other significant regulatory step. It is most valuable before an irreversible decision: a pivotal study, novel validation method, uncertain predicate strategy, cybersecurity architecture or AI change plan.

Do not file merely to introduce the company or request a broad confirmation that “the plan is acceptable.” FDA feedback quality depends on decision-ready questions. If published guidance, recognized standards and clear predicates already answer the issue, internal work may be faster and more useful.

The reviewer should understand the device, its intended use, its risk and the proposed evidence without reconstructing the story from attachments. Include a concise cover letter, purpose, device overview, regulatory history, proposed indications, architecture or mechanism, risk context, planned submission route and the specific topics for feedback.

For each question, state the sponsor’s proposed approach first. Then provide the alternatives considered, supporting data or standards, and the reason the answer matters. A protocol question should include objectives, population, endpoints, reference method, sample size rationale, statistical analysis and acceptance criteria at sufficient maturity for meaningful comment.

A productive question takes the form: “Does FDA agree with [specific proposal] for [defined purpose], given [key rationale]? If not, what additional information does FDA recommend?” This makes the sponsor’s position reviewable while leaving room for a different recommendation.

Avoid asking FDA to choose among undeveloped options, confirm ultimate clearance, identify every applicable requirement or conduct a complete submission review. Break compound questions apart. Prioritize issues by the cost of being wrong, because meeting time is limited and a long list dilutes discussion.

FDA’s Q-Submission guidance describes a goal of providing written feedback by day 70 for a written-feedback-only request, or holding a meeting by day 75 for meeting requests. The clock begins when CDRH receives a complete submission, and administrative acceptance, requests for clarification, holidays and meeting availability should be accounted for in the project schedule.

A practical sponsor schedule usually includes two to six weeks to stabilize strategy and prepare the package, the FDA interaction period, and one to two weeks after feedback to document decisions and revise plans. Complex protocols often need longer internal preparation. Filing an immature package early does not save time if FDA cannot answer the central question.

For a meeting, FDA generally sends preliminary written feedback shortly before the discussion. Use the meeting to clarify that feedback and resolve priority points, not to repeat the device overview. Submit meeting minutes on time under the current programme guidance and preserve the final record in the regulatory file.

Create a feedback matrix that records each question, FDA’s written position, meeting clarification, the sponsor decision, action owner and affected artifacts. Update protocols, requirements, risk controls, regulatory strategy and project assumptions through normal change control.

Pre-Sub feedback is not legally binding on FDA or the sponsor. It is nevertheless important regulatory history. If the future submission departs from the discussed approach, explain why—for example, new data, a product change or later guidance—and show that the alternative still answers the underlying concern. Materially new questions may justify a supplement or follow-on Q-Submission.