What Is a 510(k)? FDA 510(k) Clearance Explained — Premarket Notification, Not Approval

2026-07-28 · Caduvo Team

The 510(k) pathway clears a device for market based on substantial equivalence—not approval. This guide breaks down the submission, real-world timelines, costs, and the pitfalls that trigger FDA requests.

Your device doesn't need FDA approval. It needs FDA clearance. Those two words — cleared vs. approved — define entirely separate regulatory pathways, timelines, and market expectations. The 510(k) premarket notification is the route most Class II devices take to market, and it rests on a single concept: substantial equivalence to a device already on the market, called a predicate.

What a 510(k) Actually Is: Substantial Equivalence, Not Approval

A 510(k) is a premarket notification submitted under section 510(k) of the Food, Drug, and Cosmetic Act. You are not asking the FDA to "approve" your device. You are notifying the agency that you intend to market a device that is substantially equivalent to a legally marketed predicate device — one that did not require premarket approval.

If the FDA finds your device is substantially equivalent, you receive a clearance letter. The device is then described as "cleared," never "approved." Class III devices that go through the Premarket Approval (PMA) process are the ones labeled "approved." Getting this terminology right matters for regulatory compliance, promotional claims, and investor conversations.

Substantial equivalence does not mean identical. It means your device has the same intended use as the predicate and either:

• Has the same technological characteristics, or
• Has different technological characteristics that do not raise different questions of safety and effectiveness, and you’ve demonstrated through testing that the device is as safe and effective as the predicate.

The FDA’s decision is binary: SE (substantially equivalent, cleared) or NSE (not substantially equivalent, which means you cannot market your device through this pathway).

Who Needs a 510(k) Submission?

Most Class II devices require a 510k clearance. Some Class I devices that are not exempt also need one, and a small number of Class III devices have a 510(k) option if a predicate exists. To determine your device’s classification and whether a 510(k) is required, you start with the FDA’s product classification database. (See FDA Medical Device Classification: Class I, II, III and How to Find Your Product Code.)

If your device is truly novel and no suitable predicate exists, you may be looking at the De Novo pathway instead. But in most cases, an appropriate predicate can be found. The key is selecting one that matches your intended use and technological profile closely enough that you can demonstrate substantial equivalence without triggering excessive testing or clinical data demands. This step alone can make or break your timeline. (For a detailed walkthrough, read Predicate Device Selection for 510(k) Submissions: How to Find and Choose the Right One.)

What Does a 510(k) Submission Include?

A 510(k) submission is a comprehensive package of documentation — not just a form. While the exact list varies by device type, a typical Traditional 510(k) contains:

• Cover letter and administrative forms (including the Truthful and Accurate Statement, FDA Form 3514).
• 510(k) Summary or 510(k) Statement (summary is public, statement is confidential).
• Device description — materials, design, operating principles, specifications.
• Intended use / indications for use statement — must match or be narrower than the predicate.
• Predicate device comparison table — side-by-side showing intended use, technological characteristics, and the rationale for why differences do not affect safety or effectiveness.
• Performance testing data — bench tests, biocompatibility (ISO 10993), electrical safety (IEC 60601), EMC, software verification/validation, sterility validation, shelf-life studies.
• Labeling — proposed labels, package inserts, instructions for use.
• Risk management file per ISO 14971.
• Software documentation (if applicable) — per the FDA’s guidance on software submissions.

Since late 2023, the FDA strongly encourages use of the eSTAR electronic submission template. It structures the content and integrates technical review directly, which can reduce requests for missing information. A well-built eSTAR submission paired with a tight predicate comparison does more to shorten review time than any shortcut.

FDA Review Timelines and Costs

Under the Medical Device User Fee Amendments (MDUFA), the FDA goals are:

• 60 days for an acceptance review (is the submission administratively complete?).
• 90 days for a substantive review leading to a final decision — but the clock stops when the agency issues an Additional Information (AI) request.

That’s why the real-world timeline from submission to clearance is rarely 90 days. When AI requests occur (and they occur in around 70% of submissions), the clock pauses, you respond, and the review restarts. Roughly 6–9 months from the initial submission to a clearance letter is common, though more complex devices or multiple rounds of AI can push it beyond a year.

User fee figures for FY2024 (standard business):

• Standard 510(k) fee: $21,760
• Small business (under $100 million gross receipts/sales, including affiliates): $5,440

The total cost of preparing a 510(k) submission varies widely. A straightforward device with well-established testing protocols might cost $30,000–$60,000 in engineering, testing, and regulatory consulting. For devices requiring novel biocompatibility panels, electromagnetic compatibility testing, or software documentation, $100,000 or more is realistic. Plan your budget around the testing, not just the FDA fee.

The Most Common Reasons for Additional Information Requests

AI letters are the single biggest source of delay. They happen because the initial submission doesn’t answer a specific review question. The most frequent triggers:

• Insufficient predicate comparison. Vague statements like “similar materials” without quantified data. The reviewer needs to see how the difference doesn’t matter, not just that it exists.
• Indications for use broader than the predicate. The FDA will flag this immediately. Align your IFU statement tightly with the predicate’s cleared indications.
• Missing or incomplete performance testing. A test protocol that doesn’t follow the recognized standard, or results left unexplained.
• Sterilization validation gaps. If you deviate from a standard cycle without full rationale and re-validation data.
• Software documentation that doesn’t match the FDA’s guidance on software submissions. This includes incomplete hazard analysis or traceability matrices.
• Labeling inconsistencies. Conflicts between proposed labeling, device description, and indications for use.

Avoiding all of these starts with predicate selection. Choose a predicate that is as close as possible to your device in both technology and intended use, then build the submission to over-explain the comparison. When in doubt, include the extra data.

Actionable Takeaways

• Always refer to a 510(k)-cleared device as “cleared,” not “approved.”
• Start predicate selection early — use the FDA’s public database and plan for a device that lets you write the comparison in quantitative terms.
• Realistically, plan for 6–9 months from submission to clearance, not 90 days.
• Budget for user fees plus the full cost of testing; a tight regulatory budget is often a project-killer.
• Use the eSTAR template from day one; it reduces administrative rejections.

Once you’re on the path to clearance, the reimbursement puzzle starts. Caduvo helps MedTech teams map the coding, coverage, and payment steps that follow FDA clearance, so your market-access strategy isn’t an afterthought.