What it is about
Clause 8.3 applies to organisations that determine for themselves what their products or services are like. Anyone who turns requirements into a new product, an assembly, software or a new service offering is doing design and development in the sense of the standard, even without a development department of their own.
The standard describes design and development as a controlled path. Stages, reviews, responsibilities, interfaces and the involvement of customers and users are planned. The inputs are determined: function and performance, statutory requirements, relevant standards, experience from earlier developments and the potential consequences of failure. Control is exercised through reviews, verification and validation. At the end there are outputs that purchasing, production and inspection can work with, and changes are carried out in a controlled way.
Verification and validation answer two different questions. Verification asks whether the product was developed correctly, that is whether it meets the defined inputs. Validation asks whether the right product was developed, that is whether it is fit for its intended purpose at the customer’s.
An organisation that does no design, such as a subcontractor manufacturing to the customer’s drawings, can declare 8.3 not applicable. The exclusion is justified in the scope and must not affect the ability to supply conforming products and services.
What the auditor checks
“Who decides what the product looks like and what it has to be able to do?”
The question behind every exclusion. If the organisation determines dimensions, materials, processes or the scope of a service itself, it is designing, and 8.3 applies. Adapting a standard product for a customer can also be design.
“Show me a development project from the beginning to release.”
Whether planning, inputs, reviews, verification, validation and outputs can be seen on a real project. A project followed through says more than any procedure.
“Where do the inputs come from, and how can you tell they are complete?”
Whether, besides the customer’s wishes, statutory requirements, standards, experience from similar projects and complaints have been taken into account, and whether conflicting inputs were resolved.
“How did you show that the product works at the customer’s?”
Validation: field test, pilot customer, trial run, acceptance. Organisations often verify thoroughly in the laboratory and leave out the step with the user.
“What happens if something changes after the design has been released?”
Whether changes are reviewed, approved and recorded, and whether their effects on parts already delivered and on current production are considered.
“Who took part in the last design review?”
Whether production, purchasing, quality and, where appropriate, the customer are involved. A review attended only by development often overlooks what will later be difficult in production.
Which evidence convinces
A project plan with stages, reviews and responsibilities
It shows that design and development is controlled and does not simply happen.
The recorded inputs, for example a requirements specification
Verification is carried out against them. Without recorded inputs, there is no way to show that the output meets them.
Minutes of design reviews with decisions
They show that checks took place at defined points and that a decision was made about going on, with actions where there were problems.
Results of verification and validation
Test reports, trial records, acceptance by the customer. They are the actual evidence that design and development achieved its aim.
Released design outputs with their change history
Drawings, bills of materials, inspection plans or service descriptions with their revision, plus the controlled changes. They are the basis for purchasing, production and [release](/en/standard-chapters/9001-8-6-release).
Typical nonconformities
Exclusion without a sound justification
8.3 is excluded although the organisation designs products or shapes services itself. A whole part of the system that should apply is then missing: a major nonconformity, which often also affects the scope on the certificate.
Validation missing
The product has been checked against the requirements specification, but never under the customer’s conditions. If this is missing in a single project, it is a minor nonconformity.
Inputs not recorded
The requirements are spread across emails, telephone notes and people’s heads. Verification is carried out against whatever someone remembers.
Uncontrolled changes
Design changes go straight into production without review and without a new drawing revision. This often only shows up in a complaint.
Reviews without decisions
The planned milestones took place, but the minutes record neither problems nor actions. Whether the review achieved anything remains open.
Differences by standard
ISO 9001ISO 9001
Only ISO 9001 has a clause on design and development. ISO 14001 requires, in operational planning and control (8.1), environmental requirements to be addressed in the design and development of products and services with a view to the life cycle; in ISO/IEC 27001, 8.3 covers information security risk treatment, and secure development is a control in Annex A. The 2026 edition of ISO 9001 keeps the structure of 8.3.
How IMScollect covers it
IMScollect deliberately has no separate module for design and development. The chapter page 8.3 brings together the evidence for the requirements of the standard and leads to the places where design and development appears in the system: the development process in the process map, tasks, controlled documents such as the requirements specification and inspection plan, and planned changes.
If your organisation does no design, you exclude 8.3 in the scope with a justification. The chapter then disappears from the navigation, and the chapter page shows the exclusion with its justification, just as the auditor wants to see it.
Frequently asked questions
When may clause 8.3 be excluded?▾
When the organisation does not itself determine what its products and services are like, for example as a subcontractor manufacturing to the customer’s drawings or as a trader without its own design. The exclusion is justified in the scope and must affect neither the conformity of the products nor customer satisfaction.
Does 8.3 also apply to service providers?▾
Yes, if they design new services, for example a new training format, a maintenance package or a new consulting process. Design and development does not only mean engineering hardware.
What is the difference between verification and validation?▾
Verification checks whether the output meets the defined inputs. Validation checks whether the product is fit for its intended use, usually under real or simulated conditions at the user’s.
Does every small adjustment need a development project?▾
No. The scope and depth of control depend on the nature, duration and complexity of the design and development. A small variant can manage with a short check and release; what should be defined is when the full path applies.
