What you will learn
By the end of this topic, you should be able to explain the purpose of design transfer, define a transfer baseline, plan production-readiness evidence, use pilot builds effectively and make a controlled release decision.
Transfer is a controlled conversion—not a handover
Design transfer converts approved design outputs into production specifications, processes, resources and controls. It succeeds when the receiving organisation can make, inspect, release and support the device consistently—not when a document package has merely changed ownership.
Transfer therefore begins before design completion. Manufacturing, supplier, service and quality knowledge should influence architecture, tolerances, test access, assembly methods and acceptance criteria while changes are still practical.
The transferred product is the design plus the production system needed to realise it. Both must be demonstrably ready.
Plan scope, ownership and evidence
A transfer plan should identify products and variants, sites, suppliers, processes, facilities, equipment, software, records, responsibilities, acceptance criteria and unresolved risks. Define who supplies each input, who accepts it and what evidence permits progression.
- Appoint accountable design and operations owners.
- Identify critical-to-quality characteristics and risk controls.
- Map outsourced processes and supplier dependencies.
- Plan equipment, tooling, fixtures, training and production software.
- Define pilot quantities, representative lots and approval gates.
- Control deviations, open actions and configuration changes.
Establish a complete transfer baseline
Product definition
Drawings, specifications, bills of material, software, labelling, packaging and approved variants.
Process definition
Work instructions, process parameters, environmental controls, inspection points and acceptance methods.
Risk controls
Controls allocated to product, process, supplier, labelling, service and production monitoring.
Resources
Qualified equipment, fixtures, methods, software, premises and competent personnel.
Supply chain
Approved suppliers, purchasing specifications, incoming controls and change-notification arrangements.
Records
Device or batch history, traceability, status identification, release and nonconformance records.
The baseline should remain traceable to the approved design outputs described in MTL-104 — Design Controls and Technical Documentation.
Demonstrate production readiness
Readiness is broader than equipment installation. The team must show that materials, instructions, controls, operators and information systems work together under realistic conditions.
- Confirm manufacturability and tolerance capability against design intent.
- Qualify equipment, utilities, tooling and production environments.
- Validate processes whose results cannot be fully verified later.
- Demonstrate inspection and test-method suitability.
- Train personnel and confirm competence for consequential tasks.
- Exercise material status, traceability, nonconformance and release controls.
- Confirm packaging, storage, transport and service arrangements.
Use pilot builds to test the system
Pilot builds should use representative people, equipment, materials, suppliers, instructions and production conditions. They reveal ambiguous work instructions, unstable processes, inaccessible measurements, unrealistic cycle times and undocumented operator knowledge.
Record deviations and rework rather than hiding them. Review yield, defects, test escapes, process capability and configuration accuracy. A successful build is not simply one that eventually produces acceptable devices; it is one that demonstrates a controlled and repeatable route to them.
Make an evidence-based release decision
The release record should state the configuration, evidence reviewed, limitations, conditions and accountable approvers. Commercial urgency does not convert incomplete evidence into readiness.
Control change and learn after transfer
Transfer is not finished at the first production release. Early production, supplier, complaint and service data should be reviewed against assumptions made during development. Define heightened monitoring where uncertainty remains.
Production changes must follow the same connected logic as design changes: describe the need, assess regulatory and risk consequences, update affected specifications and validate or verify the change before implementation.
Common misconceptions
“Transfer happens after design is finished.”
Late involvement creates avoidable redesign. Production knowledge should influence the design throughout development.
“A complete drawing pack proves readiness.”
Documents are necessary, but readiness also depends on capable processes, trained people, controlled suppliers and representative evidence.
“One successful pilot build validates production.”
A build may demonstrate integration, but validation must represent relevant variation and predefined acceptance criteria.
Authoritative external references
- ISO 13485:2016 — Medical devices — Quality management systems
- FDA — Quality Management System Regulation (QMSR)
- Regulation (EU) 2017/745 on medical devices
Use the editions and regulatory requirements applicable to the device, market and organisation.
Transfer the production system, not just the product definition
A credible transfer connects an approved design to capable processes, controlled suppliers, competent people and objective release evidence.