US 510(k) Submission · eSTAR-Ready Substantial Equivalence
Show your device is as safe and effective as a legally marketed device. We choose the right route, write the SE narrative, and package it in FDA’s eSTAR template so acceptance checks pass.
We provide a consulting and documentation service that builds a clean substantial-equivalence (SE) story for your device, selects the correct 510(k) route (Traditional, Special, or Safety & Performance Based), and organizes everything inside FDA’s eSTAR template so it is ready for acceptance review. We do not run tests or submit on your behalf—we plan, organize, and write. For 510(k)s, eSTAR electronic submissions are required unless exempted.
The 510(k) pathway still turns on substantial equivalence—but how you select the predicate, structure your comparison, and package your file in eSTAR determines how smoothly FDA can review it.
eSTAR is mandatory for 510(k): Since October 1, 2023, 510(k) submissions must use FDA’s eSTAR electronic template unless specifically exempted. Aligning your content to eSTAR’s sections and automated checks improves first-pass acceptance.
Substantial equivalence is the core standard: A 510(k) must show your device is as safe and effective as a legally marketed predicate for the same intended use, with similar technology—or justified differences supported by data.
Choosing the right route saves cycles: Traditional, Special, and Safety & Performance Based 510(k)s have different assumptions and documentation flows. Picking the wrong route can create unnecessary questions or requests.
RTA screening blocks progress if incomplete: FDA’s Refuse-to-Accept (RTA) policy uses checklists to decide if a 510(k) is administratively complete. If you fail RTA, substantive review never starts.
We focus on the three big risks—wrong route, weak SE story, and RTA issues—and address them in a single, eSTAR-ready package.
Who This Service Is For
We support teams responsible for getting a 510(k) accepted and reviewed without avoidable back-and-forth.
510(k) owners and RA/QA leaders responsible for U.S. submission strategy.
Technical writers and regulatory specialists who must turn complex data into clear comparisons and narratives.
Project owners launching a new device or managing significant design/indication changes to an existing device.
Teams facing:
Unclear predicate selection.
Need to re-frame claims and labeling.
New performance testing, standards, or usability expectations.
eSTAR formatting and RTA readiness concerns.
What You Will Receive
Deliverables are centered on four outcomes: route clarity, a defensible SE comparison, evidence traceability, and an eSTAR file that is ready for acceptance review.
Shortlist and evaluation of candidate predicate devices against your intended use, indications, technology, and claims.
Recommended 510(k) route: Traditional, Special, or Safety & Performance Based Pathway.
Rationale for the chosen route, including risks and limitations of alternatives.
Notes on any open questions that may justify a prior Q-Submission.
SE Comparison Table & Labeling/Claims Map
Labeling and claims map: how your proposed labeling compares to the predicate’s, including where claims are narrower, equivalent, or extended.
Structured SE narrative that explains similarities and differences and how your data support equivalence.
Side-by-side comparison table covering:
Intended use and indications.
Technological characteristics (design, materials, energy source, key features).
Performance characteristics where relevant.
Performance Evidence Crosswalk
Crosswalk table linking each claim and key technological difference to the supporting evidence (bench tests, simulated use, usability, literature, etc.).
Identification of recognized consensus standards applied, including how test methods and acceptance criteria support SE.
Highlighted gaps where additional data or clarifications are needed before submission.
eSTAR Package & Preflight (Acceptance-Check Readiness)
510(k) sections drafted and organized according to eSTAR’s structure and prompts.
Content tailored to anticipate FDA reviewer questions, with reviewer-style Q&A notes for internal use.
RTA pre-check against FDA’s Refuse-to-Accept checklist, with a mapping showing where each item is addressed.
Submission-ready eSTAR package for your regulatory owner to upload and submit.
How Our 510(k) Service Works
We move from understanding your device and options to an eSTAR-ready file with a clear SE narrative.
Clarify intended use and indications for use, device technology, and risk profile.
Confirm candidate predicates and collect labeling drafts, V&V plans, and existing results.
Align on target submission date and any prior FDA interactions (e.g., Q-Subs, previous 510(k)s).
02
Predicate & Route Selection
Evaluate candidate predicates for suitability (intended use, indications, technology, and data expectations).
Decide on the 510(k) route—Traditional, Special, or Safety & Performance Based—and document the rationale in a short memo.
03
Comparison & Evidence Development
Build the SE comparison table (indications, technology, performance) and labeling/claims map.
Construct the performance evidence crosswalk and identify any gaps or additional testing needed to support SE.
Draft the SE narrative, integrating similarities, differences, and supporting data in reviewer-friendly language.
04
Documentation & eSTAR Packaging
Draft and assemble all required 510(k) sections into FDA’s eSTAR template.
Perform an RTA-style preflight and refine content until it is acceptance-ready.
Provide reviewer-style internal Q&A notes and a brief handover for your regulatory owner to submit via eSTAR.
What We Need From You
We focus your effort on decisions and data only you can provide.
Draft intended use and indications for use.
Candidate predicate(s) and rationale for considering them.
Device technology description (design, materials, features, energy sources, key differences vs. predicate).
Risk management files and verification/validation (V&V) plans and results.
Applicable test standards (bench, software, usability, biocompatibility, etc.).
Labeling drafts (IFU, labels, marketing claims) and any internal claim boundaries.
Target 510(k) submission date and constraints (launch timing, dependencies).
Consulting and documentation only. We do not perform laboratory testing and do not act as the official submitter. We organize and author content; your regulatory owner submits the 510(k) to FDA via eSTAR.
Yes. For most 510(k)s, eSTAR electronic submissions are required unless FDA has granted a specific exemption. Our service delivers an eSTAR-packaged file ready for your regulatory owner to submit.
We evaluate Traditional, Special, and Safety & Performance Based Pathway options against your device, claims, changes vs. the predicate, and applicable performance criteria—then document the rationale and risks.
Only where necessary. We first use your existing verification/validation, literature, and recognized standards. Where gaps remain—for example, because of new technology or expanded claims—we highlight the tests or analyses needed to support SE.
No. Your regulatory owner or U.S. Agent remains the official submitter. We organize and author the content, package it in eSTAR, and provide a handover so they can submit confidently.
That is common. A core part of the service is the predicate & route memo, which weighs options and clarifies where a Q-Submission might be helpful before finalizing your strategy.
Technically, FDA clears a 510(k) device based on substantial equivalence to a predicate; it is not the same as a PMA approval. We avoid language that suggests formal “approval” in your 510(k) narrative.
Build an eSTAR-Ready 510(k) With a Clear SE Story
A strong 510(k) does more than list tests—it explains clearly why your device is as safe and effective as a legally marketed predicate and packages that story in a structure FDA can review efficiently. We help you choose the right route, develop a transparent SE comparison, map evidence to claims, and deliver an eSTAR-ready file that is tuned for RTA acceptance and reviewer expectations.
To provide the best experiences, we use technologies such as cookies to store and/or access device information. Consenting to these technologies allows us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent may negatively affect certain features and functions.
Funcional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Statistics
The technical storage or access that is used exclusively for statistical purposes.O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anónimos. Sem uma intimação, conformidade voluntária por parte do seu Fornecedor de Serviços de Internet ou registos adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
The technical storage or access is required to create user profiles in order to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Para fornecer as melhores experiências, usamos tecnologias como cookies para armazenar e/ou aceder a informações do dispositivo. Consentir com essas tecnologias nos permitirá processar dados, como comportamento de navegação ou IDs exclusivos neste site. Não consentir ou retirar o consentimento pode afetar negativamante certos recursos e funções.
Funcional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Statistics
The technical storage or access that is used exclusively for statistical purposes.O armazenamento técnico ou acesso que é usado exclusivamente para fins estatísticos anónimos. Sem uma intimação, conformidade voluntária por parte do seu Fornecedor de Serviços de Internet ou registos adicionais de terceiros, as informações armazenadas ou recuperadas apenas para esse fim geralmente não podem ser usadas para identificá-lo.
Marketing
The technical storage or access is required to create user profiles in order to send advertising, or to track the user on a website or across several websites for similar marketing purposes.