LEARN:

Quality assurance (QA) and quality control (QC) in construction get used interchangeably on most building sites. They're not the same thing, and the difference matters when a defect dispute opens or when a client audits the builder's quality program.

The cleanest version: QA is the system — plans, processes, hold-points, evidence templates, document control, audit trail. QC is the inspection — the day-to-day act of checking work against the QA system on site.

QA says what gets checked and how. QC is the act of checking.

QA in construction

A construction QA program covers:

• The overarching quality plan
• Inspection Test Plans (ITPs) per trade or work package
• Document control and version management
• Conformance evidence templates
• The non-conformance report (NCR) workflow
• Periodic audits of the QA program itself
• Sub-contractor pre-qualification and management
• Training records

It's the system. The QA program exists whether or not anyone is on site that day. It's referenced by the contract, audited by the client, scrutinised by the insurer, and called on as the main defence in a defect dispute.

QC in construction

Quality control is the inspection rhythm that runs against the QA system:

• Hold-point inspections at each named hold-point in the ITP
• Witness-point oversight
• Sample testing and result review
• Sub-contractor work inspection
• NCR issue when work doesn't conform
• Conformance record completion

QC is what actually happens on site. Each QC inspection generates a record that feeds back into the QA audit trail.

Why builders mix them up

Three reasons the terms get conflated:

• One person often does both. On smaller builds, the same QA lead designs the ITPs (QA) and runs the inspections against them (QC). The work blends together.
• Document templates use the terms loosely. Many off-the-shelf QA templates use "QA/QC" as if it's a single function. It isn't.
• The trades only see the QC. From a sub-contractor's point of view, the inspector showing up at the hold-point is QC. The QA system that decided the hold-point existed is invisible to them.

Why the distinction matters

Three places the difference becomes practically important:

• In a client audit. A sophisticated client tests the QA program (system) and the QC records (inspections). They expect both. A builder who's good at one and weak on the other gets caught.
• In an insurance review. Insurers test QA program design first (because it scales across all projects) and QC execution second (because it varies by project). Both matter; the QA program is the longer-term value driver.
• In a tribunal or court matter. The QA program proves the builder had a defensible system. The QC records prove the system was followed on this project. A builder needs both to defend against a defect claim.

Common failure modes

QA failures:

• No real ITPs. Generic templates that don't reflect the project.
• No document control. Drawings and specifications versioned inconsistently across the project team.
• No NCR workflow. When a non-conformance is found, there's no path to closure.
• No audit schedule. The QA program never gets tested against itself.

QC failures:

• Missed hold-points. Work proceeds past inspections that should have stopped it.
• No conformance evidence captured. Inspections happen but the record is thin or absent.
• NCRs raised but not closed. Findings sit open without action.
• Wrong sign-off authority. Approvals from people who weren't qualified to give them.

Each failure mode is fixable. The fix usually starts with a fresh look at whether QA and QC are actually structured as separate disciplines on the project.

How to set up QA and QC properly

Three principles:

1. Design QA at project setup, not mid-build. The QA program is cheapest and most effective when designed before work starts.
2. Make QC the act of running the QA. Each QC inspection ticks an ITP hold-point. Each conformance record feeds the QA audit trail.
3. Audit the QA program separately from the work. Periodic QA audits test whether the system is being followed, not whether the trades are conforming.

QBFS designs construction QA programs and runs the QC inspection rhythm on projects across Australia.

Call Paul on 0407 146 737.

Start With a Call

Best way to start is a phone call. Tell Paul the project, the issue, where you sit in the build cycle. The next step gets sorted on the call: site visit, desktop review, or a referral if QBFS isn't the right fit.