A finished product fails its final inspection. Is that a quality assurance problem or a quality control problem? What about creating the inspection procedure that should have caught the issue earlier?
QA and QC are closely related, but they do different jobs within quality management. Understanding that distinction helps businesses build better processes, detect non-conformities, and decide where quality responsibilities belong.
This guide explains what QA and QC mean, their key differences, roles and responsibilities, practical examples, and how they work together in manufacturing and other industries.
QA/QC stands for quality assurance and quality control. Both are parts of quality management, but they focus on different aspects of achieving and maintaining quality.
Quality assurance is concerned primarily with the processes and systems used to consistently meet quality requirements.
It can include activities such as establishing procedures, defining responsibilities, training employees, reviewing processes, conducting audits, and improving the systems used to produce a product or deliver a service.
The International Organization for Standardization describes QA as a systematic process for ensuring that products, services, and processes consistently meet defined quality requirements.
Quality control focuses more directly on checking whether a product, service, material, or other output meets specified requirements.
Typical QC activities include inspection, measurement, testing, recording results, and identifying non-conforming outputs.
The American Society for Quality defines QA and QC separately while recognizing that the terms are sometimes used interchangeably in practice.
The simplest distinction is that QA focuses primarily on how quality is built into a process, while QC checks whether the resulting output meets the required standard.
One common oversimplification is that QA happens “before production” and QC happens “after production.”
In reality, both can operate throughout the lifecycle. QA activities may continue while production is running, while QC can take place when materials are received, during manufacturing, and at final inspection.
Another oversimplification is that QA belongs only to a QA department. Quality responsibilities can extend across management, production, procurement, engineering, operations, and other teams depending on the organization.
QA and QC are most effective when information flows between them.
Consider a manufacturer receiving raw materials from a supplier.
The QA side may help establish:
QC then applies those requirements operationally by inspecting the received material, taking measurements or carrying out required tests, recording results, and determining whether the material meets the defined criteria.
Suppose QC repeatedly discovers the same dimensional defect in material from one supplier.
Rejecting or isolating each affected batch addresses the immediate quality-control problem. But repeated failures may indicate a broader process issue.
The QA process can then examine why the defect continues to occur. That may involve reviewing supplier controls, specifications, purchasing requirements, inspection procedures, or another part of the quality system.
QC therefore provides important evidence about actual quality performance, while QA uses that information alongside other inputs to improve the processes intended to produce consistent results.
Quality-assurance responsibilities vary significantly by industry, company size, risk level, and quality-management system. In general, QA is concerned with whether the organization has appropriate processes for consistently meeting its quality requirements.
Common QA responsibilities can include:
Auditing is particularly associated with quality assurance because an audit examines whether processes or systems conform to defined requirements.
According to ASQ, audits are planned, documented assessments used to compare actual conditions with requirements and report findings.
The exact division of responsibilities will differ between organizations. A small manufacturer, for example, may combine several quality responsibilities within one team, while a larger or highly regulated organization may use specialized roles and more formal separation of duties.
Quality control deals more directly with verifying actual materials, products, services, or other outputs against defined requirements.
Depending on the operation, QC responsibilities may include:
Inspection is one of the clearest examples of QC.
ASQ describes inspection as examining, measuring, or testing characteristics and comparing the results against specified requirements to determine conformity.
QC should not simply become a final checkpoint where every problem is discovered after production is finished. Depending on the process, inspections can be placed earlier.
For manufacturers, receiving and in-process inspections can identify certain problems before additional time, materials, or production capacity are invested in an item that already fails defined requirements.
The distinction between QA and QC becomes clearer when both are applied to the same situation.
Exact activities depend on the industry.
The important distinction is not the industry itself. QA asks whether appropriate processes are in place and operating as intended, while QC evaluates whether specific outputs satisfy their defined requirements.
Manufacturing provides one of the clearest examples of how QA and QC can work together throughout a process.
Start by defining what the material or finished product must meet.
Requirements may come from product specifications, customer requirements, engineering documents, contracts, internal standards, or applicable regulatory requirements.
Determine where quality checks should take place and what will be checked.
Depending on the product, checkpoints could include:
The plan should also establish the relevant criteria, responsibilities, and records.
QC can verify selected incoming materials or components before they enter production.
If something does not meet the defined requirements, the issue can be documented and handled according to the organization's quality process.
Waiting until the end of production can make some quality problems more difficult or expensive to address.
In-process inspections allow defined characteristics to be checked at relevant production stages.
Before finished goods move to the next stage, final QC checks can verify the characteristics specified by the applicable quality plan.
Inspection failures should be documented so the organization has a traceable record of what happened and how the issue was handled.
Repeated failures are particularly useful signals.
If the same defect appears regularly, QA and operational teams can investigate whether the underlying process, supplier, specification, equipment, training, or control plan requires improvement.
For a broader view of how quality checkpoints fit into manufacturing operations, see HAL's guide to production planning and control.
Quality management is the broader discipline within which QA and QC operate.
The ISO overview of quality assurance describes both quality assurance and quality control as distinct parts of the wider quality-management approach.
A useful way to understand the relationship is:
These boundaries are not always represented by separate departments.
The organizational structure depends on factors such as industry, company size, risk, regulatory requirements, and the quality-management system being used.
The distinction between audits and inspections is also useful.
A quality audit generally evaluates processes, systems, or conformity with defined requirements. An inspection more directly examines an output, product, service, or other item against specified criteria.
That is why auditing is commonly associated with QA, while product inspection is closely associated with QC.
Quality management depends heavily on documented requirements and evidence, although the exact documents vary considerably between organizations and industries.
Common examples can include:
Different documents serve different purposes.
A specification defines what an output should meet. A procedure explains how a process should be performed. An inspection record provides evidence of what was checked and what result was found.
Documentation alone, however, does not create quality.
A detailed procedure provides little value if employees do not follow it, while inspection records cannot compensate for an unreliable production process.
Useful QA/QC documentation should therefore reflect how work is actually performed, make responsibilities clear, preserve appropriate evidence, and provide information that teams can use when investigating recurring problems or improving processes.
The skills required for QA/QC depend on the industry and the responsibility of the individual role. Someone inspecting machined components will need different technical knowledge from someone auditing a software-development process.
Several skills are nevertheless commonly valuable:
Quality professionals need to recognize differences between actual results and defined requirements.
QA/QC teams must be able to interpret the specifications, procedures, drawings, acceptance criteria, or other requirements relevant to their work.
Accurate records make it possible to trace inspections, findings, decisions, and corrective actions.
Finding a defect is different from understanding why it keeps occurring. Quality roles often require teams to investigate patterns and possible root causes.
Quality issues frequently involve production teams, suppliers, engineering, management, customers, or other departments. Findings need to be communicated clearly and objectively.
Some roles require knowledge of measurement tools, testing methods, statistical techniques, or quality data analysis.
Quality professionals need to follow defined criteria while recognizing when a problem requires escalation, specialist review, or further investigation.
As manufacturing operations grow, managing quality through separate spreadsheets, paper inspection records, production systems, and inventory records can make it difficult to maintain a connected view of quality activity.
Integrated software can help teams bring operational QC information closer to the manufacturing process.
Depending on the system, this can include:
HAL Quality Control currently supports quality control plans with inspection points for receiving, manufacturing, and final inspection. Its documented functionality also includes in-process inspections, quality alerts, quality zones, and integration with inventory and manufacturing operations.
For businesses that need quality information connected with the wider production process, HAL Manufacturing brings manufacturing, inventory, production tracking, and quality-control workflows into the broader ERP environment.
Software does not replace the quality-management system, appropriate procedures, qualified personnel, or professional judgment. Its role is to help teams execute, record, and connect the operational information used within those processes.
QA and QC work toward the same goal from different directions.
Quality assurance asks whether the processes used to deliver consistent quality are properly designed and managed. Quality control checks whether the resulting materials, products, or services actually meet defined requirements.
Manufacturers need both the process discipline and the operational visibility required to identify problems and learn from recurring quality issues.
HAL Quality Control helps manufacturers manage control plans, receiving inspections, in-process inspections, final inspections, and quality alerts alongside manufacturing and inventory workflows.
If you want to see how these capabilities could fit into your manufacturing operations, book a demo with HAL.
QA/QC stands for quality assurance and quality control. QA focuses primarily on the processes used to achieve quality, while QC focuses primarily on checking whether specific outputs meet established requirements.
Quality assurance is primarily process-focused and preventive. Quality control is primarily output-focused and detective. QA aims to build confidence that appropriate processes are in place, while QC uses activities such as inspection and testing to verify conformity.
Not necessarily. There is no universal organizational hierarchy in which QA must always be “higher” than QC. Responsibilities and reporting structures vary according to the company, industry, quality-management system, and applicable requirements.
Testing a product or other output against defined requirements is generally considered a QC activity. Designing the procedures, processes, and systems that govern testing can form part of QA. The exact classification depends on what is being tested and why.
Inspection is generally associated with quality control when it involves examining or measuring an output and comparing it with defined requirements. Quality audits, by contrast, are more closely associated with QA because they evaluate processes or systems.
QA processes are often established before individual QC inspections take place, but QA and QC should not be viewed as a simple one-time sequence. Both can operate throughout production or service delivery, and QC findings can feed back into QA improvements.
They can be combined in some organizations, particularly smaller businesses. However, the appropriate separation of responsibilities depends on the industry, risk, applicable standards, regulatory requirements, customer requirements, and internal governance.
