Free checklist for SaMD and software medical device teams
Five handoffs to own before your FDA submission.
Development, quality, regulatory, testing, and cybersecurity each own a piece of your submission to the U.S. Food and Drug Administration (FDA). This checklist covers the handoffs between them.
What's inside
Five handoffs.What to check at each.
For each handoff between two of your teams, here is the question to ask. Run it with your teams before your file goes in.
Handoff 1
Development → Quality
Do your requirements, code, and IEC 62304 records describe the same software, at the same version?
Handoff 2
Quality → Regulatory
Does your Design History File (DHF) hold every document your submission points to, in its current version?
Handoff 3
Regulatory → Testing
Does your verification and validation evidence support each claim your submission makes about the software?
Handoff 4
Testing → Cybersecurity
Do your security tests trace back to your threat model and cybersecurity risk assessment? FDA recommends traceability between those, your Software Bill of Materials (SBOM), and your testing documentation (FDA premarket cybersecurity guidance, February 3, 2026).
Handoff 5
Cybersecurity → Development
Does your threat model change when your architecture changes? FDA recommends threat modeling throughout the design process (same guidance).
You can answer 0 of 5 today.
Walk through your five handoffs with usWho it's for
You're a Founder, VP R&D, or VP RA-QA at a US company building software medical devices. You have an FDA submission on your plan.
- Your development, quality, regulatory, testing, and cybersecurity work sits with different teams or vendors
- You're the one connecting them today
- Your product is software: Software as a Medical Device (SaMD), software in a device, or embedded firmware
Prefer to talk it through?
Walk through your five handoffs with us.
Book 30 minutes. Bring your submission plan. We'll go through each handoff with you and point out which ones need an owner. We'll suggest a first step.