TL;DR
- FDA runs two broad categories of inspection: routine surveillance inspections, done on a general schedule to check ongoing compliance, and for-cause inspections, triggered by a specific reason to suspect a problem (FDA Investigations Operations Manual (IOM), Chapter 5).
- A for-cause inspection can be triggered by a consumer complaint, an adverse event report, a prior inspection finding, information from a whistleblower, or a referral from another agency or a foreign regulator.
- Both inspection types can result in a Form 483 or a Warning Letter — the trigger doesn't change what FDA can cite, only why the investigator showed up.
- Surveillance inspection frequency for drug manufacturers is risk-based under the FDA Safety and Innovation Act (FDASIA) of 2012, not a fixed calendar interval.
What Triggers an FDA For-Cause Inspection?
Is a for-cause inspection worse than a routine one? Not automatically — but it does mean FDA already has a specific reason to look, which changes the tone and scope of the visit before an investigator even walks in the door.
What Counts as "Routine" in FDA's Inspection System?
FDA's Investigations Operations Manual describes surveillance inspections as the agency's general compliance-monitoring tool — covering firms on a periodic basis regardless of any known problem, to confirm ongoing conformance with CGMP and other applicable regulations (FDA IOM, Chapter 5). For drug manufacturers specifically, the FDA Safety and Innovation Act of 2012 replaced the old fixed two-year inspection cycle with a risk-based schedule, meaning how often a facility gets a routine visit depends on factors like compliance history, product risk, and manufacturing complexity, not a flat calendar rule.
What Counts as "For-Cause"?
A for-cause inspection happens because FDA has a specific, articulable reason to believe there's a problem at a facility, rather than because the facility is simply due for a periodic check. Common triggers include:
- A consumer or healthcare provider complaint about a specific product
- An adverse event report submitted through FDA's reporting systems
- Findings from a prior inspection that FDA wants to verify were corrected
- A referral from a state regulator, another federal agency, or a foreign regulatory authority
- Import-related concerns, such as a pattern of refused shipments
- Information from a whistleblower or a competitor
Because the investigator already has a specific concern in mind, a for-cause inspection is often narrower and more targeted than a routine surveillance visit, focused on the systems and records most likely to confirm or rule out the reported issue.
Does the Trigger Change What FDA Can Cite?
No. Once an investigator is on-site, whether the visit started as routine or for-cause, they can document any violation they observe, not just the one that prompted the visit. A for-cause inspection triggered by a single complaint about mislabeling can still turn up an unrelated CGMP data-integrity finding if the investigator sees one. The outcome document — a Form 483 listing observations, potentially followed by a Warning Letter if FDA's headquarters review agrees the findings are significant — works the same way regardless of which type of inspection produced it.
Routine vs. For-Cause, Side by Side
| Routine Surveillance | For-Cause | |
|---|---|---|
| Trigger | Periodic schedule, risk-based | Specific complaint, report, or referral |
| Scope | General compliance check | Often narrower, focused on the reported concern |
| Can still find unrelated issues | Yes | Yes |
| Possible outcomes | Form 483, Warning Letter, or no findings | Form 483, Warning Letter, or no findings |
| Advance notice | Sometimes announced in advance for domestic sites | Often unannounced |
FAQ
Does a for-cause inspection always mean someone reported us?
Not necessarily by name — the source could be an adverse event report filed by a patient or provider, a pattern FDA noticed in import data, or a referral from another regulator. FDA generally does not disclose the specific source of a for-cause trigger during the inspection.
Can a routine inspection turn into something more serious mid-visit?
Yes. If an investigator finds evidence during a routine inspection that suggests a more serious or unrelated problem, they can expand the scope of that visit or recommend a follow-up for-cause inspection.
Is a for-cause inspection announced in advance?
Often not. For-cause inspections, especially those following a complaint or adverse event report, are frequently unannounced, while some routine surveillance inspections at domestic facilities may be scheduled with advance notice depending on the program.
Does getting a for-cause inspection affect our routine inspection schedule?
It can. A for-cause inspection that finds significant problems typically affects a firm's compliance history, which is one of the risk factors FDA uses to set the timing of future routine surveillance inspections under its risk-based schedule.
Related reading
- How to read your FDA inspection classification: NAI vs. VAI vs. OAI
- What's the difference between a Form 483 and an FDA Warning Letter?
- What Are the Six Rungs of FDA's Enforcement Escalation Ladder?
Search the Warning Letter database →
Sources: FDA Investigations Operations Manual (IOM), Chapter 5, FDA: FDASIA Overview, 21 CFR Part 211 (eCFR). Byline: The Argus Regulatory Analysis Team. Published 2026-07-16.