FDA 510(k) Application: Submission Components and Format Requirements

Every section of an FDA 510(k) application explained — cover sheet, indications for use, device description, SE discussion, testing, labeling, software, and the eSTAR template structure.

What Goes Into a 510(k) Application

A 510(k) application — formally called a premarket notification — is a structured package of information that demonstrates to the FDA that your medical device is substantially equivalent to a legally marketed predicate device. The regulatory basis is Section 510(k) of the Federal Food, Drug, and Cosmetic Act (FD&C Act) and the implementing regulations in 21 CFR Part 807 Subpart E.

Since October 1, 2023, all 510(k) submissions must be submitted electronically using the FDA's eSTAR (electronic Submission Template and Resource) template. The days of free-form PDF submissions are over. eSTAR provides a standardized, interactive PDF that guides you through each required section with built-in validation checks, dropdown menus, and links to relevant guidance documents.

This guide breaks down every component of a 510(k) application, explains what each section requires, and shows how the eSTAR template structures the submission for both the applicant and the FDA reviewer.

The Legal and Regulatory Foundation

The content requirements for a 510(k) are defined in 21 CFR 807.87, which lists the information that must be included in a premarket notification. The recommended format is described in the FDA guidance document "Format for Traditional and Abbreviated 510(k)s" (originally issued August 2005, updated subsequently). eSTAR implements these requirements in a structured electronic format.

A 510(k) submission is not a form. It is a comprehensive technical and regulatory dossier. The eSTAR template provides the structure, but you must populate it with your device-specific content.

510(k) Application Sections: The Complete Breakdown

The sections below follow the structure of both the traditional 510(k) format and the current eSTAR template (Version 7.0, 2026). eSTAR groups them into functional categories that align with how FDA reviewers evaluate submissions.

Section 1 — Medical Device User Fee Cover Sheet (Form FDA 3601)

The first section is the user fee cover sheet. Before FDA will accept your 510(k) for review, you must pay the applicable user fee. For FY 2026 (October 1, 2025 through September 30, 2026), the standard 510(k) user fee is $26,067. Small businesses that qualify for the reduced fee pay $6,517.

To qualify as a small business, you must submit a Small Business Certification Request to FDA before submitting your 510(k), with supporting documentation showing that your firm (including all affiliates) had gross receipts of $100 million or less in the most recent tax year.

Form FDA 3601 documents your payment and is included as the first page of your submission.

Key point: FDA will not begin review until the user fee is paid and verified. Submit your fee payment early enough that it clears before your planned submission date.

Section 2 — CDRH Premarket Review Submission Cover Sheet

This is the administrative cover sheet that identifies the submission type (Traditional, Special, or Abbreviated 510(k)), the submitter's contact information, and the regulatory information that routes the submission to the correct FDA review branch.

In eSTAR, this section uses dropdown menus and auto-populated fields to capture:

Submitter name and address
Contact person (name, phone, email)
Submission type (Traditional 510(k), Special 510(k), Abbreviated 510(k))
Device classification information
Product code and classification regulation
Reviewing center (CDRH or CBER)

Section 3 — 510(k) Cover Letter

The cover letter is your submission's executive summary. It should include:

The purpose of the submission (new 510(k), supplement, or amendment)
The device name (both proprietary and common)
The classification and product code
The predicate device(s) you are comparing against, including their 510(k) numbers
A brief statement of why the device is substantially equivalent
Any requests for confidential treatment of specific information

The cover letter sets the tone for the review. FDA's lead reviewer reads it first, and a clear, well-organized cover letter helps the reviewer understand what they are evaluating.

Section 4 — Indications for Use Statement

The indications for use (IFU) statement is one of the most critical sections of the 510(k). It defines what the device is intended to do, for whom, and in what clinical context.

FDA evaluates substantial equivalence by first comparing the indications for use of your device against the predicate. The indications must be the same as or narrower than the predicate's cleared indications. Broader indications — even slightly broader — will result in an NSE (not substantially equivalent) determination or a request for additional information.

Common mistakes:

Writing indications that are broader than the predicate's cleared scope
Adding specificity that raises new questions about safety or effectiveness rather than narrowing the scope
Using marketing language instead of clinical language
Failing to match the predicate's indications line by line

The IFU should be written precisely, reviewed against the predicate's cleared IFU, and finalized before you begin the substantial equivalence discussion.

Section 5 — 510(k) Summary

The 510(k) Summary is a public document. FDA makes it available in the 510(k) database within 30 days of a substantial equivalence determination per 21 CFR 807.95(d). Because it becomes publicly searchable, it requires careful drafting — include enough to satisfy FDA requirements without disclosing proprietary competitive information.

The summary must include:

Submitter identification
Device name and classification
Predicate device identification (including 510(k) number)
Device description and intended use
Summary of the technological characteristics comparison
Summary of performance testing
Summary of the substantial equivalence conclusion

Section 6 — Truthful and Accuracy Statement

A signed statement certifying that all information in the submission is truthful and accurate, and that no material facts have been omitted. This is a regulatory requirement and is standard across FDA submissions.

Section 7 — Class III Summary and Certification

Required only when the device was previously classified as Class III and has been reclassified to Class II or I. Most 510(k) submitters do not need this section. If applicable, it summarizes the reasons for reclassification and certifies that the device meets the reclassification criteria.

Section 8 — Financial Certification or Disclosure Statement

Required when clinical data from investigator-initiated studies is included in the submission. This documents whether any financial arrangements exist between the sponsor and the clinical investigators that could affect the integrity of the data. Most 510(k) submissions that rely on bench testing rather than clinical studies do not need this section, but it must be addressed (even if to state it is not applicable).

Section 9 — Declarations of Conformity and Summary Reports

This section documents compliance with FDA-recognized consensus standards and special controls. For each standard you declare conformity to:

Identify the standard (number, title, edition, and year)
Specify which parts of the standard you conform to
Describe any deviations from the standard and justify them
Provide a summary of the test results demonstrating conformity

Declarations of conformity are a key component of Abbreviated 510(k)s, which rely on conformity to standards and guidance documents rather than full raw data submissions.

Section 10 — Executive Summary

The executive summary provides a concise overview of the entire substantial equivalence argument. It should clearly state:

What the device is and what it does
What predicate device(s) it is being compared to
What the key technological similarities and differences are
What testing was performed to address any differences
Why the device is substantially equivalent

This is the section where you tell the reviewer the story of your device in 2–4 pages.

Section 11 — Device Description

The device description must be detailed enough for the reviewer to understand the device's design, materials, principles of operation, and physical characteristics. It should include:

Physical dimensions and construction
Materials in contact with the patient (with biocompatibility status)
Principles of operation (mechanism of action)
Accessories and components included with the device
Software functionality (if applicable)
Packaging configurations
Sterile or non-sterile status
If sterile, the sterilization method

The device description is where you demonstrate that you have thoroughly characterized your product. Compare each element against the predicate device to highlight similarities and differences.

Section 12 — Substantial Equivalence Discussion

This is the legal and technical heart of the 510(k) application. FDA's substantial equivalence evaluation follows a decision framework defined in Section 513(i) of the FD&C Act:

Step 1 — Same intended use? FDA first determines whether the new device and the predicate have the same intended use. Different intended use means automatic NSE.

Step 2 — Same technological characteristics? If the intended use matches, FDA evaluates whether the technological characteristics are the same or different.

Step 3 (if different) — Do the differences raise new questions of safety or effectiveness? If the technology is different, FDA asks whether those differences introduce new risks or require new types of evidence.

Step 4 (if no new questions) — Is the device as safe and effective as the predicate? The submitter must provide performance data (bench testing, engineering analysis, and in some cases clinical data) demonstrating that the device performs as well as the predicate.

Your substantial equivalence discussion must walk through each step with supporting evidence.

Section 13 — Proposed Labeling

Labeling includes the device label, instructions for use (IFU), and any patient labeling. The labeling must:

Include all required elements per 21 CFR 801
Be consistent with the indications for use statement
Include warnings, precautions, and contraindications supported by the risk analysis
Be compared against the predicate device labeling to demonstrate consistency

FDA reviews labeling carefully because it defines the boundaries of how the device can be marketed. Promotional claims that go beyond the cleared indications are considered off-label promotion.

Section 14 — Sterilization and Shelf Life

For devices labeled sterile, this section must include:

Sterilization method and parameters
Sterility assurance level (SAL), typically 10⁻⁶
Packaging validation (per ISO 11607)
Shelf life validation (accelerated and real-time aging)
Residual testing (if applicable, e.g., ethylene oxide residuals)
Bioburden and pyrogen testing data

For non-sterile devices, this section may be minimal but should address any shelf-life stability claims made in the labeling.

Section 15 — Biocompatibility

For devices that contact the patient, a biocompatibility evaluation per ISO 10993-1 is required. The evaluation should include:

Device categorization by nature of body contact and contact duration
Identification of endpoints to evaluate (cytotoxicity, sensitization, irritation, systemic toxicity, etc.)
Test results or a justification for why specific endpoints do not need testing
Chemical characterization of materials (if used as part of the evaluation)

FDA expects a biocompatibility evaluation report, not just test certificates. The report should integrate test results with the device's intended use and risk profile.

Section 16 — Software Documentation

For devices that include software, the software documentation section must include:

Software description and level of concern (per FDA's "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices")
If using eSTAR, the template incorporates the updated QMSR terminology and the 2025 Real World Evidence guidance
Software lifecycle documentation per IEC 62304 (now aligned with QMSR requirements)
Risk analysis for software-related hazards
Verification and validation testing results
Version history and unresolved anomalies

The level of documentation required scales with the risk level of the software. FDA defines three levels of concern: Minor, Moderate, and Major.

Section 17 — Electromagnetic Compatibility and Electrical Safety

For electrically powered devices:

EMC testing per IEC 60601-1-2 (including the applicable edition referenced by FDA)
Electrical safety testing per IEC 60601-1
Wireless coexistence testing (if applicable, per FDA guidance on radio-frequency wireless technology)

Section 18 — Performance Testing

Performance testing is the evidence that supports your substantial equivalence claim. This section includes:

Bench testing protocols and results
Engineering analysis
Comparative testing against the predicate device (when applicable)
Animal studies (if included)
Clinical studies (if included — not required for most 510(k)s)

Each test should be traceable to a design input requirement and the test methods should be described in sufficient detail for the reviewer to evaluate their adequacy.

Cybersecurity Documentation

For devices that connect to the internet, a network, or other devices, FDA expects cybersecurity documentation including:

A cybersecurity risk analysis identifying threats, vulnerabilities, and risk mitigations
A Software Bill of Materials (SBOM) in SPDX or CycloneDX format
An interoperability profile describing how the device connects and communicates
A plan for ongoing vulnerability management and patch deployment (required by Section 524B of the FD&C Act for cyber devices)

Even if your device does not have connectivity features, include a brief statement explaining why cybersecurity documentation is not applicable. Leaving sections unaddressed without explanation triggers follow-up questions from FDA.

eSTAR Template: What Changed in 2026

The current eSTAR template (Version 7.0, released June 1, 2026) incorporates several updates from Version 6:

QMSR alignment: Terminology reflects the Quality Management System Regulation (effective February 2, 2026), including references to Design and Development File (replacing DHF), Medical Device File (replacing DMR), and batch records (replacing DHR)
Real World Evidence (RWE): Content aligned with the FDA's updated RWE guidance (effective February 16, 2026), including structured fields for documenting real-world data sources and analytical methods
IDE submissions: eSTAR is now available for voluntary use for Investigational Device Exemption (IDE) original submissions and supplements
PreSTAR updates: The Early Submission Requests eSTAR (PreSTAR) now supports Q-Submissions, IDEs, and 513(g) requests

Older template versions (6.2) will be retired on August 3, 2026. Submitters must use Version 7.0 after that date.

Three Types of 510(k) Applications

Traditional 510(k)

The most common type. Used when you are making a direct comparison to a predicate device and providing performance data to support substantial equivalence. The sections described above are all applicable.

Special 510(k)

Used for certain design changes to your own legally marketed device where the intended use remains the same and the changes do not raise new questions of safety or effectiveness. The review relies heavily on design control documentation rather than new performance data. Special 510(k)s typically have shorter review times.

Abbreviated 510(k)

Used when FDA guidance documents, special controls, or recognized consensus standards can facilitate the review. The submission relies on declarations of conformity to standards and summary test reports rather than full raw data sets. This pathway is efficient when applicable standards cover all relevant performance questions.

Submission and Review Process

After you prepare your eSTAR template:

Submit via the CDRH Portal. The FDA's online portal receives and processes electronic submissions. Submissions received before 4 PM ET on a business day are processed the same day.
Receive your 510(k) number. FDA assigns a unique K-number (e.g., K260001) upon receipt. Reference this number in all subsequent correspondence.
Acceptance review. FDA conducts a technical screening to verify completeness. eSTAR submissions that are properly prepared generally bypass the Refuse to Accept (RTA) process, but FDA will verify that all required fields are populated.
Substantive review. FDA has a target of 90 calendar days for the substantive review. During this period, the lead reviewer evaluates your substantial equivalence claim.
Additional Information (AI) Request. If the reviewer has questions or needs additional data, they issue an AI Request. You have 180 calendar days to respond. If you do not respond within 180 days, the submission is considered withdrawn.
Decision letter. FDA issues either an SE (Substantially Equivalent) letter allowing you to market the device, or an NSE (Not Substantially Equivalent) letter.

Common Reasons for Additional Information Requests

Based on published FDA data and industry experience, the most common triggers for AI Requests include:

Insufficient predicate device comparison — technological differences not adequately addressed
Performance testing gaps — test methods do not cover all performance characteristics
Labeling inconsistencies — indications for use, labeling, and substantial equivalence discussion are not aligned
Software documentation incomplete — missing risk analysis, incomplete test coverage, or unresolved anomalies not explained
Biocompatibility evaluation incomplete — test matrix does not cover all required endpoints for the device's contact type and duration
Missing declarations of conformity for applicable standards

Preparing Your Application: Practical Recommendations

Start with the predicate research. Before writing a single section, identify and analyze your predicate device(s) in the 510(k) database. Understand their cleared indications, technological characteristics, and what testing they submitted.

Use the eSTAR template from the beginning. Do not draft your submission in Word and then try to fit it into eSTAR. Work directly in the template so you understand the structure and can address built-in prompts as you go.

Build your traceability matrix early. Map every design input to a verification test, and map every verification test to a section of the 510(k) application. This prevents gaps.

Get a pre-submission meeting. For complex devices or novel technologies, a Q-Submission (pre-submission) meeting with FDA allows you to get feedback on your planned testing and approach before committing resources. FDA's feedback in a pre-submission is not binding but is highly influential.

Budget for at least one AI Request cycle. Most 510(k) submissions receive at least one AI Request. Building this into your timeline prevents surprise delays.

Sources

FDA, "510(k) Submission Process" — fda.gov
FDA, "eSTAR Program" — fda.gov
FDA, "Electronic Submission Template for Medical Device 510(k) Submissions: Guidance for Industry and FDA Staff"
FDA, "Format for Traditional and Abbreviated 510(k)s" (Guidance)
21 CFR Part 807 Subpart E — Premarket Notification Procedures
RegDesk, "FDA eSTAR Template Program Overview" (2026)
Greenlight Guru, "FDA 510(k) Submission: A Step-by-Step Guide"
Complizen, "What Is FDA's eSTAR? Electronic Submission Template Guide"
Celegence, "FDA 510(k) Submissions to Use eSTAR — Change in Submissions"