ISO Compliance Insights & Best Practices
CART
ISO Compliance Insights & Best Practices
Clause 8.3 is the part of ISO 9001 most often either excluded without justification or implemented
as a filing exercise. This guide covers what ISO 9001 design and development records
must actually capture, template by template, and how to decide whether the clause applies to you at
all.
Start here, because getting ISO 9001 design and development scope wrong is expensive in both directions. Clause 8.3 applies where you
determine the characteristics of a product or service yourself rather than receiving them fully
specified. If a customer hands you a complete drawing and you manufacture to it, you may be able to
exclude design. If you interpret a brief, specify materials, write software, formulate a recipe or
configure a service offering, you are designing.
Service organisations exclude 8.3 far too readily. Designing a new training programme, a new
insurance product or a new consulting methodology is design and development, and an auditor who finds
new service lines launched with no design records will say so. If you do exclude it, the exclusion
must be justified in your scope statement, and “we don’t do design” is not a justification when your
website advertises bespoke solutions.
The ISO 9001 design and development plan. Stages of the project, review, verification and
validation activities at each stage, responsibilities and authorities, resources, the interfaces
between the people involved, customer involvement, and the level of control expected by customers.
One plan per project or per project type.
Design inputs record. Functional and performance requirements, applicable
statutory and regulatory requirements, information from previous similar designs, standards or codes
of practice you have committed to, and the potential consequences of failure. Inputs must be adequate,
complete and unambiguous, and conflicting inputs must be resolved — so the template needs a
field recording that resolution, not just the inputs themselves.
Design review record. Held at planned stages, evaluating whether results meet
requirements, identifying problems and proposing action. Record who attended, because a review signed
by one person is not a review.
Verification record — did the outputs meet the inputs? — and
validation record — does the result meet the intended use in practice? These
are distinct activities and a great many ISO 9001 design and development templates collapse them into
one signature box. Verification is against specification; validation is against reality.
Design outputs record. Outputs must meet the input requirements, be adequate for
subsequent provision, include or reference monitoring and acceptance criteria, and specify the
characteristics essential for intended purpose and safe use.
Design change record. Changes made during or after development, reviewed and
controlled to avoid adverse effect on conformity, with records of the change, the review results, the
authorisation and any actions taken.
The full clause 8.3 record set, already drafted.
The ISO 9001 Toolkit includes the design and development procedure, project plan, inputs and outputs registers, review, verification and validation records and the design change form — 45+ editable templates mapped to the clause each satisfies.
Clause 8.3 explicitly allows the extent of control to reflect the nature, duration and complexity
of the design activity. A two-week service redesign does not need the stage-gate apparatus of an
aerospace programme. What it does need is the same logical chain: planned stages, recorded inputs, a
review, separate verification and validation, controlled outputs, and change control. Scale the
paperwork, not the logic.
See also the ISO 9001 clauses explained and our guide to
ISO 9001 procedures and forms.
All of these are covered by the ISO 9001 Toolkit, or start with the free ISO templates.
August 13, 2026
August 13, 2026
August 13, 2026
August 13, 2026