What should your design-transfer review answer?
Start with a defined handoff scope. Name the device configuration, manufacturing location, supplier involvement and activities you plan to transfer. Then ask whether the receiving functions can identify the controlled instructions and evidence relevant to that scope. A successful prototype alone does not answer those questions.
You might review an assembly operation first rather than treat the entire device as one transfer decision. Record what that review includes and what it leaves for another decision, such as packaging, servicing or a later manufacturing site. Without that boundary, a signature can look broader than the evidence behind it.
The worksheet below is a practical review aid, not a prescribed regulatory form or a complete compliance assessment. Adapt it to your device, quality management system and applicable requirements. Your responsible quality, engineering and manufacturing functions determine the evidence and approvals appropriate to the actual handoff.
Which US requirements should you check first?
The US Food and Drug Administration's Quality Management System Regulation, or QMSR, incorporates ISO 13485 into the device quality-system framework. Current 21 CFR 820.7 identifies the incorporated edition as ISO 13485:2016. Section 820.10(c) applies the design-and-development requirements to manufacturers of class II and class III devices and the specified class I devices. Do not assume every class I device has the same design-and-development obligations.
Use those current provisions to establish applicability with your regulatory lead. Do not rely on an older checklist that presents former section 820.30(h) as today's standalone transfer rule. Current Part 820 reserves sections 820.20 through 820.30 and directs applicable manufacturers to ISO 13485 through section 820.10.
There is useful context in FDA's 2024 final-rule response to Comment 31, pages 7507 to 7508. FDA explains that final design output forms the basis or starting point for the medical device file and describes that file as containing or referencing the procedures and specifications current on the manufacturing floor. That explanation supports examining the connection between design outputs and production documents. It does not make the worksheet here a legal requirement.
For an exact assessment of the transfer obligations within the incorporated standard, consult the applicable ISO text and qualified advice. This guide does not reproduce that clause or replace a device-specific review.
How can you build a useful evidence worksheet?
Take one selected design output and follow it into the documents the receiving function will actually use. Identify the revisions, the evidence relevant to the activity and any unresolved question. Keep document identifiers and links explicit enough that another reviewer can repeat the trace without guessing which copy you meant.
| Review field | What to record | Question it helps answer |
|---|---|---|
| Transfer scope | Device configuration, site and activity under review | What does this decision cover? |
| Selected design output | Identifier, revision and relevant requirement | Which output are we handing over? |
| Production instruction | Controlled drawing, specification or instruction and revision | What will the receiving function use? |
| Supporting evidence | Relevant assessment or test record, revision and limitations | What supports this particular handoff? |
| Responsible functions | Preparing function, reviewer and decision authority under your QMS | Who resolves the question and approves the outcome? |
| Open action and disposition | Gap, assigned owner, next action and recorded decision | What still prevents a decision? |
These fields are suggested working categories. They do not establish a universal evidence set, testing program or approval hierarchy. For example, a process may raise a validation question, but this worksheet cannot determine the answer without the process, device and applicable requirements.
Use your own supplier qualification record to inform supplier-related questions, and consult the supplier qualification guide for that separate assessment. Keep supplier approval and this specific transfer decision distinct. An approved supplier does not by itself resolve a mismatch between the drawing you reviewed and the instruction a production operator receives.
What does a revision mismatch look like in practice?
Consider a fictional manufacturer reviewing a fixture-assisted assembly operation. Engineering selects assembly drawing AD-014 revision C, but the proposed production instruction WI-022 revision B references revision B of that drawing. The available trial report also records revision B. The review cannot establish from those records alone whether the change to revision C affects the operation or the relevance of the trial evidence.
The useful outcome is an explicit question and a responsible owner, rather than a checked box saying that all three documents exist.
| Evidence item | Illustrative review result | Next review action |
|---|---|---|
| AD-014 revision C | Selected output for the scoped handoff | Engineering identifies the change from revision B and its relevance |
| WI-022 revision B | References the earlier drawing revision | Manufacturing and quality review whether the instruction needs a controlled update |
| Trial report TR-009 | Records work against revision B | Responsible functions assess whether the evidence supports the intended revision C operation |
| Transfer decision | Evidence relationship remains unresolved | Record the gap, owner and decision after the assessment; do not describe this review as complete |
Do not assume that every revision change demands a repeat test, or that a document update alone resolves the issue. In this example, the responsible functions first assess what changed and what the existing evidence can support. They then determine the action through the manufacturer's established processes.
A resolved record should show the rationale and the resulting controlled references. If the assessment supports using existing evidence, make that reasoning traceable. If further work is necessary, identify it and preserve the limit on what has actually been reviewed. This is an illustrative review method, not a validated release decision for a real device.
How should you close the review?
Close against the scope you defined, with the evidence available to the functions authorized to decide. A compact decision note can identify the reviewed configuration, document revisions, remaining actions and the rationale for the disposition. Separate a completed action from an accepted limitation so the next reader can tell them apart.
For internal tracking, you could use categories such as ready for the designated approval, further assessment needed and outside this review's scope. Those are practical labels, not regulatory statuses. None replaces the approvals your quality system requires, authorizes commercial distribution or establishes regulatory clearance.
Agree when the evidence trace should be revisited. A changed production instruction, manufacturing location or supplier may raise a question about the previous decision. Define how your existing change process identifies and assesses that question rather than inventing a separate approval route for this worksheet.
If your immediate problem is selecting a system to organize controlled work, use the eQMS guide for medical-device startups. If a later product complaint raises a manufacturing or design question, the US complaint-record guide addresses a different record and investigation decision. Neither guide replaces the transfer assessment.
Sources and further reading
- 21 CFR 820.7, incorporation by reference identifies the standard and edition incorporated into the US rule.
- 21 CFR 820.10, requirements for a quality management system helps establish the US design-and-development applicability boundary.
- FDA's 2024 Quality System Regulation Amendments, response to Comment 31 explains the relationship between final design output, the medical device file and current manufacturing documentation. This is explanatory final-rule material, not a separate worksheet requirement.
