FDA 510(k) RTA Checklist: How to Submit Without Getting Refused to Accept

What Is FDA's Refuse to Accept Policy and Why It Exists

Every year, a significant percentage of 510(k) submissions are refused before FDA reviewers even look at the substance. This is the Refuse to Accept (RTA) process, and it is the single most frustrating obstacle for medical device manufacturers trying to get products to market.

FDA implemented the RTA policy to address a real problem: incomplete submissions were consuming reviewer time and creating backlogs that delayed decisions for everyone. Rather than spending months reviewing a submission only to issue a deficiency letter for missing basic elements, FDA now screens every 510(k) within the first 15 business days of receipt.

If your submission fails the RTA screen, it is returned to you. You lose your place in the review queue, you lose the filing date, and you lose weeks or months of timeline. For a startup with limited runway or a manufacturer racing to beat a competitor, an RTA refusal can be devastating.

The good news: RTA refusals are almost entirely preventable. FDA publishes exactly what they check during the RTA screen. The criteria are specific, documented, and checkable before you submit.

The bad news: many manufacturers still do not use a systematic pre-submission RTA check. They rely on institutional memory, outdated checklists, or the assumption that their regulatory affairs team "knows what to include." This is how submissions get refused.

What Triggers an RTA Refusal

FDA's RTA checklist covers both administrative and substantive elements. Here are the most common triggers for refusal:

Missing or incorrect administrative elements. This includes incomplete cover letters, missing device description, incorrect product codes, missing establishment registration numbers, and incomplete truthful and accurate statements. These sound trivial, but they account for a surprisingly large share of RTA refusals.

Inadequate predicate device comparison. Your submission must include a clear comparison between your device and the predicate device. This comparison must address intended use, technological characteristics, and performance data. A vague or incomplete comparison is one of the most common substantive RTA triggers.

Missing performance data summaries. Even if your full test reports are included, FDA expects summary tables of performance testing results in the body of the submission. Reviewers should not have to dig through appendices to find basic test outcomes.

Incomplete biocompatibility information. If your device contacts the body, you need biocompatibility data or a rationale for why existing data is sufficient. Missing biocompatibility assessments or inadequate justification for not testing are frequent RTA triggers.

Software documentation gaps. For devices with software, FDA expects documentation following the guidance on Content of Premarket Submissions for Device Software Functions. Missing software level of concern determination, software description, or hazard analysis will trigger an RTA.

Sterilization information gaps. For sterile devices, incomplete sterilization validation information or missing sterility assurance level documentation will result in refusal.

Electrical safety and EMC gaps. For powered devices, missing IEC 60601-1 testing information or electromagnetic compatibility data.

The Complete 510(k) RTA Checklist

Use this checklist before every 510(k) submission. Each item corresponds to an element FDA reviewers check during the RTA screen:

Administrative Elements

Verify each of these is present and correct in your submission:

1. 1CDRH Premarket Review Submission Cover Sheet (FDA Form 3514). Fully completed with accurate product code, panel, and classification information.

1. 1Cover letter. Identifies the submission type (Traditional, Special, or Abbreviated 510(k)), states the device name and product code, identifies the predicate device(s), and provides contact information for the responsible individual.

1. 1Indications for use statement (FDA Form 3881). Completed and signed, matching the predicate device's indications for use or clearly describing any differences.

1. 1Truthful and accurate statement. Signed by an authorized representative of the company.

1. 1Class III summary or certification. Required for all 510(k) submissions.

1. 1Financial certification or disclosure statement. Required for clinical data from investigators with financial interests.

1. 1Establishment registration and device listing numbers. Your facility must be registered and the device listed with FDA before submission.

1. 1Comparison table. Side-by-side comparison of your device with the predicate device, covering intended use, device design, materials, performance specifications, and any differences.

Substantive Elements

These require technical depth and are where most substantive RTA failures occur:

1. 1Device description. Comprehensive description including principles of operation, design features, materials, specifications, accessories, and variations or models included in the submission.

1. 1Substantial equivalence discussion. Detailed argument for why your device is substantially equivalent to the predicate. This must address both intended use and technological characteristics.

1. 1Performance testing — bench testing. Summary results for all bench testing performed, including test methods, acceptance criteria, sample sizes, and results. Reference standards used (ASTM, ISO, IEC) must be cited.

1. 1Performance testing — animal testing. If applicable, summary of animal study design, results, and relevance to device safety and effectiveness.

1. 1Performance testing — clinical data. If applicable, summary of clinical data supporting substantial equivalence. This may include clinical studies, literature reviews, or a justification for why clinical data is not needed.

1. 1Biocompatibility assessment. Risk assessment per ISO 10993-1 identifying required biological evaluations based on device contact type and duration. Test reports or rationale for using existing data.

1. 1Sterilization information. For sterile devices: sterilization method, validation status, sterility assurance level, and packaging validation.

1. 1Software documentation. For devices with software: level of concern, software description, software requirements specification, architecture design chart, software design specification, traceability analysis, software development environment description, verification and validation documentation, revision level history, and unresolved anomalies.

1. 1Electromagnetic compatibility (EMC) and electrical safety. For electrically powered devices: IEC 60601-1, IEC 60601-1-2, and any applicable collateral and particular standards.

1. 1Labeling. Proposed labeling including device labels, instructions for use, and any patient-facing materials. Labeling must comply with 21 CFR Part 801.

How to Select the Right Predicate Device

Predicate device selection is arguably the most strategically important decision in your 510(k) submission, and getting it wrong is a common path to RTA refusal or, worse, a Not Substantially Equivalent (NSE) determination.

Start with intended use. Your predicate must have the same intended use as your device. FDA defines intended use broadly — it includes the condition or disease being diagnosed, treated, or prevented, the patient population, and the part of the body involved. Any differences in intended use will require additional justification and may push you toward a de novo classification instead.

Then evaluate technological characteristics. If your device has different technological characteristics than the predicate, you must demonstrate that those differences do not raise new questions of safety and effectiveness. Performance data (bench, animal, or clinical) may be needed to support this argument.

Avoid "predicate creep." Do not choose a predicate solely because it has a broad clearance or because it was recently cleared. The predicate must genuinely represent the same type of device for the same intended use. FDA reviewers will scrutinize the predicate choice, and selecting a poor predicate is a common reason for Additional Information requests that delay your review.

Consider using multiple predicates. In some cases, you may reference one predicate for intended use and another for specific technological characteristics. This is acceptable but requires clear explanation of how each predicate supports your substantial equivalence argument.

Check the predicate's classification. Verify that the predicate device is classified under the same product code and regulation number you intend to use. If the predicate is classified differently, your substantial equivalence argument will face additional scrutiny.

Review the predicate's 510(k) summary. FDA publishes 510(k) summaries for cleared devices. Review your predicate's summary to understand what testing and arguments were used to support its clearance. This can inform your own testing strategy.

Common 510(k) Submission Failures Beyond RTA

Even submissions that pass the RTA screen can encounter significant problems during substantive review. Understanding these failure modes can help you prepare a stronger initial submission:

Insufficient predicate comparison depth. Passing a table comparison is not enough. FDA expects a narrative discussion of each difference and why it does not affect safety or effectiveness. Provide data, not just assertions.

Incomplete risk analysis. While a full ISO 14971 risk management file is not required for 510(k), FDA expects evidence that you have identified and mitigated the key risks associated with your device. A risk analysis summary should accompany your submission.

Outdated standards. Using outdated test standards (for example, referencing a superseded ASTM method) will raise questions. Always verify you are testing against the current recognized consensus standard.

Poor labeling. Labeling that does not comply with 21 CFR Part 801, contains unsubstantiated claims, or contradicts the indications for use statement is a common deficiency.

Inadequate software documentation. FDA has increased scrutiny of software in medical devices. The Content of Premarket Submissions for Device Software Functions guidance is your roadmap. Follow it closely, particularly for Level of Concern determination and cybersecurity documentation.

Missing use environment considerations. Electromagnetic compatibility testing, environmental testing, and use environment characterization are frequently overlooked, particularly by first-time submitters.

510(k) Submission Timeline and Strategy

Understanding the review timeline helps you plan product launches and resource allocation:

Pre-submission meeting (optional but recommended). Submit a Q-Sub (pre-submission) request 3 to 4 months before your planned 510(k) submission date. A pre-submission meeting with FDA can clarify expectations around testing requirements, predicate selection, and submission format. This upfront investment frequently prevents costly deficiency responses later.

RTA screening period. FDA targets 15 business days for the RTA screen. During this period, your submission is checked against the RTA checklist. No substantive review occurs.

Substantive review. For Traditional 510(k)s, FDA targets a 90-calendar-day review cycle. For Special 510(k)s, the target is 30 days. These are targets, not guarantees. Complex submissions or those requiring Additional Information requests will extend the timeline.

Additional Information (AI) requests. If FDA identifies deficiencies during substantive review, they will issue an AI request. You typically have 180 days to respond. Your response restarts a portion of the review clock.

Practical timeline. For a well-prepared Traditional 510(k) with no AI requests, expect approximately 4 to 6 months from submission to clearance. Factor in pre-submission meetings, testing timelines, and internal review cycles, and most manufacturers should plan for 12 to 18 months from project initiation to 510(k) clearance.

The single most effective strategy for reducing your 510(k) timeline is submitting a complete, high-quality initial package that avoids both RTA refusal and AI requests. Every deficiency cycle adds 2 to 4 months to your timeline.