Who this is for
Use this checklist if you are preparing for a first FDA market-entry conversation, checking whether a portfolio company's regulatory plan is grounded in public evidence, or trying to give a consultant a clean intake package before paid strategy time starts.
- A founder preparing for a first FDA market-entry conversation.
- An investor checking whether a portfolio company's regulatory story is source-backed.
- An early RA/QA hire trying to understand a product family quickly.
- A consultant who wants structured intake before spending expert time.
- An importer or distributor trying to understand whether a public-record review is needed before supplier onboarding.
What to prepare before the call
The strongest first-call package is not a regulatory conclusion. It is a clean evidence base. It should help the consultant see what is known, what is source-backed, what is uncertain, and which decisions still require professional judgment.
- A one-page product identity sheet: product name, model, manufacturer or specification developer, intended user, patient population, environment, accessories, software, and major claims.
- A plain intended-use statement and a marked list of claims that may increase evidence burden.
- Candidate FDA product-code clues with product code, regulation number, device class, specialty panel, and source link.
- A similar-device shortlist with K-number, applicant, device name, decision date, product code, 510(k) type, and 510(k) Summary link where available.
- Public safety-history review points from recalls, Medical Device Reporting (MDR) / MAUDE, warning letters, safety communications, and import alerts where relevant.
- A list of open questions for the consultant: pathway, predicate options, testing strategy, standards, timeline, fees, and whether a Pre-Submission conversation may be worth discussing.
Why search summaries are not enough
A quick summary can make the first search feel finished, but the hard part is product mapping, source discipline, boundary control, and keeping the record reviewable.
If the request is framed as 'find my predicate,' the answer may look useful while skipping the professional judgment step. A safer workflow asks for candidate public records, source links, open questions, and rationale for why a human reviewer should look at each item.
Workload and cost framing
A careful founder can spend 8 to 20 hours preparing the first evidence base by hand. A consultant can do the same retrieval work, but then the first paid hours are used on search and formatting rather than judgment.
The practical economic question is whether the output is traceable, product-mapped, bounded, and ready for a qualified reviewer to use without redoing the work.
What TrueMedDevice can prepare
TrueMedDevice prepares the source-backed review packet: public 510(k) records, candidate product-code clues, source ledger, similar-device shortlist, safety-history review points, open questions, and an attachment-ready evidence structure for the next RA/QA or consultant review.
Source ledger
What it can tell you
FDA's overview of 510(k), substantial equivalence, who may need a 510(k), when changes can trigger a new 510(k), and that a 510(k) order clears a device for commercial distribution.
What it cannot decide
Whether your device requires a 510(k), which pathway applies, or which predicate is suitable.
What it can tell you
FDA preparation concepts, including predicate device, guidance documents, electronic Submission Template And Resource (eSTAR), and content references.
What it cannot decide
Whether a Traditional, Special, Abbreviated, De Novo, or premarket approval path applies to your product.
What it can tell you
Required content concepts: classification, predicate devices, labeling, specifications, performance data, sterilization where applicable, and guidance.
What it cannot decide
Whether your evidence is sufficient for FDA review.
What it can tell you
Public 510(k) records searchable by device name, applicant, product code, decision date, and K-number.
What it cannot decide
Which public device should be selected as predicate.
What it can tell you
Candidate product code, regulation, panel, and class clues.
What it cannot decide
Final classification for your product.
What it can tell you
Programmatic access to public 510(k) clearances, product records, original sponsors, receipt dates, and decision dates.
What it cannot decide
A complete product evidence packet without source review and product mapping.
Frequently asked questions
Does this replace a 510(k) consultant?
No. It prepares source-backed inputs so a 510(k) consultant or RA/QA reviewer can spend more time on judgment and less time on retrieval. It does not determine classification, pathway, predicate suitability, substantial equivalence, safety, effectiveness, clearance, approval, or legal obligations.
What should I bring to the first consultant call?
Bring a product identity sheet, draft intended-use statement, candidate product-code clues, similar-device records, public safety-history review points, source links, and your written open questions.
Can I do this with a general search or summarization tool?
You can use general tools to speed up search and summarization, but you still need source verification, product mapping, boundary language, and a reviewer-ready record. The risky output is a confident conclusion without traceable sources.
What does TrueMedDevice deliver?
A Product Evidence Pack: source ledger, candidate product-code clues, public similar-device records, safety-history review points, open questions, and a structured review packet for qualified RA/QA or consultant review.
Want the first consultant call to start from evidence instead of search?
Use the product-specific checklist to prepare your product facts, FDA search clues, similar-device records, and consultant questions before paid expert time starts.