Design verification asks whether you built the device right. Design validation asks whether you built the right device. Neither one asks the question that actually decides what rolls off the line: did everything you verified and validated make it, intact and reviewed, into the documents production runs against? That third question is design transfer — ISO 13485:2016 clause 7.3.8, incorporated into 21 CFR Part 820 when FDA's Quality Management System Regulation took effect on February 2, 2026. It is the step most design-controls programs document loosely, if at all, and the gap inspectors find precisely because everything upstream of it looks clean.
What design transfer actually requires
Under the old QSR, this sat at 21 CFR 820.30(h): design output had to be reviewed before release, and verified against design input before becoming the basis for production. ISO 13485:2016 restates the same intent at clause 7.3.8 with sharper procedural language — the organization must document procedures for the transfer of design and development outputs into production, and those procedures must confirm the outputs are verified as suitable for manufacturing before they are used that way. The QMSR's incorporation of the standard did not relax this; it gave it a new clause number inside a harmonized framework. Teams that already run disciplined design controls and design history file work sometimes assume transfer is just the last box on that same checklist. It isn't — it is the control that governs everything that happens after the design history file closes.
Why validated doesn’t mean transferred
The failure mode is rarely a missing procedure. Most device companies have a design-transfer SOP. The failure mode is that the SOP describes a review that, in practice, never happens on a document-by-document basis — engineering hands drawings to manufacturing, manufacturing writes work instructions against its own understanding of them, and nobody formally reconciles the two against what design validation actually tested. Four patterns account for most of what a delta assessment finds:
- Post-validation engineering changes. A tolerance, material, or supplier changes after validation closes, without a documented review against the validated design — and without re-verification that the change is still covered.
- Work instructions written independently. Manufacturing engineering drafts production work instructions from its own interpretation of the drawings rather than from the reviewed, approved design output itself.
- Acceptance criteria that drift. Incoming and in-process inspection criteria get simplified for the shop floor in ways that no longer match the tolerances design validation actually exercised.
- Software builds that diverge. The validated software build and the build loaded onto production units separate over successive engineering or manufacturing changes, with no formal transfer checkpoint re-establishing that they match.
A certificate audit samples your procedures. An inspection traces a specific production document back to the design output it is supposed to implement — and asks who reviewed that it still does. Why the trace matters more than the paperwork
What this looks like under scrutiny
Design transfer rarely surfaces as its own finding. It surfaces downstream — as a complaint or medical device report tracing back to a production unit that quietly diverged from the validated design, or as a 483 observation written against a different clause that nonetheless traces to an untransferred change. By the time it shows up in a quality system review, the question an investigator asks is simple: show me the documented link between this production specification and the design output it implements, and show me who reviewed it. Teams that treat transfer as a formality rather than a control usually cannot answer either half of that question for every document in the chain — only for the ones someone happened to check.
- Inventory the validated outputs. List every drawing, specification, software build, and acceptance criterion design validation actually tested, before assuming production matches them.
- Trace each output into production. Find the production document each validated output is supposed to implement, and confirm the link is documented.
- Close out unreviewed changes. Flag any production document that moved after validation without a documented review against the design file.
- Formalize the transfer record. Document who reviewed the transfer, what was approved, and when, so it stands as evidence rather than an assumption.
None of this requires rebuilding your design-controls program. It requires treating clause 7.3.8 as a distinct control with its own evidence, not as the last line of a validation report. Companies that run the trace now — before an inspector or notified-body auditor runs it for them — are the ones who find the drifted tolerance in a quality review instead of a 483.
Frequently asked questions
Is design transfer required under the QMSR?
Yes. The QMSR incorporates ISO 13485:2016 by reference into 21 CFR Part 820, and clause 7.3.8 requires documented procedures for transferring design and development outputs into production — reviewed and approved before they become the basis for routine manufacturing. It carries forward the intent of the former 21 CFR 820.30(h) design transfer requirement under a different clause number.
What is the difference between design validation and design transfer?
Design validation confirms the finished device meets user needs and intended uses, typically under actual or simulated use conditions. Design transfer is the separate step that converts the validated design outputs — drawings, specifications, acceptance criteria — into the documents and instructions production actually runs against. A device can pass validation and still have an incomplete transfer.
What does FDA look for in a design transfer inspection?
Investigators typically trace a sample of production specifications and work instructions back to the validated design outputs they are supposed to implement, looking for a documented review and approval step, not just that the two sets of documents happen to agree. A gap here often surfaces as a drawing or tolerance that changed after validation without re-verification, or a work instruction written independently of the design file.
Sources & further reading
- ISO 13485:2016. Medical devices — Quality management systems — Requirements for regulatory purposes. iso.org
- FDA. Medical Devices; Quality System Regulation Amendments — Final Rule (89 FR 7496, Feb 2, 2024). federalregister.gov
- eCFR. 21 CFR Part 820 — Quality System Regulation (current). ecfr.gov
This article is provided for general informational purposes and reflects the regulatory landscape as of November 2026. It is not legal or regulatory advice. Confirm current QMSR and ISO 13485 requirements with FDA, your notified body, or qualified counsel before acting.