top of page

Medical Device Design Controls: Requirements, Reviews and Transfer

Oct 12
9 min read

Updated: 1 day ago

Reviewed by Aaron Lyon, President of A.P. Lyon and former Director of Quality Assurance and International Regulatory, with more than 30 years in medical device quality. Last reviewed November 10, 2026.


What documentation does a design project need?


A useful design-control set connects the device’s intended use and requirements to development decisions, evidence and a controlled manufacturing handoff. Start with the project’s gaps: unclear inputs, weak review records, missing verification or validation plans, an incomplete transfer package, or uncontrolled changes. The right document is the one that supports the missing workflow.


A design-control procedure provides the governing framework. A project’s completed records demonstrate how that framework was applied. Purchasing the framework does not supply a completed design file, proven device performance or an approved regulatory submission.


Current regulatory framework


The QMSR incorporates ISO 13485:2016. FDA’s design-and-development presentation explains planning, inputs, outputs, review, verification, validation, transfer and change control. Verification addresses outputs against inputs; validation addresses intended use on representative product. Confirm applicability to the device before approving the project plan.




Begin with a requirement the team can assess


A vague requirement creates difficulty later because the team cannot agree what constitutes success. For example, “easy to connect” does not identify the intended users, the configuration, the task or the evidence needed. Translate the need into controlled requirements while preserving its source and intended-use context.


A.P. Lyon recommends keeping a requirements record with an identifier, source, rationale, approved wording, associated risks and the planned evidence route. The record should show which requirements will be addressed by analytical or bench evidence and which require evaluation of use. These fields are a practical organizing approach; they do not replace applicable requirements.


Buyer decision

Useful project record

Gap it helps reveal

Are the inputs clear?

Requirements list with source and intended-use context.

Ambiguous, conflicting or unsupported requirements.

Does the design meet specifications?

Verification plan and requirement-to-result links.

Requirements without adequate supporting evidence.

Does it meet intended-use needs?

Validation plan and representative-use rationale.

Bench results being used to answer a different question.

Can production implement it?

Transfer readiness assessment and approved outputs.

Incomplete manufacturing instructions or acceptance methods.


Use reviews to make decisions


A review is more useful when it identifies what can proceed, what must change and who owns the remaining work. Build the agenda around the decision for that stage. Present unresolved requirements, risk assumptions, evidence gaps, changes since the last review and the readiness of downstream activities.


Record the configurations reviewed, participants and perspectives, conclusions, actions and approval responsibilities. An action should have an owner and an evidence-based closure route. Closing an action because someone sent an email is different from confirming that its technical objective was met. Where an issue affects later tests, identify the dependency before proceeding.


Worked example: a connector that passes bench testing


Imagine a fictional medical-device connector intended to be assembled by a defined group of users. Bench checks show that the parts meet dimensional requirements and that the assembled connection meets a specified mechanical criterion. The team is preparing to move beyond prototype development.


These results may support specific verification requirements. They do not, by themselves, show that intended users can reliably complete the connection under the relevant use conditions. The team should compare the planned evidence with the intended-use needs and use-related risks. A strong test result remains valuable, but its conclusion must stay within the question actually tested.


In this example the review identifies a use question, assigns an owner to the evaluation plan and links that work to the relevant risk record. The design record retains both the existing bench results and the additional decision. The team does not relabel the bench study as user validation simply to close the project.


Question in the example

Evidence to consider

Conclusion boundary

Do the parts meet the drawing?

Controlled dimensional method and results.

Applies to the assessed dimensions and configurations.

Does the assembled connection perform?

Defined mechanical test and acceptance criteria.

Applies to the tested mechanical conditions.

Can intended users connect it appropriately?

Use evaluation matched to users, task and context.

Requires evidence relevant to the intended-use question.


Design transfer is a readiness decision


Treat transfer as a review of whether development outputs can be used by the receiving production organization. A practical transfer inventory can cover approved drawings, material specifications, supplier interfaces, manufacturing instructions, acceptance methods, equipment and process evidence, labeling controls, training and unresolved issues. Tailor the inventory to the device and division of responsibilities.


For each item, record the current revision, owner, receiving function and readiness evidence. If a contractor manufactures the product, identify who controls the specifications and how changes are communicated. A folder containing documents does not necessarily show that the receiving team can perform the work with those documents.


The Design Transfer Procedure supports this handoff. Facility-to-facility Technology Transfer is a related but different offer; choose by whether the missing work is the design-to-manufacturing transition or transfer between sites.


How should a design change be assessed?


Identify what changes, why it changes and which released or in-development configurations are affected. A practical assessment should trace effects on requirements, risk assumptions, evidence, manufacturing instructions and labeling where relevant. Decide what existing evidence can still support and what additional work is needed.


For example, changing a connector material may affect more than a purchasing specification. Consider whether performance assumptions, manufacturing settings or biological evidence need review. This is a prompt for a documented assessment, not a claim that every material change requires the same studies. Retain the reasoning for both additional work and justified reuse of existing evidence.


Choose a document by the missing workflow



Design Control supplies the phase framework, tasks, review gates and development-record guidance.



Product Performance Specification supports translating needs into measurable technical requirements.



Design Review supports structured milestone assessment, decisions and follow-up records.



Design Verification and Validation supports the separate evidence questions and their planned documentation.



Design Transfer supports the controlled handoff to manufacturing.



Design Change supports assessment and control of proposed changes.



Design Analysis supports structured analytical methods used to examine design and process concerns.



The four-procedure Design Control Bundle includes Control, Review, Transfer, and Verification and Validation. Check existing overlaps before selecting the set.


Before adding more documentation


If these workflows are already established, identify whether the problem is an unfilled record, an unclear responsibility or missing evidence. A focused gap may justify one procedure rather than a broader collection. The 26-procedure Design and Development collection augments an existing QMS; it is not a complete standalone system.


Project review checklist


  • Intended use and requirement sources are clear.

  • Requirements have planned evidence routes and traceable results.

  • Review decisions and open actions are recorded.

  • Verification and validation conclusions answer their separate questions.

  • Manufacturing readiness is supported by controlled outputs and receiving-team evidence.

  • Changes have documented impact assessment and approval.


Inside the A.P. Lyon procedure: design release decisions


Source: A.P. Lyon Design Control, SOP 7-001, revision 3, effective September 19, 2026, supplied for this guide by A.P. Lyon. The table below is a shortened adaptation of the Launch Phase procedure, project checklist control and Attachment 9 release gate. It is a selected preview, not the complete procedure or an approved release record.


A design project can have completed testing and still lack a defensible release decision. This procedure connects the evidence to a defined device configuration, release purpose and market. Launch preparation and inventory builds are separate from authorization to distribute.


Selected procedure element

What the source asks the team to document

What a buyer can assess

Project checklist control

Applicable tasks, stage decisions, objective evidence and an accountable owner in the approved design and development plan. An N/A decision requires justification and Project Leader and Quality approval.

Can your existing checklist identify evidence and justify omitted tasks?

Release identity and scope

Device/configuration, investigational or commercial release purpose, countries, scope and effective release date.

Does the approval identify precisely what is being released and where?

Evidence at the release gate

Design review and verification/validation approval; risk acceptability; applicable clinical and regulatory actions; transfer, validated processes, labeling/UDI and production acceptance.

Can reviewers locate the records behind each readiness conclusion?

Open actions and approval

Disposition of unresolved actions, with Quality and Regulatory Affairs approval of the completed release gate before authorized distribution.

Who can approve release, and how are remaining actions handled?


Selected field labels from Attachment 9, Product Approval Form: Product Name; Item Numbers; Lot Numbers; DHF #; Date. The form also separates release type, geographic markets and management approvals. These labels are reproduced as a preview; the explanatory table above is adapted.


Buyer decision: use this preview to compare the procedure with your current release controls. If your existing system already links configurations, evidence, market scope and approvals, you may need to improve execution rather than purchase another procedure. If those interfaces are missing, the Design Control procedure provides a starting structure that must be tailored to your organization. Purchasing it does not complete testing, grant market authorization or approve a device for release.


Original document previews: design flow and release fields


These previews are cropped renderings of the supplied SOP 7-001, revision 3, effective September 19, 2026. The source artwork and wording are retained. They show selected content, not the full procedure, complete flowchart or an approved project record.


SOP 7-001 Attachment 11 concept and feasibility design flow, showing activities, review loops and management approval before development.

Figure 1. SOP 7-001, Attachment 11: concept and feasibility portion of the Design Process Flow. Later development, verification, validation and release stages are outside this preview.



Read the review diamonds and return paths as decisions, rather than a list of tasks to tick off. The concept portion connects prototype, market-needs and patent-search activities to a review; the feasibility portion connects customer requirements, preliminary specifications and risk work to a further review and management decision. These are company planning activities to tailor to the project, not a claim that every depicted activity is mandated by a standard. Approval to enter development does not authorize commercial release.


Selected fields from SOP 7-001 Attachment 9 Product Approval Form: product, item and lot identity, release type, DHF reference and date.

Figure 2. SOP 7-001, Attachment 9: selected identity and release-type fields. Region and approval sections continue in the full form and are omitted here.



The form distinguishes Customer Requirement Validation (CRV), Limited Market Release (LMR) and Full Market Release (FMR), and ties the selection to a DHF reference and date. These are the company’s form labels. Use them with the governing release gate, evidence, market scope and required approvals; a checked box alone is not authorization to distribute a device.


Scope and how to use this guide


This is general implementation guidance for selecting and organizing documentation. The worked planning scenarios are fictional. Separately labeled procedure and form extracts are drawn from the A.P. Lyon files identified in their source notes. Neither is a completed study or evidence of compliance. Apply the requirements for your device, process and markets, and have the responsible technical and quality personnel approve decisions. Product downloads supply editable documentation; your organization remains responsible for its implementation and evidence.


Related buyer decisions





Primary references and review date


Technical references and linked product scope checked October 13, 2026. Regulatory summaries are identified above; checklists, decision tables and fictional examples are A.P. Lyon implementation recommendations. Consult the full applicable standards and regulations before approving a project.




Publisher and editorial standards


Published by A.P. Lyon. Aaron Lyon is the company’s founder; his professional background is described on the About page. These guides use AI-assisted research and drafting. Each guide is reviewed and approved by Aaron Lyon before publication; that review does not certify applicability to your device.





Watch the Design Control video



Frequently asked questions


What is the difference between design verification and design validation?


Verification confirms that design outputs meet design inputs. Validation confirms that the device meets user needs and its intended use, on representative product under relevant conditions. A passing bench test can support verification, but it does not by itself show that intended users can use the device as intended.


How does the FDA QMSR affect design controls?


The QMSR took effect on February 2, 2026 and incorporates ISO 13485:2016 by reference. Design and development requirements are therefore read through the ISO 13485 structure: planning, inputs, outputs, review, verification, validation, transfer and change control.


What should be ready before design transfer?


Treat transfer as a readiness decision. Confirm that approved drawings, material specifications, manufacturing instructions and acceptance methods are complete and usable by the receiving production organization, and that open actions from design reviews are closed with evidence.


Building a complete quality system? Build Your QMS lets you choose ISO 13485 + FDA QMSR, Dual-Standard or ISO 9001:2026 procedures in one place, and applies volume discounts automatically: 20% off 5–9 procedures, 35% off 10–19, 50% off 20–39 and 60% off 40 or more.


Not sure where your quality system stands? Take the free QMS gap check: about 20 questions, an instant report of your gaps by clause, and the procedures that close each one.


Just getting started? The free Startup Quality Plan shows which procedures you need now, which can wait, and how long they take to put in place.

Recent Posts

See All
QSR to QMSR: What to Change in Your Procedures

How to update procedures written for the old Quality System Regulation to the FDA QMSR: what changed, the substantive gaps that come up most often, a repeatable revision method, before and after wordi

 
 
 

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page