The FDA’s Electronic Submission Template and Resource (eSTAR) has fundamentally changed how 510(k) submissions are prepared, validated, and reviewed. What was once a largely document-driven process is now a structured, rules-based workflow that enforces completeness, consistency, and technical compliance before a submission is ever accepted for review.
For regulatory teams, eSTAR improves standardization, but it also raises the bar. The template does not just collect information. It actively checks whether required sections are complete, whether forms are properly filled, and whether attachments meet FDA technical requirements. Teams that treat eSTAR as a formatting exercise often encounter delays, technical screening holds, or avoidable rework.
Understanding the eSTAR process end-to-end is now essential for efficient 510(k) preparation.
Step 1: Confirm eSTAR Eligibility for Your Submission
Before starting, teams must confirm that their submission type is eligible for eSTAR. Most traditional, special, and abbreviated 510(k) submissions fall under the eSTAR requirement, but eligibility depends on both device type and reviewing center.
The FDA provides formal guidance outlining which submissions must use eSTAR and which are exempt.
Failing to confirm eligibility upfront can result in preparing the wrong submission format and losing time late in the process.
Step 2: Download the Current eSTAR Template from the FDA
Once eligibility is confirmed, teams should download the most current eSTAR PDF directly from the FDA. The template is periodically updated, and outdated versions may trigger technical screening issues.
The eSTAR file is a dynamic PDF that includes embedded instructions, logic checks, and validation rules. It is not a static form and should be treated as an interactive submission environment.
Step 3: Follow the eSTAR Structure and Embedded Instructions
The eSTAR template guides teams through a predefined structure aligned with FDA review expectations. Each section includes prompts and validation rules designed to ensure required content is provided.
Key sections include:
- Applicant and contact information
- Indications for use
- Device description and technological characteristics
- Predicate device comparisons
- Performance testing and standards conformity
- Labeling and claims
While the template provides structure, it does not generate regulatory strategy. Teams remain responsible for ensuring that pathway decisions, predicate selection, and substantial equivalence rationale are defensible and supported by FDA precedent.
Step 4: Attach Supporting Documentation Correctly
Supporting documentation must be attached directly within the relevant eSTAR sections. This typically includes:
- Detailed device descriptions
- Performance and bench testing reports
- Biocompatibility assessments
- Software documentation, when applicable
- Clinical data, if required
- Draft labeling
To avoid technical screening issues, attachments should be consolidated logically by section. Excessive file fragmentation increases the risk of formatting errors and review delays.
Step 5: Manage File Size and Format Requirements
The FDA enforces strict technical constraints on eSTAR submissions. The total submission size must not exceed 4 GB, and all files must use FDA-accepted formats.
Best practices include compressing PDFs where possible, avoiding unnecessary duplication, and ensuring multimedia files meet FDA specifications.
The FDA publishes a checklist outlining common technical screening issues.
Ignoring these requirements is one of the most common causes of early submission holds.
Step 6: Complete Required FDA Forms Within eSTAR
Several FDA forms are completed directly within the eSTAR workflow rather than uploaded separately. These include:
- Form FDA 3514 (Truthful and Accurate Statement)
- Form FDA 3881 (Indications for Use)
- 510(k) Summary or Statement
- Declarations of Conformity, where applicable
Because these forms are embedded, inconsistencies between narrative sections and form responses are more easily flagged by the template.
Step 7: Confirm eSTAR Completion Status Before Submission
At the top of the eSTAR file, the template displays a status indicator. Submissions should only be transmitted once the status reads “eSTAR Complete.”
Submitting while the status shows “eSTAR Incomplete” can result in the FDA placing the submission on an eCopy or technical screening hold, delaying review until a corrected submission is provided.
Step 8: Submit Through the Appropriate FDA Portal
Completed eSTAR submissions are transmitted electronically based on the reviewing center.
For CDRH-regulated devices, submissions are sent through the CDRH Customer Collaboration Portal.
For CBER-regulated products, submissions are sent through the Electronic Submission Gateway (ESG).
All non-exempt 510(k) submissions must now be submitted electronically using eSTAR.
Step 9: FDA Technical Screening and Status Outcomes
After submission, the FDA conducts an initial technical screening to confirm that the eSTAR file meets all structural and formatting requirements.
Outcomes include:
- Technical Screening OK (TSOK), allowing substantive review to begin
- Technical Screening Incomplete (TSIC), placing the submission on hold until deficiencies are corrected
If a submission is deemed technically incomplete, teams typically have up to 180 days to submit a complete replacement eSTAR.
Where Veridocx Fits in the eSTAR Workflow
While eSTAR enforces submission structure, it does not determine regulatory strategy. Teams must still establish defensible pathway decisions, predicate selections, substantial equivalence rationale, and evidence planning before populating the template.
Veridocx supports this upstream work by providing structured classification analysis, systematic predicate identification, substantial equivalence comparisons, and gap analysis with FDA-recognized standards mapping and citations. These outputs can then be translated directly into eSTAR sections with greater confidence and traceability.
Final Thoughts
The eSTAR template has improved consistency and submission quality across FDA premarket reviews. At the same time, it has made gaps in regulatory strategy more visible and more costly.
Teams that treat eSTAR as the final step, rather than the endpoint of a well-reasoned regulatory process, are better positioned to avoid delays, reduce rework, and move through review more efficiently.
eSTAR does not replace regulatory judgment. It makes that judgment visible.
Frequently Asked Questions (FAQ)
1. What is eSTAR, and why does FDA require it for 510(k) submissions?
eSTAR is the FDA’s electronic submission template designed to standardize how premarket submissions are prepared and reviewed. It replaces traditional static PDF submissions by guiding manufacturers through required content in a structured, interactive format. FDA requires eSTAR to improve submission quality, reduce administrative deficiencies, and streamline technical screening.
2. Are all 510(k) submissions required to use eSTAR?
Yes. With limited exceptions, all 510(k) submissions must be submitted using the eSTAR template. Submissions that do not follow the eSTAR format may be rejected or placed on hold during technical screening.
3. What happens if an eSTAR submission is marked “Incomplete”?
If an eSTAR submission is submitted while still marked as incomplete, FDA may place the submission on an eCopy or Technical Screening hold. This pauses the review clock and requires the manufacturer to correct deficiencies and resubmit a complete version before review can proceed.
4. What types of documents need to be attached within eSTAR?
Manufacturers must attach supporting documents such as device descriptions, performance testing reports, biocompatibility data, sterilization information, software documentation (if applicable), clinical data (if required), and draft labeling. Each attachment must meet FDA file format and size requirements.
5. How strict are eSTAR file size and formatting requirements?
eSTAR has defined limits for total submission size and acceptable file formats. Exceeding these limits or using unsupported formats can result in submission errors or holds. Teams often need to consolidate documents, compress files appropriately, and ensure consistent formatting across sections.
6. Does eSTAR change the regulatory requirements for a 510(k)?
No. eSTAR does not change the substantive regulatory requirements for a 510(k). It changes how information is organized, presented, and validated before submission. All regulatory expectations around substantial equivalence, safety, and effectiveness remain the same.
7. Can multiple team members collaborate on an eSTAR submission?
Yes, but collaboration must be managed carefully. Because eSTAR is a structured PDF, version control and coordination are critical. Teams often assign clear ownership of sections to avoid conflicts, overwriting, or inconsistencies across the submission.
8. How does FDA review eSTAR submissions differently from traditional PDFs?
FDA reviewers receive information in a standardized format, which helps them locate key content more quickly and identify missing elements earlier. While the scientific and regulatory review principles are unchanged, the structured format can reduce back-and-forth related to administrative issues.
9. What are the most common mistakes teams make with eSTAR?
Common issues include incomplete sections, missing attachments, inconsistent device descriptions across sections, unclear predicate rationale, and submitting before the system indicates completion. These mistakes frequently lead to technical screening delays.
10. How should teams prepare before starting an eSTAR submission?
The most effective approach is to finalize regulatory strategy before opening the eSTAR template. This includes confirming pathway, predicate selection, testing strategy, and labeling claims. Teams that treat eSTAR as a documentation step rather than a strategy tool tend to move through the process more smoothly.
