FDA Inspections
FDA For-Cause Inspection
A for-cause inspection happens because FDA has a reason to look at something specific. It is focused on that issue, may arrive unannounced, and moves quickly toward the records that explain what went wrong and what you did about it.
At a Glance
- Conducted by
- FDA investigators
- Notice
- May be unannounced
- Prompted by
- Specific information, such as complaints, MDRs, recalls, trade complaints or prior findings
- Framework
- An inspection type under Compliance Program 7382.850
- Possible outcome
- Observations on Form 483; NAI, VAI or OAI classification
What It Is
Compliance Program 7382.850 lists for-cause as a distinct inspection type. Unlike surveillance, it starts from a question FDA already has: a pattern of adverse event reports, a recall, a trade complaint, or something left unresolved from an earlier inspection.
The investigator arrives knowing what prompted the visit and goes to the records that bear on it: complaint and MDR files, investigations, CAPAs, design and process records for the affected product, and any field actions. The inspection can expand if the trail leads into other parts of the system.
For-cause inspections still happen when a firm participates in MDSAP. FDA accepts MDSAP audit reports in place of routine surveillance inspections, not for-cause ones.
Who Conducts It
FDA investigators conduct it, sometimes with specialists in the technology or failure involved. Domestic for-cause inspections may begin without notice, with a Form 482 presented on arrival.
Because the issue is specific, the people who handled it (complaint investigators, the MDR decision maker, the CAPA owner, the design or process engineer) are the ones who'll be interviewed. Their accounts need to match the records and each other.
What Triggers It
- Complaint or Medical Device Report patterns that suggest a device problem
- A recall, correction or removal, or a failure to report one
- Trade complaints from competitors, customers, health professionals or current and former employees
- Unresolved findings from a prior inspection
- Information FDA receives from other sources, such as other regulators
What They Look At
The Triggering Issue
Everything FDA knows about the problem, and whether your records show you knew it too, investigated it and acted.
Complaint Handling and MDR Decisions
Whether complaints were received, evaluated and investigated, and whether reportable events were reported under Part 803, with a documented rationale for each decision.
Corrections and Removals
Whether field actions were assessed for reporting under Part 806, and whether actions that weren't reported have records explaining why.
CAPA and Root Cause
Whether the investigation reached a real root cause, whether the corrective action addressed it, and how effectiveness was verified.
Design and Process Records for the Affected Product
Design history, risk analysis, process validation and changes that could explain the failure.
Management Awareness
When leadership learned of the problem, what it decided, and whether resources followed the decision.
How to Prepare
- 01
Build a Timeline of the Issue
From first signal to today: complaints, reports, decisions, investigations, field actions and CAPAs, each tied to its record.
- 02
Check Every Reportability Decision
Review MDR and correction-and-removal decisions for the affected product. Each one needs a documented rationale that someone can explain.
- 03
Test the Root Cause
Make sure the investigation is evidence-based, the corrective action matches it, and effectiveness was verified with data rather than a closure date.
- 04
Choose and Prepare Your Spokespeople
Pick the people closest to the issue, prepare them together, and check that their accounts match the records.
- 05
Fix What You Find Now
If your review turns up gaps, open CAPAs and start corrections before the inspection rather than promising them afterward.
Common Pitfalls
- Late or missing MDRs where the complaint file shows the firm knew of the event.
- Root cause investigations that stop at 'operator error' or 'isolated incident' without evidence.
- Different people telling different versions of the same event.
- Field actions treated as product improvements with no documented assessment for Part 806 reporting.
- Starting the fix only after the investigator arrives, so the record shows reaction instead of control.
How QMSAdvisor Helps
- A targeted review of complaint, MDR, CAPA and field action records for the affected product, with advisor-reviewed findings that cite each source.
- An issue timeline reconstructed from the documents in your library, so gaps between events and records surface before FDA finds them.
- A focused FDA Inspection Simulator session on the triggering issue, with interview scoring that flags inconsistent or speculative answers.
- If a Form 483 follows, the tracker starts the 15-business-day countdown and the composer helps draft a response tied to evidence.
FDA Inspection Readiness (CP 7382.850)
FDA device inspection preparation built around Compliance Program 7382.850 and its risk-based approach.
Form 483 Response and Remediation
A structured, evidence-backed response to each Form 483 observation, and the remediation behind it.
CAPA System Remediation
Fixing a CAPA system auditors keep citing: the procedure, the records, root cause, effectiveness and backlog.
Warning Letter Response and Remediation
A thorough, systemic response to an FDA warning letter, and the remediation and updates that follow it.
Standards and Regulations Involved
Questions About the FDA For-Cause Inspection
How do we know an inspection is for-cause?
The investigator's opening requests usually make the focus clear, because they go straight to a product, event or record set. You can ask about the scope at the opening; even if the answer is brief, the requests that follow will tell you.
Does MDSAP participation prevent a for-cause inspection?
No. FDA accepts MDSAP audit reports in place of routine surveillance inspections, but not in place of for-cause or pre-approval inspections.
Should we stop shipping the affected product?
That's a product and regulatory decision that depends on the risk involved, and it may raise correction and removal questions of its own. Make it deliberately, document the risk assessment behind it, and get qualified regulatory and legal input.
Can a for-cause inspection lead to a warning letter?
It can, if FDA finds significant violations and classifies the inspection OAI. A thorough, evidence-backed response to any Form 483, received within 15 business days after the inspection closes, is your opportunity to show the issue is being addressed.
Related Audits and Inspections
FDA Compliance Follow-Up Inspection
An FDA inspection verifying that corrective actions promised after earlier findings are done and working.
FDA Baseline Surveillance Inspection
FDA's comprehensive surveillance inspection of your quality system under Compliance Program 7382.850.
Mock Audit and Mock Inspection
A realistic practice inspection, with an advisor playing the FDA investigator, before the real one arrives.
Primary Sources
- FDA Compliance Program 7382.850: Inspection of Medical Device Manufacturers (opens in a new tab)
- FDA: Inspection Classifications (opens in a new tab)
- FDA: About Warning and Close-Out Letters (opens in a new tab)
- eCFR: 21 CFR Part 803 (Medical Device Reporting) (opens in a new tab)
- eCFR: 21 CFR Part 806 (Corrections and Removals) (opens in a new tab)
Request an Assessment
Prepare for Your FDA For-Cause Inspection With an Advisor
Tell us what's coming and when, and an advisor will scope readiness work around it. Please don't send confidential documents yet: secure upload is set up after onboarding.
