The first thing you notice about eSTAR is that it isn’t a document you write and then format — it’s an interactive PDF that won’t let you move forward until each required field is filled. The second thing worth noticing, if you actually read it closely instead of racing to complete it, is that its structure isn’t arbitrary. It mirrors the internal review template FDA reviewers work from, section by section. That makes it worth reading like a map of the review before you use it as a form.
What eSTAR actually is
eSTAR is a fillable PDF built around a guided series of questions and required attachments, walking through the same content a traditional paper 510(k) needed — device description, indications for use, predicate comparison, performance testing — but as discrete fields instead of narrative sections you assemble yourself. It won’t let you generate a final submission file until the fields marked required are filled, which is exactly why so many of the old administrative acceptance problems show up less often in eSTAR files than in the legacy paper-style submissions that preceded it.
What that structure is actually doing, underneath the form-filling, is previewing the review itself. FDA didn’t design the template as a generic intake form; the section order and required fields track the acceptance checklist and the reviewer’s own template closely enough that reading through eSTAR’s structure before you start is a reasonable way to understand what a reviewer is going to look for, and in what order.
How the structure maps to the review
- Guided required fields
- Each maps to a specific content requirement a reviewer checks for individually — not a paragraph buried in a longer narrative, but a discrete answer with its own place in the file.
- Auto-generated table of contents
- Built from the fields you complete, which means it’s also effectively the reviewer’s navigation through your file — a weak or thin section is exactly as easy for them to jump to as a strong one.
- Attachments tied to specific fields
- Every test report or supporting document is linked to the field it supports, so a reviewer can trace a claim straight to its evidence without hunting through a general appendix.
- Conditional logic
- Some fields only appear based on earlier answers — the device type and pathway you select upstream determine what the template asks for later, so an early answer chosen carelessly can quietly change what the rest of the form demands.
What it changes about how you prepare
The practical effect of a fixed, field-by-field structure is that there’s nowhere to bury a weak answer. In a traditional narrative submission, a thin section could hide inside a well-written surrounding paragraph. In eSTAR, that same thin answer sits in its own field with its own heading, exactly as visible as every strong one next to it. Reviewers see the gaps immediately, because the form puts every required answer in the same size box.
- Draft substantive answers — device description, indications for use, the SE argument — in a separate document first. The PDF form handles heavy editing and version comparison poorly once a section is built out.
- Confirm you’re working from the current template version. FDA revises eSTAR periodically, and an outdated copy can be missing fields a reviewer now expects.
- Read the conditional fields your early answers unlock before you finalize those early answers — know what you’re committing the rest of the file to.
Where teams get tripped up
Treating template completion as review-readiness
A fully filled eSTAR file passes acceptance review more reliably than a hand-assembled one, but eSTAR checks for presence, not for whether your answers actually agree with each other across fields. That consistency check is still yours to do.
Writing directly into the form under deadline pressure
The temptation to skip drafting and just type the answer straight into the field shows up later as thin, unedited prose sitting next to sections you actually took time with — and the format makes that contrast obvious.
Ignoring the conditional fields until they appear
Because later fields depend on earlier answers, discovering a downstream requirement late in the process can mean reworking a section you thought was finished. Read ahead in the template before you commit to the answers that unlock it.
None of this replaces judgment about the substance of your submission — building the file itself is still the harder problem. What eSTAR changes is how visible your answers are once you’re done, which is exactly why it rewards being read closely before you start typing into it.
Sources & further reading
- FDA — Electronic Submission Template and Resource (eSTAR) Program fda.gov
- 21 CFR 807.87 — information required in a premarket notification submission ecfr.gov
- Regulatory Academy — How to read FDA’s Refuse-to-Accept checklist 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.
