What You Are Actually Proving

The most expensive misunderstanding in medical device development is thinking a 510(k) proves your device is safe and effective. It does not. It proves your device is substantially equivalent to a device already legally on the US market, called the predicate. FDA is not evaluating your product in isolation; it is comparing it to something that already cleared.

Substantial equivalence has two prongs. Your device must have the same intended use as the predicate, and it must either have the same technological characteristics or, where the characteristics differ, you must show that the differences do not raise new questions of safety or effectiveness and that performance data demonstrate equivalent performance. That second clause is where most submissions live and where most of them get into trouble.

The practical consequence is that predicate selection is a strategic engineering decision made early, not a paperwork step at the end. Pick a predicate whose indications for use statement is close to yours and whose technology is close to yours, and the comparison writes itself. Pick one that is merely convenient and you will spend a year answering questions. The selection criteria are worked through in how to choose a predicate device.

Before any of this, confirm that 510(k) is even your pathway. Most Class II devices go this route, most Class I devices are exempt, and Class III devices generally require PMA. If nothing comparable exists, De Novo may be the correct path instead. The classification logic is in FDA device classes explained.

What Goes in the File

A 510(k) is submitted electronically through the eSTAR template, which enforces a fixed structure and will refuse to generate a submission with missing required fields. That template alone has eliminated a large share of the administrative rejections that used to plague first-time submitters. The substantive content breaks down as follows:

  • Indications for use. One page, and arguably the most consequential page in the file. It defines the market you may legally sell into and it anchors the equivalence comparison. Write it narrowly enough to be defensible and broadly enough to be commercially useful.
  • Device description. Materials, components, principles of operation, accessories, and how the device is supplied. Include drawings and photographs.
  • Substantial equivalence discussion. A side-by-side table of your device against the predicate across every meaningful characteristic, with each difference identified and each difference addressed by data. Reviewers read this table first.
  • Performance testing, bench. Whatever the device's function demands: mechanical strength, flow rates, accuracy, durability, shelf life. Wherever an FDA-recognized consensus standard exists, test to it and say so.
  • Biocompatibility. Required for anything contacting the patient, scoped by contact type and duration under the framework described in ISO 10993 biocompatibility testing. This is frequently the longest-lead item in the entire program.
  • Sterilization and shelf life. Validation of the sterilization method, package integrity, and accelerated plus real-time aging data.
  • Electrical safety and EMC. For powered devices, testing to IEC 60601 and its relevant collateral and particular standards.
  • Software documentation. Scaled to the documentation level assigned by risk, plus cybersecurity documentation for anything with a network or wireless interface.
  • Human factors. Usability engineering evidence where use error could cause harm.
  • Clinical data. Required in a minority of 510(k)s, but when it is required it dominates the schedule and budget.
  • Labeling. Draft instructions for use, package labels, and any patient-facing materials.

Two things are not submitted but must exist and will be inspected: your quality system under 21 CFR Part 820 and its harmonized ISO 13485 counterpart, and your design history file. FDA does not review the DHF as part of a 510(k), but an inspector will ask for it, and a submission whose testing was never traceable to documented design inputs is a compliance problem waiting to happen. The requirements are in FDA design controls, and the distinction between verification and validation, which reviewers do notice, is explained in verification vs validation.

Timeline, Cost, and the Review Itself

FDA's statutory goal is a decision within 90 review days, but review days pause whenever the agency issues an Additional Information request and the clock does not restart until you respond. Roughly two thirds of submissions receive at least one AI request, and applicants get 180 calendar days to respond before the submission is withdrawn. The honest planning number is therefore six to nine months from submission to clearance, not three, and twelve months is not unusual for a device with novel technology.

Cost splits into three buckets. The FDA user fee runs in the low tens of thousands of dollars for a standard applicant, with a substantially reduced small-business rate available if you qualify and apply for the certification in advance. Testing is usually the largest line: biocompatibility, sterilization validation, electrical safety, and bench performance commonly total $50,000 to $250,000 depending on the device. Consulting and regulatory writing add another $15,000 to $80,000. Full program budgeting is covered in FDA approval cost for a medical device.

One process step is worth its weight: the Pre-Submission meeting. It is free, it takes roughly seventy-five days to schedule, and it lets you put your predicate choice and proposed test plan in front of the review division before you spend money on testing. Teams that skip it and later discover the reviewer wanted a different animal study or a different predicate lose far more time than the meeting would have cost.

After Clearance

Clearance is a beginning, not an end. You must register your establishment and list the device annually, maintain the quality system and expect an inspection, report adverse events and certain malfunctions under the MDR regulation, comply with UDI labeling and database submission, and handle recalls and corrections through a defined process.

You also have to manage change. A modification that could significantly affect safety or effectiveness, or a change in intended use, requires a new 510(k). Manufacturers are expected to document a formal analysis for every significant change, deciding and justifying whether a new submission is required. Building that decision into your engineering change process from the start is far cheaper than reconstructing the rationale during an inspection.

Plan the Submission Into the Development

Projects House develops medical devices with the regulatory file assembled alongside the engineering rather than after it: predicate strategy, design controls, test planning, and submission-ready documentation. Describe your device and intended use through our contact form and we will map the pathway.