510(k) Submission Content: Building an Acceptable Premarket Notification

1. Key takeaways

An acceptable 510(k) submission comes down to three questions answered clearly and consistently from the first page to the last. First, what the product is: the device name, its classification, the product code, the intended use, and a technical description sufficient for a reviewer to understand the design. Second, who it is equivalent to: the selection of the predicate device and the substantial equivalence argument built on it. Third, why it is equivalent: the performance data that support the comparison. In addition to these three pillars, the submission must include labeling, sterilization and biocompatibility evidence where applicable, software documentation where applicable, and information related to UDI.

• The device identity block — name, classification, product code, intended use, technical description — must be complete and internally consistent.
• The predicate device must be identified and the substantial equivalence argument must rest on it, as required by the framework of section 513(i) of the FD&C Act.
• Performance data are scoped by the technical differences against the predicate: no differences mean limited data needs, while every difference needs supporting evidence.
• Labeling, sterilization evidence, biocompatibility evidence, software documentation where applicable, and UDI information are part of the submission content, not afterthoughts.

2. Legal basis

The content of a premarket notification is anchored in the regulation below, and the procedure itself sits in the same part of the code. Together with the substantial equivalence benchmark in the statute and the labeling and UDI provisions, these instruments define what a complete 510(k) dossier must contain. The table lists the instruments referenced in the source material, their subject matter, and where they can be consulted.

3. Expert insights

Insight one: 21 CFR 807.87 is the legal source of the content checklist, and eSTAR is the vehicle that carries it.

21 CFR 807.87 defines the scope of information that must be submitted in a premarket notification. The eSTAR template takes that same information and structures it into fields that can be validated automatically. The two instruments stand in a relationship of requirement and vehicle: the regulation says what must be conveyed, and the template says how it is conveyed in practice. In day-to-day work, using eSTAR directly covers the structural requirements of 807.87, so there is no need to maintain a separate in-house checklist that mirrors the regulation.

Insight two: the wording of the intended use is the first gate of the substantial equivalence determination.

A substantial equivalence determination begins with a comparison of intended use. The formulation of intended use in the submission can therefore be neither too broad nor too narrow. If it is broader than the predicate, the submission introduces new questions of safety and effectiveness that the predicate comparison cannot answer. If it is narrower than what the evidence supports, the sponsor wastes indication space that has already been earned. This is the part of the dossier that deserves word-by-word scrutiny, because a single loose phrase can shift the review onto harder ground.

Insight three: the type of performance data depends on the differences in technical characteristics.

Where the device is technically identical to the predicate, the need for performance data is low. Where technical differences exist, performance data must be provided for each difference — bench data, animal data, or clinical data, as appropriate — to demonstrate that the difference does not raise different questions of safety and effectiveness. The practical discipline is to walk through the technical description against the predicate, list every difference, and attach evidence to each line of that list rather than relying on a general declaration of similarity.

Insight four: the order of the submission sections should match the FDA internal review template.

One of the design principles of eSTAR is that its content and structure map completely to the FDA internal review template. Organizing the material according to that template is not merely a matter of form: it means the reviewer finds the expected information in the expected place. A submission that follows the template reduces friction, shortens the administrative path through the review, and avoids the impression of disorder that invites closer scrutiny of substance. Treating the template as the organizing principle of the dossier, rather than a shell to be filled at the end, is what keeps the whole document coherent under review.

4. Practical recommendations

• Use eSTAR as the single skeleton of the submission; do not build a parallel format of your own alongside it.
• Scrutinize the intended use word by word, and compare it literally against the intended use of the predicate device before the submission goes out.
• Build a difference-to-evidence mapping table: for every technical difference from the predicate, assign one corresponding item of performance data.
• Complete the labeling draft before submission; do not leave it to be patched during the review phase.
• Settle UDI information at the submission stage, so that GUDID data do not have to be supplemented after clearance.

5. Verification checklist

• □ Every item within the scope of 21 CFR 807.87 has been checked off, with no gaps
• □ The intended use has been compared word by word against the predicate device
• □ A technical-difference-to-performance-evidence mapping table has been built
• □ The labeling draft is complete, covering each item of 21 CFR Part 801
• □ Sterilization and biocompatibility evidence is complete, where applicable
• □ Software documentation and the cybersecurity section are complete, where applicable
• □ UDI information has been settled at the submission stage

Regulatory information verified as of October 28, 2026.

How GRZAN can help. GRZAN provides medical device and IVD registration, quality system, US Agent and local testing support for the United States market. Our team manages FDA establishment registration and listing, 510(k)/De Novo/PMA submissions, and supports post-market reporting obligations. Business enquiries: info@grzanglobal.com