Before a reviewer ever weighs in on your predicate, your testing, or your indications for use, someone in FDA’s document control room decides whether your 510(k) is even complete enough to look at. That decision happens fast, it happens against a written checklist, and it has nothing to do with whether your science is any good. It is entirely about whether the file is administratively whole.
What the RTA review is actually checking
Acceptance review happens early and quickly, ahead of the substantive scientific review that everyone thinks of as “the 510(k) review.” A reviewer works through a written checklist — not the deep predicate and equivalence questions, but whether the required sections are present, internally consistent, and addressed in the form FDA expects. If the file passes, the substantive review clock starts. If it doesn’t, FDA issues a hold letter identifying exactly what’s missing, and you’re working against the same kind of response clock that governs an unanswered request for additional information — let it lapse and the submission can be considered withdrawn rather than merely delayed.
That distinction matters for how you prepare. A substantive reviewer is evaluating an argument. An acceptance reviewer is confirming a shape — that the pieces required by the file are all present and none of them contradict each other.
What actually gets checked
- Administrative completeness
- Cover letter, 510(k) summary or statement, the truthful and accuracy statement, and the correct user fee or small business documentation — the paperwork that has to exist before anyone reads the science.
- Internal consistency
- The device name and the indications for use statement have to read identically everywhere they appear — cover letter, labeling, the summary, the comparison table. A reviewer isn’t being pedantic when they flag a mismatch; it’s a real signal the file was assembled in pieces.
- Substantial equivalence discussion
- Not the full argument — that’s substantive review’s job — but a comparison table has to be present and actually filled in, not referenced as forthcoming.
- Explicit answers, not silence
- Every checklist item needs a stated answer, including “not applicable.” A blank section reads as an omission; a section that says why it doesn’t apply reads as a decision.
Where files actually get held
The pattern across RTA holds is rarely a missing study. It’s smaller and more mechanical than that: an indications for use statement that says one thing in the labeling and a slightly different thing in the summary. A truthful and accuracy statement that’s present but unsigned. A performance testing section that’s silent on biocompatibility instead of stating explicitly that it doesn’t apply to this device. None of these are scientific problems. All of them stop the clock before science gets discussed.
- The device name and indications for use statement read identically in every section they appear.
- Every checklist item is addressed explicitly, including the ones where the honest answer is “not applicable.”
- The predicate comparison table is filled in with real values, not a placeholder or a forward reference.
eSTAR narrows this, it doesn’t eliminate it
FDA’s eSTAR template forces most of the structural gaps closed before you can even generate a submission — required fields have to be filled before the file locks. What it can’t do is check whether your free-text answers agree with each other, or whether the indications for use you typed into one field matches the wording in the labeling you attached three fields later. That part is still on you, and it’s the part most worth a deliberate final pass.
Where people get stuck
Assuming a completed eSTAR file is a consistent one
The template enforces presence, not agreement. It will happily accept two slightly different versions of your indications for use in two different fields, because from its perspective both fields are filled.
Treating “not applicable” as optional to state
Leaving a section blank because it genuinely doesn’t apply reads the same to a checklist as leaving it blank because you forgot. State the exemption; don’t just assume the reviewer will infer it.
Reviewing the file section by section instead of end to end
Most consistency problems only show up when you read the device name, indications for use, and labeling claims back to back, in order. Reviewing each section in isolation is exactly how they slip through.
The most reliable way to avoid a hold is the least glamorous one: before you submit, read the file the way an acceptance reviewer will — checklist in hand, checking for presence and agreement rather than persuasion. It’s a different exercise from preparing for a Pre-Submission meeting, where the goal is shaping the science before you commit to it. This is the last mechanical check before the clock starts.
Sources & further reading
- FDA — Acceptance Review for 510(k)s: Refuse to Accept Policy for 510(k)s fda.gov
- 21 CFR Part 807, Subpart E — premarket notification procedures and required content ecfr.gov
- Regulatory Academy — How to read FDA’s eSTAR submission template regulatoryacademy.com
- Regulatory Academy — Building the 510(k): eSTAR, screening, and the testing burden regulatoryacademy.com
This essay is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal, regulatory, or career advice.
