A team can spend months building a submission strategy around a 510(k), only to learn late in development that FDA views the product differently. That is exactly where a 513(g) request medical device strategy can create value. Used at the right time, it helps sponsors get FDA’s informal view on classification and the likely regulatory pathway before larger budget and timeline commitments are locked in.
For founders, regulatory leaders, and product executives, the practical question is not whether a 513(g) request is available. It is whether it will materially reduce uncertainty for this device, at this stage, and for this business decision. Sometimes the answer is yes. Sometimes it simply adds time without changing the core regulatory work ahead.
What a 513(g) request medical device submission does
A 513(g) request is a formal mechanism for asking FDA how it views a product under the device framework. In plain terms, the agency may provide its perspective on device classification, the applicable regulation if one exists, and the submission pathway that is likely to apply, such as 510(k), De Novo, or PMA. It may also indicate that the product is not a device, or that the information provided is not enough to make a meaningful assessment.
That makes the tool useful when the regulatory identity of the product is still unsettled. This often happens with novel technologies, software-enabled products, combination product questions, and devices that do not fit neatly into an obvious existing classification regulation.
What a 513(g) request does not do is provide marketing authorization, bind FDA to a future review position, or substitute for a well-developed submission strategy. It is an early-stage interpretive tool, not a shortcut around substantive evidence requirements.
When a 513(g) request makes business sense
The strongest use case is when classification uncertainty could materially affect investment, product design, clinical planning, or launch timing. If leadership is deciding between a lower-cost 510(k) route and a more resource-intensive De Novo or PMA path, an early read from FDA can help shape the program before costly assumptions harden into the development plan.
It can also be valuable when the product sits near the edge of device jurisdiction. For example, some digital health products, accessories, wellness-adjacent technologies, and products with drug or biologic elements may trigger real questions about how FDA will view the offering. In those cases, waiting until a premarket submission can create avoidable rework.
That said, a 513(g) request is not automatically the best first move for every company. If the classification is already reasonably clear based on regulations, product codes, predicates, guidance, and prior agency positions, the better investment may be in a direct submission strategy or a pre-submission meeting focused on testing, clinical, or performance expectations.
513(g) request vs pre-submission
This is where many teams lose time. A 513(g) request and a pre-submission are not interchangeable.
A 513(g) request is generally about how FDA classifies the product and which regulatory framework likely applies. A pre-submission is better suited for feedback on specific study designs, bench testing, software validation, biocompatibility plans, clinical protocols, or content planned for a future marketing application.
If your main question is, “What is this product in FDA’s eyes?” a 513(g) request may be appropriate. If your main question is, “Will this test plan support clearance or approval?” a pre-submission is usually the stronger tool.
There are situations where both are useful, but sequence matters. A company that asks detailed pre-submission questions before resolving basic classification uncertainty may end up discussing the wrong pathway. On the other hand, if FDA classification is already predictable, starting with a 513(g) may add an extra cycle with limited incremental benefit.
What FDA typically expects in a 513(g) request medical device package
The quality of the request strongly affects the usefulness of the response. FDA can only react to the product as described, so vague positioning tends to produce vague answers.
A strong package usually includes a precise device description, intended use, indications for use if sufficiently developed, technological characteristics, operating principles, and a clear explanation of how the product will be used in clinical practice. If comparable products, classification regulations, or product codes appear relevant, they should be discussed carefully and objectively.
This is not the place for aggressive analogies or selective comparisons. FDA reviewers can usually spot when a sponsor is trying to force a product into a lower-burden pathway by emphasizing superficial similarities. A more credible approach is to explain where the product aligns with existing device types, where it differs, and why those differences may or may not affect classification and review expectations.
For software and connected devices, clarity matters even more. High-level language such as “AI-enabled platform” or “decision support tool” is rarely enough. FDA needs to understand what the software actually does, what data it uses, what output it provides, and whether that output informs diagnosis, treatment, or clinical management.
Common mistakes that weaken the response
One frequent mistake is filing too early, before the product concept is stable enough to describe with precision. If the intended use is still shifting, the agency’s response may become less relevant as the program evolves.
Another is asking FDA to answer questions a 513(g) process is not designed to answer. Sponsors sometimes try to use it to obtain agreement on test methods, clinical evidence thresholds, or substantial equivalence arguments. Those topics generally belong elsewhere.
A third issue is incomplete competitive and regulatory research. If the request ignores obvious classifications, product codes, or similar products already on the market, FDA may view the submission as underdeveloped. That can reduce the practical value of the response and signal that the sponsor has not yet done the foundational work.
Finally, teams sometimes overread the answer. A favorable pathway indication is helpful, but it is not a guarantee that the eventual submission will be straightforward. Review complexity still depends on the final device design, claims, risk profile, evidence package, and how well the submission is assembled.
How to decide whether to submit one
The right decision usually comes down to three questions.
First, is there genuine uncertainty around classification, jurisdiction, or pathway? Second, would greater clarity change a near-term business or development decision? Third, is the product defined well enough today to support a useful agency response?
If the answer to all three is yes, a 513(g) request may be a smart strategic investment. If only the first answer is yes, but the product is still immature, it may be better to refine the concept first. If only the second answer is yes, but classification is already fairly clear, the effort may be better spent on submission planning and evidence generation.
This is also where experienced regulatory judgment matters. The same fact pattern can look different depending on intended use wording, feature scope, and the degree to which the device introduces new questions of safety or effectiveness. Small drafting choices can move a product closer to or farther from an existing classification framework.
Building the request around decision quality
The best 513(g) submissions are not written as academic exercises. They are built to improve decision quality. That means tying the regulatory question to the actual choices facing the business, whether that is financing, clinical sequencing, verification and validation scope, or market entry timing.
A disciplined team uses the process to reduce ambiguity, not to chase reassurance. If the likely answer points toward a more demanding pathway, that information is still valuable. It allows leadership to reset budgets, evidence plans, and investor expectations before the organization commits to the wrong launch model.
For med tech companies operating with limited internal bandwidth, this is often where external support pays off. A well-prepared request can frame the product accurately, anticipate FDA’s likely points of tension, and position the company to act on the response rather than simply receive it. That practical execution mindset is where firms like Qualira can help teams turn a narrow regulatory mechanism into a commercially useful planning tool.
FDA pathway uncertainty rarely disappears on its own. If a 513(g) request can resolve a meaningful question early, it may be one of the more cost-effective decisions in the program.
