Quality assurance is the system that helps prevent defects; quality control is the field verification that checks whether the work meets requirements. Construction teams need both because planning without inspection is blind, and inspection without a quality system is reactive.
Key takeaways:
- QA sets the process, standards, roles, submittals, mockups, training, and hold points.
- QC checks the installed work through inspections, tests, measurements, and documentation.
- QA is preventive; QC is confirmatory.
- Strong teams connect both to the schedule so quality does not become a last-minute punch list.
The Difference in Plain English
QA asks, "What will we do to make the work right the first time?" QC asks, "How do we know the work is right now?" In construction, QA may include the project quality plan, approved submittals, pre-installation meetings, training, design coordination, procurement controls, mockup requirements, and defined inspection points. QC may include checking anchor spacing, witnessing tests, reviewing welds, measuring slopes, verifying sealant joints, and documenting nonconforming work.
The American Society for Quality explains that the ISO 9000 series helps organizations document and implement quality management systems, and ASCE recognizes quality management standards as relevant to civil engineering and construction. Those references support a practical view: quality is a managed process, not just the last inspection. See ASQ's overview of ISO 9000 quality management and ASCE's statement on quality management system standards for broader context.
QA and QC Compared
| Area | Quality Assurance | Quality Control |
|---|---|---|
| Main purpose | Prevent problems before work is installed | Verify installed work or completed steps |
| Timing | Before and during the work | During and after installation activities |
| Typical tools | Quality plan, submittal controls, mockups, checklists, training | Inspections, tests, measurements, deficiency logs |
| Owner concern | Is the contractor's process reliable? | Does the finished work meet the contract requirements? |
| Common failure | A plan exists but is not used in the field | Inspections happen too late to prevent rework |
Where QA Shows Up on a Project
A useful quality assurance plan names the standard of care for each major work package. It should identify applicable drawings, specifications, codes, approved submittals, manufacturer instructions, tolerances, mockups, testing agencies, and acceptance criteria. It should also explain who has authority to accept work, reject work, or pause work when conditions change.
QA becomes especially valuable before complex or repeatable work. For facade and waterproofing assemblies, for example, the plan may require preconstruction meetings, sample panels, sequencing diagrams, compatibility checks, and mockups. That is why mockups for facade and waterproofing work are often considered a QA tool before they become a QC checkpoint.
Where QC Protects the Installed Work
QC is the evidence trail. It can include inspection reports, photos, test results, manufacturer field reports, special inspection records, commissioning checklists, and signed closure of deficiencies. QC should not be limited to final punch list because many construction details become inaccessible. A waterproofing transition, firestop condition, embedded anchor, or above-ceiling valve cannot be checked easily once finishes are complete.
QC also needs context. A checklist that says "approved" without location, date, responsible party, drawing reference, and photo evidence may not help later. If a deficiency appears months after turnover, the team needs enough information to understand what was checked and what changed.
Why Teams Confuse the Terms
QA and QC are often used interchangeably because both live inside the same quality program. The confusion becomes a problem when contracts assign responsibilities vaguely. Owners may expect the contractor to prevent and find issues, the contractor may expect the design team to catch problems, and the design team may expect special inspectors to verify everything. Clear responsibility prevents gaps.
A practical contract or project plan should define who prepares the quality plan, who reviews submittals, who witnesses testing, who closes deficiencies, and who maintains records. For exterior cladding, the comparison in EIFS vs stucco vs fiber cement upkeep shows why quality roles matter. Each system has different substrates, joints, drainage expectations, and maintenance points. Treating them as interchangeable can lead to poor inspections.
Mistakes That Weaken Quality Programs
The first mistake is treating the quality plan as a binder created for contract compliance. If superintendents, foremen, and trade partners do not use it, it has little value. The second mistake is scheduling inspections after work is concealed. A third mistake is allowing repeated minor deficiencies to stay open because none of them looks serious alone.
Quality programs also suffer when field teams do not get feedback. If the same door hardware, sealant joint, hanger layout, or finish detail fails in multiple locations, the issue should be discussed with the crew before more work is installed. Good QA turns QC findings into process improvements.
A Quality Plan That Uses Both Sides
Start with the highest-risk scopes: envelope, structure, life safety, MEP shutdowns, waterproofing, accessibility, and high-wear finishes. Define what must be prevented through training and planning, then define what must be verified through inspection and testing.
For projects inside operating buildings, QA and QC should also connect to occupant protection. The coordination approach in planning occupied renovations is a reminder that quality is not only about the finished surface. It includes safe phasing, clean turnovers, reliable shutdowns, and documented readiness for occupancy.
Hold Points That Make Both Systems Work
Hold points are moments when work should pause until a defined person verifies a condition. Good examples include substrate acceptance before waterproofing, framing inspection before wall closure, above-ceiling review before ceiling tile installation, and first-room approval before a finish is repeated. These checks connect QA and QC because the quality plan defines the hold point, while the field inspection verifies it. The record should state what was checked, who checked it, what standard applied, and what corrective action was needed. Without that record, the team may remember that an inspection happened but not what it proved.
Documentation Should Be Easy to Retrieve
Quality records should be stored so the team can find them by location, date, trade, and scope. Photos should show context, not only close-ups. Test reports should be connected to the exact area tested. Deficiency logs should show open, corrected, and verified status. When the closeout record is searchable, future maintenance teams can understand what was built and why certain decisions were accepted.
A simple rule helps: if a quality record would not help someone understand the work six months later, it needs more context. Add the location, reference detail, responsible trade, and acceptance basis while the information is still fresh.
This article is for educational use only and is not professional engineering, legal, compliance, quality management certification, or project management advice. Project-specific requirements should be confirmed in the contract documents and with qualified professionals.
