Regulatory & Submissions · 510(k) Support
510(k) Submission Support
The short answer
A 510(k) is an argument for substantial equivalence, supported by evidence your quality system has to be able to produce on demand. We support the technical build of that submission — predicate comparison, performance testing strategy, design control records, sterilization and manufacturing information — and we make sure what you claim in the submission matches what an investigator would find at the site.
01
Why this matters
- Most Additional Information requests are not strategy failures. They are gaps in test rationale, device description detail or the traceability between requirements and verification results.
- The design history file behind a cleared device becomes an inspection target. A submission assembled outside the quality system creates a records problem later.
- Manufacturing and sterilization information is routinely under-described, and it is the part of the file our consultants have evaluated most often from the Agency side.
02
Applicable regulations and standards
- 21 CFR Part 807 Subpart E
- Premarket notification procedures and content requirements.
- 21 CFR Part 820 / QMSR
- Design controls and records that must support the device described in the submission.
- FDA Refuse to Accept Policy for 510(k)s
- The acceptance checklist your file is screened against before substantive review.
- ISO 10993, ISO 11135/11137, IEC 60601
- Biocompatibility, sterilization and electrical safety evidence commonly referenced.
03
What our consultants actually do
- Assess predicate options and build the substantial equivalence comparison table with a defensible rationale for each difference
- Structure the performance testing plan — bench, biocompatibility, sterilization, shelf life — before testing money is spent
- Write or remediate the device description, indications for use and technological characteristics sections
- Build the manufacturing, sterilization and quality system content of the submission from actual site records
- Reconcile design control records so the DHF supports the submission rather than contradicting it
- Draft responses to Additional Information requests and interactive review questions
04
Across the product lifecycle
01 / DEVELOP
Design inputs written so verification can later be traced to them.
02 / SCALE
Manufacturing process defined at the scale the submission will describe.
03 / TRANSFER
Design transfer records that show the process is reproducible.
04 / VALIDATE
Process, sterilization and packaging validation supporting the file.
05 / MANUFACTURE
Production consistent with the cleared device description.
06 / MAINTAIN
Change assessment: when a modification requires a new 510(k).
05
Problems we are usually called about
- Predicate chosen for convenience rather than technological comparability
- Testing performed before the rationale for the test selection was documented
- Device description in the submission that does not match the current DMR
- Sterilization validation referenced but never reconciled with the contract sterilizer's records
- No documented decision process for whether a post-clearance change requires a new submission
06
Typical deliverables
- Predicate analysis and substantial equivalence comparison
- Testing strategy and gap assessment against recognized standards
- Drafted device description, manufacturing and sterilization sections
- DHF reconciliation report and remediation plan
- Additional Information response package
07
Frequently asked
- Does xFDA write the whole 510(k)?
- We routinely build the technical and quality content, and for many clients we assemble the full submission. Where a program needs global market strategy or simultaneous international registrations, we bring in GlobalRegulatory.com rather than pretend that is our specialty.
- When does a change to a cleared device require a new 510(k)?
- FDA's guidance on modifications to existing devices asks whether the change could significantly affect safety or effectiveness. The decision itself is not the hard part — documenting the analysis in a way that holds up during inspection is. We build that decision record into change control.
- Can you help after we receive an Additional Information request?
- Yes. That is one of the most common ways we get called. We assess what the reviewer is actually asking for, identify whether the answer exists in your records, and draft a response that closes the question rather than inviting another round.
08
References
More for regulatory & submissions
Technical, manufacturing and quality support for US FDA submissions — written by people who have reviewed and inspected against them.
- PMA SupportA PMA is reviewed alongside a pre-approval inspection of the manufacturing site, which means the manufacturing section is not paperwork — it is a description of a facility that will be examined.
- De Novo SupportA De Novo asks FDA to create a classification, which means the submission has to propose the controls that will make the device type safe and effective.
- IND SupportFor an IND, the section that most often holds up a program is CMC.
- NDA SupportBy NDA, the manufacturing story has to be complete: a justified control strategy, validated process, qualified methods and a site that can demonstrate all of it during a pre-approval inspection.
- ANDA SupportGeneric applications are decided as much on manufacturing quality and data credibility as on bioequivalence.
- BLA SupportFor a biologic, the process is a substantial part of the product.
- IDE SupportAn IDE requires a description of how the investigational device is made and controlled, and design controls apply even though the device is not yet cleared.
Start a project
Tell us what you're working on.
Describe the product, the process or the problem. We will tell you honestly whether we are the right people to help, and who should be on the team if we are.