Quality Assurance vs Quality Control: Fixing the Process or Checking the Product

Quality assurance (QA) and quality control (QC) are often used interchangeably, but they do different jobs. QA prevents defects by making the process reliable. QC detects defects by checking the product before it ships.

The difference matters most when the same defect keeps coming back. If inspectors on a bottling line keep finding underfilled bottles, QC is catching bad product before it reaches customers. The filling process is still producing those bottles, though, and stopping that requires changes to the process, which is the role of QA.

A factory needs both. This guide covers how they differ, which activities belong to each, and how QC data helps QA stop defects from recurring.

What Is the Difference Between Quality Assurance and Quality Control?

ISO 9000:2015 distinguishes the two by describing QA in terms of providing confidence that quality requirements will be fulfilled, while QC focuses on fulfilling those requirements.

How QA and QC Work on a Production Line

Before a bottling line starts production, QA work includes qualifying suppliers, writing operating procedures, training operators, and maintaining equipment. Calibration keeps measuring instruments reliable. Process audits check whether the system is being followed and working as intended.

QC takes place as bottles move through production and before the batch is released. Checks cover fill volume, cap placement, seal integrity, and other product specifications. If results fall outside acceptable limits, the team holds the affected products and investigates.

Examples of QA and QC Activities

Using QC Data to Improve the Process

QC also produces data that is useful beyond the pass/fail decision. A single result tells you whether one bottle is acceptable; a record of fill weights over time shows how the process behaves.

This is the idea behind control charts. Plotting measurements against time, with limits based on the process's normal variation, separates the routine scatter every process has from shifts that point to a specific cause. If fill weights start drifting downward across a shift, the chart shows it while the bottles are still within specification. The team can then adjust the filler before it produces rejects.

Used this way, QC measurements support QA. Statistical process control is how many manufacturers make that link systematic.

FlowFuse helps manufacturers put this into practice. It connects PLCs, sensors, test stations, and other industrial systems over protocols such as OPC UA, Modbus, and MQTT, so measurement data from across a plant is collected in one place. Teams then build dashboards that chart key quality characteristics, alerts that flag a drift before it produces rejects, and records that show whether corrective actions are holding. The same setup makes recurring deviations easier to monitor across lines, shifts, and sites.

FlowFuse also connects AI agents to industrial systems, letting teams build applications from plain-language prompts. In this example, we used Claude and FlowFuse to build a torque traceability application that checks each tightening result against its required limit.

Why Finding Defects Late Costs More

An underfilled bottle discovered at final inspection has already consumed product, packaging, machine time, and labor. Some bottles can be reworked; others are scrapped along with their contents.

If the defect reaches a customer, the business also faces complaints, replacements, investigations, or a recall.

The 1-10-100 rule illustrates how the cost of a problem grows: preventing it at the source costs $1, correcting it inside the factory $10, and addressing it after it reaches a customer $100 or more. These figures are illustrative ratios, not universal costs.

Detecting a defect late doesn't recover the resources already spent producing it. Prevention avoids both the defect and the downstream work required to contain it.

Why Manufacturers Need Both QA and QC

QC remains necessary, because even a well-designed process can fail. Materials vary, equipment wears, and operating conditions change. Process controls reduce risk, but they can't guarantee that every product will meet its specifications.

QC provides an essential check on the output. It identifies nonconforming products before they move further through production or reach customers. In regulated and safety-critical industries, testing and inspection are required safeguards.

The important distinction is between using inspection to manage risk and relying on it to compensate for process problems. W. Edwards Deming made this point in the third of his 14 points for management: "Cease dependence on inspection to achieve quality."

On the bottling line, repeated underfills could come from a filling-system fault, incorrect settings, changing product characteristics, or a problem that occurs when production restarts. QA finds and fixes the cause; QC confirms whether the fix reduced the failures. Each relies on the other: QA needs QC data to know whether its changes work, and QC on its own does not reduce how often defects occur.

Is It QA or QC? Classifying Overlapping Activities

Some activities overlap, so the easiest way to distinguish them is to ask what they're intended to achieve.

Calibration is a useful edge case. Calibrated instruments are used during QC inspections, but the calibration process establishes confidence in the measurements themselves, which makes it a QA activity.

Regulated industries draw the same line. In pharmaceuticals, process validation and deviation management are QA, while testing a batch against release specifications is QC.

The department's name doesn't settle the question. Some manufacturers use quality control as a broad term for their entire quality function. ASQ describes QC as a subset of QA, reflecting how product checks fit within the wider quality system.

What matters is whether the activity checks an output, strengthens the process, or does both.

QA vs QC Roles: Quality Engineer vs QC Inspector

The split shows up in job titles too, although the exact responsibilities vary by company.

A QC inspector or QC technician measures and tests product: checking incoming materials, performing in-process and final inspections, recording results, and flagging nonconforming product.

A QA engineer or quality engineer works on the system: writing procedures, running audits, leading root cause investigations, managing corrective actions, and analyzing quality data to find where the process needs to change.

In smaller plants, one person often does both. It still helps to be clear which task is which, because inspecting a part and improving the process that made it involve different questions.

How to Measure Whether Quality Is Improving

When defects appear, adding an inspection is often a sensible short-term response, because it protects customers while the team investigates. Over the longer term, though, the process itself needs to change, or the extra inspection becomes permanent.

Prevention is also harder to measure. A rejected batch is visible and needs immediate action, while a process improvement shows up only as problems that no longer occur. As a result, adding inspections can look like progress even when the underlying process hasn't changed.

A stronger quality system tracks whether recurring defects are declining, scrap and rework are falling, and corrective actions are keeping problems from returning.

A practical starting point is to review recent rejects. For each one, ask what allowed it to happen, where the process could have prevented it, and what change would stop it happening again.

Inspection will remain part of any quality system. The goal is for it to find fewer problems over time as the process improves.