Quality assurance and quality control are often grouped together as “QA/QC” on construction projects, but they do different jobs. Quality assurance (QA) is primarily concerned with the processes used to achieve the required standard of work. Quality control (QC) checks whether materials, workmanship, installations, and completed work actually meet those requirements.
For contractors and project teams, understanding the difference matters because good procedures alone do not prove that work is acceptable, while inspections alone cannot prevent the same problems from recurring. This guide explains how QA and QC differ, where each fits into a construction project, and how they work together.
QA and QC are both parts of quality management, but their focus is different. ISO’s guidance on quality assurance describes QA as a systematic approach to making sure defined quality requirements can be met and distinguishes it from QC, which focuses more directly on checking outputs against requirements.
Quality assurance (QA) in construction focuses on the system used to achieve the required level of quality.
That can include establishing responsibilities, quality procedures, approved methods, document controls, inspection arrangements, competency requirements, and processes for managing nonconforming work. The objective is to create conditions in which work is more likely to be completed correctly in the first place.
QA therefore asks a process question: Are we managing the work in a way that gives us confidence the required quality can be achieved?
QC means quality control. In construction, it is primarily concerned with verifying the actual work, material, installation, or completed output.
QC activities can include site inspections, measurements, material checks, testing, workmanship checks, and review of results against drawings, specifications, approved submittals, or other applicable acceptance criteria.
The American Society for Quality’s QA and QC guidance similarly distinguishes process-oriented assurance from the inspection and operational activities associated with quality control.
The main difference between quality control and quality assurance in construction is what each discipline is trying to control. QA concentrates on the processes that should produce acceptable work. QC examines the work or materials to determine whether the specified requirements have actually been met.
QA and QC should not operate as separate administrative exercises. Quality assurance establishes the framework; quality control generates evidence about how the work is actually performing within that framework.
A useful way to view construction quality is as a continuous sequence:
Requirements → quality planning → construction → inspection/testing → corrective action → process improvement
Before work begins, QA activities help establish what is required, who is responsible, which procedures apply, what documents need approval, and where inspections or tests should occur.
During construction, QC provides the field-level verification. Teams inspect work, review materials and test results where required, record findings, and identify work that does not meet the agreed criteria.
Those QC results should then inform the wider quality system. If the same defect keeps appearing, repeatedly repairing the finished work is not enough. The project team may need to review the method, sequencing, supervision, supplier controls, drawings, training, or another underlying process.
Quality activities may include:
QA and QC operate together. Procedures and approved information guide execution, while inspections and tests verify whether work meets the required criteria.
Good records also matter. For contractors managing multiple activities or sites, consistent construction progress reporting can help keep project activities, inspections, milestones, delays, and other site information easier to trace.
Quality control continues through outstanding inspections, testing, defect closure, commissioning where applicable, and verification of completed work. Quality records are then organized for the project’s required handover and closeout process.
Lessons from recurring defects or process failures should also be carried into future projects.
The distinction becomes clearer when QA and QC are applied to actual construction activities.
These are examples rather than universal requirements. The exact inspection, testing, approval, and documentation process depends on the project contract, specifications, applicable standards, authority requirements, and nature of the work.
Construction quality depends heavily on reliable documentation, but not every document belongs exclusively to either QA or QC.
Common QA-oriented documents can include:
Common QC records can include:
An Inspection and Test Plan (ITP) is a good example of where QA and QC meet. The plan establishes which activities require inspection or testing, the applicable requirements or acceptance criteria, responsibilities, and any required intervention points. QC then involves performing and documenting the relevant checks.
The specific format and terminology vary between projects. Contract documents and project-specific requirements should therefore determine how an ITP is structured and used.
There is no single responsibility model that applies to every construction project. Quality duties may be distributed among:
QA responsibilities generally cover the project’s quality system, procedures, roles, planned controls, and review processes. QC responsibilities are more directly connected with carrying out inspections or tests, recording results, reporting nonconformance, and verifying corrective work where required.
The project contract and quality plan remain important because different delivery models can assign responsibilities differently. For example, the U.S. Army Corps of Engineers’ Construction Quality Management framework explicitly separates contractor quality-control responsibilities from government quality-assurance responsibilities for its construction contracts. Other clients and jurisdictions may structure those roles differently.
A practical QA/QC process should connect quality requirements with what actually happens on site.
Start with the contract, drawings, specifications, approved submittals, applicable standards, and other project requirements. Teams need a clear definition of what acceptable work looks like before they can plan or inspect it.
Identify who prepares, reviews, approves, executes, inspects, tests, records, and closes quality-related activities. Clear ownership reduces gaps between the office, site teams, subcontractors, and consultants.
Document how quality will be managed. Procedures should reflect the actual project rather than simply repeating a generic template.
Quality planning should also connect with the wider construction schedule. HAL’s guide to planning construction projects covers the broader coordination of timelines, resources, budgets, and execution that surrounds project delivery.
Use ITPs, checklists, or the project’s required equivalent to define what must be checked, when checks happen, who is involved, what acceptance criteria apply, and what records must be retained.
Teams need access to the correct drawings, specifications, approved documents, and material information. Working from superseded documents or using unapproved materials can create quality problems before an inspection takes place.
Carry out the required inspections, measurements, and tests at the appropriate stages. Record results so that approvals, findings, and outstanding issues can be traced later.
When work or materials fail to meet requirements, record the issue and follow the project’s agreed process for review, disposition, corrective action, reinspection, and closure as applicable.
Quality control should provide more than a pass-or-fail record. Repeated defects can point to problems with procedures, coordination, suppliers, training, supervision, sequencing, or project information.
That feedback loop is what turns QA/QC from a documentation exercise into a useful management process.
Construction quality activities depend on much more than the inspection itself. Project teams also need reliable information about materials, procurement, documents, resources, costs, schedules, and progress.
ERP and project-management systems can support that wider operational environment, but they should not be confused with construction inspection or testing processes.
HAL Construction brings project workflows together around areas such as budgeting, resources, material requests and deliveries, project progress, and centralized project documents. HAL’s Document Manager also provides centralized document storage, document history, and user attribution.
For contractors, that connected information can support coordination around quality-related work—for example, keeping project documentation accessible or connecting material and project information with wider operations. It does not replace the project’s required inspections, tests, engineering judgment, contractual approvals, or specialist QA/QC processes.
The same distinction applies financially. Quality issues can affect materials, labor, schedules, and rework, while disciplined construction cost management helps teams maintain visibility into the wider project cost picture.
Quality assurance and quality control in construction serve different purposes, but effective project quality depends on both. QA establishes the processes, responsibilities, and controls intended to support good work. QC checks the actual work and creates evidence about whether requirements have been met.
For contractors managing multiple projects, those quality activities also depend on accurate project, procurement, material, resource, document, and cost information. HAL Construction brings these wider operational workflows into a connected system, helping teams maintain clearer visibility across project execution.
Book a HAL demo to explore how HAL can support your construction operations.
QA focuses primarily on the processes used to achieve the required standard of construction, while QC verifies the actual materials, workmanship, installations, or completed work against defined requirements. Put simply, QA helps establish how work should be controlled; QC provides evidence about whether the work meets the required criteria.
QC means quality control. It covers activities used to check construction work against specified requirements, such as inspections, measurements, material checks, testing, and documented verification. The exact QC activities depend on the contract, specifications, project quality plan, and applicable technical requirements.
No. They are connected parts of quality management, but they are not identical. QA is more process-oriented and preventive, while QC is more focused on inspecting and verifying actual outputs. A construction quality system generally needs both functions working together.
QA planning normally begins first because teams need requirements, responsibilities, procedures, and inspection arrangements before work starts. However, QA does not simply end when QC begins. Both continue throughout project execution, with QC findings providing information that can be used to improve QA processes.
An ITP, or Inspection and Test Plan, sets out the planned inspections and tests for relevant construction activities. Depending on the project, it may identify requirements or acceptance criteria, responsibilities, inspection stages, test methods, intervention points, and required records. Its exact contents should follow the applicable contract and project requirements.
Responsibility depends on the project and contractual structure. Contractors, QA/QC personnel, site engineers, supervisors, subcontractors, consultants, testing organizations, and client representatives may all have defined roles. The contract, project quality plan, specifications, and approved procedures should establish who performs and approves each activity.
