Since October 2023, there has been exactly one way to submit a 510(k): the eSTAR — FDA's interactive PDF template — delivered electronically through the CDRH Customer Collaboration Portal. Paper is gone, unstructured eCopies are gone, and with them went the freedom to organize the file your own way. The eSTAR mirrors the reviewer's own checklist, section by section, and it will not let you mark the submission complete with the hard parts empty. That discipline is the point — and it moves the real work upstream, into the testing programme your predicate choice committed you to.

What the file contains

The spine of the submission, per 21 CFR 807.87
  1. Administrative identity — device trade name, classification, product code, and the Indications for Use on FDA's Form 3881, which becomes a public document on clearance.
  2. The substantial equivalence discussion — your device and the predicate, intended use and technological characteristics, set side by side and argued. This is the section the whole file serves.
  3. Proposed labeling — because intended use lives in the labeling, the labeling is evidence, not packaging.
  4. Performance data — bench, biocompatibility, sterilization, shelf life, electrical safety, software, and where the differences demand it, animal or clinical evidence.
  5. The closing certifications — a 510(k) summary or statement, and the Truthful and Accuracy statement someone in your company signs.

The testing burden — set by the comparison, priced by the standards

No regulation lists the tests a 510(k) requires, because the requirement is not a list — it is a consequence. Every technological difference between your device and the predicate either raises no different questions of safety and effectiveness, or it does; where it does, performance data closes the question. What FDA will accept as closure is where consensus standards come in: the agency maintains a database of recognized standards — ISO 10993-1 for biocompatibility evaluated within a risk framework, IEC 60601 for electrical safety and EMC, ISO 11135 and 11137 for sterilization validation, and hundreds more. Test to the recognized version and declare conformity, and the reviewer has nothing to reconstruct.

Two modern additions deserve their own line. Software gets a documentation package scaled to risk under FDA's 2023 premarket software guidance — Basic or Enhanced, decided by what failure could cost. And any device that connects — to a network, to other devices, to the internet — is a “cyber device” under section 524B of the FD&C Act, which makes a cybersecurity plan and a software bill of materials statutory content, not optional appendix. Both are places where files built from a five-year-old template quietly fail a current screening.

Screening — what stops the file at the door

For a decade the door was guarded by the Refuse to Accept policy: a named reviewer walking a published checklist within 15 calendar days, returning anything administratively incomplete without review. The eSTAR absorbed that checklist into the template itself — a completed eSTAR cannot omit what RTA screened for, so eSTAR submissions are not subject to RTA review. What remains is a technical screening: does the file open, is it complete as constructed, is it free of malware, and — decisively — has the MDUFA user fee actually been paid. The review clock we walk through in the final lesson does not start until the door closes behind a fee-paid, screening-clean submission.

Where files go wrong

Testing to the standard on your shelf, not the version FDA recognizes

Standards revise, and FDA's recognition moves with them — sometimes with transition windows, sometimes not. A biocompatibility package built to a superseded edition invites a deficiency letter asking you to justify the delta, which can mean re-testing you could have scheduled a year earlier. Check the recognized-standards database at test-plan time, not at submission time.

Writing the substantial equivalence discussion last

Teams treat the SE section as the summary you write once testing is done. It is the opposite: it is the argument the testing exists to support. Draft it first, from the predicate comparison, and it tells you exactly which differences need data. Write it last and you discover the missing test after the schedule has no room for it.

Treating the eSTAR as a form to fill on submission week

The template enforces internal consistency — indications that match Form 3881, attachments that match declared sections, software and cybersecurity content where the device description implies it. Files assembled in a rush contradict themselves, and while the eSTAR catches blanks, it cannot catch a labeling claim your own performance section undercuts. The reviewer can.

Frequently asked questions

Does a 510(k) need clinical data?

Usually not — most 510(k)s clear on bench and analytical evidence, because the argument is equivalence to a predicate, not independent proof of safety and effectiveness. Clinical evidence enters when technological differences from the predicate raise questions bench testing cannot close, or when the device type's guidance expects it. If you find yourself designing a pivotal trial, check whether you are still on the right pathway.

What does submitting a 510(k) cost?

A MDUFA user fee is due at submission — on the order of twenty-five thousand dollars at the standard rate, with qualified small businesses paying roughly a quarter of it. The fee buys review, not clearance, and it is not refunded if the outcome is NSE. FDA will not start the review clock until the fee clears, which makes the payment receipt part of the critical path.

What is the difference between a 510(k) summary and a 510(k) statement?

Every submission includes one or the other. A 510(k) summary is a public account of the substantial equivalence argument, posted in FDA's database on clearance. A 510(k) statement instead certifies that you will provide the information to anyone who asks within 30 days. Most sponsors file summaries — and your competitors' summaries are exactly where predicate research starts, so write yours knowing its audience.

Sources & further reading

  1. FDA Guidance — Electronic Submission Template for Medical Device 510(k) Submissions (eSTAR) fda.gov
  2. 21 CFR 807.87 — Information required in a premarket notification submission ecfr.gov
  3. FDA Recognized Consensus Standards Database — the versions FDA currently accepts accessdata.fda.gov
  4. FDA Guidance — Use of ISO 10993-1 in the biological evaluation of medical devices fda.gov
  5. FDA — Medical Device User Fee Amendments: current fee schedule and small business qualification fda.gov

This lesson is provided for general educational purposes and reflects the regulatory landscape as of its publication date. It is not legal or regulatory advice.