QA vs. QC
Quick facts
| Category | Process-level prevention vs. output-level detection |
|---|---|
| Used by | Manufacturing, medical devices, pharmaceuticals, aerospace, automotive and other regulated industries |
| Also called | QA, QC |
| Related standards | ISO 9001, ISO 13485 |
| Related processes | Document control, internal audit, inspections, process control |
| Semantic match | QA vs QC, quality assurance vs quality control, proactive vs reactive quality, process control vs inspection |
What is QA vs. QC?
Quality assurance is the proactive, process-oriented side of quality management, concerned with designing and maintaining the systems, procedures and controls needed to consistently produce a conforming product or service before any output is actually made. QA activities include process design, document control, training, internal audits and process capability studies.
Quality control is the reactive, output-oriented side, concerned with checking whether a specific product, batch or service actually meets requirements. QC activities include incoming, in-process and final inspection, testing, and sampling, typically resulting in an accept or reject decision for the item being checked.
The two functions are complementary rather than interchangeable. A strong QA system reduces the number of defects QC needs to catch, while QC provides the feedback data that helps QA identify where processes need improvement.
Why is QA vs. QC important?
Confusing QA and QC, or relying on one without the other, leaves gaps in a quality system. An organization with excellent inspection (QC) but weak process design (QA) will keep catching the same defects without ever reducing how often they occur.
Understanding the distinction helps organizations invest appropriately: QA investment reduces the underlying defect rate over time, while QC investment catches defects that do occur before they reach the customer.
Clarity between QA and QC also supports better organizational design, ensuring that process improvement responsibilities are not confused with inspection responsibilities, even though both may report through the same quality function.
How does QA vs. QC work?
In practice, QA and QC typically operate together as follows:
- QA: process design. Define procedures, work instructions and controls intended to produce conforming output.
- QA: system maintenance. Conduct internal audits, training and document control to keep the system effective.
- QC: inspection and testing. Check incoming materials, in-process work and finished products against specifications.
- QC: disposition. Accept, reject or route nonconforming items for further action.
- Feedback loop. QC data on defects and trends informs QA's ongoing process improvement efforts.
Quality Assurance (QA) vs. Quality Control (QC)
| Comparison | Quality Assurance (QA) | Quality Control (QC) |
|---|---|---|
| Orientation | Proactive, process-focused | Reactive, output-focused |
| Goal | Prevent defects from occurring | Detect defects that have already occurred |
| Typical activities | Process design, document control, internal audit | Inspection, testing, sampling |
Real-world examples of QA vs. QC
A manufacturer's QA team designs a new work instruction and trains operators on it, while the QC team subsequently inspects output produced under that instruction to confirm it meets specification.
A medical device company's QA function conducts an internal audit of the assembly process, while its QC function performs final inspection on each unit before release, together covering both the process and the output.
A food manufacturer's QC team identifies a recurring defect during inspection, feeding that data back to QA, which investigates and revises the underlying process to reduce the defect rate going forward.
Regulations and standards related to QA vs. QC
ISO 9001 does not use the specific terms QA and QC as separate clauses, but its requirements span both functions: clauses addressing process planning and control reflect QA-style prevention, while clauses on monitoring, measurement and control of nonconforming outputs reflect QC-style detection.
ISO 13485 similarly incorporates both dimensions, with design and process controls representing QA and inspection and testing activities representing QC, though the standard does not draw a formal line between the two terms.
Required by
How QT9 helps with QA vs. QC
QT9 QMS capabilities supporting both QA and QC
- Support QA activities through document control, training and internal audit modules.
- Support QC activities through inspections, nonconforming product and calibration modules.
- Connect QC inspection data directly to QA-driven corrective actions.
- Provide real-time dashboards showing both process and output performance.
- Maintain a single, connected system covering the full scope of quality management.
- Support compliance with ISO 9001, ISO 13485 and other applicable standards.
See QT9 Software in Action
Discover how QT9 Software helps manufacturers improve efficiency, strengthen compliance and connect quality management and ERP processes within one integrated platform.
Common mistakes with QA vs. QC
Common mistakes include treating QC inspection results as the entire quality program, without investing in the QA-side process improvements that would reduce the defect rate over time.
Other problems include using the terms interchangeably in a way that confuses responsibilities, such as assigning process design work to a role intended for output inspection.
Frequently asked questions
Related quality management terms
Related content
Ready to Transform Your Business?
See how QT9 Software helps manufacturers simplify operations, improve traceability and drive continuous improvement with integrated quality management and ERP software.