Class 1 medical device submission: a practical path to U.S. market entry

Most guides on Class I medical devices stop at the reassuring statement that these products are "low risk" and "generally exempt" from premarket review. That framing is accurate as far as it goes, but it leaves regulatory leads without the decision logic they actually need before setting up accounts, finalizing labels, or deciding whether to draft a 510(k).

The reality is that Class I devices can follow one of three submission paths depending on their product code. Choosing the wrong one delays market entry or, worse, creates a compliance gap. This article gives you the step-by-step workflow to confirm which path applies to your device, complete the administrative steps that apply to every exempt product, and prepare a right-sized 510(k) when one is required.

Overview

Start by understanding how FDA assigns device class and where the statutory exemptions come from (see 21 U.S.C. § 360c and FDA's Classify Your Medical Device pages). Under the Federal Food, Drug, and Cosmetic Act, FDA classifies medical devices into three risk-based classes.

Class I covers devices that present minimal potential harm and for which general controls alone are sufficient to provide reasonable assurance of safety and effectiveness. Think elastic bandages, examination gloves, tongue depressors, and manual stethoscopes.

The critical nuance is that "Class I" does not automatically mean "no submission required": if a device is classified as Class I or II and is not exempt, a 510(k) will be required for marketing. FDA explains this on its Classify Your Medical Device page. This distinction drives the practical decision logic covered below.

Class I devices produce three distinct regulatory outcomes: fully exempt from 510(k), exempt with limitations (where statutory carve-outs apply), or reserved (510(k) explicitly required). The applicable path flows from the product code and the exemption note attached to the governing regulation in 21 CFR Parts 862–892. The next sections show how to read those notes, verify your device's status in FDA's Product Classification database, and follow the appropriate pathway.

Submission path for Class I devices: exempt, reserved, or 510(k) required

Begin any Class I submission decision by confirming that exemption is determined at the product code level (see FDA's Class I and Class II Device Exemptions page). Exemption is not automatic at the class level. Most Class I and some Class II devices are exempt from 510(k) requirements, subject to the limitations in section 510(l)(1) of the Federal Food, Drug, and Cosmetic Act.

Those statutory limitations are the key variable that decides whether a 510(k) is required.

A device will be fully exempt when the product-code regulation confirms no 510(k) conditions. It is "exempt with limitations" when the exemption is subject to the 510(l) carve-outs. Examples include devices intended for a use of substantial importance in preventing impairment of health or devices that present an unreasonable risk.

A device is "reserved" when the product code record explicitly withholds the exemption and requires a 510(k). Treating a reserved device as fully exempt is a frequent and consequential mistake, so always verify the product code record rather than assuming class-level exemption.

How to read limitations-of-exemption and product code notes

When checking exemption notes, consult both the Product Classification database entry and the governing CFR regulation (21 CFR Parts 862–892) for the device type. The product code record will show key fields such as device class, the 510(k) exempt indicator ("Yes," "No," or "Yes — with limitations"), and any exemption or regulation notes.

The regulation text is the authoritative source if the database entry is ambiguous. Read the device-type definition in the CFR alongside your intended use statement to confirm whether your device falls squarely within the exempt description.

Determine whether the intended use triggers a statutory limitation. Capture the product code record (screenshot or export) for your regulatory decision file. That evidence demonstrates the basis for your pathway selection.

Verify exemption status using FDA's Product Classification database

Confirming exemption status is a database-first exercise; use FDA's Product Classification database as the authoritative starting point. Search by intended-use keywords (not trade names) or by a known product code at the Product Classification database. The database displays device class, regulatory panel, applicable CFR citation, and exemption status for matching product types.

Begin with a keyword linked to intended use, review returned product codes, and match your device's intended use to the device-type definition in the result. Once you identify the most specific applicable product code, open the full record and read the exemption-status field and any attached notes.

If the record shows Class I and confirms exemption without limiting conditions, you can proceed to establishment registration, device listing, and UDI/GUDID tasks. If the record shows Class I reserved or flags a 510(k) requirement, move directly to submission planning.

Retain a screenshot or export of the product code record as evidence in your regulatory decision file so reviewers and auditors can verify your analysis.

Worked example: from intended use to decision

Use a concrete example to illustrate the database workflow. A manufacturer plans to market a non-powered, non-sterile reusable wrist splint intended to immobilize the wrist after a sprain.

The regulatory lead searches the Product Classification database using an intended-use keyword like "orthopedic immobilization" and reviews the returned product codes to find the most specific match within 21 CFR Part 888 (orthopedic devices). Opening the full product code record, the lead confirms device class "1," the applicable CFR citation in Part 888, and an exemption field reading "Exempt" with no limiting notes.

The intended use—immobilizing the wrist after a soft-tissue injury—does not implicate the 510(l) carve-outs for substantial importance in preventing impairment of health or unreasonable risk. So no 510(k) is required.

The manufacturer records the product code and CFR citation in its regulatory decision file and proceeds to registration, labeling, and UDI/GUDID tasks. If the labeling had instead claimed prevention of post-surgical nerve damage or an essential post-operative function, the intended-use analysis would need to be revisited before finalizing that outcome.

U.S. market entry workflow for exempt Class I devices

After confirming no 510(k) is required, follow the defined administrative sequence in FDA's Device Registration and Listing resources to enter the market compliantly. Completing these steps in order reduces setup errors that commonly delay first-time filers and foreign firms establishing a U.S. presence.

The typical sequence is:

1. Obtain any required identifiers for your organization and facilities (U.S. establishments receive a Facility Establishment Identifier (FEI) through registration).

2. Complete establishment registration via FDA's Unified Registration and Listing System (FURLS) during the October 1–December 31 window for the following fiscal year; foreign firms must designate a U.S. Agent before registration can be completed.

3. Submit device listings tied to the applicable product code and update listings when devices are added or removed from the marketed portfolio.

4. Finalize labeling under 21 CFR Part 801, ensuring required elements (establishment name and place of business, directions for use or relevant exemptions, warnings) are present.

5. Assign UDIs, apply UDI labeling, and submit device data to FDA's GUDID per the applicable compliance dates.

Annual registration renewal is required regardless of device additions. Missing the October–December renewal window creates a registration lapse that places every listed device in a non-compliant marketing status. Set calendar reminders well in advance.

Roles and responsibilities for registration/listing

Clarify who must register and who must list, especially when contract manufacturing or private labeling is involved (see FDA registration and listing guidance). The specification developer—the entity that owns device design and specifications—holds the primary obligation to list the device, even if manufacturing is outsourced.

Contract manufacturers must register their establishments but do not list the device under their name. Private labelers that rebrand another firm's device must register their own establishment and submit a separate device listing. The private labeler is responsible for the labeled product from a regulatory standpoint.

For foreign manufacturers, the initial importer has registration and listing obligations. The foreign firm must designate a U.S. Agent (a U.S.-based contact for FDA communications) in FURLS before registration completes.

The recommended order of operations for foreign firms is: appoint a U.S. Agent, complete establishment registration, then submit device listings. Doing these steps out of sequence commonly triggers account-setup errors and delays.

If a 510(k) is required for a Class I device

When a Class I product code is reserved or the device falls within section 510(l) limitations, you must submit a premarket notification (510(k)) before marketing. Follow FDA's eSTAR guidance for the current electronic submission format.

A Class I reserved device typically supports a shorter 510(k) than higher-risk devices, but the submission still must establish substantial equivalence to a legally marketed predicate device. The predicate must have the same intended use and substantially equivalent technological characteristics.

File the 510(k) through FDA's electronic submission system using the eSTAR template. Expect an initial administrative acceptance review before substantive review begins.

Administrative deficiencies result in Refuse to Accept (RTA) determinations that return the submission to the applicant and restart the review timeline. Prepare the submission to meet FDA's acceptance criteria up front to avoid preventable delays.

What to include in a Class I 510(k) via eSTAR

Follow eSTAR's section structure and include focused content scaled to the device risk profile (see FDA's eSTAR resources). Core components for a Class I reserved 510(k) commonly include:

• Indications for use statement: precise description of intended purpose, patient population, and use environment.
• Device description: functional and physical description, materials, components, accessories, and all variants or sizes.
• Predicate device identification: 510(k) or PMA number for the predicate, with a side-by-side comparison of intended use and technological characteristics.
• Standards declarations: applicable voluntary consensus standards (ISO, ASTM, IEC) with statements of conformance and noted deviations.
• Sterilization information: only if the device is supplied sterile.
• Biocompatibility: rationale or testing data for patient-contacting materials, typically guided by ISO 10993-1.
• Labeling: draft label, instructions for use (if applicable), and any promotional materials included with the submission.

Use eSTAR's embedded instructions; do not leave required fields blank or mark "not applicable" without an explanation. Unexplained omissions trigger RTA findings.

Acceptance review pitfalls to avoid

Anticipate common acceptance-stage issues by consulting FDA's Refuse to Accept policy for 510(k)s and cross-checking your package against those criteria. Frequent RTA triggers include:

• Incomplete or ambiguous indications for use—be specific about anatomy, patient population, and use conditions.
• Missing or inappropriate predicate identification—ensure the predicate's intended use aligns with the subject device.
• Standards section left blank—affirmative statements are required even if no standards apply.
• Labeling that conflicts with the indications for use—labels must be consistent with the submission's claims.
• Missing device descriptions for all variants—describe every size, configuration, and accessory covered by the submission.

Address these items before submission to reduce the risk of an RTA determination and associated delays.

Costs and timelines to plan for

Separate recurring administrative costs from one-time submission fees when budgeting (see FDA establishment registration fee and 510(k) user fee pages). Establishment registration fees are assessed per establishment each fiscal year under MDUFA. Check the current fee schedule and confirm small business eligibility if applicable.

510(k) user fees are also set annually and include a reduced small business fee for qualifying firms. The fee is due at submission and non-refundable, even in RTA cases.

Expect the FDA review process to follow established milestones: an acceptance review (typically within 15 calendar days) to check completeness, followed by substantive review with a target decision timeline under MDUFA (90 FDA review days). Total calendar time is longer because the clock pauses for any additional information (AI) requests.

AI cycles are common; budget four to eight months of calendar time from a clean submission to clearance for a straightforward Class I reserved 510(k). Account for at least one AI cycle.

UDI and GUDID for Class I devices: nuances and exceptions

Plan UDI and GUDID tasks early, consulting FDA's UDI basics and GUDID guidance to determine label and database obligations. Most Class I devices must bear a UDI on their label and packaging, including a Device Identifier (DI) and Production Identifier (PI) where applicable.

Mark UDI in both human-readable and AIDC formats. For reusable Class I devices, direct marking on the device itself may be required in addition to label marking—verify the regulation for your specific product code.

A retail point-of-sale exemption can relieve the AIDC requirement for certain Class I devices sold at retail. The exemption is narrowly defined and conditions must be met.

For GUDID submission, the labeler (usually the specification developer or private labeler) must create a GUDID account and submit the required device record data before labeling and marketing. Commonly missed GUDID fields for Class I devices include MRI safety status, device size attributes, and single-use indicators. Ensure these fields are completed accurately to avoid delays in account approval.

Change control and claim boundaries that can trigger a new submission

Treat post-market changes to labeling, intended use, or design as potential triggers for a new submission. Follow FDA's "Deciding When to Submit a 510(k)" guidance to assess whether a change requires premarket notification.

The clearest trigger is an intended-use change: expanding claims into a condition or population not covered by the original product code—or claims that implicate the 510(l) carve-outs—may void an exemption or require a new 510(k). Labeling and promotional claims are closely scrutinized. FDA considers the totality of labeling, websites, and promotional materials when determining intended use.

Design changes can also trigger submission requirements if they could significantly affect safety or effectiveness, introduce new indications, or change the operating principle. For Class I devices that hold a 510(k) clearance (reserved devices), changes outside the cleared indications or involving new technological principles typically require a new or supplemental 510(k).

Maintain a formal change control process and assess every change against FDA criteria before implementation. Document the decision rationale.

Inspection-readiness for Class I manufacturers

Prepare for FDA inspections by maintaining organized quality and regulatory records even for exempt devices. Review 21 CFR Part 820 and FDA's QMSR materials for applicable requirements.

Although design controls have historically been exempted for many Class I devices, other elements of the quality system regulation apply broadly. Examples include complaint handling (21 CFR 820.198), CAPA (21 CFR 820.100), and recordkeeping.

The QMSR transition aligns Part 820 with ISO 13485; review FDA's QMSR resources for current implementation status and effective dates.

During inspections, FDA commonly requests complaint files and evidence of investigation, CAPA records including verification of effectiveness, labeling-control documentation, supplier controls for critical components, and MDR records under 21 CFR Part 803. Typical 483 observations for Class I manufacturers involve inadequate complaint investigations, incomplete CAPA records without effectiveness verification, and labeling deviations from the listed version without documented change control.

Organized, retrievable records and documented procedures are the most reliable defense against inspection findings.

Multi-market note: coordinating U.S. Class I with EU/UK/Australia Class I

Coordinate documentation strategies across jurisdictions by building a technical file to the most demanding applicable standard and adapting jurisdiction-specific front matter. See EU MDR (Regulation (EU) 2017/745) and TGA guidance for reference.

In the EU, most Class I devices follow a self-declaration pathway under EU MDR and require a Declaration of Conformity plus a technical file. The EU MDR's documentation expectations often exceed what FDA requires for exempt Class I devices.

In Australia, the TGA's inclusion process for Class I non-sterile, non-measuring devices is largely administrative and relies on compliant technical documentation and a Declaration of Conformity.

For multi-market strategies, building documentation to EU MDR Class I standards usually satisfies TGA expectations and provides a strong internal record for FDA inspections, even when no formal dossier is submitted to FDA. The practical principle is to create a robust, modular technical file that can be adapted with jurisdiction-specific front matter (FDA device listing data, EU Declaration of Conformity, TGA inclusion documentation) to avoid duplicative work.

Decision tools: Class I submission decision tree and market-entry checklist

Use a short sequence of verifiable questions to reduce the Class I submission decision to a practical decision tree; start each analysis with a Product Classification database lookup. Step 1: confirm device class by locating your device in FDA's Product Classification database—if the class is not "1," follow the appropriate pathway for Class II or III.

Step 2: check the exemption status and any regulation notes for the product code: if "Exempt" without limiting notes, no 510(k) is required; if "Exempt with limitations," assess section 510(l) conditions; if "Reserved / Not exempt," plan for a 510(k).

Step 3: complete market entry tasks for exempt devices using the checklist below. If uncertainty remains after reviewing the product code and CFR, consider a 513(g) request to confirm classification or a Q-Submission (Pre-Submission) to seek FDA feedback on regulatory strategy. Both programs and fees are detailed on FDA's respective program pages.

Checklist for exempt Class I market entry:

• [ ] Product code and regulation number documented in regulatory decision file
• [ ] U.S. Agent designated (foreign firms only)
• [ ] Establishment registered in FURLS (within annual October–December window)
• [ ] Device listed with correct product code in FURLS
• [ ] Labeling finalized per 21 CFR Part 801 (name/address, directions for use, warnings)
• [ ] UDI assigned and applied to label (human-readable + AIDC barcode)
• [ ] GUDID account created and device record submitted
• [ ] Direct marking assessed for reusable devices
• [ ] Complaint handling procedure and CAPA procedure documented
• [ ] MDR reporting procedure documented per 21 CFR Part 803
• [ ] Annual registration renewal calendared (October 1 each year)

Where to go next

Build a well-documented regulatory decision file that records your product code, exemption analysis, and the administrative steps you will complete for market entry. Verify each claim against FDA resources such as the Product Classification database, the Device Registration and Listing page, the GUDID portal, and the eSTAR 510(k) guidance.

If you need structured workflows and traceability for multi-jurisdiction submissions or 510(k) preparation, consider medical device regulatory submission software that supports collaborative review and checklist-driven assembly. Early investment in documentation discipline—clear decision records, organized technical files, and controlled change processes—pays dividends in faster market entry and fewer inspection or submission setbacks.