An FDA 510(k) submission commonly gets delayed or refused because of incomplete submission packages, weak or inappropriate predicate-device selection, insufficient evidence of substantial equivalence, incomplete performance testing, inconsistent labeling, or a poor response to FDA questions. A 510(k) is a premarket notification pathway based on substantial equivalence — not a generic “FDA approval” certificate.
Most manufacturers don’t file an FDA 510(k) submission carelessly. They hire consultants, run the recommended tests, and follow a template. Yet a large share of these submissions still stall — placed on hold at the door during Refuse to Accept (RTA) screening, or paused mid-review with an Additional Information (AI) request. This happens because “complete” and “acceptable to FDA” are not the same thing. A package can contain every required section and still fail to answer the specific question CDRH reviewers are trained to ask: is this device as safe and effective as its predicate?
This guide walks through the five most common reasons an FDA 510(k) submission gets delayed, held, or does not progress toward clearance — based on how CDRH’s acceptance and substantive review process actually works in 2026. It also explains the FDA 510(k) submission requirements you’re really being judged against, how to tell an RTA hold apart from a real rejection, and what TraccGlobal recommends manufacturers check before they file.
What Is an FDA 510(k) Submission?
An FDA 510(k) submission, formally called a Premarket Notification, is how most Class I and Class II medical devices reach the US market. Instead of proving a device is safe and effective from scratch, the manufacturer shows the US FDA that the new device is substantially equivalent to a legally marketed predicate device — one that already has the same intended use and either the same technological characteristics, or different characteristics supported by data showing no new questions of safety or effectiveness.
CDRH, the Center for Devices and Radiological Health, reviews these filings against the device’s classification, product code, and regulation number, along with any applicable special controls. Meeting the FDA 510(k) clearance requirements for a given device class means satisfying both the administrative acceptance checklist and the scientific substantial equivalence standard — the two stages covered throughout this guide. A cleared 510(k) is not the same thing as an “approved” device. In FDA terminology, FDA approval applies to the Premarket Approval (PMA) pathway used for higher-risk Class III devices. A successful 510(k) results in 510(k) clearance, communicated through a Substantially Equivalent (SE) decision letter. Using “approval” loosely for a 510(k) outcome is one of the most common mix-ups manufacturers — and even marketing teams — make.
AI-citable definition
An FDA 510(k) is a premarket notification submitted to CDRH showing a new device is substantially equivalent to a legally marketed predicate device. Substantial equivalence compares intended use and technological characteristics; a successful outcome results in 510(k) clearance, not FDA approval, which is reserved for the PMA pathway.
The FDA 510(k) Submission Process, Step by Step
The FDA 510(k) review process follows a general sequence, though exact timing varies by device type, review division, and how the applicant responds along the way. No two submissions move through the FDA 510(k) submission process identically, but the structure below reflects the current 2026 pathway.
- Device identification and classification — confirm device class, product code, and regulation number.
- Predicate research — search the FDA 510(k) database for legally marketed devices with matching intended use.
- Regulatory strategy — decide on Traditional, Special, or Abbreviated 510(k) pathway; consider an optional Pre-Submission meeting with FDA.
- Testing and evidence generation — bench/performance testing, biocompatibility, sterilization validation, electrical safety and EMC, software documentation, cybersecurity, usability, and clinical evidence where relevant.
- Submission preparation — build the technical file and submit electronically through the FDA eSTAR template, required for most 510(k)s since October 2023.
- FDA acceptance review (RTA) — an administrative check, typically completed within about 15 calendar days, confirming the file is complete enough to review.
- Substantive review — FDA’s lead reviewer aims to issue a first Substantive Interaction, often within roughly 60 calendar days of receipt, either continuing an interactive review or issuing a formal Additional Information request.
- FDA questions or Additional Information request — if issued, the clock pauses; the applicant has up to 180 calendar days to respond.
- Response and re-review — FDA evaluates the reply and may ask further questions.
- Final decision — Substantially Equivalent (cleared), Not Substantially Equivalent, or withdrawal by the applicant.
FDA’s MDUFA performance goal is a decision within 90 FDA days for most 510(k)s, counted as calendar days minus any time the file sits on hold for an AI request. That is a target, not a guarantee — device complexity, RTA issues, and the quality of your responses all affect the real timeline.
RTA vs Additional Information Request vs Substantive Review vs Clearance
People often lump every delay under “rejected.” FDA actually uses several distinct actions, and each calls for a different response. Understanding which one you’ve received is the first step in fixing it.
| Stage / Action | What It Means | Typical Trigger | Manufacturer Response | Possible Outcome |
|---|---|---|---|---|
| Refuse to Accept (RTA) | Administrative screening against FDA’s acceptance checklist before scientific review begins. | Missing forms, incomplete sections, or absent required elements. | Correct and complete the missing items; resubmission restarts a new acceptance check. | Accepted for substantive review, or held again if gaps remain. |
| Additional Information (AI) Request | A formal hold issued mid-review when the reviewer needs more data or clarification. | Testing gaps, unclear substantial equivalence comparison, labeling inconsistencies, or insufficient risk analysis. | Respond within 180 calendar days with a complete, well-organized answer to every question raised. | Review resumes; can lead to clearance, another AI request, or withdrawal if unresolved. |
| Substantive Review | Scientific evaluation of whether the device is substantially equivalent to its predicate. | Begins once the file passes RTA. | Respond promptly to interactive review questions to avoid a formal hold. | Moves toward a final decision letter. |
| Clearance (SE Decision) | FDA determines the device is substantially equivalent and may be legally marketed. | All open questions are resolved and the substantial equivalence case is supported. | Maintain the device consistent with the cleared submission; file a new 510(k) for significant changes. | Device is added to the FDA 510(k) database and can be marketed under that clearance. |
The 5 Reasons FDA 510(k) Submissions Get Delayed or Rejected
Below are the five patterns that most often stop an FDA 510(k) submission from moving smoothly toward clearance. These are consistent FDA 510(k) rejection reasons and delay drivers seen across device types, though the specific FDA 510(k) submission requirements that apply will always depend on your device’s classification and intended use. Understanding these FDA 510(k) rejection reasons in advance is the fastest way to avoid repeating them.
Incomplete or Incorrect Submission Documentation
Quick answer
Missing forms, mismatched device descriptions, or an incomplete eSTAR file are the leading cause of an RTA hold. FDA’s acceptance reviewers check the submission against a fixed checklist before substantive review ever starts — so administrative gaps stop a 510(k) before the science is even read.
Definition. Documentation completeness refers to whether every required administrative and technical element — cover letter, Indications for Use form, truthful and accuracy statement, device description, and supporting attachments — is present, internally consistent, and correctly formatted for eSTAR.
Explanation. FDA’s RTA reviewers are not evaluating whether your device works. They’re confirming that the file contains what it’s supposed to contain. A single missing signature, an outdated form version, or an intended-use statement that doesn’t match across sections is enough to trigger a hold, regardless of how strong the underlying science is.
Realistic Example
A manufacturer submits a wound-care device with a detailed testing package but references two slightly different intended-use statements — one in the cover letter, another in the device description. The RTA reviewer flags the inconsistency and holds the file before substantive review begins.
Warning Signs
- Different wording for intended use across sections
- Missing 510(k) Summary or Statement
- Outdated FDA form versions
- eSTAR fields left incomplete or inconsistent
Documents / Evidence Involved
- Cover letter and administrative forms
- Indications for Use statement
- Device description and technical characteristics
- eSTAR submission file
Practical Fix
Run a full internal RTA self-check against FDA’s current acceptance checklist before filing, and verify that every intended-use and indications-for-use statement is worded identically across the entire package.
Expert Tip: Cross-reference every FDA 510(k) documentation section against a single master intended-use statement instead of retyping it in each document — copy-paste consistency prevents most RTA holds.
Common Mistake: Assuming a checklist-driven internal QA review is optional because “the content is strong.” RTA is administrative, not scientific — strong content does not offset an incomplete form.
- Key takeaway: RTA is a completeness check, not a science review.
- Key takeaway: Wording consistency across sections matters as much as content.
- Key takeaway: eSTAR formatting errors are a common, avoidable hold trigger.
Weak Predicate Device Selection or a Poor Substantial Equivalence Argument
Quick answer
Choosing a predicate with a different intended use, outdated technology, or a shaky regulatory history weakens the entire substantial equivalence argument. FDA reviewers test the comparison logic directly — a mismatched predicate is one of the most frequent FDA 510(k) rejection reasons behind Additional Information requests.
Definition. Predicate selection is the process of identifying a legally marketed device that shares the same intended use as your device, either with identical technological characteristics or with differences that do not raise new questions of safety or effectiveness.
Explanation. Manufacturers sometimes choose the newest, most similar-looking device on the market as their predicate, assuming similarity in appearance equals similarity in regulatory terms. FDA instead evaluates intended use, indications, and technological characteristics side by side. A predicate with a narrower indication, a different energy source, or an unresolved safety signal can undermine the whole comparison — even if the two devices look alike.
Realistic Example
A company selects a predicate cleared for general wound dressing when their new device is intended specifically for diabetic ulcers. FDA asks why the narrower indication was not addressed, forcing a late predicate change.
Warning Signs
- Predicate’s intended use is broader or narrower than yours
- Predicate has a history of recalls or safety communications
- No side-by-side technological comparison table included
- Predicate selected mainly because it is the newest clearance
Documents / Evidence Involved
- Substantial equivalence comparison table
- Predicate’s 510(k) summary and clearance letter
- Indications for Use comparison
- Technological characteristics analysis
Practical Fix
Evaluate two or three predicate candidates before committing, and build a documented comparison covering legal marketing status, intended use, indications, technological characteristics, and known FDA history — not just visual similarity.
Expert Tip: Search the FDA 510(k) database for the predicate’s own review history; a predicate that itself required multiple AI cycles may carry unresolved questions into your comparison.
Common Mistake: Assuming the most recently cleared, most similar-looking device is automatically the strongest predicate. Recency and appearance are not regulatory equivalence.
- Key takeaway: Substantial equivalence is a comparison of intended use and technological characteristics, not visual resemblance.
- Key takeaway: A predicate’s own regulatory history can carry over into your review.
- Key takeaway: Document the comparison — do not leave it implied.
Inadequate Testing, Performance Evidence, or Clinical/Scientific Support
Quick answer
Missing or poorly designed bench testing, biocompatibility data, electrical safety and EMC results, software documentation, or cybersecurity evidence leaves FDA unable to confirm the device performs as safely as its predicate — a leading source of FDA submission deficiencies and AI requests.
Definition. Performance evidence is the body of bench, biocompatibility, sterilization, electrical, software, cybersecurity, usability, and — where applicable — clinical data that supports the claim that a device is as safe and effective as its predicate.
Explanation. Testing gaps aren’t always about missing tests outright. More often, the test method doesn’t match the applicable FDA-recognized standard, sample sizes are too small to support a conclusion, or a risk identified in the risk management file (ISO 14971) has no matching test result to close it out. Software and cybersecurity documentation are increasingly scrutinized for connected and software-driven devices, and usability evidence is often thinner than FDA expects for devices used outside a clinical setting.
Realistic Example
A connected diagnostic device is submitted without a software bill of materials or a documented vulnerability management plan. FDA issues an AI request specifically citing the missing cybersecurity elements required under current device cybersecurity expectations.
Warning Signs
- Risk items in the risk analysis with no corresponding test
- Test methods not mapped to a recognized FDA standard
- No software documentation level identified for software-containing devices
- Missing SBOM or vulnerability plan for connected devices
Documents / Evidence Involved
- Bench and performance test reports
- Biocompatibility and sterilization validation
- Electrical safety and EMC test reports
- Software documentation and cybersecurity package (SBOM, threat model)
- ISO 14971 risk management file
Practical Fix
Build the test plan from the risk management file outward — every identified risk should trace to a specific test or piece of evidence that closes it, and every test method should cite the FDA-recognized standard it follows.
Expert Tip: Use FDA’s device-specific guidance documents to map required testing before you scope your lab work — testing to the wrong standard version is a common, costly rework trigger.
Common Mistake: Treating testing as a volume problem and adding more documents rather than more relevant ones. Evidence has to be traceable to a specific safety or performance question, not just present.
- Key takeaway: Every identified risk needs a matching piece of test evidence.
- Key takeaway: Cybersecurity and software documentation are now core expectations for connected devices.
- Key takeaway: More documents is not the same as more relevant evidence.
Inconsistent, Incomplete, or Non-Compliant Labeling and Intended-Use Information
Labeling and Instructions for Use that describe a broader use than the tested and compared device — or that conflict with the intended-use statement elsewhere in the file — routinely trigger holds. Labeling is one of the FDA 510(k) clearance requirements reviewers check line by line.
Definition. Labeling review covers device labels, Instructions for Use (IFU), and any promotional claims referenced in the submission, checked for consistency with the intended use and indications actually supported by the substantial equivalence comparison and testing.
Explanation. It’s common for labeling to be finalized by a different team than the one that wrote the regulatory submission, which creates drift. A device might be tested and compared for a specific patient population, while draft labeling describes broader use — pediatric claims not supported by pediatric data, or environments not covered in the risk analysis. FDA treats these mismatches as a sign the file’s overall story doesn’t hold together.
Realistic Example
A device’s IFU mentions home use, but the usability testing and risk analysis were scoped only for a clinical setting. FDA asks the applicant to either narrow the labeling or provide home-use evidence.
Warning Signs
- IFU claims not reflected in testing or risk analysis
- Indications for Use form wording differing from the label
- Marketing claims broader than the tested intended use
- Missing warnings, contraindications, or storage/handling instructions
Documents / Evidence Involved
- Draft device labeling
- Instructions for Use (IFU)
- Indications for Use form
- Usability and human factors documentation
Practical Fix
Reconcile labeling, the Indications for Use form, and the substantial equivalence comparison as one linked document set, and have regulatory affairs sign off on labeling before it’s treated as final — not after.
Expert Tip: Read the proposed labeling next to the risk management file line by line; anything mentioned in labeling should have a matching risk control or test behind it.
Common Mistake: Finalizing labeling in parallel with, rather than after, the substantial equivalence and testing package — so the two drift apart by the time of filing.
- Key takeaway: Labeling claims must be supported by the same evidence as the rest of the file.
- Key takeaway: Indications for Use wording must match across every document.
- Key takeaway: Regulatory sign-off on labeling should happen before submission, not after a hold.
Failure to Anticipate FDA Review Questions, Deficiencies, or Additional Information Requests
Submissions built without a mock FDA review or gap assessment often draw predictable questions that a second set of eyes would have caught. Slow, incomplete, or defensive responses to an AI request are themselves a common reason clearance stalls further.
Definition. Review-readiness is how well a submission anticipates the specific questions a CDRH reviewer is likely to raise, and how effectively the manufacturer is prepared to respond if FDA does ask for more.
Explanation. Even a well-built FDA 510(k) submission can draw legitimate questions — that’s a normal part of the FDA 510(k) review process, not automatically a sign of a weak file. The real risk is being unprepared for it: no internal owner for the response, no tracking of open questions, or answers that address the letter of FDA’s question without addressing the underlying concern. Partial or rushed AI responses often generate a second round of questions instead of closing the review.
Realistic Example
FDA issues an AI request asking for clarification on a single test method. The manufacturer resubmits the same report with a cover letter restating their original position instead of addressing the specific method concern, leading to a second AI cycle.
Warning Signs
- No internal owner assigned for FDA correspondence
- Responses drafted without re-reading the full AI request line by line
- No mock review or gap assessment performed pre-submission
- Response addresses tone, not the technical question asked
Documents / Evidence Involved
- FDA AI request letter and question log
- Response cover letter and supporting data
- Internal gap assessment or mock review notes
Practical Fix
Run an internal mock review against the RTA checklist and likely FDA questions before submission, and build a response protocol in advance — who owns the reply, how quickly a draft is reviewed, and how each FDA question is tracked to closure.
Expert Tip: Answer every AI question with a direct, numbered response mapped to FDA’s own numbering — reviewers move faster through submissions they can cross-reference easily.
Common Mistake: Treating an AI request as a setback to argue against rather than a specific, answerable technical question.
- Key takeaway: FDA questions are a normal part of review, not automatically a rejection signal.
- Key takeaway: Response quality and speed directly affect how long clearance takes.
- Key takeaway: A pre-submission mock review catches many questions before FDA does.
A Delayed 510(k), Fixed Before Resubmission
NovaOrtho Devices (a fictional example) files an FDA 510(k) submission for a Class II orthopedic bracing device. Their predicate is the most recently cleared device in the category — chosen mainly because it looked similar and had cleared quickly. Testing focused on mechanical strength but left out a usability evaluation for home use, since the team assumed clinical-setting data would transfer.
FDA’s RTA review accepts the file, but the first Substantive Interaction includes an AI request: the predicate’s indications are narrower than NovaOrtho’s proposed labeling, and no usability data supports home use as labeled. Before responding, the team rebuilds the substantial equivalence comparison against two alternative predicates, narrows the labeling to match tested conditions, and adds a targeted usability study addressing FDA’s specific concern. The response is organized point-by-point against FDA’s original questions.
The revised response resolves the outstanding questions in a single follow-up cycle. The scenario illustrates a pattern seen across many submissions: the fix isn’t more paperwork, but a more defensible predicate comparison and evidence that matches the labeling actually proposed.
How Long Does FDA 510(k) Review Take?
FDA’s MDUFA performance goal targets a decision within roughly 90 FDA days for most 510(k)s — calendar days minus any time the file is on hold for an AI request. FDA also aims to issue a first Substantive Interaction within about 60 calendar days of receipt. These are performance goals, not promises for any individual submission.
In practice, total time to decision — the full calendar-day span from filing to a final letter — often runs longer once RTA cycles, AI holds (up to 180 days each), and response quality are factored in. A submission with strong documentation and a well-supported predicate can move close to the target timeline; one that draws multiple AI requests can take considerably longer. Because these figures change as FDA updates its performance data each fiscal year, always confirm current goals on FDA’s official 510(k) and MDUFA pages before setting internal deadlines.
What Does an FDA 510(k) Submission Cost?
None of the five reasons above are unusual or exotic — which is also why they’re preventable. A few practical habits reduce risk across the entire FDA 510(k) submission process:
- Start predicate research early, and compare at least two or three candidates before committing.
- Run a regulatory gap assessment against current FDA guidance before finalizing your test plan.
- Map testing to FDA guidance documents and recognized standards for your device type, not a generic checklist.
- Perform a document consistency check across the cover letter, IFU, labeling, and Indications for Use form.
- Review labeling against tested claims before it’s treated as final.
- Run a mock FDA review using the current RTA checklist before you file.
- Build a submission quality control step separate from the person who authored the file.
- Plan your AI-response process in advance — owner, timeline, and review steps.
Adding more documents is not the fix if the underlying evidence isn’t traceable to a specific safety or performance question. A shorter, well-mapped submission generally moves faster than a thicker one built to look thorough.
FDA 510(k) Pre-Submission Readiness Checklist
- Device classification, product code, and regulation number confirmed
- Intended use and indications for use finalized and consistent everywhere
- Predicate device selected and substantial equivalence comparison documented
- Technological characteristics comparison completed
- Risk analysis (ISO 14971) completed and mapped to test evidence
- Performance / bench testing completed against recognized standards
- Biocompatibility evaluation completed, where applicable
- Sterilization validation completed, where applicable
- Electrical safety and EMC testing completed, where applicable
- Software documentation prepared per applicable documentation level, where applicable
- Cybersecurity documentation (SBOM, threat model) prepared, where applicable
- Usability / human factors evidence prepared, where applicable
- Clinical evidence assembled, where needed
- Labeling and Instructions for Use finalized and reconciled with testing
- Administrative forms, cover letter, and financial disclosure completed
- eSTAR requirements reviewed and file structured accordingly
- Applicable FDA guidance documents identified and addressed
- Internal mock RTA review and response strategy in place
Meeting the FDA 510(k) clearance requirements for your specific device class means every item below is addressed with traceable evidence, not just listed as complete.
Predicate Device Selection Checklist
A candidate predicate should be evaluated against all of the following — not chosen solely because it is the newest or most visually similar clearance:
- Confirmed as a legally marketed device (not withdrawn or subject to a related safety action)
- Same intended use as your device
- Same or comparably supported technological characteristics
- Matching or appropriately comparable indications for use
- No unresolved safety or effectiveness questions in its FDA history
- Same or closely related product code
- Reviewed for how many AI cycles its own clearance required, if discoverable
FDA 510(k) Documentation Checklist
Exact requirements depend on device type and applicable FDA 510(k) submission requirements, but most files include:
- Cover letter and administrative information
- 510(k) Summary or 510(k) Statement
- Indications for Use form
- Device description and substantial equivalence comparison
- Labeling and Instructions for Use
- Sterilization and shelf-life data, where applicable
- Biocompatibility data, where applicable
- Software and cybersecurity documentation, where applicable
- Electrical safety and EMC reports, where applicable
- Performance testing data (bench, and clinical where needed)
- Risk analysis summary
If you need support with FDA 510(k) strategy, submission documentation, testing requirements, or regulatory responses, TraccGlobal’s medical device regulatory consulting team can help you prepare a submission built to withstand FDA’s acceptance and substantive review from the start.
Frequently Asked Questions
Why do FDA 510(k) submissions get rejected?
What are the most common 510(k) deficiencies?
What is the FDA 510(k) review process?
What is an RTA in a 510(k) submission?
What is substantial equivalence in a 510(k)?
How long does FDA 510(k) clearance take?
How much does a 510(k) submission cost?
What documents are required for a 510(k)?
What is the difference between 510(k) clearance and FDA approval?
Can FDA ask for additional information after a 510(k) submission?
Where TraccGlobal Fits In
TraccGlobal supports medical device manufacturers — including startups and foreign companies entering the US market — with FDA 510(k) strategy, technical documentation, and the surrounding regulatory infrastructure that determines whether a submission holds up under FDA review. That includes predicate research and substantial equivalence positioning, testing-strategy mapping, technical documentation support, and quality management system alignment under ISO 13485. For manufacturers also pursuing markets outside the US, TraccGlobal’s team works across CE Marking and CDSCO registration in India, giving companies one coordinated regulatory partner across regions rather than a fragmented approach per market. None of this guarantees a specific FDA outcome — no consultant can promise clearance — but disciplined preparation measurably reduces avoidable delay.
To see how TraccGlobal’s regulatory affairs team approaches an FDA 510(k) submission from device classification through response strategy, visit the FDA 510(k) Consulting page, learn more about the team, or get in touch to discuss your device.
