Study guide

4.2 Clause 8.3 — Design and Development

CQI-IRCA ISO 9001 QMS Lead Auditor Exam

Track your progress as you read

Finished sections get a check mark.

1 Quality Management & Exam Foundations

1.1 Exam Facts, Format & the IRCA Certification Pathway 1.2 The ISO Standards Family, the Auditor's Role & Key ISO 9000 Terms 1.3 The Seven Quality Management Principles 1.4 The Process Approach and the PDCA Cycle 1.5 Risk-Based Thinking & the Annex SL High-Level Structure

2 ISO 9001 Clauses 4 & 5: Context and Leadership

2.1 Clause 4 — Context, Interested Parties, QMS Scope & Processes 2.2 Clause 5.1 — Leadership, Commitment & Customer Focus 2.3 Clause 5.2–5.3 — Quality Policy, Roles, Responsibilities & Authorities

3 ISO 9001 Clauses 6 & 7: Planning and Support

3.1 Clause 6 — Planning 3.2 Clause 7.1 — Resources 3.3 Clause 7.1.6 & 7.2–7.4 — Organizational knowledge, competence, awareness & communication 3.4 Clause 7.5 — Documented information

4 ISO 9001 Clause 8: Operation

4.1 Clause 8.1–8.2 — Operational Planning & Requirements for Products and Services 4.2 Clause 8.3 — Design and Development 4.3 Clause 8.4 — Control of Externally Provided Processes, Products & Services 4.4 Clause 8.5 — Production and Service Provision 4.5 Clause 8.6–8.7 — Release of Products/Services & Control of Nonconforming Outputs

5 ISO 9001 Clauses 9 & 10: Performance Evaluation and Improvement

5.1 Clause 9.1 — Monitoring, measurement, analysis & evaluation 5.2 Clause 9.2 — Internal audit 5.3 Clause 9.3 — Management review 5.4 Clause 10 — Improvement

6 Audit Principles & Managing an Audit Programme (ISO 19011)

The Seven Principles of Auditing & Core Audit Terminology Audit Types & Establishing an Audit Programme Implementing, Monitoring, Reviewing & Improving the Audit Programme

7 Planning & Conducting the Audit

7.1 Initiating the Audit & Reviewing Documented Information 7.2 Preparing the Audit Plan, Checklists & Working Documents 7.3 The Opening Meeting & Communication During the Audit 7.4 Collecting & Verifying Evidence: Interviews, Observation, Audit Trails & Sampling

8 Findings, Nonconformities & Reporting

8.1 Generating Audit Findings & Evaluating Evidence Against Criteria 8.2 Grading Nonconformities: Major, Minor, Conformity & Opportunities for Improvement 8.3 Writing Nonconformity Statements: Requirement, Evidence & Nonconformity 8.4 Audit Conclusions, the Closing Meeting, the Audit Report & Follow-Up

9 Certification, Competence & Professional Conduct

9.1 Third-party certification & accreditation (ISO/IEC 17021-1) & the certification cycle 9.2 Auditor competence, evaluation, personal behaviours & IRCA certification grades

4.2 Clause 8.3 — Design and Development

Key Takeaways Explain This Topic AI

Clause 8.3 can only be excluded under Clause 4.3 if it genuinely does not affect the organization's ability to ensure conformity — auditors must test, not just accept, exclusion claims.

Design inputs (8.3.3) must be adequate, complete, and unambiguous, with conflicting inputs resolved before design proceeds.

Review, verification, and validation (8.3.4) are three distinct controls: review evaluates progress, verification checks outputs against inputs, and validation checks the product against intended use.

Validation must be completed before delivery or implementation unless the customer stipulates otherwise.

Design and development changes (8.3.6) require documented review, authorization, and evidence that adverse impact on conformity was prevented.

Last updated: July 2026

When 8.3 Applies — and When It Can Be Excluded

Design and development is one of the few ISO 9001:2015 requirement clauses an organization can legitimately exclude, under the exclusion mechanism in Clause 4.3, if it can demonstrate the requirement does not affect its ability or responsibility to ensure conformity of products and services and to enhance customer satisfaction. Manufacturing strictly to a customer's complete specification, with no design input of its own, is the classic justified exclusion. An auditor should test this claim rigorously rather than accept it at face value: if the organization selects materials, determines dimensions, develops a formulation, or writes software logic to meet a stated functional requirement rather than a fully defined specification, it is designing - and 8.3 applies whether or not the organization's own procedures use the word "design."

8.3.1 General

Where 8.3 applies, the organization must establish, implement, and maintain a design and development process that is adequate to ensure the subsequent provision of products and services.

8.3.2 Design and Development Planning

In determining the stages and controls for design and development, the organization must consider the nature, duration, and complexity of the activities; the required process stages , including applicable reviews; required verification and validation activities; responsibilities and authorities involved; internal and external resource needs ; the need to control interfaces between people involved in the process; the need for customer and user involvement ; requirements for subsequent provision of products and services; the level of control expected by customers and other relevant interested parties; and the documented information needed to demonstrate that design requirements have been met.

Auditor evidence: a design and development plan - a gate chart, stage-gate schedule, or project Gantt - naming reviewers, specifying verification and validation methods, and showing resourcing against each stage.

8.3.3 Design and Development Inputs

Inputs must be determined for the specific type of product or service, and must include functional and performance requirements; information derived from previous similar design activities; statutory and regulatory requirements; standards or codes of practice the organization has committed to implement; and potential consequences of failure arising from the nature of the products and services. Inputs must be adequate for the purposes of design, complete, and unambiguous , and conflicting inputs must be resolved before proceeding. The organization must retain documented information on design and development inputs.

8.3.4 Design and Development Controls

This is the heart of the sub-clause, and it covers three distinct activities that candidates must be able to tell apart on the exam:

Control Purpose Typical evidence

Review Evaluate the ability of the results to meet requirements; identify problems and propose necessary actions Design review minutes, action log

Verification Confirm that design and development outputs meet the input requirements ("did we build it right?") Test reports, calculations, independent peer check, comparison to a proven design

Validation Confirm the resulting product or service meets requirements for the specified application or intended use ("did we build the right thing?") Field trial data, customer acceptance test, prototype trial results

Controls must ensure that results define acceptance criteria, that participants include all functions relevant to the design stage being reviewed, that problems are identified with actions determined, and that documented information on these activities is retained. Validation must, unless otherwise stipulated by the customer, be completed prior to delivery or implementation of the product or service, not afterward.

8.3.5 Design and Development Outputs

Outputs must meet input requirements; be adequate for the subsequent processes for the provision of products and services; include or reference monitoring and measuring requirements, and acceptance criteria; and specify characteristics of the products and services essential for their intended purpose and for their safe and proper provision. Documented information on design and development outputs must be retained.

8.3.6 Design and Development Changes

Changes made during or after design and development of products and services must be identified, reviewed, and controlled to the extent necessary to ensure there is no adverse impact on conformity to requirements. Documented information must cover the design and development changes, the results of reviews, the authorization of the changes, and the actions taken to prevent adverse impacts.

What the Auditor Actually Traces

A strong 8.3 audit follows one design from input to output to change : start with a customer functional specification (an input), locate the review, verification, and validation records with named participants and dated sign-off, confirm the output package - drawings, specifications, acceptance criteria - is genuinely what production uses on the floor, and then pull one engineering change to see whether it was reviewed for downstream impact before implementation, rather than only being documented after a nonconformity had already surfaced in the field.