What should you gather before an FDA 510(k) consultant call?
If you are the founder or first Regulatory Affairs / Quality Assurance (RA/QA) hire preparing a U.S. handoff, the useful package is not "we think this is a 510(k)." It is a dated, source-backed brief that already contains the intended use, candidate product code and class clues, a predicate shortlist with K numbers, a first-pass comparison table, a draft 510(k) content map, eSTAR readiness notes, and explicit open questions for qualified review. That package does not determine Food and Drug Administration (FDA) classification, predicate suitability, substantial equivalence, submission pathway, compliance, safety, effectiveness, clearance outcome, or legal obligations. It gives your qualified RA/QA reviewer or consultant the minimum official-source starting point needed to spend paid time on judgment instead of re-collecting public inputs.
Target query: what to gather before FDA 510k consultant call.
This is not regulatory, legal, or compliance advice. TrueMedDevice does not determine FDA classification, submission pathway, predicate suitability, substantial equivalence, reportability, complaint disposition, corrective and preventive action need, file closure, risk acceptability, compliance status, product safety, effectiveness, clearance outcome, inspection outcome, or legal obligations. We organize source-backed evidence for qualified RA/QA professionals or consultants to review.
Pre-production brief
Role
Founder or first RA/QA hire preparing a U.S. FDA 510(k) consultant handoff
Scenario
The team knows a U.S. market-entry review is coming and wants the first paid consultant hour spent on judgment, not basic FDA source collection.
Concrete problem
They do not know which official-source artifacts should exist before a consultant is asked to comment on 510(k) fit, predicate strategy, and submission preparation.
Available inputs
Product description, draft indications for use, draft labeling, known device identifiers, any existing similar-device notes, and the planned U.S. commercial use case.
Useful output
- •A one-screen U.S. handoff brief with the intended use, device summary, and open review questions.
- •A predicate shortlist with K numbers, source links, and a first-pass comparison table.
- •A draft 510(k) content map showing what is already available versus what still needs evidence or judgment.
TrueMedDevice role
- •Organize public FDA-source evidence into a dated consultant handoff brief.
- •Turn predicate, product-code, and content requirements into candidate review points and visible gaps.
- •Leave classification, pathway, predicate suitability, and final submission decisions with qualified reviewers.
The official-source handoff workflow
1. Lock the indications for use before discussing predicates
FDA's 510(k) pages treat intended use and indications for use as central comparison points. Before a consultant evaluates a predicate strategy, gather a stable intended-use statement and the latest labeling draft. If those inputs are moving, your predicate logic will move with them.
2. Capture candidate product code and class clues
Search the Product Code Classification Database and the relevant Title 21 Code of Federal Regulations category to create candidate product-code and class notes. These are clues, not final classification decisions. The goal is to help the consultant start from a visible rationale instead of from a blank page.
3. Build a predicate shortlist with K numbers
FDA recommends identifying a primary predicate that is most similar with respect to indications for use and technological characteristics, and it recommends identifying the predicate K number. A useful handoff should therefore list candidate predicates, why they are being considered, and where the comparison still feels weak.
4. Draft the side-by-side comparison before the call
FDA's Content of a 510(k) page says substantial-equivalence comparison should be provided in a clear and comprehensive format, and that a chart or table is a systematic way to compare devices. That means your handoff should already include a first-pass comparison table for intended use, technology, materials, energy, performance, and labeling.
5. Map what 510(k) content already exists
FDA says there is no 510(k) form and points submitters to the content requirements, including indications for use, labeling, specifications, substantial-equivalence comparison, and performance. A consultant handoff is stronger when these are listed as "exists," "draft," or "missing" before the call starts.
6. Include eSTAR and fee-cover-sheet readiness
FDA's current eSTAR page says 510(k) submissions, unless exempted, must use eSTAR. The user-fee page also says 510(k) submissions require a user fee and a Medical Device User Fee Cover Sheet (Form FDA 3601). That does not tell you the right pathway. It does tell you what operational submission surfaces should already be on the consultant checklist.
Source ledger
Every hard claim in this article maps to one of the official FDA pages below. The same ledger structure should travel with the consultant handoff.
| Claim supported | Official URL |
|---|---|
| A 510(k) is a premarket submission used to show substantial equivalence to a legally marketed device, and a device may not be marketed in the U.S. until FDA issues an SE letter. | https://www.fda.gov/medical-devices/premarket-submissions-selecting-and-preparing-correct-submission/premarket-notification-510k |
| FDA says the submitter should identify a primary predicate that is most similar with respect to indications for use and technological characteristics, and recommends identifying the predicate K number. | https://www.fda.gov/medical-devices/premarket-notification-510k/how-prepare-traditional-510k |
| FDA's predicate guidance says substantial equivalence is established with respect to intended use, design, energy used or delivered, materials, performance, safety, effectiveness, labeling, biocompatibility, standards, and other applicable characteristics. | https://www.fda.gov/medical-devices/premarket-notification-510k/how-find-and-effectively-use-predicate-devices |
| The Product Code Classification Database contains device names and associated product codes, and the product code identifies the generic category of a device for FDA. | https://www.fda.gov/medical-devices/classify-your-medical-device/product-code-classification-database |
| FDA's classification page says the agency has established classifications for about 1,700 generic device types and grouped them into 16 medical specialties, and points users to the product code database to find the classification. | https://www.fda.gov/medical-devices/overview-device-regulation/classify-your-medical-device |
| FDA's traditional 510(k) page says there is no 510(k) form and points users to 21 CFR 807.87, Content of a 510(k), device-specific guidance, and the electronic submission template. | https://www.fda.gov/medical-devices/premarket-notification-510k/how-prepare-traditional-510k |
| FDA's Content of a 510(k) page lists the statement of indications for use, proposed labeling, specifications, substantial equivalence comparison, and performance among the expected content areas. | https://www.fda.gov/medical-devices/premarket-notification-510k/content-510k |
| FDA's eSTAR program page says all 510(k) submissions, unless exempted, are mandatory eSTAR submissions and that PreSTAR can be used voluntarily for Pre-Submissions and 513(g) requests. | https://www.fda.gov/medical-devices/how-study-and-market-your-device/estar-program |
| FDA's medical device user-fees page says 510(k) submissions require a user fee and a Medical Device User Fee Cover Sheet (Form FDA 3601). | https://www.fda.gov/medical-devices/premarket-submissions-selecting-and-preparing-correct-submission/medical-device-user-fees |
Workload and cost framing
FDA publishes user-fee mechanics and submission structure. It does not publish your internal preparation workload. Keep those two layers separate in the handoff.
| Layer | What the source says | Operational meaning |
|---|---|---|
| Submission structure | FDA expects a content package rather than a simple form, and identifies content areas such as indications for use, labeling, specifications, substantial-equivalence comparison, and performance. | A useful consultant brief should pre-map those content areas into available versus missing artifacts. |
| User fee mechanics | FDA says 510(k) submissions require a user fee and a Medical Device User Fee Cover Sheet. | Budget owners and operators should track user-fee readiness as a separate operational item from classification or predicate judgment. |
| Public-source prep workload | Inference from the workflow above, not an FDA claim. | Expect roughly a focused half day to two working days to collect, verify, and organize the public-source handoff if the product description already exists. More if intended use or predicate logic is still unstable. |
What TrueMedDevice prepares and what it does not decide
What we prepare
- Official-source intended-use brief and device summary.
- Candidate product-code and device-class clues with citations.
- Predicate shortlist, K numbers, and first-pass comparison notes.
- Draft 510(k) content map and visible evidence gaps.
- eSTAR and fee-cover-sheet readiness notes.
What remains with qualified review
- FDA classification and 510(k) applicability.
- Predicate suitability and substantial-equivalence strategy.
- Whether performance evidence is sufficient.
- Any legal, quality-system, safety, or compliance conclusion.
- Any final clearance, inspection, or enforcement outcome.
This is not regulatory, legal, or compliance advice. TrueMedDevice does not determine FDA classification, submission pathway, predicate status, substantial equivalence, compliance, safety, or effectiveness. We prepare a source-backed evidence pack from public FDA sources so qualified RA/QA professionals or regulatory consultants can review and decide.
Frequently asked questions
If I have a likely predicate device, does that mean I already know my 510(k) path?
No. A likely predicate shortlist is a useful preparation artifact, but FDA's substantial-equivalence review still depends on intended use, technological characteristics, performance information, and whether the comparison raises different questions of safety and effectiveness. Predicate clues are not the same as a final strategy decision.
Do I need a complete 510(k) draft before speaking with a consultant?
No. You need a structured starting package, not a polished submission. The practical threshold is a clear intended-use statement, candidate product code and class clues, a predicate shortlist with K numbers, a draft comparison table, and a list of open judgment questions.
Does FDA require eSTAR for 510(k) submissions now?
FDA's current eSTAR program page says all 510(k) submissions, unless exempted, are required to be submitted as electronic submissions using eSTAR. That makes template readiness and document structure useful prep topics before the consultant call.
Does TrueMedDevice decide FDA classification or predicate suitability?
No. TrueMedDevice does not determine FDA classification, product code, 510(k) applicability, submission pathway, predicate suitability, substantial equivalence, compliance status, safety, effectiveness, clearance outcome, or legal obligations. We organize source-backed evidence so qualified RA/QA professionals or consultants can review and decide.
Want this U.S. handoff package built on your device?
We can prepare the FDA-side evidence pack, source ledger, and consultant handoff notes for one product family. Start with the lightest next step that fits your week.
Review support only. We do not provide regulatory, legal, or compliance decisions. Final RA/QA, consultant, and manufacturer decisions remain with qualified reviewers.