What to Do When Your Predicate Device Gets Recalled

A predicate device you cleared your product against two years ago can get recalled without warning, and the first time most teams think about what that means is when someone finally asks whether it still matters.

In brief

A device recall under 21 CFR Part 806 does not retroactively undo an FDA substantial equivalence finding that already relied on that device as a predicate — a cleared 510(k) is not automatically reopened by a later recall.
FDA’s own guidance on evaluating substantial equivalence cautions against leaning on a predicate that FDA has required off the market for a safety or performance reason, because it undercuts the premise a predicate is supposed to satisfy: legally marketed, with no unresolved question hanging over it.
The practical risk sits in your next submission, not your last one — if you are still citing that device as a predicate and a recall touches the same design feature you relied on, that is exactly what a reviewer will ask about.
Nothing requires you to monitor recalls of devices you don’t make. This is a diligence habit, not a reporting obligation.

What a recall does and doesn’t change

FDA’s substantial equivalence finding for your own cleared product stands on its own; a later recall is a separate action against a different submission, and Part 806 gives FDA no mechanism to reopen your clearance automatically because someone else’s device was pulled. But standing on solid regulatory ground is not the same as being in a strong practical position. If the working file you built around that predicate hasn’t been revisited since the recall, you don’t actually know yet whether the recall touches the technological characteristic you relied on for your equivalence argument, or an unrelated manufacturing problem that says nothing about the design.

When it actually matters

The distinction that matters is between a recall over a manufacturing or quality defect — a bad lot, a labeling error, a sterility failure in one production run — and a recall tied to the device’s fundamental design or intended use. The first rarely threatens an equivalence argument built around the device’s design. The second can threaten it directly. Start by reading the recall itself — see how to read an FDA recall for how to pull the classification and root cause apart from the notice — and check whether that root cause touches the same characteristic your own comparison leaned on. If you are actively building a new submission against that same device as a predicate, a design-related recall is a reason to go looking for a stronger or additional predicate before a reviewer raises it for you.

Checking this costs little in practice. FDA’s recall database is searchable by product code and by firm, and a few minutes spent running your own predicate list against it once a quarter is usually enough to catch a design-related recall before it becomes a surprise in review. The habit matters more than the tool — most teams that get caught by this didn’t lack the data, they simply never thought to look.

Where this goes wrong

Assuming a recall is only the recalled company’s problem

If that device is your predicate, its recall is your diligence problem too, whether or not you had anything to do with it.

Not distinguishing manufacturing recalls from design recalls

Only a recall tied to the device’s design or intended use usually threatens the comparison your own submission is built on.

Finding out from the reviewer instead of finding out first

An additional information request that surfaces a competitor’s recall after you’ve submitted costs far more time than a diligence check would have, before you built the file.

None of this shows up automatically — it only surfaces if someone on the team treats the predicate file as something to revisit, not something to file away once the submission clears.

Sources & further reading

eCFR — 21 CFR Part 806, Medical Devices; Reports of Corrections and Removals ecfr.gov
FDA — The 510(k) Program: Evaluating Substantial Equivalence in Premarket Notifications [510(k)] fda.gov
Regulatory Academy — How to Read an FDA Recall regulatoryacademy.com
Regulatory Academy — Building a Working File of Predicate and Precedent Devices regulatoryacademy.com

This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.