Method·September 15, 2026 · 4 min read

The PMA clock starts at the last module

FDA lets a PMA or HDE applicant file in FDA-agreed modules instead of one complete application — but the statutory 180-day review clock, and the acceptance and filing decisions that start it, all run from the date the last module arrives, not the first.

By Connor Griggs — Regulatory & Quality Strategist

A modular Premarket Approval Application sounds like it should make a review start sooner — file the parts you have ready, keep working on the rest, let FDA get a head start. Read the guidance and the regulation together, and the opposite is closer to true. Nothing about a modular PMA is filed, in the sense that starts FDA’s statutory clock, until the single module that finishes it arrives.

A shell, then modules, then one application

FDA’s modular review guidance — finalized January 13, 2025, and since that revision available to Humanitarian Device Exemptions as well as PMAs — lets a sponsor and FDA agree in advance on a shell: an outline naming each module the application will eventually contain and what each one will hold. That shell gets an informal look from FDA to confirm modular review even fits the device before anything is submitted under it. From there, modules arrive over time, and FDA reviews each as it comes in against its own clock. None of that is a Refuse to Accept or Refuse to File review, because none of it is a PMA yet — it is pieces of one, arriving on a schedule both sides agreed to.

The application starts existing when the last piece does

21 CFR 814.42 governs filing a PMA, and a modular submission only reaches that section once the final module is in hand. That receipt is the moment FDA converts the accumulated modules into a single original application and runs the acceptance and filing review that every other PMA gets at the start, not partway through. The filing date the agency assigns is the date of the last module, full stop — not the date the shell was agreed, not the date the first module went in, not an average or a midpoint across however many modules a given device needed.

That filing date is the one 21 CFR 814.40 and 21 U.S.C. § 360e(d) both build on. FDA’s statutory 180-day period to act on a PMA — approval order, approvable letter, not approvable letter, or denial — runs from the date of filing. A modular application that spent a year in productive, module-by-module review with FDA has, procedurally, not started that clock for one day of it. The 180 days begin when the last module does, exactly like an ordinary, unmodular PMA that showed up complete on day one.

Where the confusion actually costs something

The trap is not misunderstanding modular review’s existence. It is treating a year of module-by-module engagement as review time already spent, and expecting the 180-day clock to reflect that. It doesn’t, and the guidance does not restructure21 CFR 814.40 to say otherwise — the modules change how the content of the application gets assembled and reviewed piece by piece; they do not change what “filed” means or when it happens. A sponsor tracking a modular PMA’s timeline against an internal launch date needs the actual filing date FDA assigned at the last module, not the date the shell negotiation finished or the date the first module was accepted.

The practice

Confirm the filing date directly rather than inferring it from when module submissions began. FDA Radar’s own pipeline has nothing to offer here either way: its four sources are Federal Register notices, 510(k) clearances, device recalls, and CDRH warning letters — no PMA or HDE feed at all, modular or otherwise. A shell agreement, a module receipt, and the eventual filing date of a modular application never reach this product, or most monitoring built the same way. That timeline belongs to the sponsor and FDA, tracked directly, for as long as it takes the last module to arrive. This is a description of how modular review’s clock is structured, never regulatory advice about when a specific application will, or should, be filed.

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
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