510(k) Submissions: How to Prepare and File a 510(k)

510(k) submissions to FDA via eSTAR and the CDRH Portal

Since 1 October 2023, all 510(k) submissions, unless exempted, must be submitted electronically using eSTAR (FDA). For FDA's fiscal year 2027, which started on 1 October 2026, the 510(k) user fee is USD 28,653, or USD 7,163 for a qualifying small business (Federal Register).

Most delays come from an incomplete file, not from the science. This article covers the 510(k) types, the required contents, software documentation, eSTAR and the CDRH Portal, the review clock, and when a change needs a new 510(k). Our article on 510(k) vs PMA explains when a 510(k) is the right route at all.

The three 510(k) types

Type When FDA generally reviews within
Traditional Any original 510(k), or a change that needs a submission 90 days
Special A change to the holder's own legally marketed device, evaluated with well-established methods, with results reviewable in a summary or risk analysis format 30 days
Abbreviated Relies on guidance documents, special controls or recognised standards; the 21 CFR 807.87 elements are still required 90 days

Source: FDA, 510(k) Submission Programs.

According to FDA, the user fee is the same for all three. In our view, choosing Special is an eligibility decision: the change and the evaluation methods must fit the programme. If there is no suitable predicate, a De Novo request may be the right route instead.

What the submission must contain

Under 21 CFR 807.87, a 510(k) includes:

  • (a) the device name, including trade name and common name;

  • (b) the establishment registration number, if applicable;

  • (c) the class and classification panel;

  • (d) action taken to comply with any performance standards;

  • (e) proposed labelling;

  • (f) a comparison with similar legally marketed devices, with supporting data;

  • (g) data for significant changes or new indications;

  • (h) a 510(k) summary or a 510(k) statement;

  • (i) financial certification or disclosure under 21 CFR Part 54, where applicable;

  • (j) statements on clinical investigations, where applicable;

  • (l) a statement that the information is truthful and accurate.

510(k) summary 510(k) statement
Rule 21 CFR 807.92 21 CFR 807.93
What it is The safety and effectiveness information set out in 807.92, in a separate section of the submission A certified commitment to provide that information on request
Timing Submitted with the 510(k) Information provided within 30 days of a request

Sources: 21 CFR 807.92 and 807.93.

In our view, where an item does not apply, say so and explain why, rather than leaving the reviewer to assume.

Software documentation

For device software, FDA's guidance Content of Premarket Submissions for Device Software Functions (June 2023) sets two documentation levels:

Level When
Basic Where Enhanced does not apply
Enhanced Where a failure or flaw of the device software function could present a hazardous situation with a probable risk of death or serious injury, assessed before risk controls are applied

Source: FDA, Content of Premarket Submissions for Device Software Functions, June 2023.

The elements include the documentation level evaluation, a software description, the risk management file, the software requirements specification, an architecture diagram, the software design specification (Enhanced only), development and maintenance practices (or a declaration of conformity to IEC 62304), testing, revision history and unresolved anomalies. The guidance is nonbinding.

In our view, settle the documentation level first, because it decides what the software section contains. Our articles on SaMD technical documentation and FDA software validation guidance cover the underlying records.

eSTAR and the CDRH Portal

According to FDA's eSTAR programme and CDRH Portal pages:

  • eSTAR builds in forms such as the Indications for Use form and the cover sheet, and can generate the 510(k) summary;

  • the eSTAR must show "eSTAR COMPLETE" before it is submitted;

  • the Portal accepts up to 1 GB per attachment and 4 GB per eSTAR;

  • submissions received before 4 PM ET on a business day are processed the same day.

In our view, check that device names, configurations and indications match across the eSTAR and every attachment before uploading. A complete form does not mean complete evidence.

Device listing is a separate obligation. Our article on device listing with FDA covers it.

The review clock

Stage Timing Source
Hold Letter if the fee or a valid eSTAR is missing Usually within 7 days of receipt; 180 calendar days to resolve FDA process page
Technical screening (eSTAR) Not anticipated to undergo refuse to accept (RTA); an incomplete eSTAR is placed on hold, with 180 days to send a complete replacement FDA process page
Acceptance review (eCopy) Within 15 days; an RTA hold gives 180 calendar days to respond FDA process page
Substantive Interaction Within 60 calendar days of receipt: Interactive Review or an Additional Information (AI) request FDA process page
AI response Complete response within 180 calendar days; no extensions FDA process page
MDUFA decision goal 90 FDA days, excluding days on hold for an AI request FDA process page
Missed MDUFA Communication If no decision within 100 FDA days FDA process page

Source: FDA, 510(k) Submission Process.

FDA days are not calendar days. The time spent answering an AI request is not counted, so the elapsed time is usually longer than 90 days. A cleared 510(k) receives a substantially equivalent (SE) letter with the Indications for Use and the 510(k) summary or statement attached.

When a change needs a new 510(k)

A new 510(k) is needed when a change could significantly affect safety or effectiveness, or when there is a major change to the intended use. FDA's October 2017 guidances, Deciding When to Submit a 510(k) for a Change to an Existing Device and Deciding When to Submit a 510(k) for a Software Change to an Existing Device, help with that decision.

In our view, record each "new 510(k) or not" decision in change control at the time of the change, under the QMSR.

A hypothetical example

Hypothetical example: a Dutch SaMD company has a cleared predicate with the same intended use.

  1. Type: it chooses a Traditional 510(k).

  2. Software: it assesses the documentation level and prepares the software section accordingly.

  3. eSTAR: it completes the eSTAR with the requirements specification, architecture, test results and a 510(k) summary, checks it shows "eSTAR COMPLETE", pays the FY 2027 fee and uploads it through the Portal.

  4. Review: FDA sends an AI request; the company sends a complete, point-by-point response within 180 days.

  5. Later change: it assesses a software update against the software change guidance and records the decision and rationale in change control.

Conclusion

A 510(k) succeeds or stalls on the completeness of the file: the right type, all 807.87 elements, a software section at the right documentation level, and a consistent eSTAR.

In our view, assign one owner to a pre-filing check, settle the documentation level early, and treat the AI response deadline as fixed.

If you need help preparing a 510(k), our global market registrations team can help, or contact MedQAIR.

Frequently asked questions

Is eSTAR mandatory for a 510(k)?

Yes. Since 1 October 2023, all 510(k)s must use eSTAR unless exempted.

Is a Special 510(k) faster?

FDA generally reviews a Special 510(k) within 30 days, but only changes to the holder's own device that fit the programme qualify. The fee is the same.

Should I submit a 510(k) summary or a statement?

Either is allowed. A summary is submitted with the 510(k); a statement commits you to provide the information within 30 days of a request.

What happens if I miss the AI response deadline?

If FDA does not receive a complete response within 180 calendar days, the 510(k) is considered withdrawn and you must submit a new one.

Does every software update need a new 510(k)?

No. Only changes that could significantly affect safety or effectiveness, or that change the intended use, need a new 510(k). Record the decision either way.

Latest Blogs

November 16, 2026

The MDR has applied since 26 May 2021. In the US, the Quality Management System Regulation (QMSR) took effect on

November 15, 2026

The MDR has applied since 26 May 2021, with stricter designation requirements for notified bodies than under the directives. Implementing

November 14, 2026

Since 1 October 2023, all 510(k) submissions, unless exempted, must be submitted electronically using eSTAR (FDA). For FDA's fiscal year

logo

Unlock Your Quick Guide to AI Act
Compliance!

Explore AI-enabled SaMD requirements with our easy step-by-step guide.

Cookies help us improve your experience on our website. By using our site, you consent to the use of cookies as described in this policy.