Design Validation
What a definition is not
A definition is SPEQ’s plain-language decode of how a term is used in practice, cited to the documents that define it. It is a practitioner reference, not legal or regulatory advice, it does not replace the definition in the source, and where a regulator’s wording differs the regulator’s wording governs.
Design validation confirms that a device conforms to defined user needs and intended uses under actual or simulated use conditions. It answers the question “did we build the right device?” — distinct from design verification, which confirms outputs against inputs — and normally requires testing on initial production units, lots, or their equivalent.
Validation activities include clinical evaluations, simulated-use studies, and, for devices with a user-interface component, human factors and usability testing conducted against the intended user population, use environment, and use scenarios. Software validation typically runs the finished software in its intended operating environment rather than a development sandbox.
Design validation is expected on production units or their justified equivalent — substituting an early engineering build or prototype for the finished production process is viewed as a validation gap unless equivalence is formally justified.
A common finding is validation performed against an incomplete or superseded requirements set, or validation that never involved representative users — both undermine the core claim that the finished device actually meets the need it was designed for.
- —Confirms the device meets user needs and intended use — “built the right device”
- —Distinct from design verification (outputs vs. inputs)
- —Normally performed on initial production units or a justified equivalent
- —Includes human factors/usability validation for devices with a user interface
- —Software validation runs in the intended operating environment
21 CFR 820.30(g) (pre-QMSR) / FDA QMSR (2026); ISO 13485:2016 §7.3.7; EU MDR 2017/745 Annex I §5
Frequently asked questions
What is Design Validation?
Design validation confirms that a device conforms to defined user needs and intended uses under actual or simulated use conditions. It answers the question “did we build the right device?” — distinct from design verification, which confirms outputs against inputs — and normally requires testing on initial production units, lots, or their equivalent.
Which regulations cover Design Validation?
21 CFR 820.30(g) (pre-QMSR) / FDA QMSR (2026); ISO 13485:2016 §7.3.7; EU MDR 2017/745 Annex I §5