Product Design Controls
Quick facts
| Category | Structured product design and development governance |
|---|---|
| Used by | Medical devices, aerospace, automotive and other regulated product manufacturers |
| Also called | DHF (Design History File), DMR (Device Master Record), DHR (Device History Record) |
| Related standards | ISO 13485, FDA 21 CFR Part 820, EU MDR, ISO 9001 |
| Related processes | Risk assessment, FMEA, ECR/ECN, verification and validation, document control |
| Semantic match | product design controls, design history file DHF, design verification validation, medical device design controls |
What is Product Design Controls?
Product design controls provide a structured framework for managing a product's design and development, ensuring that what gets built actually satisfies user needs and intended use, and that the process of getting there is documented and traceable. This is especially critical in industries such as medical devices, where design controls are a specific regulatory requirement.
The process generally begins with design inputs, the requirements a product must meet, and moves through design outputs, the specifications, drawings and other deliverables that define the actual design. Verification confirms that design outputs meet design inputs, while validation confirms that the finished product meets user needs and intended uses under actual or simulated conditions of use.
Design controls typically culminate in a Design History File, a compiled record of the design and development activities performed for a specific device or product, used to demonstrate that design controls were followed throughout development.
Why is Product Design Controls important?
Design flaws are often far more expensive and difficult to correct once a product reaches production or the field than if they are caught during development. Design controls build in checkpoints, such as verification and validation, specifically to catch these issues earlier.
For regulated products, particularly medical devices, design controls are not optional; they are a specific regulatory expectation, and a complete Design History File is often requested during FDA inspections or notified body audits.
Design controls also connect design decisions to risk management, ensuring that identified risks are addressed through design mitigations and verified as effective before a product reaches the market.
How does Product Design Controls work?
A typical product design controls process includes:
- Design planning. Define the design and development plan, including phases, responsibilities and reviews.
- Design inputs. Establish the requirements the product must meet, including user needs and regulatory requirements.
- Design outputs. Develop specifications, drawings and other outputs that define the design.
- Design review. Conduct formal reviews at defined stages to evaluate progress and issues.
- Verification. Confirm design outputs meet design inputs.
- Validation. Confirm the finished product meets user needs and intended use.
- Design transfer. Translate the design into production specifications.
- Design changes. Control and document any changes to the design after initial release.
- DHF compilation. Maintain a complete record of design and development activities.
Design Verification vs. Design Validation
| Comparison | Design Verification | Design Validation |
|---|---|---|
| Question answered | Did we build the design correctly? | Did we build the correct product? |
| Compares against | Design inputs | User needs and intended use |
| Typical method | Testing, analysis or inspection against specifications | Testing under actual or simulated conditions of use |
Real-world examples of Product Design Controls
A medical device manufacturer defines design inputs based on clinical user needs, develops design outputs including engineering drawings, and performs verification testing to confirm the device meets its specified requirements before moving to validation with representative users.
An aerospace component manufacturer uses design controls to link a new part's FMEA and risk assessment directly to its design review process, ensuring identified risks are addressed before the design is released to production.
A medical device company undergoing an FDA inspection produces its Design History File on request, demonstrating that design reviews, verification and validation activities were completed and documented throughout development.
Regulations and standards related to Product Design Controls
FDA 21 CFR Part 820.30 establishes specific design control requirements for medical device manufacturers, covering design planning, inputs, outputs, review, verification, validation, transfer, changes and the Design History File. ISO 13485 contains closely aligned design and development requirements for medical device quality management systems.
EU MDR similarly expects structured design and development documentation as part of a device's technical file. ISO 9001 addresses design and development more generally under its own requirements, without medical device-specific terminology such as DHF, DMR or DHR.
Auditors and regulators commonly examine whether design inputs were clearly defined, whether verification and validation were both performed and distinguished from each other, and whether the DHF provides a complete, traceable record of the design process.
Required by
How QT9 helps with Product Design Controls
QT9 QMS product design controls capabilities
- Build templates for any design control process, including DHF and ISO 9001 requirements.
- Create custom phases of design and development for each product or product family.
- Link document control, ECR, ECN, FMEA, risk assessments and inspections per design phase.
- Maintain a complete Design History File, ready for review, inspection or audit.
- Assign responsible parties, approvers and approval levels for each design phase.
- Provide real-time status updates so teams stay aligned throughout development.
Request a Design Controls Demo Explore Design Control Software →
See QT9 Software in Action
Discover how QT9 Software helps manufacturers improve efficiency, strengthen compliance and connect quality management and ERP processes within one integrated platform.
Common mistakes with Product Design Controls
Common mistakes include confusing verification with validation, treating them as interchangeable when they answer different questions, verification confirms outputs meet inputs, while validation confirms the product meets user needs.
Other problems include incomplete Design History Files that cannot demonstrate the full design process during an inspection, and failing to formally control and document design changes made after the initial design was approved.
Frequently asked questions
Related quality management terms
Related content
Ready to Transform Your Business?
See how QT9 Software helps manufacturers simplify operations, improve traceability and drive continuous improvement with integrated quality management and ERP software.