ISO 9001 Design and Development: Verification, Validation and Change Control
A design can meet its written specification yet prove difficult to use in practice. A successful demonstration can also leave important technical requirements unchecked. ISO 9001 design and development controls help organisations examine both questions: does the design meet its requirements, and will the resulting product or service suit its intended use?
Design review, verification and validation each contribute to that evaluation. Understanding their different purposes helps teams plan useful checks, resolve problems and retain evidence that explains their decisions.
This article follows a hypothetical customer order-entry portal from initial requirements through evaluation, approval and subsequent changes. It also explains how design responsibilities affect the competence needed for certification assessment.
Design Responsibility and QMS Applicability
Design and development turns requirements into defined characteristics of a product or service. It can involve physical products, software, engineering solutions or service arrangements.
To determine applicability within your Quality Management System (QMS), examine the decisions your organisation makes. Does it develop the solution, define its characteristics or modify a design in ways that affect conformity?
Manufacturing to a customer’s complete design differs from developing a solution to achieve the customer’s intended outcome. Establish which responsibilities belong to your organisation and which remain with the customer or another party.
Outsourcing design does not automatically remove those responsibilities. Consider what your organisation retains, how it controls the external provider’s work and how the parties exchange information. ISO’s Auditing Practices Group addresses these issues in its scope and applicability guidance.
Confirm applicability against the ISO 9001 edition and scope used for assessment. Supporting guidance helps interpretation; it does not create additional certification requirements.
Functional Distinctions Between Review, Verification and Validation
| Control | Principal question | Typical evidence |
|---|---|---|
| Design review | Is the design progressing appropriately, and which problems or decisions need attention? | Evaluation results, decisions, assigned actions and follow-up. |
| Design verification | Do the design outputs meet the specified inputs? | Results comparing outputs with defined requirements. |
| Design validation | Can the resulting product or service meet requirements for its specified application or intended use? | Results from suitable evaluation of intended use. |
These activities may take place at several stages. Teams can combine them where appropriate, provided each purpose is addressed.
The activity’s name alone proves little. A meeting labelled “validation” may never examine intended use. A signed review record may show approval without explaining whether specified requirements were checked.
Make the evidence clear: identify what was examined, which criteria applied, what the evaluation found and what happened next. The ISO design and development auditing guidance discusses these distinctions.
Design Input Definition and Requirements Traceability
Useful evaluation starts with clear inputs. If a requirement says only that a service must be “easy to use”, the team still needs to establish:
Who will use it.
Which tasks those users must complete.
The relevant operating conditions.
What constitutes an acceptable result.
Which assumptions require confirmation.
Inputs may arise from customer requirements, applicable obligations, previous designs, operating experience and the consequences of failure.
Resolve contradictory requirements before different people build incompatible assumptions into the design. When requirements change during development, update the relevant information and communicate the change to affected people.
A requirements register can connect each input with its source, owner, acceptance criteria and planned evaluation. This is one practical method; the register itself is not a mandatory format.
Design Planning and Control Responsibilities
Plan review, verification and validation around the design’s complexity, the work involved and the consequences of failure.
For each activity, establish:
The subject and revision being evaluated.
The purpose and acceptance criteria.
Participants, responsibilities and approval authority.
Evaluation methods and necessary resources.
Customer or external-party involvement, where appropriate.
Records to retain and arrangements for resolving findings.
Development rarely proceeds without feedback. A review can uncover an unclear requirement; testing can reveal an assumption that needs reconsideration. Update the plan when these discoveries affect responsibilities, resources or evaluation methods.
ISO 9001:2026 recognises cycles of review, verification, validation and feedback within design and development. For broader revision and implementation context, read our ISO 9001:2026 changes and differences from ISO 9001:2015 guide.
Design Review: Technical Evaluation and Action Resolution
Design review brings together the people needed to evaluate the work at an appropriate stage.
Depending on the project, the review may examine unresolved requirements, technical assumptions, supplier information, interfaces, operating constraints and readiness to proceed.
A useful review produces decisions that people can act on. For example, the team might need to confirm an assumption with the customer, ask another department to examine an interface or revise a proposed test.
Record who will complete each action and how completion will be checked. Attendance lists and approval signatures can support the record, but they may leave the reasoning behind a decision unexplained.
Design Verification: Conformity With Specified Inputs
Verification checks whether design outputs satisfy the defined inputs.
Suitable methods depend on the design. They may include calculations, document examination, simulations, demonstrations, inspections or testing.
A clear verification record connects:
Requirement → Design output or revision → Evaluation method → Result → Necessary action
For example, if a requirement specifies that an order must receive approval before export, verification should establish whether the designed workflow enforces that rule.
Results lose value when the tested revision or acceptance criteria cannot be identified. Someone reviewing the record should be able to understand which requirement was checked and whether the result applies to the current design.
Methods can also include alternative calculations or comparison with a proven design, where appropriate. Retain evidence that explains the method and its results. For broader guidance on organising management-system records, refer to our ISO documents required for UAE companies.
Design Validation: Suitability for Intended Use
Validation examines whether the resulting product or service can meet requirements for its intended application.
Choose evaluation conditions that reflect relevant users, tasks and operating situations. Depending on the design, suitable methods may include trials, representative scenarios, prototypes or commissioning activities.
Technical checks can pass while practical difficulties remain. Users may encounter an operating condition that the original inputs overlooked, or a workflow may require a workaround that makes routine tasks impractical.
Customer participation can help establish suitability. However, a general approval email may leave important questions unanswered. Record what the customer or users evaluated, the conditions involved, the results and any necessary follow-up.
Applied Example: Customer Order-Entry Portal
This hypothetical example illustrates the controls. It does not prescribe a software-development method.
A company develops a portal through which customers submit orders. The agreed requirements include:
Capturing the customer’s order reference.
Checking availability against an approved product-data source.
Routing orders requiring approval to an authorised reviewer.
Exporting approved orders to the order-processing system.
| Stage | Evaluation activity | Example evidence |
|---|---|---|
| Input definition | Agree functions, conditions and acceptance criteria. | Requirements register and approved assumptions. |
| Design review | Examine approval responsibilities, unavailable products, revised orders and interfaces. | Decisions, assigned actions and updated inputs. |
| Verification | Check fields, routing and export behaviour against specified inputs. | Results linked to requirements and the tested revision. |
| Validation | Have representative users complete realistic order scenarios under agreed conditions. | Trial results, observations and acceptance decisions. |
| Change control | Evaluate a request for delegated approval during absences. | Impact review, authorisation and repeat checks. |
Verification confirms that orders route to the nominated approver exactly as specified. During validation, representative users discover that an absent approver prevents ordinary orders from progressing.
Both results are useful. The routing rule works, but the intended working arrangement needs further consideration.
The organisation reviews whether to change the requirements, the solution or the operating arrangements. It then evaluates the chosen response and records the outcome.
Requirements-to-Release Evidence Traceability
Connected records make design decisions easier to understand.
In the portal example, a requirement identified as REQ-04 could link to:
The requirement and its source.
A review decision concerning approval authority.
The resulting workflow revision.
Verification results for that revision.
Validation results from representative scenarios.
Identified issues and completed actions.
Authorisation of the approved output.
Later changes affecting the requirement.
Identifiers are one possible approach. The aim is to make the evidence retrievable and show which design it concerns.
For instance, a successful test from an earlier revision may remain relevant, but the record should explain why. The person reviewing it should not have to infer whether subsequent changes affected the result.
Design Change Assessment and Authorisation
Design changes can arise from customer requests, supplier substitutions, defects, operational feedback or new requirements.
Before relying on earlier evaluation results, assess what the proposed change could affect.
In the portal example, delegated approval may alter permissions, routing, notifications, records and export behaviour. A request that appears to concern one screen can have consequences elsewhere in the system.
| Change-control element | Question |
|---|---|
| Purpose | Why is the change needed? |
| Affected design | Which requirements, outputs and revisions are involved? |
| Impact | What else could be affected, including delivered products or operating services? |
| Evaluation | Which reviews, verification or validation activities are appropriate? |
| Authority | Who can approve the change? |
| Implementation | How are affected people and documented information updated? |
| Results | What demonstrates that the change achieved its purpose? |
The extent of repeat evaluation depends on the change’s effects and applicable requirements. Some changes warrant extensive testing; others may justify a more limited evaluation.
Retain the reasoning, particularly when accepting earlier results as still valid. To understand how this evidence fits into the wider certification assessment, read our ISO 9001 application and audit guide.
Design and Development Audit Evidence
Certification assessment should follow the organisation’s actual design activities and responsibilities.
Relevant evidence may include:
Design plans and assigned responsibilities.
Inputs and controlled updates.
Review decisions and completed actions.
Verification methods, criteria and results.
Validation arrangements and findings.
Approved outputs suitable for subsequent activities.
Controls over outsourced-design interfaces.
Change decisions and affected revisions.
Be prepared to explain why the evaluation methods suit the work. A clear sequence of requirements, decisions and results can be more informative than a large collection of disconnected documents.
Certification-Body Competence for Design Assessment
The assessment team needs suitable competence to evaluate the organisation’s design responsibilities, methods and evidence.
That includes understanding the distinction between review, verification and validation, examining relevant interfaces and assessing whether the evidence supports the organisation’s conclusions.
When discussing assessment coverage, explain:
What your organisation designs.
Which design decisions it makes.
Which activities are outsourced.
How intended use is established.
Which technical interfaces and locations are involved.
The certification auditor evaluates the management system. The auditor does not take responsibility for the design, approve the solution on the customer’s behalf or replace separate product or regulatory approvals.
Our guide to ISO 9001 certification bodies in UAE explains the related accreditation checks, provider comparisons and proposal arrangements.
Design-Control Gaps and Assessment Implications
| Potential gap | Question to investigate |
|---|---|
| Inputs are vague or contradictory. | Were requirements and acceptance criteria clarified? |
| Reviews record approval without decisions. | What was examined, and how were issues resolved? |
| Tests are not linked to a revision. | Do results apply to the output being released? |
| Verification is presented as validation. | Was intended use evaluated? |
| Customer approval is treated as complete evidence. | What did the customer examine, and which responsibilities remain? |
| Changes bypass evaluation. | Were effects on requirements and earlier results considered? |
| Outsourced work is treated as outside the QMS. | Were retained responsibilities and supplier controls addressed? |
Use these questions to investigate the evidence. They are not a universal list of audit findings. Any conclusion must relate to the applicable requirements and the circumstances examined.
Explore ISO Certification Information by Country
For country-specific ISO certification information and enquiries, select your location below. Certification arrangements depend on your organisation’s activities, operating locations, applicable standards and relevant requirements.
| Region | Country information |
|---|---|
| Gulf countries | United Arab Emirates · Saudi Arabia · Qatar · Bahrain · Kuwait · Oman |
| Other Middle Eastern countries | Iraq · Jordan · Lebanon |
| North Africa | Egypt · Morocco · Tunisia |
| Asia | India · Malaysia · Singapore · Philippines |
| Europe | United Kingdom |
| North America | United States · Canada |
Contact Veritas Assurance to discuss your certification requirements. Include your business activities, operating locations and the ISO standards you are considering.
ISO 9001 Assessment Enquiries and Certification Scope
An assessment enquiry should give the certification body enough information to understand the proposed engagement.
Provide your business activities, proposed scope, operating locations, workforce and current certification status. Describe your design responsibilities, relevant outsourced work and customer conditions that may affect assessment arrangements.
For standard-specific enquiries, visit ISO 9001 certification services in UAE. For enquiries involving several management-system standards, start with the ISO certification in UAE overview.
Contact Veritas Assurance to discuss your proposed scope and available certification arrangements.
Frequently Asked Questions
What distinguishes a design input from a design output?
How can an organisation determine whether it holds design responsibility?
Does working from customer drawings make design and development inapplicable?
Can a service organisation have design and development activities?
Does outsourcing all design work remove the need for design controls?
How should conflicting design inputs be handled?
How can vague customer expectations become usable design inputs?
Is a requirements traceability matrix compulsory?
Who should participate in a design review?
What makes a design review record useful beyond attendance signatures?
Can design review, verification and validation take place together?
Does design verification always require physical testing?
Can simulation results support design verification?
Why should verification results identify the design revision?
What happens when verification identifies an unmet requirement?
Can a design pass verification but fail validation?
Is customer approval sufficient evidence of design validation?
How should representative users be selected for validation?
What should validation cover when unusual operating conditions matter?
Can commissioning contribute to design validation?
What should happen when validation reveals a missing requirement?
What should an approved design output contain?
Which events should trigger design change assessment?
Does every design change require complete revalidation?
Can a supplier substitution affect design verification or validation?
How should a change affecting products already delivered be assessed?
How can design changes be controlled during iterative development?
How should outsourced design evidence connect with internal records?
What design information helps a certification body plan a competent assessment?
Does ISO 9001 certification approve an individual product design?
Discuss Your ISO 9001 Design Assessment Scope
Share your design responsibilities, outsourced activities and operating locations with Veritas Assurance to discuss the scope and arrangements for ISO 9001 certification assessment.



