510(k) Checklist
A practical, reviewer-friendly checklist you can use to track what you have, what’s missing, and what must be consistent across the dossier. This aligns to common eSTAR sections and RTA expectations.
Educational Resource
This checklist is provided for educational and strategic planning purposes only. It is not legal advice and does not represent an official FDA checklist. 510(k) requirements vary based on device classification, product code, technological characteristics, and risk profile. The FDA may request additional information beyond the items listed here.
Tip: your progress saves locally in your browser (no data sent anywhere).
Submission Checklist (eSTAR-aligned)
Keep a tight “single source of truth” for: device name/model, intended use, indications, technological characteristics, performance claims, predicate(s), and labeling. Inconsistencies are the #1 preventable cause of RTA/AI churn.
1) Administrative & Submission Setup
2) Intended Use, Indications & Claims
3) Device Description & Technology
4) Predicate Selection & Substantial Equivalence
5) Performance Testing (Bench/Non-Clinical/Clinical)
6) Software Documentation (as applicable)
7) Cybersecurity (as applicable)
8) Biocompatibility (as applicable)
9) Electrical Safety / EMC (as applicable)
10) Sterilization / Reprocessing / Shelf Life (as applicable)
11) Labeling & Promotional Consistency
12) Risk Management & QMS Touchpoints (as needed)
13) Final QA Before Submission
Optional: “Investor-Ready” Attachments
If you’re raising or selling alongside submission prep, consider preparing a short pathway memo and evidence map that explains: predicate logic, what testing is needed, timelines, and cost drivers—without exposing proprietary detail.
What’s Missing or Should Be Tightened for “FDA-Accurate” Specificity
If you want this checklist to align even closer with true eSTAR / RTA-level specificity, consider refining or adding the following elements.
Classification & Product Code Confirmation
Confirm the regulation number, product code, device class, and review panel early. This anchors the entire strategy and drives testing expectations.
Standards Declarations / Conformance Statements
Clearly identify recognized standards used and how conformity was established. eSTAR often expects explicit declarations and summarized results.
Sterility — Method-Specific Expectations
EO, radiation, and steam sterilization each carry different validation and documentation expectations. Method-specific evidence must align with FDA-recognized standards.
Reusable Device Reprocessing Validation
Reprocessing validation (cleaning, disinfection, sterilization) remains an area of significant FDA scrutiny. Documentation should clearly support IFU instructions.
UDI Considerations
While UDI details may not always be central to the 510(k) file, labeling structure and UDI compliance considerations should be aligned.
Clinical Section Framing
If clinical evidence is leveraged, ensure literature summaries, endpoints, statistical rationale, and justification language are clearly structured and reviewer-ready.
eCopy / PDF Quality Rules (If Applicable)
File structure, searchable text, bookmarks, and consistent naming conventions continue to trigger avoidable RTA issues.
FAQs
Does every 510(k) need software and cybersecurity sections?
No—only if your device includes software (including firmware) or connects/transmits/stores data. But if it does, expect scrutiny and keep documentation consistent.
Can we use more than one predicate?
Yes. Secondary predicates are common when one device doesn’t cover all technological characteristics, but the “same intended use” logic must remain clean.
What’s the fastest way to reduce RTA risk?
Run an internal RTA-style completeness pass, then do a consistency sweep across intended use, device description, comparison tables, test reports, and labeling.
Want Verus FDA to pre-screen your checklist?
We can run a fast submission readiness review to identify gaps, inconsistencies, and the highest-risk missing artifacts before you build in eSTAR.
Need a predicate and pathway first?
Start with a Predicate Search + Pathway Memo to lock the fastest defensible route and define the evidence plan.
