Practice·September 13, 2026 · 3 min read

Least burdensome changes the ask, not the bar.

Sponsors invoke ‘least burdensome’ as leverage for a lighter review. The statute defines it the other way — a limit on what FDA may ask for, with its own line, written into the law, that the underlying standard does not move.

By Connor Griggs — Regulatory & Quality Strategist

“Just argue least burdensome” gets said in submission strategy meetings the way “just ask for an extension” gets said about deadlines — as if the phrase itself were a lever. It is a real statutory term, and it does real work. It does not do the work most people reach for it to do.

What the statute actually constrains

Section 513(i)(1)(D) of the FD&C Act (21 U.S.C. 360c(i)(1)(D)) governs what FDA may ask for in a 510(k) review of a device with differing technological characteristics from its predicate:

“Whenever the Secretary requests information to demonstrate that devices with differing technological characteristics are substantially equivalent, the Secretary shall only request information that is necessary… In making such request, the Secretary shall consider the least burdensome means of demonstrating substantial equivalence and request information accordingly.”

The parallel provision for PMAs — Section 515(c)(5) (21 U.S.C. 360e(c)(5)) — binds FDA the same way when it requests additional information toward a reasonable-assurance-of-safety-and-effectiveness finding. Both provisions constrain a request. Neither touches the finding it supports. The statute says so itself, in nearly identical language attached to each: nothing in the 510(k) provision alters the standard for determining substantial equivalence, and nothing in the PMA provision “alters the standards for premarket approval of a device.” That sentence is not guidance color. It is in the law, next to the least-burdensome instruction, on purpose.

Three statutes built the current version

“Least burdensome” entered the FD&C Act in 1997, through Section 205 of the FDA Modernization Act (Public Law 105-115) — language about collaborative determinations of device data requirements, aimed at early-stage disagreements over what a device would need to show. FDASIA revisited it in 2012: Section 602, titled “Clarification of Least Burdensome Standard,” is where Congress went back in and pinned down what “necessary” means — the minimum information that would support the determination in question, not the minimum information a sponsor would prefer to supply. The 21st Century Cures Act added an institutional layer in 2016: Section 3058 required every CDRH reviewer working premarket submissions to be trained on what least burdensome means, required the CDRH Ombudsman to audit that training within eighteen months and interview industry about their actual experience of it, and required FDA to publish the findings and report them to Congress. Congress treated inconsistent application as a compliance problem worth auditing, not a phrase worth leaving to interpretation.

The argument that actually works

A least-burdensome argument that holds up names the specific determination FDA is trying to reach — substantial equivalence on a particular technological characteristic, or reasonable assurance for a particular condition of use — and shows that a smaller or different dataset reaches it. “This bench test is sufficient because it addresses the same failure mode as the requested clinical data” is a least-burdensome argument. “A full study would be expensive and slow” is not one; it never touches what the statute actually asks FDA to consider. The provision aims at the request, not the reviewer’s sympathy.

The practice

Treat least burdensome as a targeting question, not a closing argument: for each piece of information a reviewer asks for, what determination does it actually feed, and does a lighter version of it still feed that determination completely? That question gets answered against your own device and your own file — the accepted-evidence record for a comparable clearance is not public, and FDA Radar’s clearance data stops at what FDA discloses: K-number, applicant, product code, and decision, not the underlying submission. This is regulatory intelligence and method, never regulatory advice about what a specific reviewer will accept from a specific file; that argument gets built by the regulatory professional who has to defend it.

Method
A granted De Novo becomes a predicate.
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