How to Pick a 510(k) Predicate Device — A Founder’s Guide

If you’re a medical device founder working toward FDA 510(k) clearance, predicate device selection is one of the most consequential decisions you’ll make. Get it right and your path to clearance is clear and defensible. Get it wrong and you may not discover the problem until you’re staring at a deficiency letter 90 days into review.

This guide walks you through exactly what a predicate device is, why it matters so much, and how to find and evaluate strong predicate candidates — the same process we use at Evolve Regulatory Strategies before every strategy call.

What Is a Predicate Device — and Why Does FDA Care?

A predicate device is a legally marketed device that your new device is “substantially equivalent” to. Under the 510(k) pathway, you’re not proving your device is safe and effective from scratch — you’re demonstrating that it is substantially equivalent to something FDA has already cleared.

Substantial equivalence means your device has the same intended use as the predicate, and the same or similar technological characteristics — or different technological characteristics that don’t raise new safety or effectiveness questions.

If FDA agrees, you’re cleared. If they don’t, you’re in a deficiency cycle or looking at a more burdensome pathway entirely. This is why predicate selection isn’t just a paperwork exercise. It’s the foundation your entire submission is built on.

The Most Common Predicate Selection Mistakes

Picking a predicate based on name or description alone. Two devices can sound identical and have meaningfully different classification codes, intended uses, or technological characteristics. Always go deeper than the device name.

Ignoring the predicate’s own 510(k) history. Your predicate used a predicate too. If that chain is weak — or if the original device was cleared under conditions that don’t apply to yours — your argument may be vulnerable.

Choosing the most recent cleared device without checking whether it’s actually strong. Recency doesn’t equal strength. A device cleared last year with a shaky substantial equivalence argument is a weaker predicate than a well-established device cleared a decade ago.

Overlooking technological differences that matter to FDA. If your device has features the predicate doesn’t — even features you consider improvements — FDA may flag them as raising new safety questions. Know your differences before you submit, not after.

How to Search the 510(k) Database Effectively

FDA’s 510(k) database is free and publicly available at accessdata.fda.gov. Here’s how to use it properly:

Step 1: Search by product code, not device name. Every 510(k)-cleared device has a three-letter product code. Searching by product code gives you a far more accurate set of potential predicates than searching by name. Find the right product code using FDA’s Product Classification database.

Step 2: Pull the 510(k) summary — not just the clearance letter. The clearance letter tells you a device was cleared. The 510(k) summary tells you why — what substantial equivalence argument FDA accepted, what predicate was used, and what testing was required. Read it carefully. It is your roadmap.

Step 3: Check the 21 CFR regulation number. Your device and your predicate should fall under the same regulation. If they don’t, understand why and whether that difference affects your substantial equivalence argument.

Step 4: Look at clearance dates and submission volume. A product code with hundreds of cleared devices over many years signals a well-established pathway. A product code with only a few recent clearances may indicate a newer category where FDA’s thinking is still evolving.

How to Evaluate Whether a Predicate Is Actually Strong

Intended use alignment. Does your device have the same intended use as the predicate — same indication, same patient population, same clinical context? A different intended use is not a different degree of similarity. It’s a disqualifier.

Technological characteristics. List every technological feature of both devices side by side. For each difference, ask: does this raise a new question of safety or effectiveness? If yes, you need data to answer that question before you submit.

The predicate’s own clearance history. Was the predicate cleared through a robust 510(k) with strong substantial equivalence reasoning? The strength of your predicate’s clearance affects the strength of your argument.

Is it currently marketed? A predicate should be a legally marketed device. FDA has challenged predicates that haven’t been commercially available for years.

Should You Use One Predicate or Multiple?

You can use multiple predicates in a 510(k) — a split predicate approach where one device establishes your intended use and another establishes your technological characteristics. This is legitimate and commonly used.

However, split predicates add complexity and FDA scrutinizes them carefully. For most straightforward Class II devices, a single strong predicate is cleaner and lower risk. A split predicate makes sense when your device has a genuinely novel feature that no single predicate fully covers. It doesn’t make sense when you’re using two predicates because you can’t find one good one — that’s a signal your device may need a different pathway.

When to File a Pre-Submission Before You Choose Your Predicate

If you’re genuinely uncertain about your predicate strategy — especially if your device has novel features, sits at the edge of a product code, or has a combination of intended uses — a Pre-Submission meeting (Q-Sub) with FDA is worth considering before you finalize anything.

A Pre-Sub lets you ask FDA directly: “Here is our proposed predicate. Do you agree this is appropriate for our device?” Getting FDA’s input before you submit is far less expensive than responding to a deficiency letter after. Not every submission needs a Pre-Sub — but if your predicate selection involves meaningful uncertainty, the investment is almost always worth it.

A Quick Predicate Evaluation Checklist

Before finalizing your predicate, run through this list:

  • Does my device have the same intended use as the predicate?
  • Have I pulled and read the full 510(k) summary for the predicate?
  • Do my device and the predicate share the same product code and 21 CFR regulation number?
  • Have I identified and documented every technological difference between the two devices?
  • For each difference, do I have data or a clear rationale showing it doesn’t raise new safety questions?
  • Is the predicate currently legally marketed?
  • Is the predicate’s own 510(k) clearance history solid?
  • Am I confident FDA will accept this as a strong substantial equivalence argument?

If you can answer yes to every question above, you have a defensible predicate strategy. If you’re uncertain on any of them, that uncertainty is worth resolving before you invest in a full submission.

The Bottom Line

Predicate selection is where most 510(k) submissions are won or lost — and it’s almost entirely determined before the submission is written. Spending two or three hours doing thorough predicate research before you commit to a strategy is one of the highest-return investments you can make in your regulatory pathway.

If you want to pressure-test your predicate strategy before committing to it, that’s exactly what our Regulatory Strategy Call is designed for. Ninety minutes, a written summary of our recommendations, and an honest read on whether your approach will hold up under FDA review.

Evolve Regulatory Strategies is a boutique regulatory consulting practice founded by a medical device entrepreneur who achieved FDA 510(k) clearance through strategic resubmission. We help early-stage founders get clear on their regulatory pathway — without the overhead of a full-time RA engagement.