QA vs QC in Construction Explained

Quality Assurance (QA) and Quality Control (QC) are used almost interchangeably on site, but they're not the same thing. Confusing them leads to teams that inspect hard but never fix the underlying process — catching the same defect over and over. Understanding the difference makes your whole quality effort more effective.

The core difference

QA is about the process; QC is about the product. QA asks "do we have the right systems in place to produce good work?" QC asks "is this specific piece of work actually good?" QA is proactive and prevents defects; QC is reactive and detects them.

A simple way to remember it: QA is building it right (the system), QC is checking it's right (the output).

Quality Assurance in practice

QA is everything you do to make sure the work will meet the standard before it's built:

• Method statements and approved procedures.
• Competent, trained operatives.
• Approved materials and suppliers.
• The quality plan and ITPs.
• Audits of your own processes.

QA is largely office and planning work. It sets up the conditions for success so defects are less likely in the first place.

Quality Control in practice

QC is the hands-on checking of actual work against the standard:

• Inspecting completed work.
• Testing materials (concrete cubes, weld tests, pressure tests).
• Snagging and de-snagging.
• Raising NCRs when work fails.
• Measuring and verifying dimensions.

QC happens on site, in real time, against real output.

Why you need both

Relying on QC alone is exhausting and expensive — you catch defects after they've cost time and material, and the same root cause keeps producing them. Relying on QA alone is naïve — even the best process produces the occasional defect, and only inspection catches it. The two work together: QA reduces how many defects occur; QC catches the ones that slip through; and the defects QC finds feed back to improve QA.

A worked example

Say a project keeps getting paint runs on window reveals. QC catches them at snagging and they get fixed — but they keep coming back. QA asks why: the painters aren't masking properly because the method statement doesn't specify it. Update the procedure and brief the team (QA), and the defect stops appearing at QC. That feedback loop is the whole point.

Where the responsibility sits

QA is usually owned by a quality manager or the company's management system. QC is carried out by site engineers, supervisors, clerks of works, and independent inspectors. On smaller jobs the same person may do both — but they should know which hat they're wearing.

Capturing the loop with software

The value of digital quality tools is that they connect QC findings back to QA. When every inspection and NCR is logged in one place, you can see which defects recur, on which trades, in which locations — and that data tells you which processes to fix. Without it, QC findings stay as isolated snags and the underlying cause is never addressed.

Key takeaways

QA is the system that prevents defects; QC is the checking that detects them. You need both, and the real power comes from the feedback loop: use what QC finds to improve what QA controls. Inspect the product, but fix the process.