Quality control (QC) is checking product, inspecting and testing output to catch defects before they ship. Quality assurance (QA) is managing process, building and auditing the systems that prevent defects from happening at all. QC detects, QA prevents, and a plant that runs on only one of them pays for it.
The two terms get used interchangeably in a lot of plants, usually by whoever is writing the job posting. That blur causes real problems: inspectors get blamed for process failures they can't control, and "the quality department" becomes a bottleneck instead of a system. This post draws the line clearly, shows where each function lives in the org, and gives you a checklist for balancing both.
What is quality control?
Quality control is the set of activities that verify product against specification: incoming inspection, in-process checks, final inspection, lab testing, and the measurement tools behind them. QC answers one question, does this unit meet spec? and it answers it after the product exists.
Typical QC work on a plant floor:
- First-piece and in-process dimensional checks against the drawing or spec sheet
- Sampling plans and lot acceptance testing on incoming material
- Final inspection, functional test, and release before shipment
- Control charts and gauges at the point of production
- Writing up a non-conformance report when something fails
QC is reactive by design. That is not an insult, you need detection. But every defect QC catches already cost you the material, the labor, and the machine time that went into making it.
What is quality assurance?
Quality assurance is the set of activities that make the process trustworthy: writing procedures, qualifying suppliers, training and certifying operators, auditing the system, validating processes, and running corrective and preventive action. QA answers a different question, is our system capable of producing good product every time?
Where QC looks at units, QA looks at the machinery around the units: document control, calibration programs, supplier quality, change management, internal audits, and management review. When an auditor certifies your plant to ISO 9001 or a GFSI food safety scheme, they are auditing your QA system, and spot-checking your QC records as evidence it works.
QC vs QA: what is the actual difference?
The difference is focus, timing, and the question being asked. QC is product-focused and happens during and after production. QA is process-focused and happens before, during, and after, it wraps around everything, including QC itself.
| Quality control (QC) | Quality assurance (QA) | |
|---|---|---|
| Focus | The product | The process and system |
| Goal | Detect defects before they ship | Prevent defects from occurring |
| Question asked | Does this unit meet spec? | Can the system reliably make units that meet spec? |
| Timing | During and after production | Before, during, and after, continuous |
| Typical tools | Inspection, testing, sampling plans, SPC gauges | Procedures, audits, supplier qualification, training, CAPA, management review |
| Typical output | Accept/reject decisions, inspection records, NCRs | Documented system, audit findings, capable processes, corrective actions |
| Failure mode if missing | Defects escape to customers | Same defects recur forever; QC becomes a permanent tax |
A useful mental model: QA is the envelope, QC is one activity inside it.
Where does each live in the org?
In most small and mid-size plants, QC reports through operations or through a quality manager: inspectors, lab techs, and line-side checkers who touch product every shift. QA sits one level up and one step away from the line: the quality engineer or quality manager who owns the quality management system the audit calendar, supplier files, and CAPA board.
Two org rules keep the functions honest:
- QC needs authority to stop product. If an inspector's reject can be overridden by a shipping deadline without a documented concession, you have inspection theater, not quality control.
- QA needs independence from output pressure. Whoever audits the process should not be graded on this month's shipment numbers. In small plants one person wears both hats, fine, as long as the two roles are separated on paper and in the audit trail.
The connection point between them is data. Every QC record, inspection results, defect counts, NCRs, is raw material for QA work like trend analysis, root cause analysis and CAPA. Plants where QC results live on clipboards starve their QA function; digitizing those checks is usually the fastest QA upgrade available, which is why quality reporting is one of the first workflows plants move onto a platform like Harmony (quality and downtime intelligence is one of its core modules).
Why does prevention beat detection?
Because the cost of a defect grows the longer it survives. A process error prevented at the design or setup stage costs a procedure change. The same error caught at final inspection costs the scrapped unit. Escaped to the customer, it costs returns, credits, complaint handling, and sometimes the account. Quality economics people group these as prevention, appraisal, and failure costs, the cost of quality and failure costs dominate when QA is weak.
The data on this is old and consistent. The American Society for Quality notes that cost of quality often runs as high as 15–20% of sales revenue for manufacturers, with some organizations reaching 40% of total operations, and most of that spend is failure cost, the kind prevention would have avoided. ASQ's framework splits quality spend into prevention, appraisal, internal failure, and external failure; the ratio between the first two and the last two is effectively a scorecard of your QA-to-QC balance.
How do you balance QC and QA? A 6-step check
Run this sequence once a quarter. It takes an afternoon and tells you which side of the house needs investment.
- Map your detection points. List every inspection and test from receiving to shipping. Note what each one catches per month.
- Trace your top three defects backward. For each, ask where in the process it is created versus where it is caught. A long gap between the two is money burning.
- Check the loop. Do QC findings actually trigger CAPA? Count last quarter's NCRs and how many produced a process change. If the answer is near zero, you have QC without QA.
- Audit the paperwork path. If inspection results take days to reach whoever owns the process, trends die on the clipboard. Digitize the checks that matter first.
- Score prevention spend. Compare hours spent on training, audits, supplier work, and process validation against hours spent inspecting and reworking. Heavily lopsided toward inspection means you are renting quality, not owning it.
- Move one control upstream. Pick a final-inspection catch and replace it with an in-process check, a control chart or an error-proofed fixture closer to where the defect is created.
What happens when a plant has only one?
Only QC: the plant catches most defects but makes the same ones forever. Inspection headcount grows with volume, scrap stays flat or climbs, and every audit finding gets patched instead of prevented. Only QA: beautiful binders, certified system, and product escapes, because nobody is measuring reality at the line. Auditors have a name for that gap: it is the difference between a documented system and an implemented one.
The plants that get this right treat QC data as the fuel and QA as the engine. CLS is a working example of the first step, moving paper production and quality logging into real-time records the whole team can act on (read the CLS case study). Once the data flows, prevention finally has something to work with.