Study guide
18.3 Change Control, Configuration Management, V&V
ASQ Certified Quality Auditor CQA
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
0.1 Current Exam Facts 0.2 Eligibility, Fees & Recertification 0.3 Case Studies & Study Strategy
2 Chapter 1: Types of Quality Audits
1.1 Product, Process, System, Hybrid & Remote Audits 1.2 First-, Second- & Third-Party Context 1.3 CAPA Verification, Risk-Based, Surveillance & For-Cause 1.4 Common Elements with Sustainability, EHS & Financial Audits
3 Chapter 2: Purpose, Scope & Audit Criteria
2.1 Elements of Purpose and Scope 2.2 Benefits of Audits (Effectiveness, Risk, Cyber) 2.3 Criteria: Standards, Contracts, Specs & QMS
4 Chapter 3: Roles, Ethics & Audit Credibility
3.1 Roles: Lead Auditor, Team, Client, Auditee, Observer 3.2 ASQ Code of Ethics, Due Care & Confidentiality 3.3 Legal Consequences of Improper Auditor Actions 3.4 Independence, Objectivity & Qualifications
5 Chapter 4: Audit Planning Fundamentals
4.1 Elements of the Audit Planning Process 4.2 Auditor Selection Criteria 4.3 Pre-Audit Documentation & Gap Assessments 4.4 Logistics: Safety, Escorts, Access & PPE
6 Chapter 5: Auditing Tools, Strategies & the Audit Plan
5.1 Sampling Plans, Checklists & Working Papers 5.2 Forward/Backward Tracing, Discovery & Observation 5.3 Creating and Distributing the Audit Plan
7 Chapter 6: Audit Performance Management
6.1 On-Site Management for the Auditor 6.2 On-Site Management for the Auditee 6.3 Opening Meeting
8 Chapter 7: Evidence Collection & Closing Meetings
7.1 Audit Data Collection and Analysis 7.2 Characteristics of Objective Evidence 7.3 Organizing Evidence by Risk and Significance 7.4 Exit and Closing Meetings
9 Chapter 8: Audit Reporting
8.1 Report Development and Content 8.2 Effective Reports: Summary, Findings & OFIs 8.3 Approvals, Distribution & Audit File Retention
10 Chapter 9: CAPA Follow-Up & Audit Closure
9.1 CAPA Process Elements & Root Cause 9.2 Reviewing and Negotiating CAPA Plans 9.3 Verifying CAPA Effectiveness 9.4 Ineffective CAPA Escalation & Audit Closure
11 Chapter 10: Auditor Characteristics, Resources & Conflict
10.1 Auditor and Lead Auditor Characteristics 10.2 On-Site Audit Resource Management 10.3 Conflict Resolution Techniques
12 Chapter 11: Communication, Interviewing & Team Dynamics
11.1 Communication and Presentation Techniques 11.2 Interviewing Techniques 11.3 Team Building, Facilitation & Development Stages
13 Chapter 12: Audit Program Management Core
12.1 Senior Management Support for the Audit Function 12.2 Staffing and Resource Management 12.3 Auditor Training and Development 12.4 Audit Program Evaluation Metrics
14 Chapter 13: Internal & External Audit Programs
13.1 Internal Audit Program Management 13.2 External / Supplier Audit Program Management 13.3 Standardizing Best Practices from Audit Results
15 Chapter 14: Risk, Management Review & Electronic Systems
14.1 Organizational Risk Management & Continuity 14.2 Management Review Input from the Audit Program 14.3 Electronic Records, Data Integrity & Cybersecurity
16 Chapter 15: Business & Financial Impact of Auditing
15.1 Auditing as a Management Tool 15.2 Interrelationships of Business Processes 15.3 Cost of Quality Principles
17 Chapter 16: Quality Tools & Process Improvement
16.1 Seven Basic Tools, Root Cause & PDCA 16.2 Six Sigma DMAIC for Auditors 16.3 Lean Principles and Tools
18 Chapter 17: Statistics & Process Variation
17.1 Mean, Median & Mode 17.2 Dispersion & Qualitative vs Quantitative Analysis 17.3 Common Cause vs Special Cause Variation 17.4 Process Capability Metrics & Outliers
19 Chapter 18: Sampling, Change Control, V&V & Risk Tools
18.1 Acceptance Sampling & Sampling Types (incl. MSA) 18.2 Consumer Risk, Producer Risk & Confidence 18.3 Change Control, Configuration Management, V&V 18.4 FMEA, HACCP, CTQ & SWOT
18.3 Change Control, Configuration Management, V&V
Key Takeaways Explain This Topic AI
Change control is the formal process to propose, evaluate, approve, implement, and verify changes so unintended effects do not escape.
Configuration management identifies, controls, and tracks the baseline of hardware, software, documents, products, processes, and services so the as-built matches the as-designed/as-approved.
Verification asks “Did we build/do it right against specifications?”; validation asks “Did we build/do the right thing for user needs/intended use?”
Qualifications (IQ/OQ/PQ or equivalent) provide documented evidence that equipment, systems, and processes are installed, operate, and perform as required in the intended environment.
Auditors analyze change records for impact assessment, approvals, V&V evidence, training, document updates, and post-change monitoring—not just a signature on a form.
Last updated: August 2026
18.3 Change Control, Configuration Management, V&V (CQA BoK V.F–G — Understand/Analyze)
Quick Answer: Change control = formal evaluate–approve–implement–verify loop for changes. Configuration management = identify and control baselines so hardware/software/docs match approved state (include security for software). Verification = meet specified requirements (“build it right”); validation = meet user needs/intended use (“build the right thing”). Qualifications document fitness of equipment/systems/processes. BoK V.F–G . Practice at /practice/cqa .
Uncontrolled change is a leading root of quality escapes, audit findings, and regulatory action. Domain V.F–G expects you to understand change and configuration concepts and analyze whether evidence shows control—across products, processes, services, hardware, and software.
Change control — the managed decision path
Change control (engineering change, process change, document change, supplier change, software change) is the system that ensures modifications are:
- Requested with clear description and reason
- Impact-assessed (quality, regulatory, safety, cost, validation, customers, labeling, training, inventory)
- Reviewed and approved by authorized roles
- Implemented under controlled conditions
- Verified / validated as needed
- Communicated and documented
- Monitored after release for unintended effects
- Scope examples auditors encounter
- Change type Example Typical risks if uncontrolled
- Product / design Material alternate, tolerance change Fitness for use, reliability, regulatory filing
- Process New machine, parameter shift, line transfer Capability, yield, latent defects
- Document Spec revision, SOP rewrite Training lag, dual procedures
- Supplier New source, site move Incoming quality, CoC integrity
- Software Patch, feature release, library update Cybersecurity, data integrity, regression
- Service New delivery method, outsourced step Customer experience, SLA, privacy
- Analyze-level auditor focus
Do not stop at “there is a form.” Analyze:
Was impact assessment substantive or checkbox?
Were affected documents revised and obsolete versions removed?
Was training completed before effective date?
Were customer / regulatory notifications required and done?
Is there objective evidence of verification or validation proportional to risk?
Were in-process inventory and field product assessed?
For temporary changes / deviations: time limits, approvals, and closeout?
Scenario — change control failure
A plant “temporarily” increases cure temperature to recover throughput. No change request, no impact on material properties, no update to the validated process range. Field failures appear months later. The CAPA later cites failure to follow change control —a classic system finding, not only an operator error.
Configuration management (CM)
Configuration management maintains integrity of the product/system definition over time. Core activities (classic CM view):
- CM activity Meaning
- Configuration identification Define items, baselines, version/part numbers, BOMs
- Configuration control Control changes to baselines (tight link to change control)
- Configuration status accounting Know what version is approved, built, installed, released
- Configuration audit Verify as-built / as-installed matches baseline (functional & physical)
- Hardware and products
- Part numbers, revision levels, BOMs, drawings, approved manufacturer lists
- Traceability from serial/lot to configuration
- Spare parts and field upgrades matching approved configs
- Software (including security)
Software CM is non-negotiable for quality and security :
- Version control, release notes, build provenance
- Controlled promotion (dev → test → production)
- Access control, code review, segregation of duties
- Patch management and vulnerability remediation with regression testing
- Backup/restore and disaster recovery configuration
- Protection of electronic records and audit trails where applicable
Auditors of computerized systems look for unauthorized production changes , missing validation of patches, and configuration drift between documented and actual server/application settings.
Processes and services
Process “configuration” includes controlled parameters, recipes, work instructions, tooling IDs, and service scripts. Service CM may cover rate cards, approved scripts, knowledge-base articles, and third-party tool versions used in delivery.
Domain CM artifact examples Audit question
Hardware Drawing rev, BOM, serial config Does as-built match released BOM?
Software Version, commit hash, config files Can they prove what runs in production?
Process Recipe ID, parameter set, WI rev Was the validated recipe the one used?
Service Playbook version, tool build Are agents using current controlled content?
Verification vs validation
These terms are exam favorites. Keep them clean.
Verification
Verification confirms that outputs meet specified requirements . Question: “Did we build / implement it right?”
Examples:
- Design verification tests against design inputs/specs
- Inspection and test to drawing tolerances
- Code review and unit tests against software requirements
- IQ/OQ-style checks that equipment meets installation and operational specs
- Document review verifying procedure steps match standard clauses
- Validation
Validation confirms that the product, process, or system meets user needs and intended use in the real operating context. Question: “Did we build / implement the right thing?”
Examples:
- Clinical / user validation of a device for intended use
- Process validation that the commercial process consistently produces acceptable product
- Software user-acceptance testing in a realistic environment
- Service validation that the redesigned workflow meets customer outcome metrics
- Dimension Verification Validation
- Focus Specifications / requirements Intended use / user needs
Classic question Build it right? Build the right thing?
- Timing Often earlier / throughout development Often later / under real use conditions
- Example Dimensional test to drawing Customer usability / clinical performance
- Failure mode Spec wrong but tests pass Specs met but users still fail to achieve intent
- Scenario — both required
A software update to a quality record system:
Verification: unit tests, requirements traceability, security scans, IQ/OQ of the installed instance.
Validation: UAT with real roles (QA, production) confirming the workflow supports intended use and data integrity under production-like load.
Skipping validation after “all tests passed” can still leave a system unusable or unsafe in practice.
Qualifications needed (IQ, OQ, PQ and analogs)
Qualification provides documented evidence that equipment, facilities, utilities, or systems are suitable. Common staged model (life sciences and widely borrowed elsewhere):
- Stage Name Core idea
- IQ Installation Qualification Installed correctly per specs; utilities, IDs, documentation, calibration hooks
- OQ Operational Qualification Operates across intended ranges; alarms, interlocks, functions work
- PQ Performance Qualification Performs consistently in routine use with real or simulated product/load
Related concepts:
- Process validation (often IQ/OQ/PQ of process equipment + process performance qualification)
- Computer system validation (CSV) / GAMP-style risk-based validation
- Requalification after major change, move, or defined interval
- Commissioning as engineering readiness feeding formal qualification
- Auditor analysis points
Protocols pre-approved with clear acceptance criteria?
Deviations to qualification handled and justified?
Traceability from requirements → tests → results?
Change after qualification triggers impact assessment and partial/full requal?
Training and SOPs effective concurrent with go-live?
Integrating change control + CM + V&V
A mature system treats these as one story:
Identify current configuration baseline.
Propose change with risk/impact (including security for software).
Decide verification, validation, and qualification needs.
Execute testing/qual under approved protocols.
Update configuration status, documents, training, labels.
Release only when evidence complete.
Monitor post-change metrics and complaints.
Mini case for analysis
A contract manufacturer changes sterilization parameters. Change request exists and is signed, but:
- No bioburden/impact scientific rationale
- No update to process validation summary
- Software recipe version in the PLC not updated in CM records
- Training matrix still lists old parameters
Findings analysis: change control incomplete; configuration status accounting broken; validation not demonstrated; training ineffective. Multiple BoK V.F–G issues from one event.
Audit application checklist
Sample closed changes—high risk first (process, software security, sterile, labeling).
Read impact assessments for substance.
Trace configuration: what was approved vs what is installed/running.
Separate verification evidence from validation evidence in the package.
Confirm qualifications/requalifications proportional to change.
Check temporary changes and emergency changes for retrospective control.
For software: access logs, release tickets, security patches, and segregation of duties.
- Common exam traps
- Treating verification and validation as synonyms
- Assuming a signature equals impact assessment
- Forgetting software security as part of configuration/change control
- Believing IQ alone is process validation
- Ignoring document and training updates as part of change
- Thinking configuration management is only for aerospace hardware
- Link forward
Change and V&V decisions should be risk-informed . Next section covers FMEA, HACCP, CTQ, and SWOT as risk tools auditors must understand. Study the full guide at /study-guides/cqa .