Your predicate was recalled. Now what?

It is the alert this product was built to surface, so we should be precise about what it means. A recall posts against a device you cited as a predicate — in a cleared 510(k), or worse, in a submission currently under review. What follows is the assessment a regulatory professional runs, in order. What follows is not regulatory advice for your specific device; it is the shape of the question, so the day it arrives you are working the problem instead of discovering it.

First, what a predicate recall does not do

A recall does not revoke your clearance. Substantial equivalence was a finding made on the day of your decision letter, against a predicate that was legally marketed at the time; a later recall of that predicate does not unwind the finding by operation of law. FDA’s own predicate-selection guidance treats recall history as a quality signal in choosing a predicate going forward, not as a retroactive tripwire. So the first answer to “now what?” is: not panic.

But “my clearance stands” is the beginning of the assessment, not the end of it — because the recall record contains a fact that may be about your device too, and you are the only party who will check.

The question is the reason for recall

Pull the enforcement report and read the stated reason for recall, then put it next to your substantial equivalence comparison. The whole assessment lives in that comparison:

• Manufacturing-specific causes — a supplier lot, a sterilisation failure at their facility, a labelling mix-up in their packaging line — belong to the predicate’s quality system, not to the technology you compared against. Note it, file it, move on.
• Design-related causes are the ones that deserve your evening. If the recall traces to a design characteristic — and it is one your device shares because your file argued it was equivalent — then the recall is evidence about your device, arriving through the predicate. Your risk file, not FDA, is where that evidence has to land: does the failure mode exist in your design, did your risk analysis foresee it, and does your post-market data show it?
• Use-related causes — instructions, human factors, use environment — sit in between, and turn on whether your labelling and intended use inherit the same use scenario.

If a submission is in flight

A pending 510(k) citing a freshly recalled predicate is a different conversation, because the reviewer can see the recall too. The comparison you filed is now a comparison against a device with a public failure record, and the productive posture is to get ahead of the question: assess the recall’s cause against your technological characteristics, document why it does or does not raise a new question of safety and effectiveness, and be ready to say so — proactively if the cause is design-related and shared. Whether to amend, respond, or hold is a judgment call that depends on your file, your reviewer, and your timeline — which is exactly why it is a call a professional makes with the record in front of them, not one a blog post makes for you.

Write the assessment down

Whatever the answer, the artifact matters as much as the conclusion. A dated memo — recall record, stated cause, your comparison, your determination, your name — is the difference between “we assessed it at the time” and “we think we looked at it” when the question resurfaces in an audit or an inspection two years later. The decision not to act, documented, is a defensible position. The same decision, undocumented, is a gap.

FDA Radar’s part in this is the beginning of the chain, done without you watching: recalls join against your portfolio — including reviewer-keyed product codes, since FDA publishes no identifiers on recalls, and we disclose that on the match — so the alert arrives while the assessment still has all its options. The assessment itself is yours. It always was.