eSTAR 510(k) Submissions: A Practical Walkthrough
The FDA’s eSTAR template was designed to make medical-device submissions more structured, consistent, and complete.
That does not necessarily make preparing a 510(k) easy.
eSTAR can tell you which fields are incomplete. It cannot tell you whether your predicate is appropriate, your worst-case test article is scientifically justified, your acceptance criteria are adequate, or your substantial-equivalence argument is convincing.
That distinction is where many companies get into trouble.
They treat eSTAR as a sophisticated electronic cover sheet and wait until the end of product development to begin completing it. They then discover that the template is asking questions the development program was never designed to answer.
The most effective way to use eSTAR is not as the final packaging step. It should be used as a regulatory planning framework throughout the development process.
What Is eSTAR?
The electronic Submission Template and Resource—better known as eSTAR—is an interactive PDF that guides applicants through the preparation of medical-device submissions. Its questions change based on the answers entered, displaying the sections FDA considers relevant to the device and submission type. FDA developed the standardized format to improve submission quality and make information easier for applicants and reviewers to locate.
Unless an exemption applies, 510(k) submissions must be prepared and submitted electronically using eSTAR. This requirement applies to Traditional, Special, and Abbreviated 510(k)s, as well as supplements, amendments, and subsequent submissions associated with the original application.
For most medical-device companies, eSTAR has effectively replaced the old model of assembling a manually numbered collection of independent PDF sections.
The submission is now built inside a dynamic framework that contains:
Administrative information
Applicant and correspondent information
Device classification
Indications for use
Device descriptions
Predicate comparisons
Performance testing
Biocompatibility
Sterilization and shelf life
Software and cybersecurity information
Human-factors information
Labeling
Required certifications and statements
Submission attachments
Some of these sections appear only when triggered by earlier answers.
That makes accuracy especially important. An incorrect response can prevent a necessary section from appearing, creating an incomplete or misleading submission.
Before Opening eSTAR: Build the Regulatory Strategy
A common mistake is downloading the template before the team has resolved the fundamental regulatory questions.
Before substantial work begins inside eSTAR, the company should know:
Which type of 510(k) is appropriate?
What is the proposed device classification and product code?
What are the final indications for use?
Which device is the primary predicate?
What technological differences must be addressed?
Which testing supports each difference?
Which device configurations represent the appropriate worst cases?
What manufacturing, sterilization, packaging, software, or usability evidence is required?
Does the tested device represent the final commercial configuration?
Are any issues significant enough to justify a Pre-Submission?
FDA recommends identifying a primary predicate that is most similar to the proposed device in its indications for use and technological characteristics. FDA also recommends reviewing applicable device-specific guidance during the planning stage—not after development and testing have been completed.
eSTAR organizes the submission. It does not create the strategy behind it.
Step 1: Download the Correct Template
Always download the current eSTAR template directly from FDA’s eSTAR Program page.
FDA periodically releases major and minor updates. Major updates may reflect new regulations, policies, final guidance documents, or significant changes to submission expectations. FDA encourages immediate use of an updated version, although an earlier version may remain available until its stated retirement date. Using an older major version can result in additional questions when the changes apply to the device.
Do not assume that the eSTAR saved from a prior project is still the appropriate version.
For each new submission:
Confirm whether the device is an in vitro diagnostic or non-IVD device.
Confirm that the template supports the intended submission type.
Review the version history.
Check the retirement date of the prior version.
Save an untouched master copy before entering information.
Because eSTAR is a dynamic PDF, it cannot be opened and completed properly inside a web browser. FDA instructs users to download the file locally and open it with compatible PDF software. Adobe Acrobat Pro is recommended, while certain current versions of PDF-XChange Editor and Foxit PDF Reader are also supported. Adobe Acrobat Reader may open the template, but FDA notes that it does not allow users to save changes or add attachments.
A surprisingly large number of eSTAR problems begin with the wrong software rather than the wrong regulatory strategy.
Step 2: Establish Document Control
eSTAR is not well suited for uncontrolled, simultaneous editing by a large team.
FDA states that eSTAR can be edited through platforms such as SharePoint and Box, but concurrent co-authoring of dynamic PDF files is not supported. Team members must work sequentially. FDA also suggests printing a static copy when broader team review and markup are needed.
A practical document-control structure should include:
One designated eSTAR owner
A controlled working copy
A dated backup schedule
A submission attachment index
Assigned owners for each section
A comment-resolution log
A final consistency-review checklist
A preserved unsigned version
A preserved signed submission version
Use clear file names such as:
Company_Device_Traditional510k_eSTAR_Working_2026-07-31.pdf
Avoid names such as:
Final eSTAR New Final FINAL 3.pdf
The eSTAR owner should be the only person integrating approved content and attachments into the controlled file. Other team members can develop and review the underlying documents without directly editing the master eSTAR.
Step 3: Complete the Administrative and Classification Sections Carefully
The early eSTAR questions may look routine, but they control which later sections appear.
These entries may include:
Submission type
Application subtype
Applicant information
Official correspondent
Consultant information
Device trade and common names
Review panel
Product code
Regulation number
Device class
Combination-product status
Previous submissions
Third-party-review eligibility
Small-business information
Accuracy matters because eSTAR is logic-driven.
For example, an incorrect product code can direct the submission toward the wrong device classification or prevent the appropriate questions from appearing. An inaccurate response about sterility, software, patient contact, reusability, or electrical functions may hide entire evidence sections.
FDA warns that inaccurate dropdown selections or other incorrect answers that cause eSTAR to omit relevant questions may lead to an early hold during review.
Do not answer a question based on what creates the shortest template. Answer it based on the actual device.
Step 4: Finalize the Indications for Use
The indications for use are the regulatory anchor of the submission.
They influence:
Device classification
Predicate selection
Patient population
Anatomical location
Surgical approach
Clinical claims
Testing requirements
Labeling
Substantial equivalence
Every word matters.
For a spinal implant, seemingly small distinctions can change the regulatory analysis:
Cervical versus thoracolumbar use
Interbody fusion versus supplemental fixation
Open versus minimally invasive placement
Standalone versus supplemental use
One-level versus multilevel use
Skeletally mature patients versus broader populations
Use with autograft, allograft, or another graft material
Specific disease conditions or contraindications
The indications should not be expanded to satisfy marketing ambitions when the predicate and evidence do not support those claims.
Before entering the final text, compare the proposed indications line by line with:
The primary predicate’s cleared indications
The product requirements
The device description
The surgical technique
The test configurations
The risk analysis
The proposed labeling
The 510(k) Summary
Inconsistencies here can affect the entire submission.
Step 5: Develop a Reviewer-Friendly Device Description
The device description should allow a reviewer to understand what the device is, how it works, how it is manufactured, how it is provided, and how it differs from the predicate.
For a spine device, this section may need to cover:
Implant geometry
Available sizes
Materials
Coatings or surface treatments
Porous or additive-manufactured features
Fixation mechanisms
Locking features
Instrumentation
Surgical approach
Implantation sequence
Packaging configuration
Sterility status
Single-use or reusable status
Accessories
Compatible components
Manufacturing methods that affect performance
Key drawings and photographs
Do not make the reviewer search across six attachments to understand the basic configuration.
A strong device description normally includes a concise narrative supported by well-labeled drawings, tables, photographs, and dimensional ranges. Complex systems should include a component matrix identifying part numbers, descriptions, materials, sizes, and regulatory function.
The device description should also clearly separate:
Subject-device components
Reusable instruments
Optional accessories
Previously cleared components
Components included only for procedural convenience
Components manufactured by third parties
Clarity at this stage reduces questions later.
Step 6: Build the Substantial-Equivalence Argument
A 510(k) is not approved merely because the subject device resembles a legally marketed product.
The applicant must demonstrate that the proposed device is substantially equivalent to one or more legally marketed devices. FDA describes a 510(k) as a submission demonstrating that the proposed device is as safe and effective as its predicate. The comparison must address intended use and technological characteristics, including whether any differences raise new questions of safety and effectiveness.
The predicate section should include more than a side-by-side marketing comparison.
A useful comparison table should address:
Indications for use
Intended users
Anatomical location
Surgical approach
Device design
Dimensions
Materials
Coatings
Fixation method
Implantation method
Sterility
Packaging
Shelf life
Mechanical performance
Biocompatibility
Software or electrical functions, when applicable
Every meaningful difference should lead to a clear explanation:
What is different?
Why does it not change the intended use?
Does it raise a different question of safety or effectiveness?
What evidence evaluates the difference?
Where is that evidence located?
The best predicate table is not necessarily the longest one. It is the one that makes the regulatory logic easy to follow.
Step 7: Organize Testing Around Regulatory Questions
Testing should not be uploaded as a pile of reports with the expectation that FDA will assemble the argument.
For each test, explain:
Why it was conducted
Which risk or technological difference it addresses
Why the test method is appropriate
Whether an FDA-recognized consensus standard was followed
Whether deviations occurred
Why the selected device represents the worst case
How the acceptance criterion was established
What predicate or benchmark was used
Whether the device passed
What failures occurred
Why the results support substantial equivalence
The eSTAR Standards section contains recognized standards in dropdown menus. FDA permits applicants to enter non-recognized standards manually, although those entries will not have an FDA recognition number.
A complete performance-testing package may include:
Test protocols
Protocol deviations
Final reports
Raw-data summaries
Photographs of test setups
Failure analyses
Predicate reports
Statistical analyses
Engineering rationales
Worst-case justifications
Standards declarations
Acceptance-criteria justifications
For spine devices, it is particularly important to demonstrate that the tested configurations represent the final design and the relevant worst case for each failure mode. The largest implant is not always the worst case, and one configuration may not represent every test.
Step 8: Address the Specialized Evidence Sections
Depending on the answers entered, eSTAR may generate sections covering specialized evidence such as:
Biocompatibility
Sterilization
Pyrogenicity
Shelf life
Packaging
Reprocessing
Software
Cybersecurity
Electrical safety
Electromagnetic compatibility
Human factors
Magnetic resonance safety
Animal studies
Clinical evidence
These sections should not be treated as isolated attachments.
Each one must remain consistent with the device description, manufacturing process, risk analysis, labeling, and commercial configuration.
For example:
The biocompatibility assessment should evaluate the final finished device.
Sterilization validation should cover the final packaging configuration.
Shelf-life testing should support the proposed expiration date.
Reprocessing validation should represent the most difficult-to-clean reusable device.
Software documentation should match the released software version.
Human-factors activities should reflect the actual users, use environments, and critical tasks.
MRI labeling should match the available evidence.
As of June 2026, FDA’s current eSTAR versions incorporated content associated with its updated human-factors submission guidance, illustrating why companies should review version changes rather than automatically reusing an older template.
Step 9: Prepare Attachments for the Reviewer
FDA does not require a particular attachment naming convention, but it recommends concise, descriptive names. Applicants may use the harmonized IMDRF numbering structure, and attachment names are limited to 124 characters.
A good file name helps the reviewer understand the document before opening it:
18.02 Static Compression Test Report.pdf
A poor file name creates uncertainty:
Final Report Revised.pdf
eSTAR accepts multiple file types, including PDFs, Word files, Excel workbooks, and certain video formats. ZIP files and other unsupported formats are rejected automatically. FDA recommends combining similar content when appropriate and using tables of contents or bookmarks in larger combined documents. Password protection and other PDF security restrictions are discouraged because they can interfere with FDA’s document-handling and redaction processes.
For submissions sent through the CDRH Portal, FDA currently limits individual attachments to 1 GB and the complete eSTAR package to 4 GB. Images and videos should be compressed sufficiently to preserve reviewable detail without unnecessarily increasing the package size.
FDA has also received reports that attachments added directly from shared drives can become corrupted or may not attach correctly. FDA recommends moving documents to a local drive before adding them to the eSTAR.
Before submission, open every attachment from inside the eSTAR—not from its original folder—to confirm that the embedded copy is correct and readable.
Step 10: Complete the Statements, Summary, and Signature
eSTAR incorporates several items that previously required separate forms.
FDA states that applicants do not need to provide separate copies of:
Form FDA 3881, Indications for Use
Form FDA 3514, Premarket Review Submission Cover Sheet
A Declaration of Conformity, when applicable
A separately prepared 510(k) Summary when the eSTAR-generated summary is used
These items are built into the template.
The generated 510(k) Summary should still be reviewed carefully. FDA allows applicants to edit the eSTAR-generated summary, and reviewers may request revisions during Interactive Review.
Do not sign the Truthful and Accurate Statement until all content and attachments are final.
Once an eSTAR has been electronically signed, adding or deleting attachments generally requires the original signer to clear the signature. If that cannot be done, the team may need to return to an unsigned backup or export the data into a new template and reattach every document.
This is why the preserved unsigned version is so important.
Step 11: Confirm “eSTAR COMPLETE”
When all required fields and attachments have been addressed, the status at the top of the template should display:
eSTAR COMPLETE
An eSTAR showing eSTAR INCOMPLETE will not be accepted through the CDRH Portal. An incomplete submission provided through another permitted route may be placed on hold while the deficiency is corrected.
However, “complete” does not mean “clearable.”
It means the template’s required structural elements have been populated.
The final review should therefore include two separate assessments:
Technical completion review
Does eSTAR show complete?
Do all attachments open?
Are the correct fields populated?
Are signatures valid?
Are file sizes within the applicable limits?
Is the correct template version being used?
Regulatory and scientific review
Is the predicate appropriate?
Are all technological differences identified?
Does the evidence support each difference?
Are worst-case selections justified?
Are acceptance criteria defensible?
Are the testing, labeling, risk analysis, and device description consistent?
Does the submission support every proposed claim?
Passing the first review gets the package into FDA’s system.
Passing the second gives the submission a credible chance of clearance.
Step 12: Prepare the User Fee and Submit Through the Portal
A Medical Device User Fee Cover Sheet is required for a fee-bearing medical-device submission. Completing the cover sheet generates a unique payment identification number beginning with “MD,” which FDA uses to connect the payment with the application. FDA review cannot begin until the full applicable fee has been received.
For CDRH-regulated devices, the completed eSTAR must be submitted through the CDRH Customer Collaboration Portal, subject to limited exceptions and alternative instructions for oversized submissions. The portal allows the official correspondent and authorized delegates to monitor submission progress.
FDA states that submissions received through the portal before 4:00 p.m. Eastern Time on a business day are processed that day. Submissions received after that cutoff are processed on the next business day.
Do not wait until the final hour of an internal or statutory deadline to test portal access.
Confirm in advance that:
The correct person has an account.
The official correspondent is accurately identified.
The user fee has been paid.
The final eSTAR opens correctly.
The upload package is within the size limits.
The company has retained an exact copy of the submitted package.
What Happens After Submission?
Because a properly completed eSTAR is intended to contain the required submission elements, FDA does not anticipate subjecting it to the traditional Refuse to Accept review process used for eCopy submissions. FDA instead performs virus scanning and technical screening.
That does not mean eSTAR eliminates initial holds.
FDA may place the submission on technical-screening hold when:
Required information is incomplete.
An inaccurate answer caused relevant questions to be omitted.
Attachments are unrelated to the questions where they were placed.
The submission does not pass technical validation.
The company may have up to 180 days to provide a complete replacement eSTAR. Failure to resolve the technical-screening deficiency within that period can result in the submission being considered withdrawn.
After the submission enters substantive review, FDA may proceed through Interactive Review or issue an Additional Information request. An AI request places the review clock on hold, and FDA must receive a complete response within 180 calendar days.
FDA’s MDUFA goal for a 510(k) decision is 90 FDA days, excluding the time the submission is on hold while the applicant responds to an AI request. That goal is not the same as a guaranteed 90-calendar-day clearance.
Responding to Technical Screening or Additional Information Requests
FDA instructs applicants to modify the original eSTAR when responding to a Technical Screening or Additional Information request.
The general process is to:
Open the original eSTAR.
Select the Additional Information application subtype.
Use the Additional Information Response section that appears.
Copy each FDA question into the appropriate response field.
Provide a direct response beneath each question.
Add new or revised attachments to the affected sections.
Leave unaffected sections and original attachments in place.
Resubmit the complete updated eSTAR.
Do not switch to a newer template version after the original submission has been acknowledged. FDA states that the submission is effectively grandfathered to the original eSTAR version, and responses should be prepared by updating that original file.
A strong AI response should not merely state that the company disagrees with FDA. It should identify the concern, provide the requested evidence, explain where the evidence appears, and evaluate whether related sections of the submission also require revision.
Common eSTAR Mistakes
Beginning the template too late
The company discovers missing evidence only after design verification is complete.
Using an outdated saved template
The submission misses newer questions or regulatory expectations.
Allowing multiple people to edit the master file
Attachments are lost, answers are overwritten, and version control becomes unclear.
Selecting answers that minimize the visible sections
Relevant content is omitted and the submission risks a technical-screening hold.
Uploading reports without context
FDA receives data but no clear explanation of how the data support substantial equivalence.
Using vague attachment names
Reviewers cannot quickly identify the purpose or relevance of documents.
Signing before the package is final
The team later struggles to replace attachments or correct information.
Assuming “eSTAR COMPLETE” means “510(k) ready”
Structural completion is confused with regulatory adequacy.
Failing to reconcile the submission
The indications, device description, test articles, labeling, risk file, and 510(k) Summary tell different stories.
A Practical Final Readiness Checklist
Before uploading the submission, confirm that:
The current appropriate eSTAR template was used.
The primary predicate is legally marketed and appropriate.
The indications for use are finalized and consistently reproduced.
All device configurations are accounted for.
Every technological difference is identified.
Every difference is supported by evidence or a defensible rationale.
Worst-case selections are documented.
Test articles represent the final commercial design.
Acceptance criteria are scientifically and regulatorily justified.
Manufacturing and supplier information is accurate.
Biocompatibility, sterilization, packaging, shelf life, software, human factors, and other applicable sections are complete.
Labeling matches the evidence.
The 510(k) Summary matches the submission.
Every attachment opens from inside eSTAR.
Attachments have clear, descriptive names.
The unsigned final version has been preserved.
The signed file displays “eSTAR COMPLETE.”
The user fee and cover sheet have been completed.
Portal access has been confirmed.
A complete archival copy is retained.
eSTAR Is a Framework, Not a Substitute for Readiness
eSTAR has improved the structure of 510(k) submissions. It helps standardize content, guides applicants toward relevant evidence, and makes submissions easier for FDA reviewers to navigate.
But no template can repair an unsuitable predicate, inadequate testing, unsupported acceptance criteria, inconsistent design records, or an unclear substantial-equivalence argument.
The best submission teams use eSTAR early.
They allow its questions to influence the development plan, evidence matrix, testing strategy, document structure, and final readiness review. By the time the template displays “eSTAR COMPLETE,” the underlying regulatory argument should already be complete as well.
The objective is not simply to populate every field.
The objective is to give FDA a clear, consistent, technically sound path to a substantial-equivalence decision.
Preparing an eSTAR 510(k) Submission?
Texas BioVentures supports spine, orthopedic, and medical-device companies with 510(k) strategy, predicate research, eSTAR preparation, testing plans, acceptance-criteria development, technical documentation, submission review, and FDA Additional Information responses.
An independent readiness review can identify missing evidence and inconsistencies before the submission enters FDA’s review system—when they are still easier and less expensive to correct.
This article is provided for general informational purposes and does not constitute legal or regulatory advice.