On this page
- What the design and development controls requirement is, and why it exists
- Stage-by-stage implementation of design and development controls
- Evaluating Clause 8.3 requirements against audit evidence
- Practical design control scenario and change management
- Example
- Before your audit
- Questions people ask
- What are iso 9001 design and development controls?
- What is the difference between design verification and design validation in ISO 9001?
- What documents must be retained for ISO 9001 design and development?
- When can an organisation exclude ISO 9001 Clause 8.3 from its scope?
- Reference documents
The short version
- ISO 9001 design and development controls ensure products and services meet essential input requirements through planned verification and validation.
- Subclause 8.3.3 mandates determining complete, unambiguous inputs including functional, performance, statutory, regulatory, and failure consequence requirements.
- Subclause 8.3.4 requires applying reviews, verification, and validation to confirm outputs meet specified application and intended use criteria.
- Organisations must identify, review, and control design changes under Subclause 8.3.6 to prevent adverse impacts on product conformity.
What the design and development controls requirement is, and why it exists
Establishing ISO 9001 design and development controls allows organisations to ensure that subsequent provision of products and services meets specified quality criteria. Applying ISO 9001 design and development controls under ISO 9001 standard Clause 8.3 ensures that design inputs, reviews, verification activities, validation routines, and output specifications are systematically managed. This standard clause applies to any organisation creating new products or services, or modifying existing offerings within its quality management system scope.
The strategic purpose of Clause 8.3 is to prevent product or service failures that arise from poor specification, unverified design assumptions, or uncontrolled changes. Under Clause 8.3, organisations must establish, implement, and maintain a design and development process appropriate to ensure subsequent operational provision. By embedding risk-based thinking under Clause 6.1, organisations address potential failure consequences early in the product lifecycle before volume production or service delivery begins.
Under ISO 9001:2015 verbal forms, "shall" indicates a mandatory requirement ("must"), whereas "may" indicates a permission ("may"). Organisations must satisfy mandatory design planning, input determination, control application, output definition, and change management requirements unless design activities are formally justified as non-applicable within the system scope under Subclause 4.3.
Important: Organisations must retain documented information across all design stages to prove that design and development requirements have been met under Subclause 8.3.2.j.
Stage-by-stage implementation of design and development controls
Implementing design controls requires compliance leads to execute six interconnected subclauses from initial planning through to post-design change management. Internal auditors must evaluate each process stage against planned criteria.
- Design and development planning: Under Subclause 8.3.2, determine process stages, duration, complexity, reviews, verification, validation, responsibilities, resource needs, interface controls, customer involvement, and retained documented information.
- Design and development inputs: Under Subclause 8.3.3, determine functional, performance, statutory, regulatory, code of practice, and failure consequence requirements, resolving conflicting or ambiguous inputs.
- Design and development controls: Under Subclause 8.3.4, apply reviews to evaluate result capabilities, perform verification to confirm outputs meet inputs, and execute validation to verify fitness for intended use.
- Design and development outputs: Under Subclause 8.3.5, ensure outputs meet input requirements, are adequate for subsequent provision, reference monitoring and acceptance criteria, and specify essential safety characteristics.
- Design and development changes: Under Subclause 8.3.6, identify, review, and control modifications made during or after design to prevent adverse impacts on conformity.
Tip: Verification and validation have distinct purposes under Subclause 8.3.4: verification checks output against input specifications, while validation checks the final product against customer user needs.
Evaluating Clause 8.3 requirements against audit evidence
Auditors examine retained documented information and operational records at each stage of the design cycle. Organisations must maintain documented information defining process criteria and retain records proving controls were applied.
| Requirement | What the auditor checks | Evidence to have ready |
|---|---|---|
| Subclause 8.3.2 Design planning | How project stages, reviews, verification, validation, resource needs, and interface controls were established | Design plans, project schedules, and assigned responsibility matrices |
| Subclause 8.3.3 Design inputs | Whether inputs are complete, unambiguous, and address statutory, regulatory, and performance requirements | Design input logs, regulatory compliance checklists, and resolved input conflict records |
| Subclause 8.3.4 Design reviews | Whether formal reviews evaluate the ability of design results to meet specified requirements | Design review minutes, problem resolution logs, and action tracking files |
| Subclause 8.3.4 Verification & validation | Evidence that outputs meet input criteria and that resulting products fulfill specified intended uses | Calculation checks, testing reports, prototype trial logs, and validation sign-offs |
| Subclause 8.3.5 Design outputs | Whether outputs specify acceptance criteria and essential characteristics for safe provision | Engineering drawings, service specifications, bill of materials, and user manuals |
| Subclause 8.3.6 Design changes | How changes during or after design are identified, reviewed, authorized, and controlled against adverse impact | Design change requests, change review records, authorization logs, and impact analyses |
Common finding: Organisations frequently confuse design verification with design validation under Subclause 8.3.4, failing to test products under actual operating conditions prior to customer delivery.
Practical design control scenario and change management
Example
During an internal audit of a medical equipment manufacturer, an internal auditor evaluated Subclause 8.3.6 regarding design and development changes. The auditor discovered that software engineers modified a pump control algorithm during post-validation field trials without performing a formal change review under Subclause 8.3.6. Although the modification corrected a minor user interface bug, it inadvertently altered flow rate tolerances, impacting product conformity under Subclause 8.3.5. Furthermore, the business retained no documented information showing review results or change authorization as required by Subclause 8.3.6.
The compliance lead logged a nonconformity under Subclause 10.2.1 and suspended software deployment. The design team conducted a full impact analysis under Subclause 8.3.6.d, performed re-verification calculations, and completed re-validation testing under Subclause 8.3.4.d. Top management subsequently approved the change authorization record under Subclause 8.3.6.c. When re-audited, the business presented verified testing logs, updated software revision files, and documented authorization sign-offs.
Note: Reviews, verification, and validation may be conducted separately or in any combination suitable for the organisation's products and services under Subclause 8.3.4.
Before your audit
- Verify that design planning records define stages, responsibilities, and control interfaces under Subclause 8.3.2.
- Confirm that design inputs are complete, unambiguous, and retained as documented information under Subclause 8.3.3.
- Ensure design review minutes record problem evaluations and subsequent resolution actions under Subclause 8.3.4.
- Retain documented evidence proving design verification confirms outputs meet input requirements under Subclause 8.3.4.c.
- Retain documented evidence proving design validation confirms products satisfy intended use criteria under Subclause 8.3.4.d.
- Check that design outputs specify acceptance criteria and safe operational characteristics under Subclause 8.3.5.
- Retain documented information on design changes, review results, authorizations, and adverse impact controls under Subclause 8.3.6.
Questions people ask
What are iso 9001 design and development controls?
ISO 9001 design and development controls are mandatory process checks under Clause 8.3 that ensure products and services meet requirements. They include defining project stages, evaluating inputs, conducting reviews, performing verification, executing validation, and controlling changes.
What is the difference between design verification and design validation in ISO 9001?
Under Subclause 8.3.4, design verification checks whether design outputs meet specified input requirements, such as checking calculations or dimensions against drawings. Design validation confirms that the final product or service satisfies requirements for its specified application or intended operational use.
What documents must be retained for ISO 9001 design and development?
Under Clause 8.3, organisations must retain documented information on design inputs under Subclause 8.3.3, control activities under Subclause 8.3.4, design outputs under Subclause 8.3.5, and design changes including review results and authorizations under Subclause 8.3.6.
When can an organisation exclude ISO 9001 Clause 8.3 from its scope?
An organisation may determine that Clause 8.3 is not applicable under Subclause 4.3 only if it does not design or modify products or services. If non-applicability does not affect product conformity or customer satisfaction enhancement, the justification must be maintained as documented information.
Reference documents
- ISO 9001:2015 Quality management systems — Requirements
Manage this work in 4Auditee
Keep audit plans, problems, corrective actions and document versions in one place. See the records behind each change and decision.
Book a demo