What a Refuse-to-Accept review actually checks

Fifteen days after FDA receives a 510(k), the submitter gets an answer to a narrower question than most people think they asked. The Refuse to Accept policy — most recently updated in FDA's guidance issued April 21, 2022, which superseded the September 2019 version — governs an Acceptance Review that checks whether a submission clears a minimum threshold of completeness. It does not check whether the bench-test protocol is adequate, whether the predicate comparison holds up, or whether the risk analysis is sound. Treating a passed Acceptance Review as a signal about any of those things is one of the most common ways sponsors misread their own submission's odds.

A presence test, not a quality test

The guidance provides a separate acceptance checklist for each 510(k) type — Traditional, Abbreviated, and Special — and each checklist works the same way: it enumerates the elements a submission of that type has to contain, and the Lead Reviewer checks each one off as present or absent. The guidance is explicit that the Acceptance Review is not evaluating the quality of any data the submission contains; a bench-test report that's present but methodologically weak passes the same checkbox as one that's rigorous. That's a deliberate scope limit, not an oversight — the acceptance stage exists to screen out submissions too incomplete to review at all, not to pre-judge the ones that clear it.

What “administratively complete” buys you

Within 15 days of receipt, the submitter gets an electronic notification of the Acceptance Review result. If elements are missing, FDA issues a Refuse to Accept hold rather than filing the submission for review, and the submitter has 180 calendar days to address the cited deficiencies before the submission is considered withdrawn. Clearing that review starts the substantive review clock — it doesn't shorten it, and it says nothing about what that substantive review will find. A submission can be accepted on day 15 and still receive a lengthy additional-information request during interactive review on exactly the sections that were present, and checked, at acceptance.

Where the confusion actually costs time

The failure mode isn't sponsors misunderstanding the rule once it's explained — it's a QA process structured only around the acceptance checklist, because that checklist is the one FDA publishes and the one that produces a pass/fail result in fifteen days. A completeness checklist is worth building precisely to that structure, so nothing ever triggers an RTA hold. But a checklist built to answer is this section here is the wrong tool for the separate question is this section right — the same distinction a trustworthy checklist has to make explicit between an evidence prompt and an agreement checkbox. Presence is a fact you can tick. Adequacy is a judgment, and it needs a different mechanism.

Getting the substantive question answered before it's asked

The mechanism that actually tests adequacy, ahead of submission, is the Pre-Submission — a Q-Submission built to ask a specific, answerable question about the testing strategy or protocol a sponsor is unsure of, rather than a broad request for reassurance. Run in the right order, the two mechanisms do different, complementary jobs: the Pre-Sub tests whether the substance is right before a submission is drafted, and the acceptance checklist confirms, mechanically, that what was decided in the Pre-Sub actually made it into the filed submission. Sponsors who skip the first and lean entirely on the second are relying on a review built to check whether the box is filled, not whether what's in it is any good.

An internal 510(k) completeness checklist, built section-for-section against FDA's current acceptance checklists and kept separate from any claim about substantive adequacy, is previewed in the launch catalog. If your team tracks the acceptance/substance line differently, the shelf takes that correction.