Design Controls

What are design controls?

Design controls structure development so that a device is demonstrably designed to meet user needs and intended use — not merely tested at the end. The historical U.S. anchor is 21 CFR 820.30, whose elements — design and development planning, design inputs, design outputs, design review, design verification, design validation, design transfer and design changes — map directly onto ISO 13485's design and development clause that the QMSR now incorporates.

Which devices are subject to design controls?

In the United States: all Class II and Class III devices, plus a specifically listed set of Class I devices — including devices automated with computer software. Elsewhere the same substance applies through ISO 13485 certification and the EU MDR's technical-documentation expectations, so in practice any manufacturer with regulatory ambitions develops under design controls regardless of first market.

What is the difference between design verification and design validation?

Verification confirms outputs meet inputs — the device was built to its specifications. Validation confirms the device meets user needs and intended uses under actual or simulated use conditions, on production or production-equivalent units. Confusing the two is one of the most common audit findings in development files: a device can pass every bench specification and still fail validation because the specifications themselves missed the clinical reality.

When do design controls start?

Formally, when design inputs begin to be defined — not at manufacturing transfer. The records produced along the way accumulate into the design history file, which submissions and audits in the United States trace end to end, and risk management under ISO 14971 runs interwoven with every element rather than as a parallel exercise.