A 510(k) submission can look neat, complete, and perfectly packaged inside eSTAR, then still get slowed down by questions FDA could see coming from page one.
That is the trap. FDA eSTAR gives you the structure. It tells you where to place device details, predicate information, performance data, labeling, cybersecurity evidence, and attachments. Since October 1, 2023, most 510(k) submissions must use this interactive PDF template unless an exemption applies.
But the template does not build your argument for you. It will not rescue a weak predicate, vague intended use, thin test rationale, missing software documentation, or unclear labeling.
This guide breaks down fda estar guidance from a practical 510(k) angle, so you understand what to prepare before opening the file, how to complete each major section, and how to avoid review problems that quietly cost weeks.
What is FDA eSTAR?
FDA eSTAR stands for electronic Submission Template And Resource. It is an interactive PDF template used for medical device premarket submissions. In a 510(k), it helps applicants enter submission details, answer required questions, and attach supporting documents in a structured format.
The template uses guided questions, drop-down fields, conditional logic, attachment prompts, and built-in resources. These features help organize the submission so the information is easier to prepare, review, and track.
eSTAR includes both structured and unstructured content. Structured content covers fields such as applicant details, submission type, product code, device information, recognized standards, and selected responses. Unstructured content includes supporting files such as test reports, device diagrams, labeling, software documentation, cybersecurity files, clinical data, risk management documents, and written justifications.
The template also does not show every section at once. It displays relevant questions based on the answers you choose, which makes the file more focused than a static form.
Need Help Preparing Your FDA eSTAR Submission?
Is eSTAR Mandatory for 510(k) Submissions?
Yes. eSTAR is mandatory for most 510(k) submissions sent to CDRH or CBER unless an FDA-listed exemption applies. FDA requires eSTAR for Traditional, Special, and Abbreviated 510(k) submissions, along with supplements and amendments connected to an original 510(k), unless the submission qualifies for an exemption.
FDA also states that eSTAR is the only electronic template currently available for preparing electronic 510(k) submissions. That means the requirement applies whether you are submitting your first device or your team has handled multiple FDA submissions before. If your company previously relied on eCopy workflows, your submission process now needs to fit the eSTAR format.
| Submission Type | eSTAR Status | Content Direction |
| Traditional 510(k) | Mandatory unless exempted | Used for standard substantial equivalence submissions |
| Special 510(k) | Mandatory unless exempted | Used for certain changes to a manufacturer’s own legally marketed device |
| Abbreviated 510(k) | Mandatory unless exempted | Used when relying on FDA guidance, special controls, or recognized standards |
| De Novo | Mandatory unless exempted | FDA requires eSTAR for De Novo submissions as well |
| PMA | Voluntary in certain cases | Not the main focus of this article |
| Q Submissions | Voluntary under current FDA eSTAR program status | Mentioned briefly because this guide focuses on 510(k) submissions |
What eSTAR Does Not Change About 510(k) Clearance
eSTAR changes how you organize and submit the file. It does not change what FDA expects you to prove.
A 510(k) is a premarket submission used to show that your device is substantially equivalent to a legally marketed device. In simple terms, FDA wants to see that your device has the same intended use as the predicate and that any technological differences do not raise new questions of safety or effectiveness.
That means the real work still sits inside the evidence. eSTAR can help you place information in the right fields, but it cannot make a weak comparison stronger. If the predicate device does not match the intended use, FDA can still question the submission. If technological differences are not explained clearly, the review can slow down. If performance testing does not support the comparison, the file can look complete on the surface and still fail to answer the reviewer’s main concern.
The same applies to labeling, software, cybersecurity, human factors, biocompatibility, sterilization, reprocessing, and electrical safety. A polished eSTAR file will not help much if labeling claims go further than the evidence, software documentation is incomplete, connected device security is thin, or critical user tasks are not addressed with proper human factors support.
In other words, eSTAR can help you build a cleaner submission package. It cannot replace the regulatory logic behind the 510(k).
| eSTAR Complete Means | Review Ready Means |
| Required fields are filled | Evidence supports each claim |
| Required attachments are added | Attachments are relevant and easy to review |
| Template logic is satisfied | Predicate comparison is persuasive |
| CDRH Portal can accept the file | FDA reviewer can follow the scientific rationale |
| The file passes a format gate | The submission can withstand substantive review |
For fda estar guidance, this distinction matters. The template helps you submit in the expected format, but clearance still depends on whether FDA can follow your reasoning, verify your evidence, and agree with your substantial equivalence claim.
Which FDA eSTAR Template Should You Use?
The first practical choice is simple: select the eSTAR template that matches your device type. FDA provides separate templates for non in vitro diagnostic devices and in vitro diagnostic devices.
For most 510(k) submissions, you will use one of these two templates:
- nIVD eSTAR for non in vitro diagnostic medical devices
- IVD eSTAR for in vitro diagnostic devices
FDA currently lists nIVD eSTAR Version 7.0 and IVD eSTAR Version 7.0 as the updated templates for 510(k), De Novo, and PMA device submissions. Version 6.2 templates can still be submitted until their retirement date, which FDA lists as August 3, 2026.
The June 1, 2026 FDA update also matters for teams preparing new submissions. FDA states that the nIVD and IVD eSTAR templates now include content from the Human Factors Content Guidance, published on May 29, 2026, and effective August 1, 2026.
Because eSTAR changes, avoid relying on old screenshots from 2023, 2024, or 2025 walkthroughs. A section, prompt, or attachment request shown in an older guide may not match the current template.
Here is FDA’s version rule in practical terms:
- FDA encourages applicants to use the updated version right away.
- Previous versions can be submitted until the listed retirement date.
- Retired versions may not be rejected automatically, but FDA may send Additional Information requests if current template changes apply to your device.
For a 510(k), the safest habit is to download the latest template directly from FDA before starting the submission file.
Step-by-Step FDA eSTAR 510(k) Submission Process
Opening eSTAR too early can create more work than it saves. The template asks for answers, but it will not tell you whether your pathway decision is sound, whether your predicate makes sense, or whether your evidence can carry the submission.
A better way to start is to settle the major regulatory questions first. Once those answers are clear, eSTAR becomes easier to complete because every section has a purpose.
Step 1: Confirm the Regulatory Pathway
Before you choose the 510(k) eSTAR template, confirm that your device actually belongs in the 510(k) pathway. FDA clearance depends on the device type, intended use, classification, risk profile, and the availability of a legally marketed predicate device.
For this article, we are focusing on 510(k) submissions. Still, the first check matters because not every device belongs here. Some products may need De Novo, PMA, or another FDA route.
For a 510(k), decide which submission type fits your device:
- Traditional 510(k): Used for a standard substantial equivalence submission.
- Special 510(k): Used for certain changes to your own legally marketed device.
- Abbreviated 510(k): Used when FDA guidance, special controls, or recognized standards support the submission.
Do not leave this decision as an informal assumption. Write down why the chosen pathway fits your device. Include the product code, device classification, review panel, intended use, and predicate logic. This record helps your team keep the same reasoning across the eSTAR file, attachments, labeling, and internal review notes.
Step 2: Select the Correct eSTAR Template
Pick the template that matches the device first.
Use nIVD eSTAR for devices that are not in vitro diagnostics. Use IVD eSTAR for in vitro diagnostic devices. Do not copy an old template from a past submission folder just because it looks familiar. FDA updates eSTAR, and an older file can miss prompts, wording, or attachment expectations that now apply.
Download the template directly from FDA before the project starts. Then record three details in your tracker:
- Template type
- Version number
- Download date
That small record helps later if the submission timeline stretches, a newer version appears, or the team needs to explain which template was used during preparation.
Step 3: Set Up the PDF Correctly
eSTAR is not a normal PDF you open in a browser, skim, and save later. It is a dynamic PDF, so download it first and open it from your computer.
Use PDF software that can handle the file properly. FDA recommends Adobe Acrobat Pro, PDF XChange Editor, or FoxIt PDF Reader. Adobe Acrobat Reader can open eSTAR, but it cannot save your changes or add attachments, which makes it a poor choice for preparing the actual submission.
Before anyone starts editing, set up the working file carefully:
- Save the eSTAR file on a local drive
- Create a clear backup naming system
- Keep a clean copy of the original download
- Avoid attaching documents from shared drives
- Assign one editor at a time
That last point matters. FDA says concurrent co authoring is not supported for dynamic PDFs. Team members can review and comment outside the live file, but edits need to happen one person after another. Otherwise, you risk version confusion, lost changes, or attachment problems before the FDA review even begins.
Step 4: Complete Administrative Information
This part looks routine, but it deserves a careful pass. FDA uses these details to identify the submitter, route communication, connect the file with payment records, and track the submission through the CDRH Portal.
Fill in the applicant details, correspondent details, submission type, user fee information, small business decision details if they apply, and the Truthful and Accurate Statement. Do not treat these as quick form fields. A mismatch in company name, contact details, FDA account information, cover letter, or user fee records can create avoidable back and forth.
Check these items before moving ahead:
- Applicant legal name
- Company address
- Official correspondent name
- Email and phone number
- Submission type
- User fee payment details
- Small business decision details, if used
- Truthful and Accurate Statement
- Matching information in the cover letter and FDA account
Pay close attention to the official correspondent. FDA communication and CDRH Portal tracking depend on this contact, so the person listed needs to be available, authorized, and ready to respond quickly if FDA asks for clarification.
Step 5: Enter Device Classification and Product Code Details
Now add the classification details that tell FDA what kind of device you are submitting. This includes the product code, regulation number, device class, review panel, and classification name.
Do not guess these fields from an old file or a competitor submission. Check FDA databases before entering the information into eSTAR. The product code needs to match the device’s intended use, technology, risk profile, and claimed predicate. If the code points in the wrong direction, the rest of the submission can start to feel inconsistent.
Review these details before saving the section:
- Product code
- Regulation number
- Device class
- Classification name
- FDA review panel
- Predicate device product code
- Applicable recognized standards
If you plan to rely on recognized standards, add them carefully and keep the supporting declarations or test evidence ready for attachment. The goal here is not to fill a field. It is to make sure the classification story matches the device you are asking FDA to clear.
Step 6: Add Predicate and Substantial Equivalence Information
This is the part of the 510(k) that needs real judgment. eSTAR gives you fields for the predicate and comparison, but the argument has to come from your evidence.
Start by identifying the predicate device or devices. Use the exact device name, 510(k) number, manufacturer, product code, and classification details. Do not choose a predicate only because it has the same product code. The predicate needs to make sense for the intended use, indications, technology, and risk profile of your device.
Compare intended use first. FDA will look at whether your device is meant for the same general purpose as the predicate. After that, move into technological characteristics, such as design, materials, energy source, software function, operating principles, user interface, patient contact, and performance specifications.
Your substantial equivalence narrative needs to do more than say the devices are similar. It needs to show the reader why the differences are acceptable.
Cover these points clearly:
- Predicate device or devices
- Intended use comparison
- Indications for use comparison
- Technological similarities
- Technological differences
- Safety and effectiveness impact
- Testing used to support the comparison
- Labeling or risk controls that address differences
When a difference exists, explain it directly. Then connect it to the right support. A material difference may need biocompatibility data. A software change may need software documentation and cybersecurity evidence. A new user interaction may need human factors support. A performance difference may need clinical or standards-based testing.
Step 7: Complete Device Description and Indications for Use
Write this section as if the reviewer has never seen your device before.
Start with the device itself. What is included in the box? What parts does the user touch? What connects to the patient? What powers it? What does the software do? Where is the device used? These details help FDA understand the product before they look at the test data.
Include the details that matter for review, such as:
- Main device components
- Accessories
- Models or variants
- Patient contacting materials
- Compatible systems
- Reusable parts
- Software enabled features
- Use environment
- Diagrams, images, or screenshots
Keep the indications for use tight. They need to match the predicate, labeling, and evidence in the file. If the wording claims more than your testing supports, FDA will notice.
Good visuals can also save the reviewer from guesswork. Add diagrams or images where they explain the device layout, workflow, connection points, user interface, or patient contact areas better than text alone.
Step 8. Attach Performance and Safety Evidence
Content Points
- Attach bench testing, electrical safety, EMC, mechanical testing, transport testing, shelf life, packaging validation, cleaning or reprocessing validation, sterilization validation, biocompatibility, and clinical evidence if required.
- Make each attachment easy to identify from its file name.
- In the text fields, summarize what the evidence proves rather than merely saying “see attached.”
- Cross reference the exact document section, table, figure, or test report when possible.
Step 9: Complete Software and Cybersecurity Sections
If the device uses software, treat this part with care. FDA will want to see how the software was built, tested, traced, released, and controlled.
Add the software information that applies to your device, such as:
- Software level of concern
- Software architecture
- Software requirements
- Hazard analysis
- Verification and validation results
- Traceability records
- Unresolved anomalies
- Release documentation
The software story needs to connect with the rest of the submission. If a feature appears in the labeling, user interface, risk file, or performance claims, the software evidence needs to support it.
For connected devices, cybersecurity evidence becomes just as important. FDA will expect a clear view of how the device handles security risks across design, testing, updates, and postmarket monitoring.
Include relevant cybersecurity documentation, such as:
- Cybersecurity risk management
- Threat model
- SBOM
- Vulnerability management process
- Update or patch process
- Authentication controls
- Encryption methods
- Logging
- Access controls
- Security testing evidence
For manufacturers preparing cybersecurity evidence as part of a 510(k), Qualysec can support technical testing through penetration testing, API testing, cloud testing, mobile testing, IoT testing, and external network assessments. This can help teams back their security claims with independent test evidence.
Need Cybersecurity Evidence for Your 510(k)?
Step 10: Review Labeling, Human Factors, and User Facing Claims
Labeling is not just packaging text. FDA will read it against your intended use, predicate, testing, risk analysis, and user claims. If the wording promises more than the evidence proves, the submission can invite questions even when the eSTAR file looks complete.
Attach the labeling materials that apply to your device, including instructions for use, device labels, warnings, contraindications, patient labeling, quick start guides, symbol explanations, and promotional claims where relevant.
Read each claim with care. Words like faster, safer, easier, automated, remote, continuous, or clinically proven need support in the submission. If the testing does not back the claim, revise the wording before FDA has to ask.
For devices where user interaction can affect safety, the human factors section needs the same attention. Include the planning, critical task analysis, use related risk analysis, validation protocol, validation results, and residual risk rationale where they apply.
The 2026 eSTAR human factors update makes the current template especially important. If your team is working from an older file or copied submission folder, review the usability evidence again before submission.
Step 11: Check eSTAR Completion Status
Before you upload the file, eSTAR needs to show “eSTAR COMPLETE.” That status matters because the CDRH Portal needs a completed file for submission.
Still, do not confuse complete with ready. The status only tells you that the template logic is satisfied. It does not confirm that every attachment is strong, current, readable, unlocked, or easy for FDA to review.
Open each attachment once before final upload. Check that the file matches the right section, has the correct version, opens without password issues, and is referenced properly in the eSTAR answers. Also review generated forms and the 510(k) summary content before locking the submission package.
Clear signing problems, missing attachment prompts, duplicate files, broken references, and unreadable documents before upload. These are small issues, but they can slow down a submission that could have moved cleanly into review.
Step 12: Submit Through CDRH Portal and Track FDA Communication
For CDRH submissions, upload the completed eSTAR file through the CDRH Portal. Once the file is submitted, your focus moves from preparation to tracking.
FDA says submissions received before 4 PM Eastern Time on a business day are processed the same day. If FDA receives the submission after 4 PM Eastern Time, processing moves to the next business day.
Do not leave the upload for the final hours before a response deadline, launch target, holiday, or fiscal year fee change. A login issue, file error, missing signature, or attachment problem can create last minute pressure that was easy to avoid.
After submission, assign someone to monitor:
- CDRH Portal status
- FDA emails sent to the official correspondent
- Technical screening updates
- Requests for clarification
- Review milestones and response deadlines
Your team needs to be ready for technical screening first, then substantive review. If FDA sends a question, internal ownership should already be clear so the response does not get delayed inside your own process.
Attachment Rules FDA Expects You to Know
Attachments are easy to underestimate. Your technical content may be ready, but if the file package is confusing, oversized, locked, outdated, or poorly named, FDA review becomes harder than it needs to be.
FDA does not require one naming format, but it recommends concise, descriptive file names. If you use numbering, FDA points to IMDRF style numbering, such as “1.01 Cover Letter.pdf” or “2.04.01 Device Description.docx.” Attachment names have a 124-character limit.
Use names that tell reviewers what they are opening. “6.03 Cybersecurity Threat Model.pdf” and “8.02 Software Traceability Matrix.xlsx” are clear. “Final Report Updated New Latest.pdf” is not.
Before adding files to eSTAR, check these basics:
- CDRH Portal limit is 1 GB per attachment and 4 GB for the full eSTAR file
- CBER ESG submissions are limited to 100 GB
- Word, Excel, MP4, and other accepted formats can be used
- Zip files and other unacceptable formats can be rejected
- Videos and images can be compressed, but readability must stay intact
- Final files are best stored in a controlled local folder before attachment
- Long PDFs need bookmarks or a table of contents
- Files should not be password protected or locked
- Placeholder files should be removed before submission
Keep an attachment tracker with the file name, owner, version, date, eSTAR section, and review status. This makes final quality checks easier and helps prevent the wrong file from entering the submission.
What Happens After You Submit eSTAR?
Submitting eSTAR does not mean the file moves straight to clearance. FDA still needs to process the submission, check fee information, screen the file, and review the evidence. Each stage has a different purpose, so your team needs to track both portal updates and FDA emails carefully.
After submission, the process usually includes:
- For CDRH submissions, the completed eSTAR file is sent through the CDRH Portal. The portal gives applicants near real time progress tracking for supported premarket submissions, while formal FDA notifications and requests are sent by email to the official correspondent.
- User fee details are checked against the submission. The payment, fee type, applicant details, and any small business information need to match. Fee errors can affect acceptance and timing, so the final article needs to verify the current FDA fee page because user fees change each year.
- eSTAR submissions are not expected to go through the old RTA review process. FDA uses technical screening to check whether the responses accurately describe the device and whether relevant attachments are included for applicable prompts. This is an early gate, not a scientific clearance decision.
- Technical screening issues can still cause a hold. Inaccurate drop down answers, missing attachments, irrelevant placeholder files, incomplete responses, or template logic problems can stop the file before full review begins.
- After the early checks, FDA reviews the evidence. Questions may focus on the predicate comparison, test methods, labeling, software documentation, cybersecurity controls, human factors, biocompatibility, sterilization, or clinical rationale.
Passing technical screening is useful, but it does not mean FDA agrees with the submission. It only means the file is ready to move further into review.
Technical Screening Issues That Can Delay an eSTAR 510(k)
Technical screening is not a full scientific review, but it can still stop your 510(k) from moving forward. Most delays at this point come from file logic, missing support, unclear answers, or attachments that do not match what eSTAR asks for.
| Issue | Why It Delays Review | How to Prevent It |
| Wrong dropdown answers | Relevant sections may not appear in the template | Have regulatory and technical leads review early answers before the file moves ahead |
| Outdated template version | FDA may ask for content that is missing from the older version | Download the latest eSTAR template before drafting |
| Placeholder attachments | Technical screening checks whether attachments are relevant | Attach real documents or provide clear rationales where allowed |
| Weak predicate comparison | FDA cannot assess substantial equivalence clearly | Build the intended use and technology comparison before filling eSTAR |
| Missing software files | Software enabled devices need traceability, testing, and validation support | Prepare a software evidence map early |
| Thin cybersecurity evidence | Connected devices face security review expectations | Include the threat model, SBOM, risk controls, testing, and update process |
| Locked or secured PDFs | Review and redaction can become harder | Avoid password protection and restrictive security settings |
| File names too long | eSTAR will not accept names beyond FDA’s limit | Keep attachment names under 124 characters |
| Unsupported labeling claims | Claims need evidence and predicate alignment | Review IFU, labels, marketing claims, and test reports together |
| Last minute signing changes | A signed eSTAR file may block attachment edits | Finalize attachments before signing the file |
Avoid Costly 510(k) Review Delays.
Conclusion
A 510(k) submission does not succeed because the eSTAR file looks tidy. It succeeds when FDA can see the logic without hunting for missing proof.
That is the real value of fda estar guidance. The template gives your team structure, but the strength still comes from the work behind it: a sound predicate, locked indications, relevant testing, clean labeling, complete attachments, and answers that match the evidence. If those pieces are weak, eSTAR will only organize the weakness more neatly.
The smartest teams treat the PDF as the final assembly point, not the starting point. They build the evidence map first, control the document versions, assign owners, and use the current FDA template so newer requirements, including 2026 human factors content, are not missed.
If your device includes software, connectivity, cloud features, APIs, mobile apps, or IoT components, Qualysec can help validate your cybersecurity evidence before preventable gaps reach FDA. Talk to a Security Expert
FAQs
What is FDA eSTAR?
FDA eSTAR is the electronic Submission Template And Resource used for medical device premarket submissions. For a 510(k), it works as an interactive PDF where you enter device details, choose relevant options, and attach the documents FDA needs for review. It replaces the old habit of building a scattered file package and gives the submission a more organized format.
Is eSTAR mandatory for 510(k) submissions?
For most 510(k) submissions, yes. Traditional, Special, and Abbreviated 510(k) submissions sent to CDRH or CBER generally need eSTAR unless an FDA listed exemption applies. Teams preparing a submission need to confirm the current FDA template and exemption rules before they begin drafting.
What are the benefits of using eSTAR?
The main benefit is fewer loose ends in the submission package. eSTAR guides applicants through required fields, prompts for attachments, and shows sections based on the device information entered. It can make the file easier to prepare and easier for FDA to screen, but it still depends on the strength of the evidence behind the answers.
How do you submit a 510(k) using eSTAR?
The process begins before the PDF is filled. Confirm the pathway, choose the right eSTAR template, prepare the evidence, add the required details, attach the supporting files, and check that the template shows “eSTAR COMPLETE.” For CDRH submissions, the completed file is then uploaded through the CDRH Portal, where the applicant can track status updates.
What are common mistakes in eSTAR submissions?
Delays can come from very practical problems. A team may use an old template, pick a dropdown option that hides a needed section, attach a draft file, miss software records, submit weak cybersecurity evidence, or include labeling claims that are not backed by testing. A careful review before upload can catch these issues while they are still easy to fix.
0 Comments