Quality Assurance vs. Quality Control: Differences Explained

Quality assurance (QA) focuses on the processes and systems that give confidence quality requirements will be met. Quality control (QC) focuses on checking outputs to determine whether they meet those requirements. In practical shorthand, QA helps prevent problems by organizing work; QC detects whether a result conforms. Both are part of quality management, and organizations use them together.

The boundary is not identical everywhere: some organizations use the terms interchangeably. ASQ describes QC as typically a subset of QA activities. Define the terms in context when responsibilities or requirements depend on a precise distinction.

QA vs. QC at a glance

Dimension	Quality assurance (QA)	Quality control (QC)
Focus	Processes, systems, and repeatable conformity	Outputs and whether they fulfill requirements
Typical question	Are we organizing the work so requirements can be met consistently?	Does this result meet the stated requirements?
Useful shorthand	Process-oriented and preventive	Output-oriented and verification-focused
Examples	Documenting procedures, training, planning and conducting quality-system or process audits	Measuring, examining, or testing an output against requirements
Relationship	Part of the broader quality-management system	Often treated as a subset of QA activities

This distinction follows the definitions from ASQ and ISO. “QA prevents; QC detects” is a helpful generalization, not a strict timeline. QC can happen during production, and a QA system can use checks and feedback to improve how work is done.

What quality assurance means

QA is planned, systematic work across a quality system that provides confidence requirements will be fulfilled. It asks whether the organization’s way of working is suitable for producing conforming results repeatedly. ISO describes QA as a systematic process for ensuring products, services, and processes consistently meet defined quality requirements.

QA examples include:

Defining procedures, responsibilities, and review criteria.
Training people in the process they are expected to follow.
Planning and conducting audits of a quality system or process.
Reviewing problems and feeding what was learned back into the process.

QA is not simply paperwork, and it need not be owned only by a specialized department. The relevant work is whatever establishes and maintains a process that can meet the stated requirements.

What quality control means

QC consists of operational techniques and activities used to fulfill quality requirements. It asks whether a particular product, service output, document, or other result meets its acceptance criteria. The answer comes from measurement, examination, or testing and comparison with requirements.

QC examples include checking dimensions against a specification, testing a build against acceptance criteria, or reviewing a report for required content and correctness. QC is not limited to a final inspection: checks may take place while work is underway so that a nonconforming result can be identified and handled.

Examples across different kinds of work

Manufacturing

QA can establish and maintain the production method, clarify responsibilities, and define an audit approach. QC can measure or test products and compare findings with specifications. The first addresses whether the work system is organized to produce conforming products; the second checks whether a particular product conforms.

Software and documents

QA can define a review and release process, including who reviews a change and which criteria apply. QC can inspect a specific build, report, or deliverable against acceptance criteria. This applies the general process-versus-output distinction; it does not mean every software organization assigns these activities the same way.

Services

The service itself may not be a tangible object that can be inspected. However, an organization can still control documents or tangible products used in delivering it, such as a report or a rented item. ASQ discusses these service contexts in its QA and QC guidance.

An audit assesses conformity of a system, process, product, or service against criteria. An inspection measures, examines, or tests characteristics against requirements. An audit may examine whether a process is defined and followed; an inspection may check a product characteristic against a specification. They are not interchangeable names for the same activity. ASQ includes auditing among QA activities and distinguishes it from inspection.

How QA and QC work together

Set requirements. Make the quality requirements and acceptance criteria clear enough to apply.
Organize the work. Use QA activities to define responsibilities, procedures, training, and review points.
Check results. Use QC measurements, examinations, or tests to determine whether outputs meet requirements.
Respond to findings. Handle results that do not conform and use what the checks reveal to improve the process where appropriate.

QA and QC complement each other. A sound process reduces the chance of defects, while checks establish whether requirements were actually fulfilled. Neither alone guarantees that every customer requirement is met.

Standards context

ISO 9000:2015 is a concepts-and-vocabulary reference for quality management. ISO attributes the definition of quality as “the degree to which a set of inherent characteristics of an object fulfils requirements” to clause 3.6.2 of that standard. The ISO 9000 family provides a quality-management framework, and ISO 9001 specifies quality-management-system requirements, as summarized by ASQ and ISO.

This standards context helps explain the vocabulary; it does not establish that any particular organization is certified or compliant. The QA/QC distinction does not by itself determine whether certification is needed.

Choosing the right term in your organization

Describe the activity, not just the job title: is it organizing the process or checking a result?
State the requirement or criteria being used.
Clarify when and who performs the activity, especially if the same team handles both QA and QC.
Check local procedures and role definitions because terminology varies between organizations.

For example, “review the release process to confirm required approvals are defined” describes a QA-oriented activity. “Check this release against its acceptance criteria” describes QC. A company may label roles differently while performing these functions.

Common misunderstandings

“QC only happens at the end.” QC may be performed during work as well as on completed outputs.
“QA is just documentation.” Documentation can support a process, but QA is the broader planned and systematic work that provides confidence requirements will be fulfilled.
“An audit is an inspection.” An audit assesses conformity against criteria; an inspection examines or tests characteristics against requirements.
“Every employer uses the terms the same way.” Organizations sometimes use QA and QC interchangeably, so establish the intended meaning locally.
“One function guarantees quality.” QA and QC contribute in complementary ways; neither alone guarantees every customer requirement is met.

Frequently asked questions

Is QA process-focused and QC product-focused?

That is a useful shorthand. QA focuses on processes and systems; QC checks whether outputs fulfill requirements. QC also applies to services and deliverables that are not conventional manufactured products.

Is inspection quality assurance or quality control?

Inspection is generally a QC activity because it examines, measures, or tests characteristics against requirements. An audit, by comparison, assesses conformity against criteria.

Is QC part of QA?

ASQ says QC is typically a subset of QA activities. Because terminology varies and can be used interchangeably, confirm how a particular organization defines each term.

Can a service have quality control?

Yes. A service can be checked against requirements, and tangible items or documents used in delivering it can also be controlled.

ScreenshotNeo for visual quality checks

When a quality-control checklist includes checking how a web page renders, a consistent screenshot can be one useful visual artifact. ScreenshotNeo is a website screenshot API and MCP server for developers; it does not replace a QA process, acceptance criteria, or other QC checks.

Or skip the browser setup

Make a screenshot request with cURL:

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
r.raise_for_status()
with open("shot.webp", "wb") as image_file:
    image_file.write(r.content)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

See the ScreenshotNeo API documentation for request options. Cookie and consent banners, newsletter popups, and chat widgets are removed before the shot; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and billing status. Its MCP server lets AI agents use screenshot, page-info, and PDF-capture tools. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots.