eSTAR 510(k) Submission Readiness: A Practical Checklist for Evidence and Deficiencies

An eSTAR 510(k) readiness checklist connects each applicable submission section to an accountable owner, controlled evidence and a documented gap decision. It helps a medical device team prepare the submission; it does not replace FDA's eSTAR template or establish substantial equivalence.

Since October 1, 2023, FDA requires 510(k) submissions to use eSTAR unless an exemption applies. A completed interactive PDF is not the same as a scientifically sufficient submission. This guide explains how to use the Cahir MedTech eSTAR 510(k) Submission Readiness & Deficiency Checklist to organize the work before upload.

Confirm the pathway before completing the template

Start with the device's intended use, classification regulation and product code. Determine whether a premarket notification is required and whether a suitable legally marketed predicate exists. A device is not eligible for 510(k) simply because it resembles another product. For an unfamiliar device category, read our FDA premarket pathways guide and confirm device-specific special controls and guidance.

Identify the appropriate 510(k) type and current eSTAR version. Use FDA's current submission instructions and the relevant center's delivery process; the CDRH Portal supports online submission to CDRH. Verify the user fee applicable when FDA receives the submission, any small-business determination and the correct payment identification. Do not copy a prior fiscal year's fee into a new filing plan.

Separate technical screening from substantive review

FDA's 510(k) submission process explains that eSTAR submissions are not anticipated to undergo the traditional refuse-to-accept, or RTA, process. FDA instead performs virus scanning and technical screening. An incomplete eSTAR can be placed on hold while the submitter prepares a complete replacement.

That distinction matters: an eSTAR technical-screening hold is not the same as an eCopy RTA hold, and neither proves that the device's scientific evidence is adequate. During substantive review, FDA evaluates the submission and may seek Additional Information, often abbreviated AI. Here, AI means a regulatory information request, not artificial intelligence.

FDA states that a replacement eSTAR must be received within 180 days of a technical-screening deficiency notification or the submission is considered withdrawn. A complete response to a substantive AI request is due within 180 calendar days of that request. These are different triggers. Use the actual FDA correspondence to establish each deadline; do not interpret either period as a promise of clearance within 180 days.

Use the workbook in four passes

The workbook includes Start Here, Section Readiness, Deficiency Log and Sources and Applicability. Its 20 readiness rows and 10 deficiency prompts are Cahir MedTech preparation aids, not an FDA-issued exhaustive checklist or a ranking of the most frequent deficiencies.

Use Ready only when the responsible reviewer can retrieve the right evidence. N/A needs a written rationale. A file attached under the correct heading may still concern the wrong device configuration, an obsolete protocol or a different intended use.

Build a claims-to-evidence chain

Keep Indications for Use, the device description, predicate comparison and proposed labeling consistent. Map technological differences to the evidence needed to address them. A predicate comparison table is useful only when it explains the differences, not when it hides them behind broad statements such as “equivalent technology.”

Evidence depends on the device and claims. Patient-contacting materials may need a biocompatibility evaluation; sterile devices require relevant sterility information; software functions need an appropriate documentation-level rationale. For cybersecurity risk, coordinate the filing with our premarket cybersecurity and SBOM workflow. Not every device needs every test listed in the workbook.

Check FDA recognition and any transition provisions before relying on a declaration of conformity to a consensus standard. An unrecognized standard is not automatically prohibited, but its use needs an appropriate explanation and supporting evidence. The workbook is not a substitute for confirming the applicable edition and submission expectations.

Example: an imaging AI release with mismatched evidence

Consider an illustrative radiology AI filing: the eSTAR device description identifies version 2.1, but the clinical report names version 2.0 and the software verification report names a pre-release build. Marking all three sections Ready would conceal a configuration question.

Record the mismatch in the Deficiency Log. Assign an owner to establish what changed, whether prior evidence remains applicable and what additional work is necessary. Link the approved assessment and updated reports back to the Section Readiness rows. Do not assume a version change is insignificant because performance averages appear similar. Our radiology AI validation guide explains the related dataset and clinical evidence questions.

Run a final cross-functional review

• Confirm the pathway, predicate rationale and submission type.
• Resolve contradictory indications, labeling and device configuration references.
• Retrieve every applicable report and approved applicability rationale.
• Check software, cybersecurity and device-specific evidence expectations.
• Verify the current eSTAR version, upload instructions and user fee.
• Assign an owner for FDA correspondence and deadline tracking.
• Retain the submitted version and receipt confirmation in controlled records.

Submission readiness is a team decision supported by evidence, not an automatically calculated regulatory result. Preserve review decisions and document changes rather than silently overwriting the submission baseline.

Download the checklist and coordinate the work

Open the eSTAR checklist template card and sign in with your work email to download the free branded Excel workbook. Use the spreadsheet to organize the detailed submission register and your company workspace to coordinate the toolkit work available to your team. A free template download is not a promise that its individual spreadsheet rows appear automatically in the dashboard; downloaded files do not synchronize edits with the workspace.

For help drafting and reviewing regulatory material, explore Cahir MedTech Copilot. Keep qualified regulatory and technical review in the process: generated text cannot establish substantial equivalence or replace testing.

eSTAR 510(k): quick answers

What is FDA eSTAR?

FDA eSTAR is the electronic Submission Template And Resource, an interactive template that guides medical device submission preparation. It organizes applicable information and attachments; it is not a clearance decision or a replacement for scientific evidence.

Is eSTAR mandatory for a 510(k) submission?

Since October 1, 2023, FDA requires 510(k) submissions to use eSTAR unless an exemption described in its electronic-submission guidance applies. Confirm the current guidance and submission instructions before filing.

Does a completed eSTAR avoid all FDA deficiencies?

No. FDA can identify incomplete information during technical screening and request additional evidence during substantive review. Technical completeness does not establish substantial equivalence or guarantee clearance.

How long do I have to answer an FDA Additional Information request?

FDA describes a 180-calendar-day period from the substantive Additional Information request for a complete response. A technical-screening deficiency notification has its own replacement-eSTAR deadline. Track the date and instructions in the actual FDA correspondence.

Is the Cahir MedTech eSTAR checklist an official FDA submission template?

No. It is a free, work-email-gated Excel planning aid for owners, evidence and gap decisions. Prepare and submit the actual filing using FDA's current eSTAR and instructions.

FDA sources and applicability

• FDA eSTAR Program: current templates and program instructions.
• FDA electronic submission guidance for 510(k)s: format requirements and exemptions.
• FDA 510(k) submission process: verification, screening, substantive review and response deadlines.
• 21 CFR Part 807, Subpart E: premarket notification requirements.

Published October 21, 2026. Sources checked for this edition; consult current FDA materials and device-specific requirements before submission. This article and workbook are educational preparation tools, not legal advice or FDA authorization.