The field-action review moment
Picture the founder and RA/QA lead after engineering finds a field problem. Customer support wants language, operations wants a plan, and leadership wants to know what happens next.
The useful first move is not a label. It is a source-backed review packet that shows the problem, scope, public context, internal evidence, owner map, and open decisions.
Correction, removal, or recall checklist
| Packet section | What to capture |
|---|---|
| Trigger | Complaint, service trend, product failure, software issue, label issue, supplier issue, or customer communication request. |
| Source ledger | FDA recall overview, 21 CFR Part 806, Part 7/806 FAQ, recall guidance, and public recall or early-alert records. |
| Product scope | Device name, model, lot, software version, accessory, distribution scope, customer sites, and exposure questions. |
| Internal evidence | Complaint records, service logs, risk file, CAPA screen, supplier records, design history, labeling, IFU, and prior decisions. |
| Decision boundary | Open recall, correction, removal, reporting, customer communication, CAPA, risk, supplier, legal, and clinical decisions. |
What good looks like
A useful packet makes the next review meeting faster. It does not hide uncertainty; it names what is known, what was checked, what is not yet known, and who owns each decision.
It also prevents public FDA context from being mistaken for company-specific advice. FDA source pages can frame the question, but the company still needs qualified review of its facts.
Source ledger
What it can tell you
FDA's public overview of device recalls, corrections, removals, Part 7 context, and Part 806 correction/removal reporting context.
What it cannot decide
Whether one company's field problem is a recall, correction, removal, or reportable event.
What it can tell you
Current electronic Code of Federal Regulations text for reports of corrections and removals.
What it cannot decide
How the regulation applies to one device, one correction, one removal, one customer notice, or one field action.
What it can tell you
FDA FAQ context linking medical-device recalls, removals, corrections, Part 7, and Part 806 questions.
What it cannot decide
A company's final classification, reporting path, timing decision, or adequacy of a recall strategy.
What it can tell you
FDA guidance context about recall documentation, information FDA may use to evaluate recalls, and recall process considerations.
What it cannot decide
Whether one corrective action, removal, or field communication is adequate for a device-specific situation.
What it can tell you
Public recall and early-alert records that may frame product-family and field-action review questions.
What it cannot decide
Whether a specific product, lot, customer, or service event is affected.
Frequently asked questions
Does this checklist decide whether a device event is a recall?
No. It organizes FDA source context, product facts, and open questions. Recall, correction, removal, reporting, risk, customer, CAPA, and legal decisions remain with qualified company reviewers.
What should the team gather before the review meeting?
Gather the field-problem trigger, product scope, distribution scope, complaint and service records, risk-file links, supplier facts, source URLs, access dates, owner assignments, and open decisions.
Need a field-action source ledger?
Send the field problem, affected product family, and current review question. We can scope a source-backed correction/removal/recall checklist for qualified review.
Reader feedback
Useful pages should feed the next topic choices. Leave a signal or a short comment.