FDA 510(k) Refuse to Accept Checklist: Why Submissions Get Rejected Before Review

Your 510(k) Can Be Rejected Before a Single Reviewer Reads It

You have spent months -- sometimes years -- developing your device, building your technical file, and preparing your 510(k) submission. Then, within 15 business days of receipt, FDA sends back a Refuse to Accept (RTA) decision. No substantive review. No feedback on your safety and effectiveness data. Just a checklist of administrative and structural deficiencies that disqualify your submission from entering the formal review queue.

This outcome is more common than most founders and regulatory teams anticipate. According to FDA data, a meaningful percentage of 510(k) submissions receive RTA decisions each fiscal year -- and virtually all of them are avoidable. At ADB Consulting and CRO Inc., we have helped device companies across therapeutic categories correct these exact gaps before they become costly delays. This post walks you through the most frequent RTA triggers so you can submit with confidence.

What Is the RTA Process and Why Does It Exist?

Under FDA's 510(k) Program, the Agency conducts an administrative completeness review before assigning a submission to a substantive reviewer. This process is governed by FDA's guidance document 'Refuse to Accept Policy for 510(k)s' (most recently updated in 2019) and is supported by the RTA Checklist, which FDA reviewers use to evaluate every incoming submission.

The RTA policy exists to protect FDA review resources and ensure that substantive reviewers are only spending time on submissions that are structurally complete. From a regulatory standpoint, this is reasonable. From a company standpoint, it means that a single missing section or an improperly formatted document can set your program back by months and trigger resubmission fees under MDUFA commitments.

The Most Common Reasons 510(k)s Receive RTA Decisions

1. Missing or Incomplete Indications for Use and Device Description

Section 21 CFR 807.87 defines the required elements of a 510(k) submission, and the Indications for Use statement is one of the first things FDA checks. Submissions frequently fail because the Indications for Use form (FDA Form 3881) is either missing, unsigned, or inconsistent with the device description narrative. The device description itself must be detailed enough for FDA to understand the device's intended use, technological characteristics, and mechanism of action. Vague or incomplete descriptions are a leading RTA trigger.

2. Predicate Device Section Deficiencies

The substantial equivalence argument is the foundation of your 510(k). FDA expects a clear, structured comparison between your device and the predicate under 21 CFR 807.87(f). Common failures include: failing to identify a legally marketed predicate; providing a comparison that does not address both intended use and technological characteristics; and neglecting to include performance data when technological differences exist. If your predicate identification is weak at the RTA stage, the submission will not advance to the point where your equivalence argument can even be evaluated.

3. Incomplete Performance Testing Summary

FDA's RTA checklist requires that submissions include a summary of performance testing -- not necessarily the full data, but a structured description of what testing was conducted, what standards were followed, and what the results demonstrated. Submissions that reference testing without summarizing results, or that omit testing sections entirely for device types where performance data is expected, routinely receive RTA determinations. This is particularly common for software-containing devices where cybersecurity documentation and software documentation under FDA's guidance on Software as a Medical Device (SaMD) may also be expected.

4. Missing Sterilization and Biocompatibility Sections

For devices that are sterile or that contact patients, FDA expects a sterilization section and a biocompatibility section referencing ISO 10993-1 principles. Many submissions, particularly from first-time submitters, omit these sections entirely or include placeholder language. FDA's RTA checklist specifically flags the absence of these sections for applicable device types.

3. Administrative Deficiencies: Signatures, Fees, and eCopy Requirements

A significant number of RTA decisions are issued for purely administrative reasons. These include: missing or invalid establishment registration and device listing under 21 CFR Part 807; failure to pay the correct MDUFA submission fee prior to filing; submission of an eCopy that does not conform to FDA's eCopy guidance; and missing a signed 510(k) cover letter or certifications. These are the most avoidable RTA triggers and the most frustrating, because they have nothing to do with the quality of your device or your data.

How to Conduct Your Own Pre-Submission RTA Review

FDA publicly posts the current RTA Checklist as an appendix to the 'Refuse to Accept Policy for 510(k)s' guidance. Before you submit, your team should work through that checklist line by line -- not as a formality, but as a structured gap analysis. Every 'N/A' designation should be documented and defensible. Every required section should be traceable to a specific location in your submission using a clear table of contents.

If your team does not have prior 510(k) experience, or if this is a novel device type or a complex predicate situation, a pre-submission meeting with FDA under the Q-Submission program is worth the investment. A Q-Sub does not guarantee acceptance, but it gives you documented FDA feedback before you spend resources on a full submission.

The Cost of Getting This Wrong

An RTA decision does not simply delay your submission by a few weeks. Under MDUFA IV and MDUFA V commitments, resubmissions are treated as new submissions for fee purposes in many circumstances. You lose your place in the review queue, your program timeline shifts, and your launch date moves. For venture-backed device startups operating against fundraising milestones, an avoidable RTA decision can have downstream consequences that extend well beyond regulatory affairs.

Work With Experts Who Know the Checklist Cold

At ADB Consulting and CRO Inc., we review 510(k) submissions against FDA's RTA checklist as a standard part of our pre-submission services. We identify gaps in device description, predicate comparisons, performance testing summaries, and administrative completeness before your submission ever reaches FDA's hands. Our clients do not receive RTA decisions for reasons that a structured review would have caught.

If you are preparing a 510(k) submission and want a regulatory expert to evaluate your readiness before you file, book a free discovery call with Andre Butler and the ADB Consulting team today. Visit adbccro.com to schedule your consultation and get your submission strategy right the first time.