What FDA Expects in a 510(k) Submission: Lessons from eSTAR
Since FDA made the electronic Submission Template and Resource (eSTAR) mandatory for most 510(k) submissions, we have watched medical device manufacturers uncover a simple truth about FDA eSTAR 510(k) requirements: eSTAR is more than a submission tool. It is a roadmap to what FDA reviewers actually expect to see.
The traditional 510(k) regulations have not fundamentally changed. But eSTAR gives manufacturers a much clearer view into the information FDA needs to determine whether a device is substantially equivalent to a legally marketed predicate device. Manufacturers who understand these expectations can reduce review delays, avoid Additional Information (AI) requests, and improve the overall quality of their submissions.
eSTAR Reflects FDA's Review Process
Historically, sponsors could organize a 510(k) in a variety of formats. eSTAR standardizes the process by guiding applicants through a structured series of questions and data fields, helping ensure that all required information is in place before a submission ever reaches an FDA reviewer.
You can review FDA's own guidance on the eSTAR Program directly on FDA.gov.
FDA has said eSTAR is intended to improve submission quality and completeness while reducing common deficiencies. In our experience guiding manufacturers through FDA submission preparation and filing, that means every eSTAR section functions as a signal. Each one tells you what reviewers expect to evaluate during the substantial equivalence determination, before you submit rather than after.
| What Changes | Traditional (Pre-eSTAR) 510(k) | eSTAR-Structured 510(k) |
|---|---|---|
| Submission Format | Free-form, sponsor-organized narrative | Structured template with guided questions and required data fields |
| Completeness Checks | Often caught only after FDA begins its review | Built into the template before you ever submit |
| FDA Feedback Timing | Deficiencies surface through Additional Information (AI) requests mid-review | Expectations are visible upfront, reducing AI requests |
| Software & Cybersecurity Docs | Frequently treated as supplemental information | Structured sections require proactive, dedicated documentation |
| Transparency Into FDA's Expectations | Left largely to sponsor experience and interpretation | Each section signals exactly what reviewers will evaluate |
Clear Device Description and Intended Use
One of the most important elements of any 510(k) is a clear description of the device, its intended use, and its technological characteristics.
FDA expects manufacturers to provide enough detail for reviewers to understand how the device functions, how it is used, and how it compares to the predicate device. Device descriptions should include key design features, operating principles, accessories, software functions, and device configurations where applicable. Labeling and indications for use must stay consistent throughout the entire submission, a detail we flag early in every regulatory strategy session.
Demonstrating Substantial Equivalence
At its core, a 510(k) submission must demonstrate substantial equivalence. eSTAR places significant emphasis on identifying predicate devices and providing side-by-side comparisons of intended use, technological characteristics, and performance.
FDA expects manufacturers to clearly explain the similarities and differences between the new device and its predicate. When differences exist, sponsors should provide a scientific rationale and supporting evidence showing those differences do not raise new questions of safety or effectiveness. We build these comparisons collaboratively with our clients so the argument holds up under review, not just on paper.
Robust Performance Data
One of the most common reasons for FDA questions is insufficient performance evidence.
eSTAR prompts manufacturers to provide applicable bench, software, electrical safety, electromagnetic compatibility (EMC), biocompatibility, sterilization, shelf-life, human factors, animal, and clinical performance data. The specific testing required depends on the device type, intended use, and applicable FDA guidance documents.
FDA expects testing to be scientifically sound, relevant to the device's intended use, and supported by complete protocols, acceptance criteria, and results. Summaries alone are often insufficient when reviewers need detailed evidence to support substantial equivalence.
Software and Cybersecurity Receive Increased Attention
As medical devices become increasingly connected and software-driven, FDA expects manufacturers to provide comprehensive software and cybersecurity documentation whenever it applies.
Even when software changes appear minor, manufacturers should carefully assess software risk, cybersecurity controls, architecture, verification activities, and potential impacts on safety and effectiveness. The structured nature of eSTAR highlights FDA's expectation that these areas be addressed proactively rather than treated as supplemental information. Our Chief Regulatory Officer, Brodie Pedersen, who serves as Vice Chair of IEC 62A, sees this as one of the fastest-growing areas of FDA scrutiny, and one manufacturers most often underestimate.
Risk Management and Regulatory Strategy Matter
A successful 510(k) is not simply a collection of test reports. FDA reviewers expect a logical narrative that connects device design, risk management, verification activities, and performance testing.
Manufacturers should ensure that identified risks are adequately mitigated and that supporting evidence demonstrates those mitigations are effective. Consistency among device descriptions, labeling, risk analyses, and testing documentation is critical, and it is exactly where we spend most of our time when we partner with manufacturers on a submission strategy.
The Takeaway
eSTAR has transformed the 510(k) submission process by making FDA's expectations more transparent. The most successful submissions are the ones that provide a clear device description, a well-supported substantial equivalence argument, comprehensive performance evidence, and a strong connection between risk management and testing.
For manufacturers, the lesson is straightforward: treat eSTAR not as an administrative form, but as a blueprint for how FDA evaluates a device. We believe organizations that build their submissions around these expectations are better positioned for a more efficient review and a successful clearance. If you are preparing your next 510(k), our team is ready to talk through your submission strategy.