Method·September 16, 2026 · 3 min read

The two-year inspection clock is gone

For device establishments, the Federal Food, Drug, and Cosmetic Act guaranteed an inspection at least once every two years — until 2012, when FDASIA rewrote the interval into a risk-based schedule with no fixed number of years attached to any facility.

By Connor Griggs — Regulatory & Quality Strategist

For decades, a device manufacturer’s inspection interval was not a guess. The Federal Food, Drug, and Cosmetic Act named a number: every domestic establishment registered with FDA got inspected at least once every two years, without exception, without a risk model, without discretion. That number is not on the books anymore, and hasn’t been since 2012 — though it still shows up in quality manuals that talk about an inspection calendar the statute stopped keeping.

The interval Congress wrote into the statute itself

Before FDASIA, Section 510(h) of the FD&C Act — 21 U.S.C. § 360(h) — set the schedule directly: a device or drug establishment registered under FDA’s own registration requirements had to be inspected at least once in the two-year period beginning with the date of registration, and at least once in every two-year period after that. The statute made no distinction for a facility’s compliance record, its device’s risk class, or whether an accredited third party had already reviewed the same quality system that year. Every registered establishment ran on the same clock.

Section 705 tore the interval out and left a factor list

The FDA Safety and Innovation Act — Public Law 112-144, signed July 9, 2012 — amended Section 510(h) directly. Section 705, titled Risk-Based Inspection Frequency, struck the fixed two-year language for domestic establishments and replaced it with a mandate that FDA inspect according to a risk-based schedule built from each establishment’s known safety risks. The statute names the factors: the inherent risk of the device manufactured there, the establishment’s compliance history, the history and severity of recalls traceable to it, and — a line that describes MDSAP without naming it — the establishment’s participation in an international device audit program the United States participates in or recognizes. None of those factors resolves to a number of years. They resolve to a score FDA computes internally, one establishment at a time.

What FDASIA still requires: an accounting, not a calendar

Section 705 kept one hard requirement on FDA’s own side: an annual, public report on inspections of establishments registered under Section 510. FDA publishes it — the FDASIA Section 705 Annual Reports page tallies how many domestic and foreign establishments were inspected that year against how many are registered. That is an aggregate, after-the-fact accounting of what FDA did, not a forward schedule of what it will do at any specific address. A facility can read every report back to 2012 and still learn nothing about when its own next inspection is due, because the statute that used to answer that question was rewritten specifically to stop answering it.

The old rule promised an inspection by a date. The current rule promises only that FDA is watching risk, and will say so once a year, in the aggregate.

The practice

A quality team that treats “we haven’t been inspected in five years” as evidence of low risk, or as an overdue clock about to strike, is applying arithmetic to a section of the FD&C Act that no longer does arithmetic. Since July 9, 2012, no statute sets a specific facility’s next inspection date — that date is a function of FDA’s internal risk score, built from factors the statute names but does not weight publicly. What a specific facility’s inspection history suggests about its own risk standing is a judgment for the quality and regulatory professionals who hold that facility’s file, never a conclusion this post is drawing.

None of FDA Radar’s four sources — Federal Register notices, 510(k) clearances, device recalls, CDRH warning letters — carries an inspection schedule for any establishment; per what we monitor and how often, an inspection date has never been a fact this pipeline, or any monitor built the same way, could produce for a specific facility.

Regulatory intelligence, not regulatory advice. This post describes method and published FDA records as of its date; decisions about a specific device belong with your regulatory professional.

Practice
Emergency use isn't defined in Part 812
Method
The PMA clock starts at the last module
Practice
The Q-Sub that doesn't buy you more time
Method
Lapsed and revoked end an EUA differently
Practice
A recall strategy has a grade. openFDA doesn't.
Method
A granted De Novo becomes a predicate.
Practice
Least burdensome changes the ask, not the bar.
Method
The lab is accredited. Not the device.
Practice
Breakthrough is law. STeP is a guidance.
Practice
MDSAP replaces routine. Not for-cause.
Method
No field on a 510(k) says what it treats
Method
Discretion is a policy. Exclusion is a statute.
Practice
Designated by one office. Approved by another.
Method
MedSun sits beside MAUDE, not inside it
Practice
The five-unit device never gets a K-number
Practice
Meeting the criteria isn't a tracking order
Method
The PMA clock doesn't stop at approval
Practice
The K-number doesn't track today's device
Method
A MAUDE report proves it was filed
Practice
Not every MDR starts with the manufacturer
Method
Completed. Not terminated.
Practice
The device-ban list has three entries
Method
The UDI exception has its own deadline
Method
MDUFA VI is being negotiated in public
Practice
The inspection manual changed, not the rule
Method
The count Congress had to legislate
Practice
The small-business rate isn't retroactive
Method
A detention order has no docket to read
Practice
PMA approvals moved off the Federal Register
Method
A citizen petition names names
Practice
A market withdrawal isn't a recall
Method
Not every device letter comes from CDRH
Practice
Closed on one device. Open on the rest.
Method
No IDE is confirmed until the PMA is
Practice
The remedial-action call sets the clock
Method
Jurisdiction is a letter, not a field
Practice
An address is not a footprint
Method
The final rule that isn't final yet
Practice
The special controls aren't in the record
Method
Exempt from GMP. Not from complaints.
Practice
The notify list isn't the shortage list
Method
A constraint can't be skipped. A script can.
Practice
No cron sends this. A person does.
Method
Corrected, not rewritten
Practice
Quiet is a finding, not a default
Method
The summary is public. The statement isn't.
Practice
A competitor's 513(g) leaves no trace
Practice
An empty response field proves nothing
Method
A petition is public. Its outcome isn't.
Practice
The panel is a category, not a meeting
Method
An accessory carries its own classification
Method
A TPLC report is a category, not a device
Practice
A 522 order is a question, not a verdict
Method
A PCCP change leaves no new record
Practice
Not every signal becomes a recall
Method
eSTAR did not remove the acceptance check
Practice
An early alert has no recall number yet
Practice
A consent decree isn't a database row
Method
The record has no cybersecurity field
Practice
Classification Change is not one event
Method
Publication date is not effective date
Method
One event. Many recall numbers.
Practice
Quantity is a sentence, not a number
Practice
How a firm told you is a field too
Method
A RIN outlives the document number
Method
The docket ID is not the comments
Practice
The 510(k) record doesn't name the predicate
Practice
The 510(k) FDA didn't review first
Method
The letter FDA doesn't have to post
Practice
Cleared doesn't say which track it took
Method
The clock stops. The calendar doesn't.
Method
Why a guessed match never reaches you
Practice
The standards list never names a device
Method
The guidance isn't in the Federal Register.
Practice
Filtered. Not discarded.
Method
There are two recall databases, not one
Practice
Breakthrough status is confidential by law
Practice
One MAUDE report is not one malfunction
Method
A supplement number is not a track
Method
Cleared is not approved
Practice
Nationwide doesn't mean your building
Practice
Not every correction reaches FDA
Method
Registered. Not reviewed.
Method
Contact ODE is not a pathway
Practice
Almost no recall is FDA-mandated
Method
FDA's device names read like a card catalog
Practice
openFDA is free. It is not unlimited.
Method
GUDID stores the model. Not the box.
Practice
Detention doesn't need a warning letter
Method
A Class I device, a Class I recall
Practice
21 CFR 820 didn't move. Its contents did.
Method
The product code that doesn't exist yet
Practice
The classification posts. The 483 behind it doesn't.
Method
A recall has three dates, and the pipeline had to pick one
Practice
The count is real. The rate is not.
Method
The firm on the record is not the firm on the box
Practice
Low confidence is an instruction, not a hedge
Method
The same company, spelled three ways
Practice
A device that was never a medical device
Method
FDA's warning letters, addressed by column number
Practice
Your regulation has a decimal. FDA's watch doesn't.
Method
Three letters is too short to search for
Practice
Most warning letters never close
Method
The guidance that skipped the draft
Practice
Ongoing, as of when?
Method
The least interesting fact in a 510(k)
Practice
No recall arrives with a product code attached
Practice
The deadline that doesn't email you
Method
The warning letter has two dates
Method
How to monitor FDA without drowning
Practice
Your predicate was recalled. Now what?
Method
Why no item reaches you without a human